Skip to content

feat: scaffold MkDocs site and migrate inasafe-doc + WordPress content - #31

Merged
timlinux merged 2 commits into
mainfrom
feature/mkdocs-site-migration
Oct 20, 2026
Merged

timlinux merged 2 commits into
mainfrom
feature/mkdocs-site-migration

Conversation

@timlinux

Copy link
Copy Markdown
Contributor
  • Add MkDocs Material site under docs/ (InaSAFE branding, InfrastructureMapper structure)
  • Move legacy WordPress export to legacy-site/ (kept until Phase 4 cutover, then deleted)
  • Migrate inasafe-doc manual + training content
  • Migrate WordPress news/events/case-studies/about/contributing content
  • Redesign homepage and section landing pages as grid cards
  • Full nav wiring; mkdocs build --strict passes

Tim Sutton added 2 commits October 20, 2026 19:01
Previous fix only changed --md-accent-fg-color, which Material only uses
for link colour and a focus-outline on nav tabs - it never rendered as
any visible bar. Verified by fetching the deployed site's actual CSS.

Add a real <div class="inasafe-accent-bar"> via a header block override
(confirmed against mkdocs-material's actual base.html block names before
writing this, since the first attempt silently did nothing).
Suppress mkdocs-material's default per-page <aside class="md-source-file">
(confirmed the exact template + page.meta.git_revision_date_localized
variable name against the real upstream source before writing this) via
an empty overrides/partials/source-file.html, and add the same date as
one unobtrusive line in the site footer instead.
@timlinux timlinux self-assigned this Oct 20, 2026
@timlinux
timlinux merged commit a456cc3 into main Oct 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant