openlibhums · joemull · Jul 3, 2026 · Jul 4, 2026 · Jul 4, 2026 · Jul 4, 2026
diff --git a/.github/workflows/pelican.yml b/.github/workflows/pelican.yml
@@ -1,7 +1,7 @@
 name: Deploy to GitHub Pages
 on:
   push:
-    branches: ["main"]
+    branches: ["main", "b-support-site-mvp"]
   workflow_dispatch:
 permissions:
   contents: read

diff --git a/.github/workflows/playwright.yml b/.github/workflows/playwright.yml
@@ -22,7 +22,7 @@ jobs:
       - name: Ensure browsers are installed
         run: python -m playwright install --with-deps
       - name: Run your tests
-        run: pytest
+        run: pytest --failed-first
       - uses: actions/upload-artifact@v4
         if: ${{ !cancelled() }}
         with:

diff --git a/README.md b/README.md
@@ -74,9 +74,6 @@ Documentation authors are asked to place all content in `/content/support/`,
 using GitHub-flavored Markdown and including images in
 `/content/support/images/`.
 
-Pelican interprets these pages as “articles,” so minimal requirements about
-having a `Title` in the YAML metadata apply.
-
 If they are editing on GitHub.com, they can make commits on the perpetual
 `copyediting` branch, or if they are working locally, they should open
 a dedicated feature branch. They may often need help with pull requests and

diff --git a/content/old-docs/changelog.md b/content/old-docs/changelog.md
@@ -1,5 +1,3 @@
-Title: Changelog
-
 # Changelog
 
 Release notes have moved to

diff --git a/content/old-docs/dev/api.md b/content/old-docs/dev/api.md
@@ -1,5 +1,3 @@
-Title: API
-
 # API
 
 API stands for Application programming interface. APIs are designed to

diff --git a/content/old-docs/dev/configuration.md b/content/old-docs/dev/configuration.md
@@ -1,5 +1,3 @@
-Title: Technical Configuration
-
 # Technical Configuration
 
 This section will discuss the technical configuration of Janeway

diff --git a/content/old-docs/dev/installation.md b/content/old-docs/dev/installation.md
@@ -1,5 +1,3 @@
-Title: Installation Guide
-
 # Installation Guide
 
 There are a number of ways to get Janeway up and running. For

diff --git a/content/old-docs/dev/oidc.md b/content/old-docs/dev/oidc.md
@@ -1,5 +1,3 @@
-Title: Open ID Connect (OIDC)
-
 # Open ID Connect (OIDC)
 
 Support for Open ID Connect has been added in 1.4.2 of Janeway. This

diff --git a/content/old-docs/dev/plugins.md b/content/old-docs/dev/plugins.md
@@ -1,5 +1,3 @@
-Title: Plugins, Events and Hooks
-
 # Plugins, Events and Hooks
 
 <div class="warning">
@@ -155,14 +153,14 @@ connect it with core areas of Janeway.
 {% endraw %}
 
 <figure>
-<img src="../nstatic/typesetting-plugin-dashboard.png"
+<img alt="" src="../nstatic/typesetting-plugin-dashboard.png"
 class="with-border" alt="../nstatic/typesetting-plugin-dashboard.png" />
 <figcaption>The typesetting plugin's dashboard template renders this
 block.</figcaption>
 </figure>
 
 <figure>
-<img src="../nstatic/kanban-card-example.png" class="with-border"
+<img alt="" src="../nstatic/kanban-card-example.png" class="with-border"
 alt="../nstatic/kanban-card-example.png" />
 <figcaption>Kanban cards look like this, they use the workflow/admin css
 (foundation).</figcaption>

diff --git a/content/old-docs/dev/robotsandsitemaps.md b/content/old-docs/dev/robotsandsitemaps.md
@@ -1,5 +1,3 @@
-Title: Robots and Sitemaps
-
 # Robots and Sitemaps
 
 In version 1.4.1 of Janeway we are introducing the generation of Robot

diff --git a/content/pages/accessibility-of-this-website.html b/content/pages/accessibility-of-this-website.html
@@ -3,6 +3,7 @@
 
 <head>
   <title>Accessibility of this website</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   {% call page_h1(max_char_width=16) %}

diff --git a/content/pages/copyright-and-licensing.html b/content/pages/copyright-and-licensing.html
@@ -3,6 +3,7 @@
 
 <head>
   <title>Copyright and licensing</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   {% call page_h1(max_char_width=15) %}

diff --git a/content/pages/hosting.html b/content/pages/hosting.html
@@ -8,6 +8,7 @@
 
 <head>
   <title>Hosting</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   {% include "components/hosting_splash.html" %}

diff --git a/content/pages/icons.html b/content/pages/icons.html
@@ -1,5 +1,6 @@
 <head>
   <title>Icons</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   <div class="flow">

diff --git a/content/pages/our-story.html b/content/pages/our-story.html
@@ -9,6 +9,7 @@
 
 <head>
   <title>Our story</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   {% include "components/george_space_splash.html" %}

diff --git a/content/pages/support.html b/content/pages/support.html
@@ -3,7 +3,8 @@
 {% from "components/page_section_group.html" import page_section_group %}
 
 <head>
