Plan: Public Docs and Template Enforcement
Plan: Public Docs and Template Enforcement
Status: DEFERRED
This plan depends on
plan-2026-02-24-docs-foundation completing first. The foundation plan establishes naming conventions, linking conventions, plan continuity via SessionStart, and the recursive plan structure that this plan assumes.When the foundation plan completes, this plan's phases become executable. Each phase may be promoted to its own plan if it needs more detail.
Vision
Make pal-e-docs publicly accessible, professionally styled, and structurally enforced. "I tell an agent what to do, and it already knows my platform, my SOPs, my active projects, and where I left off." Everything lives in docs — projects, repos, issues, SOPs. Agents are trained to look at pal-e-docs first, always.
Previous Plan
plan-2026-02-24-docs-foundation (prerequisite — do that first)Depends On
plan-2026-02-24-docs-foundation— naming conventions, linking, plan continuity, template enforcement at MCP level
Phases (each may become its own plan)
Phase 1: Public-Facing + Professional CSS
Goal: pal-e-docs accessible publicly with professional, readable, mobile-friendly styling.
Candidate plan slug:
plan-YYYY-MM-DD-public-css- Enable Tailscale Funnel for pal-e-docs service
- Add HTML sanitization on note content rendering
- Overhaul base.html CSS: dyslexic-friendly font, responsive, professional typography
- Test on mobile and desktop
Phase 2: Issue Tracking Migration
Goal: All issues live in pal-e-docs. Agents look here first.
Candidate plan slug:
plan-YYYY-MM-DD-issue-tracking- Migrate existing open issues into pal-e-docs notes
- Update SessionStart hook to inject open issues
- Add /browse/issues frontend page
- Create
/new-issueand/close-issueskills
Phase 3: Remaining Cleanup
Goal: Close out deferred items.
- Merge pending claude-custom PRs (#15, #16, #17)
- Merge forgejo-mcp PR #3
Next Plan Seeds
- Woodpecker CI for MCP tools
- Browse search bar
- Litestream backup
- Deprecate Project.repo_url