Skip to content

Idea: frontend working group #69

Open

Description

@codingjoe

Howdy y'all! 🤠

ECMAScript, its browser APIs, and CSS have come a long way in Django's 20ish years.

However, to go from jQuery to importmaps will require a coordinated effort. Hence, a working group tasked with adopting modern web standards.

This working group may be especially compelling given the slight hesitance towards frontend technologies within the DSF. A go-to address to review proposals and patches might as well improve the lives of our fellows.

What could be potential responsibilities?

  • proposing long-term technology adoptions to the steering committee via DEPs
  • implementing strategies to harden existing implementations against regression
  • road map coordination and oversight towards long-term goals
  • reviews of frontend feature proposals along the roadmap
  • coordination with 3rd parties like browsers, frameworks, or standardization bodies
  • flagging outdated technologies (via linters or guidelines)
  • oversight of frontend 3rd party dependencies, vendoring, or integration
  • support of fellows and other work groups like the security WS on frontend matters
  • grant applications for projects or SoC

IMHO, memberships shouldn't be limited to DSF members either. To the contrary, I would invite experienced maintainers from the frontend world.

I will go ahead and draft a loose charter for substance and give this topic a notch.
I have drafted a loose charter for substance and to give this topic a notch: #70

Meanwhile, I'd love some feedback from other DSF bodies, especially the board and the steering committee.

Cheerio 👋
Joe


Based on:

Are there any JavaScript ninjas 🥷 here? With 20 years under its belt and ECMAScripts' rollercoaster of languages and package managers, Django has become a little out of tune with JavaScript. In 2026, I'd love to put together a ragtag band of TS wizards 🧙 (in the shape of a working group) that tries to close the gap between Django and modern browsers. Or maybe even gets active in shaping modern browsers?
@codingjoe#dsf-members Discord

Activity

  1. added a commit that references this issue on Jan 26, 2026
    6379fbc
  2. rik commented on Oct 11, 2026

    @rik

    That's a great idea for a working group!

    Two questions:

    • What's needed to move forward?
    • The first draft mentions leaving HTTP out-of-scope but I can think of a few topics that might be interesting to such a WG: compression such as Zstandard or compression dictionary, image formats, speculation rules, all sorts of performance and security headers. Until there is a dedicated HTTP WG, it might be worth including it?
  3. codingjoe commented on Oct 12, 2026

    @codingjoe
    SponsorAuthor

    Sharing it and betting more community support is an important new step.

    Regarding your suggestions … 1. You should open a [new-features](https://github.com/django/new-features) for zshd support. 2. Image processing isn't really something Django ships, beyond its very basic image field. If you want the latest and greatest, consider [django-pictures](https://github.com/codingjoe/django-pictures). 3. I don't know which security headers you are referring to, but SRI is already on its way via DEP21.
    Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions