Help shape Askr while the decisions are still close to the code.
Askr is an open-source framework that runs production applications today — static marketing sites and admin consoles, including this site. Contributions land close to the code: there is room to influence how its themes, rendering, and developer experience develop, not just pick up a finished backlog.
Where your perspective matters most
These are open areas, not job descriptions. A specialist review, a working prototype, a focused fix, or a carefully documented finding can all move the project forward.
- 01CSS and design systems
Make the themes feel exceptional
Refine tokens, responsive behavior, light and dark themes, component polish, and cross-browser details without moving accessibility out of the headless layer.
@askrjs/themes · @askrjs/ui - 02Rendering
Pressure-test SSR and SSG
Push server and static rendering past what the production applications already cover — metadata, hydration, performance, and deployment behavior on workloads they do not exercise yet.
@askrjs/askr · @askrjs/server · @askrjs/cli - 03Technical SEO
Make generated pages easier to find
Help sharpen canonical URLs, structured data, crawlability, sitemaps, social metadata, and the guidance applications need to use them well.
SSG · SSR · documentation
Working on Askr is direct
There is no formal contributor program or large community around Askr. You work directly with the people maintaining it, close to the code and the reasoning behind it.
The surface is broad, and the applications running on it exercise one slice of it. Where a documented path ships narrower than it reads, the docs mark it experimental or limited — that is a map of where a contribution has the most leverage.
Contributions are volunteer open-source work. There is no expectation that one useful contribution becomes a recurring obligation.
A simple way to begin
- 01
Choose a useful edge
Bring a concrete problem, a small improvement, or an experiment from one of the areas above. You do not need to arrive with a complete solution.
- 02
Start the conversation
Open a GitHub issue in the relevant repository, or send a short email if you are not sure where the work belongs.
- 03
Shape and ship it together
Agree on scope, make the reasoning visible, and validate the result. A single focused contribution is worthwhile; there is no ongoing commitment.
Bring the part you care about.
Introduce yourself, mention the area that interests you, and include any idea or example you already have. A polished proposal is not required.