See about for Elmcraft's philosophy.
Built with elm-pages.
The entrypoint file is index.ts. That file imports the generated elm-pages harness.
git submodule init && git submodule update
npm install
# starts a local live-reloading dev server
npx elm-pages dev
From there you can tweak content/ files or change the Elm code.
The content folder markdown files are currently turned into static pages entirely via the single Route.SPLAT__ module mapping.
Pretty much everything else about the site, from theming to functionality, is done from Elm.
To make a new page, simply add a new your-path/your-page.md in content/.
The 'frontmatter' (bits between --- at the top of the markdown file) drives other static gen config i.e. SEO, and can be extended if needed (see DataSource.MarkdownElmUi).
elm-pages will pick up new pages, compile them and type check them.
Navigation UI can be updated in src/Theme/Navigation.elm.
src/Theme/* has most of the UI components split up.
See src/Theme/All.elm for which markdown/html tags end up being rendered by which components.
All the UI is built with elm-ui.
(Note: these are conceptually BackendTask in elm-pages-v3, but we've not renamed them here yet)
src/DataSourcecontains elm-pages data sources for external datasrc/DataStaticcontains static data as Elm values
For content we're generating, generally err towards static data first and if it becomes high churn then we can move elsewhere.
For content that is already curated elsewhere and available via HTTP, please automate the fetching of that data in a data source.
All static files including images should go into public/.