How to Contribute
This website is open to contributions from all partners in the SAMT-BU project. There are three ways to contribute, depending on the type of changes you want to make and your technical background:
| Method | Suitable for | Requires |
|---|---|---|
| CMS editing | Subject-matter experts and editors | GitHub account (free) |
| GitHub editing | Minor changes, technical users | GitHub account + Markdown |
| Local setup | Structural changes, developers | Hugo + Git installed |
Option 1 – Editing in the Browser via CMS
This is the recommended option for most contributors. You edit content directly in the browser using a visual editor – no knowledge of Markdown or Git required.
To edit an existing page:
- Go to the page you wish to edit on the website
- Click the “Edit” menu in the top-right corner of the header
- Select “This page” – you are taken directly to the correct page in the CMS editor
- Log in with your GitHub account (first time: click “Login with GitHub”)
- Make your changes in the editing field
- Click “Save” – the change is published automatically after a short while
To create a new page:
- Click “Edit” → “Other options” in the header to open the CMS portal
- Select the appropriate collection in the left panel
- Click “New” and fill in the title and content
- Click “Save”
Note: You need a GitHub account to log in. Create one for free at github.com. Contact an administrator to obtain write access to the correct repository the first time.
Option 2 – Editing Directly on GitHub
Suitable for individual changes and minor corrections without a local installation. Requires a GitHub account and familiarity with Markdown.
How to do it:
- Go to the page you wish to edit at samt-x.github.io/samt-bu-docs
- Click the “Edit on GitHub” link at the bottom of the page
- Make your changes in the Markdown field
- Scroll down to “Commit changes”
- Write a brief description of what you changed
- Select “Create a new branch and start a pull request” (recommended), or commit directly to
mainif you have the necessary permissions - Click “Propose changes” – an editor will review and approve it
The page is published automatically within a minute of the change being approved.
Option 3 – Local Setup (for Developers)
This option gives you a full local working environment in which you can preview all changes in the browser as you write. Recommended for structural changes, larger amounts of new content, or technical development.
What You Need
| Tool | Version | Purpose |
|---|---|---|
| Git | Latest stable | Version control |
| Hugo Extended | 0.155.3 or later | Site generator |
| Go | 1.21 or later | Required by Hugo Modules |
| Text editor | – | VS Code recommended |
Installation on Windows
winget install --id Git.Git
winget install --id Hugo.Hugo.Extended
winget install --id GoLang.Go
winget install --id Microsoft.VisualStudioCode
Restart the terminal afterwards so that the newly installed programmes are available in PATH.
Verify the installation:
git --version
hugo version
go version
Installation on macOS
brew install git hugo go
Installation on Linux (Ubuntu/Debian)
sudo apt install git golang
# Hugo Extended is obtained from GitHub Releases (the apt version is often too old):
wget https://github.com/gohugoio/hugo/releases/download/v0.155.3/hugo_extended_0.155.3_linux-amd64.deb
sudo dpkg -i hugo_extended_0.155.3_linux-amd64.deb
Clone the Repository
git clone --recurse-submodules https://github.com/SAMT-X/samt-bu-docs.git
cd samt-bu-docs
hugo mod download
--recurse-submodules ensures that the theme (hugo-theme-samt-bu) is downloaded at the same time. hugo mod download fetches content modules from the other repositories.
Start Local Preview
hugo server
Open http://localhost:1313/samt-bu-docs/ in the browser. The page updates automatically when you save a file.
File Structure – Where the Content Lives
content/
om/ ← "About" section
behov/ ← Needs (use cases)
pilotering/ ← Pilots
arkitektur/ ← Architecture
loesning/ ← Solutions
rammeverk/ ← Framework
informasjonsmodeller/ ← Information Models
innsikt/ ← Shared Insight
teams/ ← Teams (content module)
utkast/ ← Drafts and inputs (content module)
Each chapter is a folder containing two files:
content/om/om-samt-bu/
_index.nb.md ← Norwegian content
_index.en.md ← English content
Writing Content
Content files are standard Markdown files with a small header at the top (frontmatter):
---
title: "Page title"
weight: 10
---
Your content begins here in standard Markdown.
## Heading
A paragraph with **bold text** and *italic text*.
title– page title displayed in the menu and at the top of the pageweight– sort order (lower number = higher in the menu)draft: true– add this to hide the page from publication until it is ready
Saving and Publishing Changes
git add content/path/to/file/_index.en.md
git commit -m "Brief description of what you changed"
git push
GitHub Actions builds and publishes automatically after 1–2 minutes.
No write access to the repository? Create a pull request instead:
git checkout -b my-contribution→ make changes →git push origin my-contribution→ open a PR on GitHub.
Useful Commands
| Command | Description |
|---|---|
hugo server | Start local server with live reload |
hugo server -D | Include pages marked with draft: true |
hugo | Build to the public/ folder (check for errors) |
git pull | Fetch the latest changes from GitHub |
hugo mod get -u | Update all content modules to the latest version |