Skip to content

docs: add future-work doc for the next team - #226

Merged
kevinrutledge merged 2 commits into
developfrom
docs/future-work
Jun 5, 2026
Merged

docs: add future-work doc for the next team#226
kevinrutledge merged 2 commits into
developfrom
docs/future-work

Conversation

@kevinrutledge

@kevinrutledge kevinrutledge commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Developer

Kevin Rutledge

What changed?

The deferred items from the launch were scattered across code comments, env-var notes, and nowhere at all, so a next-year student had no single place to find them. This adds docs/future-work.md, one doc that lists each deferred item with what triggers it and where to start, and links it from the docs index.

  • docs/future-work.md - new doc covering e2e coverage, responsive/mobile, SMS enablement, the TanStack Table v9 lint suppression, Tailwind v4, the dependency deprecation warnings, the stale Dependabot alerts, and the MariaDB 5.5 production constraints
  • docs/README.md - adds the Future Work link to the index

How to test

  1. Open docs/README.md and confirm the Future Work link resolves.
  2. Read docs/future-work.md and confirm each item names its trigger and a starting file or version.

Checklist

  • Code works and is readable
  • Tested locally
  • Commits follow conventional commits
  • Assigned reviewers

@kevinrutledge
kevinrutledge merged commit c46c74b into develop Jun 5, 2026
2 checks passed
@kevinrutledge
kevinrutledge deleted the docs/future-work branch June 10, 2026 03: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