Skip to content

Streamline repository structure and docs - #79

Open
parker-boom wants to merge 13 commits into
mainfrom
repo-streamline-cleanup
Open

Streamline repository structure and docs#79
parker-boom wants to merge 13 commits into
mainfrom
repo-streamline-cleanup

Conversation

@parker-boom

Copy link
Copy Markdown
Collaborator

Summary

This PR streamlines the Poly Pages repo without intentionally changing product behavior. The main goal is to make the project easier to understand, run, and maintain by removing stale artifacts, organizing files around the real app structure, and tightening docs/checks.

Documentation

  • Reworked the root README so new contributors can quickly understand what Poly Pages is, how it works, and how to run it.
  • Consolidated scattered/stale docs into focused docs for architecture, product goals, brand, code style, testing, and Supabase setup.
  • Added testing notes for the local-only upload bypass so developers can test uploads without treating it like a production auth path.

Organization

  • Removed old generated design exports, stale patch files, unused public assets, duplicate docs, and other repo clutter.
  • Moved brand/landing assets into clearer asset folders.
  • Split the large global CSS file into smaller style files for theme tokens, motion utilities, and shared enrollment picker styles.
  • Canonicalized app routes so course pages live under /course/[classId] and the profile lives under /profile, while keeping redirects for older paths.

Refactoring

  • Moved generated catalog data out of TypeScript files and into JSON data files with a small helper layer.
  • Updated catalog seed scripts to read the new data shape and use the correct catalog-year conflict key.
  • Cleaned up upload preview generation to use an in-memory buffer instead of relying on temporary rendered image paths.
  • Removed dev/debug surfaces that were not worth keeping as normal app routes.

Tooling

  • Simplified root scripts so gitcheck runs lint and tests directly.
  • Updated CI to install frontend dependencies before running checks.
  • Updated a few frontend dependencies and pinned the PostCSS override needed by the current stack.

@vercel

vercel Bot commented Jun 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
note-sharer Ready Ready Preview, Comment Jun 5, 2026 2:54am

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