samui-fixit

Samui Fixit — Eleventy + Netlify CMS scaffold

This repository was scaffolded to use Eleventy (11ty) as a static site generator and Netlify CMS for easy, non-Git admin editing.

Quick start (local):

npm install
npm run start    # local dev, Eleventy server
npm run build    # build static site into _site/

You can run npm run build any time to generate production files in _site/. To preview the production build locally, npm run start will serve from _site after building.

Deploying

Netlify: connect the repository and Netlify will use netlify.toml for build settings and redirects (including /api/services.json).
Other hosts: simply upload the contents of _site/ to GitHub Pages, Vercel, Cloudflare Pages, S3/CloudFront, Firebase Hosting, etc. Ensure you replicate the /api/services.json redirect rule if your host doesn’t support Netlify-style redirects.

After deployment you’ll also need to configure your authentication/provider for Netlify CMS so editors can log in and manage content.

Netlify setup (publish + admin):

Push repository to GitHub.
On Netlify: “New site from Git” → connect this repo.
In Site settings → Build & deploy: Build command npm run build, Publish directory _site.
Enable Identity (Netlify Identity) and then go to Identity > Services > enable Git Gateway.
Visit https://<your-site>.netlify.app/admin/ to log in and create posts.

Notes:

Content files live in content/blog/ as Markdown. Netlify CMS will commit Markdown files into that folder.
For data-driven sections (services, pricing, etc.) put Markdown files under content/services/ (or a custom folder) and create collection entries in admin/config.yml.
Service cards are rendered by a reusable component (_includes/components/service-card.njk). Modify or extend this to match your design.
A JSON API endpoint is generated at /api/services.json/ (with a redirect for slashless access) so the front end or external tools can fetch service data.
Static files (admin UI) are in admin/ and are passed through to the published site.