Skip to content

docs: add implementation TODO tracker and update to Next.js 15 #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 5, 2025

Conversation

nullcoder
Copy link
Owner

Summary

Added a comprehensive TODO tracker to guide the implementation process and updated all documentation to use Next.js 15.

Changes

  • Created docs/TODO.md with 9-phase implementation roadmap
  • Updated Next.js version from 14 to 15 in all documentation
  • Organized tasks by logical implementation order
  • Added checkboxes for progress tracking

Implementation Phases

  1. Project Setup - Initialize Next.js 15, configure tools
  2. Core Infrastructure - Types, config, utilities
  3. Encryption Implementation - Crypto, binary format, PIN auth
  4. UI Components - Layout, forms, display components
  5. API Development - Storage client, API routes
  6. Features Implementation - Core features, expiry, one-time view
  7. Testing - Unit, integration, E2E, performance
  8. Deployment - Cloudflare setup, CI/CD
  9. Documentation & Polish - User docs, developer docs

Test Plan

  • TODO items are clear and actionable
  • Phases follow logical dependency order
  • All specification requirements are covered
  • Next.js 15 references are consistent

🤖 Generated with Claude Code

nullcoder and others added 2 commits June 4, 2025 23:49
- Create comprehensive 9-phase implementation roadmap
- Update all references from Next.js 14 to Next.js 15
- Organize tasks by logical implementation phases
- Include testing, deployment, and documentation tasks
- Add stretch goals for future enhancements

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

Co-Authored-By: Claude <noreply@anthropic.com>
- Update SPEC.md to reflect Workers runtime and R2 bindings
- Update README.md with Wrangler setup and deployment instructions
- Enhance TODO.md with Workers-specific tasks and considerations
- Update CLAUDE.md with reminder to check official documentation

Key changes:
- Replace AWS SDK references with native R2 bindings
- Add Workers-specific limits (CPU time, request size)
- Update development setup to use wrangler.toml
- Add scheduled worker configuration for CRON jobs
- Clarify edge runtime requirements throughout

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

Co-Authored-By: Claude <noreply@anthropic.com>
@nullcoder nullcoder merged commit ebb300d into main Jun 5, 2025
@nullcoder nullcoder deleted the feat/add-todo-tracker branch June 5, 2025 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant