Live examples
Four sites built by the technology, each with its repository. Two of them are the templates every new site starts from — deployed untouched, so you can see what you get before changing a line.
| Site | What it shows | Repository |
|---|---|---|
| template-www.pages.gitt.one | The landing-page template as it comes: a home page of four sections and a contact page. Every tag in it is taken apart on Landing pages | pages/template-www |
| template-docs.pages.gitt.one | The knowledge-base template as it comes: a front page and one section with two pages — sidebar, search, “on this page”, previous/next. Taken apart on Knowledge bases | pages/template-docs |
| pages.gitt.one | A full landing page: hero with a photo, logos, feature grids, a checklist, steps, code samples, stats, a portfolio pulled from an API, a contact form — and the component collection with every section the engine has | pages/www |
| docs.pages.gitt.one — this site | A knowledge base of about twenty pages in four sections, with images, tables and code; sidebar order set with sidebar.order | pages/docs |
The templates are the reference: when this documentation says “the template does X”, the live site is where to look, and the repository is where to copy from. Both are rebuilt on every engine release like any other site, so they always show the current engine.
What the two templates have in common
Section titled “What the two templates have in common”Open both repositories side by side: the Dockerfile, .gitlab-ci.yml and
docker-compose.yml differ only in the builder image name and in the
compose file passing the password variable. Everything else is content. That
is the whole point — see What is in the repository.