This repository contains the Updatecli website. It is a Hugo site using the Doks theme and is deployed on Netlify.
- Local development runs through
npm run start - Production builds run through
npm run build - Netlify publishes the generated
public/directory
content/en/- English site contentcontent/en/docs/- product documentation pagescontent/en/blog/<year>/- blog postsassets/js/- custom JavaScript bundled into the siteassets/scss/- SCSS overrides and site stylinglayouts/- Hugo layout overridesconfig/_default/- shared Hugo configurationconfig/production/,config/next/- environment-specific Hugo configfunctions/- Netlify functionsstatic/- static assets copied as-is at build time
- Install dependencies:
npm install - Start local dev server:
npm run start - Build the site:
npm run build - Run all lint checks:
npm run lint - Run repository tests:
npm test - Lint only Markdown:
npm run lint:markdown - Regenerate command docs:
npm run docs
- Content files use Hugo front matter at the top of each document.
- Documentation and blog content primarily live under
content/en/. - Blog posts are organized by year under
content/en/blog/. - The repo includes Markdown content and may also include AsciiDoc content.
- Keep root Markdown files lint-friendly because
*.mdis covered by the markdown lint command.
- JavaScript in
assets/js/,config/, andfunctions/is linted with ESLint. - SCSS changes should follow the structure already used in
assets/scss/common/,assets/scss/components/, andassets/scss/layouts/. - Site-specific style overrides belong in the existing custom SCSS files when appropriate instead of introducing parallel styling patterns.
- Hugo configuration is split across multiple TOML files under
config/_default/. - Language configuration currently points English content to
content/en. - The site enables Git info, Netlify redirects/headers outputs, and Hugo image processing through existing config.
- Netlify development proxies the Hugo server on port
1313through port8888.
- Prefer small, targeted edits that match existing Hugo, Doks, and content patterns.
- Update the relevant content, layout, assets, and config together when a change spans multiple site surfaces.
- Run the narrowest relevant command first, then broader validation as needed: Markdown lint for docs-only changes, full lint for frontend/config changes, and a Hugo build for rendering-sensitive changes.
- If updating CLI command reference pages, check whether
npm run docsshould be used instead of editing generated command docs manually.