Skip to content

Import static pages and populate global content #42

@mattstratton

Description

@mattstratton

Context

PRD §1.5 — The public site needs global pages (About, Organizing Guide, Speaking, Code of Conduct, etc.) that currently live as static pages in the Hugo repo. These need to be in the database for the static_page view to render them.

Pages to Import

From Hugo `content/page/`:

  • `about.md` → /about/
  • `conduct.md` → /conduct/ (global code of conduct)
  • `organizing.md` → /organizing/
  • `sponsor.md` → /sponsor/ (global sponsorship info)
  • `privacy.md` → /privacy/
  • `ignite-talks-format.md` → /ignite-talks-format/
  • `open-space-format.md` → /open-space-format/
  • `devops-gives-back.md` → /devops-gives-back/
  • `events.md` → (may conflict with /events/ route — needs special handling)

Current State

  • StaticPage model exists with slug, title, content (markdown)
  • static_page view exists at `//` and renders markdown
  • No static pages in the database
  • The view works if pages exist — just need the data

Notes

  • This is a subset of the broader blog/static page import (Import blog posts and static pages from Hugo repo #20) but simpler and higher priority
  • Could be done as a simple management command or even a fixture
  • URL routing: verify `//` doesn't conflict with other top-level routes

Acceptance Criteria

  • All Hugo static pages imported into StaticPage model
  • Pages render correctly at their URLs
  • Markdown content displays properly
  • Navigation links to global pages work

References

  • PRD §1.5 — Static pages
  • `apps/pages/models.py:StaticPage`
  • `apps/pages/views.py:static_page`

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:data-migrationHugo repo data import and migrationarea:public-sitePublic-facing pages and templatesphase:1-mvpPhase 1: Core Platform MVP

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions