docs: publish fork-owned Marka documentation at docs.marka.abhipraya.dev

[absolutepraya]

Goal

Publish a fork-owned documentation site for Marka at docs.keep.abhipraya.dev, with content that accurately documents this repository and clearly separates its behavior from upstream Karakeep.

Relationship

• Parent identity work: feat: rebrand the fork with a one-word product identity #10
• Documentation coherence: docs: establish coherent documentation and assistant context #11
• Landing-site work: feat(landing): establish a fork-owned Marka landing site #25

Scope

• Define the docs hosting and deployment model for docs.keep.abhipraya.dev, including preview environments, canonical URL, HTTPS, and rollback behavior.
• Apply the approved Marka name, navy and white visual system, favicon, navigation logo, and social card throughout the Docusaurus site.
• Rewrite or curate the docs so local development, fork deployment, production-state pull, support boundaries, and operational guidance match this repository.
• Retain upstream product documentation and attribution only where it is useful, explicitly labeled, and not misleading.
• Update docs navigation, metadata, canonical URLs, structured data, internal links, repository links, edit links, and search configuration for the fork-owned site.
• Establish a repeatable source-of-truth map and documentation-change checklist shared with docs: establish coherent documentation and assistant context #11.

Guardrails

• Do not create or change DNS records, hosting, certificates, redirects, search indexes, or production configuration without a separate reviewed cutover plan and explicit approval.
• Do not include credentials, private infrastructure details, or misleading claims that an upstream service is fork-operated.
• Preserve existing production documentation availability until the new site is fully verified and a cutover is approved.

Acceptance criteria

• docs.keep.abhipraya.dev has an approved, reproducible deployment and rollback plan.
• The public docs present Marka consistently and accurately describe the fork.
• Canonical URLs, metadata, social assets, navigation, and search configuration target the fork-owned docs site.
• Upstream references are intentional, labeled, and functional.
• The docs build, links, desktop and mobile rendering, and deployed site are verified before cutover.

[absolutepraya]

Audit 2026-08-22: valid, but the hostname in this issue needs reconciliation before implementation. The Docusaurus site exists, while docs/docusaurus.config.ts:7-20 and :83-105 still target Karakeep Docs, docs.karakeep.app, karakeep-app/karakeep, and the upstream homepage. docs/README.md:29 also explicitly leaves hosted presentation to deferred work. Keep the issue open, update the final fork-owned docs hostname from the current identity decision, then implement and verify the deployment and rollback plan. Severity is medium because documentation is important for installation and operation, but the application itself remains usable.