Skip to content

Publishing to our Website - No Fuss Computing

MKDocs Page Publishing Article Help Our website is statically generated from markdown files. The available markdown syntax can be viewed within our manual. There are certain requirements that must be met so that the page is correctly generated. Where possible we use microdata where suitable. Microdata enables the page to be described in a way that enables search engines to categorise our content. Please ensure you select the most appropriate page type under step two. Doing this will ensure that the right metadata is applied which enables the build to apply the appropriate microdata.

All of our pages contain metadata. within a Markdown file, this is placed at the top of the file. All markdown files must contain the following as the minimum metadata:

title: #(1)
description: #(2)
date: {formatted YYYY-MM-DD} #(3)
  1. This is the title of the page and will be rendered during the static page construction.
  2. This is the meta description of the page and is predominatly used by search engines to display a blurb about the page.
  3. This is the date that the page was created.


This metadata must be included in all markdown files. The other types below, must have that metadata appended to this metadata.

To view the additional requirements for adding page(s) to our website please see the applicable sections below.

Single Page

Single pages are stored within our website repo. Create the markdown file in the location of where you wish for the page to go. Ensure that when naming the file, it's as close as possible to the metadata title.

For example for an article, create the markdown file in path articles/{year}/{page title with '_' for spaces}.md

FEATURE for about not yet available. CREATE it

Use a blog post if the topic of discussion is just a random topic that is not covered by any other type below.

template: article.html
type: blog
copyrightHolder: (optional)
copyrightHolderType: (mandatory if copyrightHolder present. valid values Person or Organization)
about: (optional)
tags: (optional)
  - tagename


if the blog is about an object/item that has a url, include the about metatag with the items url.

FEATURE not yet available. don't use how to

Use a how to guide if the topic to cover explains in steps how to accomplish a task. it's important that the steps are in numbered paragraphs.

template: article.html
type: howto
copyrightHolder: (optional)
copyrightHolderType: (mandatory if copyrightHolder present. valid values Person or Organization)
about: {url to item being discussed}
tags: (optional)
  - tagename


author can be omitted if not intended to be from any particular person.

Use an article if the topic to discuss is what would be considered news worthy. i.e. a release of a product.

template: article.html
type: article
copyrightHolder: (optional)
copyrightHolderType: (mandatory if copyrightHolder present. valid values Person or Organization)
about: {url to item being discussed}
tags: (optional)
  - tagename


author can be omitted if not intended to be from any particular person.


Adding a section to the website, requires it's own repository. Below will detail the additional requirements for setting up the repository for inclusion as a section to our website. In addition to the required repository set up steps, the following items are required as part of the repositories file system:

{Repository root folder}
  |-+ pages #(1)
    |-- stylesheets #(2)
  |-- website-template #(3)
  |-- mkdocs.yml #(4)
  1. A directory call pages which will contian the markdown files for publishing. The structure od this directory, will become the site navigation structure.
  2. This directory is optional, however if you do require additional styles, include this directory with the stylesheet name of extra.css
  3. This directory is a git submodule of the project website-template
  4. This yaml file contains the settings applicable to the repository in question.


All directory and file names must be in lowercase and use _ for spaces.

Minimum contents of the MKDocs build file, mkdocs.yml
INHERIT: website-template/mkdocs.yml

repo_name: {gitlab repository name}
repo_url:{gitlab repository path}
edit_uri: '/-/ide/project/{gitlab repository path}/edit/development/-/pages/'

- Home:

- Articles: 

  - articles/

- Projects: 

  - projects/

- Operations:

  - operations/

- Contact Us:


If the repository your adding is not the root repository for the website, only include the default mkdocs.yaml contents as specified above and the navigation structure for the repository in question. This then enables the navigation table to dynamically adjust to the relevant section of the website.

Additional required entries in file .gitignore
# Ignore build Directory


# ignore python dev env



A Project is one of our projects under our projects group on gitlab. each project has it's own pages that are published as it's own section on the website, within path /projects/. The subfolder name is the same as the gitlab project slug.

Manuals are placed under the website path /operations/manuals/ in there own folder, and named after the project. To add a file to our manuals, or a new manual, use the operations repository.

template: manual.html
about: #(1)
  1. This must link to the item the manual page is about.

Website Template

We use a seperate repository as a website template. This repository contains all items that form part of the general formatting of the site.

Mkdocs Build File

detail, ToDo:

Default mkdocs.yml
site_name: No Fuss Computing
site_description: "Here at No Fuss Computing we predominately do research and development into, making your computing experience a more enjoyable one."

site_author: No Fuss Computing
copyright: Copyright © No Fuss Computing 2021

#site_favicon: favicon.ico

docs_dir: 'pages'
site_dir: build

  name: material
  logo: assets/logo.png
  custom_dir: website-template/theme-overrides
    repo: fontawesome/brands/gitlab # (1)!
  locale: en
  font: false
    - navigation.tracking
    - navigation.tabs
    - navigation.tabs.sticky
    - navigation.expand
    - navigation.indexes
    - search.highlight
    - toc.integrate
    - header.autohide
    - navigation.sections
    - content.code.annotate

    - media: "(prefers-color-scheme: light)"
      scheme: default
      primary: indigo
      accent: indigo
        icon: material/lightbulb-outline
        name: Switch to dark mode
    - media: "(prefers-color-scheme: dark)"
      scheme: slate
      primary: indigo
      accent: indigo
        icon: material/lightbulb
        name: Switch to light mode

  - stylesheets/extra.css

  - nfc_tags:
        folder: pages
        css_name: ".tags"
  - search:
      lang: en

  - git-revision-date-localized:
      type: iso_date
      enable_creation_date: true
#  - minify:
#      minify_html: true

  version: 1.0
    - link:
      name: DockerHub
      icon: fontawesome/brands/docker

    - link:
      name: Facebook
      icon: fontawesome/brands/facebook

    - link:
      name: Gitlab
      icon: fontawesome/brands/gitlab

    - link:
      name: Github
      icon: fontawesome/brands/github
    dir: articles
    author: jon_nfc
    words_read_per_minute: 300
    list_length: 25
    extended_preview: true

  - def_list
  - pymdownx.tasklist:
      custom_checkbox: true
  - meta
  - attr_list
  - admonition
  - pymdownx.details
  - pymdownx.highlight:
      anchor_linenums: true
  - pymdownx.inlinehilite
  - pymdownx.snippets
  - md_in_html
  - pymdownx.superfences
  - pymdownx.tabbed:
      alternate_style: true
  - tables
  # - pymdownx.emoji:
  #     emoji_index: !!python/name:material.extensions.emoji.twemoji 
  #     emoji_generator: !!python/name:material.extensions.emoji.to_svg
  #     options:
  #       custom_icons:
  #         - .icons

Theme Over Ride

detail, ToDo:

Gitlab CI/CD

within our Gitlab-ci repository, we have a template that can be included within your .gitlab-ci.yml file. This template automagically adds the required jobs for deployment to our website, refer to the documentation on how to use.


This page forms part of our Operations Manual.

Page Metadata
Version: ToDo: place files short git commit here
Date Created: 2022-08-25
Date Edited: 2023-05-23


Would You like to contribute to our Operations Manual? You can assist in the following ways:


ToDo: Add the page list of contributors

Back to top