Files
StarPunk/docs/projectplan/ROADMAP.md
Phil Skentelbery f28a48f560 docs: Update project plan for v1.1.0 completion
Comprehensive project plan updates to reflect v1.1.0 release:

New Documents:
- INDEX.md: Navigation index for all planning docs
- ROADMAP.md: Future version planning (v1.1.1 → v2.0.0)
- v1.1/RELEASE-STATUS.md: Complete v1.1.0 tracking

Updated Documents:
- v1/implementation-plan.md: Updated to v1.1.0, marked V1 100% complete
- v1.1/priority-work.md: Marked all items complete with actual effort

Changes:
- Fixed outdated status (was showing v0.9.5)
- Marked Micropub as complete (v1.0.0)
- Tracked all v1.1.0 features (search, slugs, migrations)
- Added clear roadmap for future versions
- Linked all ADRs and implementation reports

Project plan now fully synchronized with v1.1.0 "SearchLight" release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-25 11:31:43 -07:00

6.1 KiB

StarPunk Roadmap

Current Status

Latest Version: v1.1.0 "SearchLight" Released: 2025-11-25 Status: Production Ready

StarPunk has achieved V1 feature completeness with all core IndieWeb functionality implemented:

  • IndieAuth authentication
  • Micropub endpoint
  • Notes management
  • RSS syndication
  • Full-text search
  • Custom slugs

Version History

Released Versions

v1.1.0 "SearchLight" (2025-11-25)

  • Full-text search with FTS5
  • Complete search UI
  • Custom slugs via Micropub mp-slug
  • RSS feed ordering fix
  • Migration system improvements

v1.0.1 (2025-11-24)

  • Fixed Micropub URL double-slash bug
  • Minor bug fixes

v1.0.0 (2025-11-24)

  • Initial production release
  • IndieAuth authentication
  • Micropub server implementation
  • Notes CRUD functionality
  • RSS feed generation
  • Web interface (public & admin)

Future Roadmap

v1.1.1 (Patch Release)

Timeline: As needed Focus: Bug fixes and minor improvements

Potential Items:

  • Search configuration flags (SEARCH_ENABLED)
  • Configurable title extraction length
  • Enhanced search term highlighting
  • Performance monitoring setup
  • Documentation updates

v1.2.0 "Categories"

Timeline: Q1 2026 Focus: Organization and discovery

Planned Features:

  • Tag/Category System
    • Database schema for tags
    • Tag-based filtering
    • Tag clouds
    • Category RSS feeds
  • Hierarchical Slugs
    • Support for / in slugs
    • Directory-like organization
    • Breadcrumb navigation
  • Draft Management
    • Explicit draft status
    • Draft preview
    • Scheduled publishing
  • Search Enhancements
    • Tag search
    • Date range filtering
    • Advanced query syntax

v1.3.0 "Connections"

Timeline: Q2 2026 Focus: IndieWeb social features

Planned Features:

  • Webmentions
    • Receive endpoint
    • Send on publish
    • Display received mentions
    • Moderation interface
  • IndieAuth Provider (optional)
    • Self-hosted IndieAuth server
    • Token endpoint
    • Client registration
  • Reply Contexts
    • In-reply-to support
    • Like/repost posts
    • Bookmark posts

v1.4.0 "Media"

Timeline: Q3 2026 Focus: Rich content support

Planned Features:

  • Media Uploads
    • Image upload via Micropub
    • File management interface
    • Thumbnail generation
    • CDN integration (optional)
  • Photo Posts
    • Instagram-like photo notes
    • Gallery views
    • EXIF data preservation
  • Video/Audio Support
    • Embed support
    • Podcast RSS (optional)

v2.0.0 "MultiUser"

Timeline: 2027 Focus: Multi-author support (BREAKING CHANGES)

Major Features:

  • User Management
    • Multiple authors
    • Role-based permissions
    • User profiles
  • Content Attribution
    • Per-note authorship
    • Author pages
    • Author RSS feeds
  • Collaborative Features
    • Draft sharing
    • Editorial workflow
    • Comment system

Design Principles

All future development will maintain these core principles:

  1. Simplicity First: Every feature must justify its complexity
  2. IndieWeb Standards: Full compliance with specifications
  3. Progressive Enhancement: Core functionality works without JavaScript
  4. Data Portability: User data remains exportable and portable
  5. Backwards Compatibility: Minor versions preserve compatibility

Feature Request Process

To propose new features:

  1. Check Alignment

    • Does it align with IndieWeb principles?
    • Does it solve a real user problem?
    • Can it be implemented simply?
  2. Document Proposal

    • Create issue or discussion
    • Describe use case clearly
    • Consider implementation complexity
  3. Architectural Review

    • Impact on existing features
    • Database schema changes
    • API compatibility
  4. Priority Assessment

    • User value vs. complexity
    • Maintenance burden
    • Dependencies on other features

Deferred Features

These features have been considered but deferred indefinitely:

  • Static Site Generation: Conflicts with dynamic Micropub
  • Multi-language UI: Low priority for single-user system
  • Advanced Analytics: Privacy concerns, use external tools
  • Comments System: Use Webmentions instead
  • WYSIWYG Editor: Markdown is sufficient
  • Mobile App: Web interface is mobile-friendly

Support Lifecycle

Version Support

  • Current Release (v1.1.0): Full support
  • Previous Minor (v1.0.x): Security fixes only
  • Older Versions: Community support only

Compatibility Promise

  • Database: Migrations always provided
  • API: Micropub/IndieAuth remain stable
  • Configuration: Changes documented in upgrade guides

Contributing

StarPunk welcomes contributions that align with its philosophy:

Code Contributions

  • Follow existing patterns
  • Include tests
  • Document changes
  • Keep it simple

Documentation

  • User guides
  • API documentation
  • Deployment guides
  • Migration guides

Testing

  • Bug reports with reproduction steps
  • Compatibility testing
  • Performance testing
  • Security testing

Technology Evolution

Near-term Considerations

  • Python 3.12+ adoption
  • SQLite WAL mode
  • HTTP/2 support
  • Container optimizations

Long-term Possibilities

  • Alternative database backends (PostgreSQL)
  • Federation protocols (ActivityPub)
  • Real-time features (WebSockets)
  • AI-assisted writing (local models)

Success Metrics

StarPunk success is measured by:

  • Simplicity: Lines of code remain minimal
  • Reliability: Uptime and stability
  • Standards Compliance: Passing validators
  • User Satisfaction: Feature completeness
  • Performance: Response times <300ms

Philosophy

"Every line of code must justify its existence. When in doubt, leave it out."

This philosophy guides all development decisions. StarPunk aims to be the simplest possible IndieWeb CMS that works correctly, not the most feature-rich.


Document Created: 2025-11-25 Last Updated: 2025-11-25 Status: Living Document

For the latest updates, see: