Contribute
Everything here is a file in a public repository. Here's how to change it.
This site has no admin panel. There's no CMS and no database behind the content you're reading. Every article, event, chapter, job, learning route, and the framework itself is a file in a public Git repository.
That's deliberate. It means you can fork the whole thing, diff any change, see who wrote what and when, and improve it without asking anyone's permission first.
The fastest possible contribution
Every page has an Edit this page link at the bottom. It opens the exact source file on GitHub with an editor. Change it, describe why, submit. No local setup at all.
What we most want right now
Ordered by how much it would help, honestly:
1. Argue with the framework. It's version 0.1.0 by one person. The cells that are ambiguous, wrong, or missing are the highest-value thing you can find. If a level description would let two managers score the same engineer differently, that's a defect — report it with the axis, the level, and the situation.
2. Write about the actual work. Not "what is an FDE" — there are forty of those. Write the specific thing you learned the hard way. A deployment that failed and why. How you handled a stakeholder who was blocking. What your first ninety days looked like and how it differed from ours. Anonymise the customer.
3. Start a chapter. If there are three people in your city who do this work, that's a chapter. The playbook is written for someone who has never organised anything.
4. Post a job. If your company hires FDEs, put a real posting on the board. The board is empty right now and it stays empty until someone goes first.
5. Fix the site. It's a Next.js app. Issues labelled good first issue are real, not
decorative.
How each type of contribution works
An article
Add an MDX file to content/articles/. Frontmatter needs slug, title, description,
date, authors, tags. If it's your first, add yourself to content/authors/ as YAML
too. CI validates the frontmatter and tells you exactly which field is wrong.
A chapter
Add a YAML file to content/chapters/ with your city, region, and yourself as lead. Start
with status: proposed. It becomes forming when you have a date for a first event, and
active after you've run two.
An event
Add a YAML file to content/events/. Chapter leads post their own events — this is the
mechanism, not a request form.
A job
Add a YAML file to content/jobs/. It must be a real, currently-open role with a direct
application link and a stated level range against the framework. No recruiter aggregators,
no "always hiring" evergreen posts.
The framework
Edit content/framework/framework.yaml. Read Governance first — framework
changes have a heavier process than everything else, on purpose.
Not a Git user?
Open an issue. There are templates for chapter applications, job postings, article proposals, and framework feedback. Someone will land it for you and you keep the attribution.
The barrier to improving a standard shouldn't be tooling fluency. Plenty of the best forward deployed engineers spend more time in a customer's environment than in a terminal, and their input is worth more than their Git comfort suggests.
Running it locally
git clone https://github.com/rohithreddygopu/fde-community
cd fde-community
pnpm install
pnpm dev
No environment variables required. The whole public site builds and runs with none — the database and sign-in are optional layers, and everything readable works without them.
Licence
Content is CC BY 4.0. Code is MIT. Use it, fork it, build on it, teach from it. Attribution is all we ask.