Decap CMS is the open-source, Git-based editor that used to be called Netlify CMS. Teams hire a Decap developer to set it up on a static site, to fix a setup that broke when Netlify Identity went away, or to give a marketing team an editor without paying for a hosted CMS. We place engineers who have done this on real sites.
What does a Decap developer do for you?
- Write
config.yml. Collections, fields, widgets and slugs that match your templates, so saved files render correctly the first time. - Fix authentication. Decap needs a way to sign editors in against GitHub, GitLab or Bitbucket. Since Netlify Identity and Git Gateway were deprecated, many older sites need a new OAuth proxy or a different backend.
- Set up the editorial workflow. Drafts, review and publish steps that map to pull requests, so changes get checked before they go live.
- Add previews. Custom preview templates, so editors see something close to the real page while typing.
- Migrate content. Move a WordPress or older Netlify CMS site into Markdown files with front matter, redirects included.
What do we vet for?
Decap looks simple until a site has 300 pages and three editors. We ask candidates how they handle these cases:
- Media. Images committed to Git grow the repository fast. A candidate should know when to move them to a media library or a CDN.
- Relations. Decap handles references between collections, but it is not a relational database. We check that the person knows where that stops.
- Auth failures. The first support ticket is almost always “I cannot log in”. We ask how they would debug the OAuth flow.
- Project health. Decap is community-maintained, so a good engineer checks recent releases before betting a roadmap on a feature, and has a fallback plan.
What do the first weeks look like?
Week one is an audit of your repository, the current admin setup, who can log in and what editors complain about. The developer then ships one visible fix, often a working login or a corrected collection. Following weeks cover previews, the editorial workflow, a trimmed media setup and a short guide for editors. Every change arrives as a pull request.
Which engagement model?
Decap setups are usually a scoped project of a few weeks, and many end with a handover to your own developers. If you keep adding page types, a dedicated developer works better, and staff augmentation puts one inside your team. A rebuild with design, content and QA goes through a dedicated team. Rates across roles and seniority run from $50 to $150 per hour. Because Decap is free software, your spend goes to engineering time and hosting, not licences.
When is Decap the wrong tool?
Decap suits small to mid-size marketing sites, docs and blogs. When editors need visual, on-page editing, compare it with TinaCMS and CloudCannon in our guide to the best Git-based headless CMS platforms. For the site underneath, we build with Astro or Eleventy. Our Decap CMS services page covers the full project, and hire headless CMS developers covers other platforms.