This is the source for the ZATech community wiki built with Hugo + Docsy.
Requirements:
- Hugo Extended (>= 0.150)
- Go (for Hugo Modules)
- Node.js 18+ (for PostCSS used by Docsy)
Steps:
# 1) Clone
git clone https://github.com/zatech/zatech-wiki.git
cd zatech-wiki
# 2) Install Hugo modules (Docsy, Font Awesome)
hugo mod tidy
# 3) Install PostCSS toolchain
npm install
# 4) Run the dev server
npm run devThe site will be available at http://localhost:1313/.
content/faqs/— Frequently Asked Questionschannels/— channel-specific pagespages/— general pages (e.g. commercial channels)blog/— longer-form guides and posts
assets/scss/— custom styles;_variables_project.scssand_styles_project.scssstatic/— static files (images, favicons, etc.)layouts/— Docsy overrides (e.g.partials/footer.html)hugo.toml— site config
We welcome issues and PRs from the community.
- Create a new branch for your change.
- For small content edits, go straight to a PR.
- For structural or design changes, please open an issue to discuss.
Content conventions:
- Prefer Markdown, keep front matter minimal:
title, optionalsummary. - Use relative links within the site (e.g.
/faqs/howtoinvite/). - Images go under
static/images/...and use absolute paths like/images/...in Markdown.
Writing style:
- Be clear and concise.
- South African audience and context.
- Avoid personal info or private channel content unless explicitly allowed.
Longer, living documents belong in content/blog/. Use this front matter:
+++
title = "Post title"
date = 2025-01-01T00:00:00Z
summary = "Short summary shown on the blog list"
author = "Your Name"
+++Top navbar items are defined in hugo.toml under [menu.main].
GitHub Actions are set up to:
- Build and deploy to GitHub Pages on pushes to
main:.github/workflows/pages.yml. - Provide PR deploy previews:
.github/workflows/pr-preview.yml.
To enable Pages in the repo:
- Settings → Pages → Build and deployment → Source: GitHub Actions.
Content is © respective authors. Code and configuration is MIT unless otherwise noted.