-  <title>Support</title>
+  <title>Support - work in progress</title>
+  <meta name="alpha_site" content="main" />
 </head>
 <body>
   {% call page_h1() %}

diff --git a/content/pages/support/about/about.md b/content/pages/support/about/about.md
@@ -0,0 +1 @@
+# About
diff --git a/content/support/contributing-guide.md → ...pages/support/about/contributing-guide.md b/content/support/contributing-guide.md → ...pages/support/about/contributing-guide.md
@@ -1,5 +1,3 @@
-Title: Contributing to Janeway documentation
-
 # Contributing to Janeway documentation
 
 Work-in-process note: This page could explain how people including us and
@@ -11,11 +9,11 @@ how to name files and folders.
 ## Creating and editing pages
 
 All the pages of the support site are generated from text files stored under
-`/content/support/` in this repository. Old documentation can be found at
-`/content/old-docs/` while the support site is being built.
+`content/pages/support/` in this repository. Old documentation can be found at
+`content/old-docs/` while the support site is being built.
 
 Pages for the support site should be written in GitHub-flavored Markdown (GFM).
-Image files should be added under `/content/support/images/`. All the content
+Image files should be added under `content/pages/support/images/`. All the content
 can be edited on GitHub, so that you can make use of the Preview tab in GitHub.
 
 When creating Git commits, create a dedicated branch if you are working in
@@ -38,7 +36,7 @@ Do:
   my-folder/my-file-name.txt
 ```
 
-Don’t:
+Don't:
 
 - use spaces (reason: shell scripting)
 - use capital letters (reason: avoid broken links)
@@ -52,20 +50,10 @@ Don’t:
   my&your-folder/my&your-file-name.txt
 ```
 
-## Page metadata
-
-At the beginning of the file, please include the page title, preceded by
-`Title: `. It will appear in the browser tab, on search results, and on social
-media when the page is shared.
-
-The page you are reading has this at the top:
-
-```md
-Title: Contributing to Janeway documentation
-```
+## Headings
 
-Please also include a top-level heading for each page, using the single hash in
-Markdown syntax. Usually this will be the same as the page title.
+Include a top-level heading for each page, using the single hash in
+Markdown syntax.
 
 For example:
 
@@ -75,7 +63,7 @@ For example:
 
 ## Internal links
 
-If you want to link to another page in the documentation, use Markdown’s link
+If you want to link to another page in the documentation, use Markdown's link
 syntax, but leave the extension off the file, since eventually it will be an
 HTML file, not a Markdown file. For example, to create a link to this file from
 another file in the same folder, you can do this:
@@ -126,4 +114,4 @@ Do not put any bullet or dash before the definitions, because this will cause ex
 
 Importantly, put two spaces after the term in the first line, to maintain the line break when the Markdown is rendered.
 
-![The words "cat" and "dog" appear next to bullet points, and descriptions appear underneath each word](./images/lists-with-definitions.png)
+![The words "cat" and "dog" appear next to bullet points, and descriptions appear underneath each word](../images/lists-with-definitions.png)
diff --git a/content/pages/support/about/index.md b/content/pages/support/about/index.md
@@ -0,0 +1,78 @@
+# Janeway documentation
+
+Janeway is an open-source publishing platform for scholarly journals, presses, and repositories. It handles the whole path from submission through peer review, copyediting, and typesetting to a published article on a public website.
+
+These pages explain how to use Janeway, whether you are running a journal, managing a press, reviewing a manuscript, or submitting your own work.
+
+## Guides
+
+There are various guides available for using Janeway:
+
+- [Getting started with Janeway](../guides/getting-started.md)
+  These guides will help you set up your account, navigate Janeway and -if you are an editor or press manager- configure your first journal.
+- [Workflow guides](../guides/index.md#workflow-guides)
+  Each guide covers one role (e.g., author, reviewer, typesetter) from start to finish, so you can read only the parts that apply to you.
+- [Troubleshooting](../guides/index.md#troubleshooting)
+  Common problems and their solutions are outlined here.
+- [Setup and configuration](../guides/index.md#setup-and-configuration)
+  If you are setting up or configuring a journal, these guides collate and link to information that may be helpful.
+
+## Browse by theme
+
+### Accessibility
+
+### Accounts and roles
+
+### Analytics
+
+### Article management
+
+### Emails and reminders
+
+### Managing identifiers
+
+### Importing, exporting and updating data
+
+### Managing issues, volumes and collections
+
+### Journal management
+
+### Plugins
+
+### Press management
+
+### Repositories
+
+### Configuring review
+
+### Configuring submission
+
+_To be continued_
+
+## Browse by task
+
+### Set up your journal
+
+### Styling your journal
+
+### Handle peer review
+
+### Prepare and publish content
+
+### Managing your journal website
+
+### Communicating and monitoring
+
+### Managing a press
+
+### Managing a repository
+
+_Coming soon_
+
+## Getting help
+
+## Developer docs
+
+## All pages
+
+## About the docs
-Original file line number
+Diff line change
@@ Expand Up / @@ -3,6 +3,7 @@ @@
     <head>
       <title>Accessibility of this website</title>
+      <meta name="alpha_site" content="main" />
     </head>
     <body>
       {% call page_h1(max_char_width=16) %}
@@ Expand Down @@