Eleventy + Netlify CMS Developer

Project Brief: Static HTML Site → Static Site Generator + Git-Based CMS

Project Summary

Convert an existing static HTML/CSS website into a static site generator setup (e.g. Hugo, Eleventy, or Jekyll) with a git-based CMS (Netlify CMS/Decap CMS or CloudCannon) layered on top. Goal: preserve the current design exactly (pixel-for-pixel — layout, fonts, colors, spacing, responsive behavior) while enabling content edits through a web dashboard, with no code editing required for routine updates.

Current Setup

· Site type: Static HTML/CSS (no CMS)

· Current deployment: Git-based (manual builds/deploys)

· Domain: zimmermanatlantalaw.com

· Number of pages: 8 pages]

Scope of Work

1. Review the existing site’s HTML/CSS/JS (source files provided via current git repo).

2. Restructure the site into a static site generator format:

· Choose an appropriate generator (Hugo, Eleventy, or Jekyll — developer's recommendation welcome, but should be justified)

· Split reusable design elements (header, footer, navigation) into templates/partials

· Convert page content into content files (Markdown/YAML/JSON, depending on generator) separate from design templates

· Preserve all existing styling exactly (fonts, colors, spacing, responsive/mobile breakpoints)

· Rebuild any interactive elements (forms, menus, sliders) to function identically

3. Set up a git-based CMS on top of the generator:

· Recommend and configure either Netlify CMS (Decap) or CloudCannon

· Define editable fields for each page/content type (e.g., headline, body text, images, practice area list) so all routine content lives in dashboard-editable fields — not hardcoded in templates

· Set up authentication so only authorized users (me, and anyone I invite) can access the editing dashboard

4. Set up hosting and deployment pipeline:

· Connect the git repo to the chosen host (Netlify, CloudCannon-hosted, or other — developer's recommendation welcome)

· Confirm automatic rebuild/republish on every content save

5. Migrate all existing page content into the new content files

6. Test across major browsers and mobile devices, including the full edit-save-publish workflow.

7. Deploy to a staging URL for review before pointing the live domain at the new setup.

8. Provide handoff documentation: how to log into the CMS dashboard, edit existing pages, add new pages, update images, and what to do if a rebuild fails.

Deliverables

· Fully functional static site generator setup matching current design exactly

· Configured git-based CMS with a working editing dashboard

· All current site content migrated into the new content files

· Site live and tested on a staging URL

· Written or video walkthrough of the day-to-day editing workflow

· Documentation of the technical stack (generator, CMS, hosting) for future developers

What I'll Provide

· Access to current git repository (HTML/CSS/JS source files)

· Brand assets (logo files, fonts, brand colors) if not already embedded in the code

· Domain DNS access for final cutover (handled separately, after approval)

· Hosting account access (Netlify/CloudCannon) once created, or developer can set up and hand over credentials

Requirements

· Final result must require zero code editing for routine content updates (text changes, new pages, image swaps, menu updates) — all done through the CMS dashboard

· Design must match the current live site exactly — not “similar,” not a redesign

· Site must remain responsive/mobile-friendly exactly as it currently is

· Stack choices (generator + CMS + host) should prioritize long-term maintainability and a reasonably findable developer pool if I need help again later — avoid highly niche or unsupported tools

Timeline

· Flexible

Budget

· Seeking quotes.