What is in the repository

Both listings are the real templates, file for file. The live sites they produce: template-www.pages.gitt.one and template-docs.pages.gitt.one.

Landing page — pages/template-www

articles/
  index/index.en.mdx        ← the home page: Prose, FeatureCards, Steps, CtaBanner
  contacts/index.en.mdx     ← /contacts: a ContactForm
images/                     ← pictures referenced by name from the content (empty in the template)
assets/                     ← files served as they are: PDFs, downloads (empty in the template)
pages.config.js             ← the only configuration: title, siteUrl, contacts, brandColor, menu
Dockerfile                  ← 9 lines, FROM builder-www
docker-compose.yml          ← names the image and the port
.gitlab-ci.yml              ← 5 lines: includes the shared pipeline
README.md                   ← for the people who open the repository; not a page

Knowledge base — pages/template-docs

README.md                   ← the front page: /
Guide/
  Getting started.md        ← /guide/getting-started
  FAQ.md                    ← /guide/faq
pages.config.js             ← title, siteUrl, description, themeColor
Dockerfile                  ← 11 lines, FROM builder-docs; removes its own plumbing from the copy
docker-compose.yml          ← names the image, passes BASIC_AUTH_HTPASSWD through
.gitlab-ci.yml              ← the same 5 lines

In a knowledge base every Markdown file is a page, so the repository has no articles/ folder — the folders are the sections. Add an assets/ folder for downloadable files when you need one.

What is not there

No node_modules, no lock file, no build configuration: dependencies live inside the builder image. The Dockerfile, the compose file and the CI file come from the template and normally never change. What each of them does, line by line, is on How it works.