Table of Contents

Research & Development

Security and Authentication

  • Deny un-authenticated access
  • Creating User Accounts

Read the docs for the login plugin

Restricting Access to the Docs

More Site Defaults

Settings to add to our Ginkgo install profile.


  • Set Default Theme
  • Default Ordering: "Folder - based on prefix-less folder name"


  • Enable Markdown Extra
  • Auto URL Links


  • Force lowercase URLs: No

Edit In-place

Writers should be able to edit content without using the Admin.

Instead of providing the link to edit on GitHub, provide a link (to permissioned users) to open an editor on the front-end.

Embed Markdown From Source Control

embed repo README docs.

Add the broken link checker plugin into the default install profile.

Document it's usage.

Any way to automate via git-hooks?

I think an alternative to frequently using link checking would be to set the canonical route on pages and use that in links instead. A downside is that links will not work in a simple markdown editor (Typora). This might be worthwhile for freedom of moving content around. Broken-link checking will still be necessary, but could maybe be done less frequently.

The Grav docs have a nifty trick where pages are linked to each other in a previous-next relationship.

Theme Titles

The Learn2 (and related themes) display the title from the frontmatter as a header-1. The title is necessary for the menu system. This results in a few awkward scenarios. As the default grav theme does, the frontmatter title should not be rendered as a title on the page, so that an explicit title can be set.

Table of Contents

Add an auto-generated Table of Contents to the theme.

Warning: the editable plugin warns that twig can break the editor. Find a compatible way to add the table of contents. [TODO]

What can be done with Page Collections?

Upstream Issues to Track