makr.dk

Administrator quick start

For administrators and site owners, new to this Admin area. See Welcome to Kartotek for the vocabulary this doc assumes. This is a short first-run guide — logging in, publishing a first Post, and finding your way to the principal work areas — not the detailed reference for any one of them; each section below links onward to the doc that actually covers it.

The admin area is reached at /_admin, and is where every Post, Category, Domain, and doc on the site is written, versioned, and published.

Logging in

No passwords. Requesting access sends a one-time login link to the deployment's fixed admin email address, valid for 15 minutes and usable once. There's no persistent "remember me" — each session is a random token in a cookie, and logging back in after it expires means requesting a fresh link.

Your first Post

  1. Log in (above).
  2. In the sidebar, expand Categories and confirm at least one exists — create one if not (a Name and a UID are all that's required).
  3. Expand Posts and click + to create one. Choose a Post Type (Article is the default, general-purpose choice), give it a Title and UID, assign it to your Category, and fill in a body Text.
  4. Click Publish update. Your Post now exists, but it starts in PrePub — only you can see it.
  5. Open the Post's own page (the link at the top of its admin editor) to preview it exactly as a visitor eventually will.
  6. When you're ready, use the Post's Stage control to move it to Published — it's now live at domain/<uid>.

That's the whole loop everything else builds on: create, fill in content, publish a Version, then decide visibility separately via Stage. The full model behind this — Versions, ContentElements, Roles, and how nothing you publish is ever silently lost — is Posts and publishing.

Finding your way around the sidebar

The sidebar is organized around stable working areas, in this order: Dashboard, Domains, Categories, Tags, Analytics, Post Translations, GUI Translations, Media, Links, Documentation, and Admin. Every top-level entry sits on the same vertical rhythm, and every right-side + (or external-link) action lines up in the same column. Most sections expand and collapse to reveal their entries; a section that currently has exactly one entry opens it directly with a single click instead, with no expand step in between. There is no separate Posts section — Categories doubles as Posts' entry point, and the full sortable/filterable Posts list is always reachable at /_admin/posts, whether from there, a Category-scoped or Stage-filtered link, or a Dashboard tile. Every row's Category and Stage are editable inline, right in the list — see Posts and publishing's "Removing a Post from view" section. Expand/collapse state, for both the sidebar's own sections and the Category tree below it, is remembered across visits in this browser.

The bar at the top of every admin page shows Deployed (when the running version of the site was deployed) and Updated — the most recent durable change to the site's database, of any kind. See Dashboard and maintenance for the full at-a-glance picture these two feed into.

Where each area's own detailed guide lives:

Documentation and CSS are read-only here

The sidebar's Documentation tree — External Docs, Internal Docs, Post Type reference, Content Type reference, Release notes — and the Admin tree's Public CSS section are both read-only browsing surfaces, not editing ones: every doc and stylesheet is a repository-owned, commit-time source, compiled into the site when it's built. A change to any of them starts as a GitHub Issue and ships through the normal commit/review/deploy workflow, the same as any other source-file change — there is no way to edit a doc or a CSS file from within Admin. Reading a public doc needs no login; Internal Docs and the CSS catalogue require being logged in as admin. See "Release notes" in Roadmap and release history for the site's deploy history, sourced from GitHub Releases.

View raw markdown