From 801c6a6bdb7a5a418382850f864162cbbd96a343 Mon Sep 17 00:00:00 2001 From: culpen0 Date: Sat, 7 Feb 2026 17:25:25 -0500 Subject: [PATCH 1/2] Add initial README from plan --- README.md | 76 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..47c09bd --- /dev/null +++ b/README.md @@ -0,0 +1,76 @@ +# Polymer + +Polymer is the ongoing digital rebuild of **The Polytechnic** web presence. +This repository currently contains the early alpha frontend and deployment automation. + +## Current Status + +- Phase: early alpha +- Focus: landing/header experience, branding, and launch messaging +- Target launch window: **March 2026** + +## Project Plan + +### Phase 1: Foundation and Alpha Experience (in progress) + +- Set up a Next.js frontend in `frontend/web` +- Build a responsive newspaper-style header/navigation +- Ship a temporary alpha overlay with rollout messaging +- Establish CI-driven deployment workflow + +### Phase 2: Core Content Experience (planned) + +- Replace placeholder homepage body with real content modules +- Implement section pages (News, Features, Opinion, Sports, etc.) +- Add search and archive browsing paths + +### Phase 3: Editorial and Platform Readiness (planned) + +- Add content publishing/editorial workflows +- Improve accessibility, performance, and SEO +- Finalize analytics/observability and release hardening + +## Repository Structure + +```text +. +|-- docs/ # Mockups and design artifacts +|-- frontend/web/ # Next.js web application +|-- .github/workflows/ # Deployment workflow(s) +|-- package.json # Root package metadata +|-- pnpm-workspace.yaml # Workspace config +``` + +## Tech Stack + +- Next.js (App Router) +- React +- TypeScript +- Tailwind CSS v4 +- pnpm + +## Local Development + +### Prerequisites + +- Node.js 20+ +- pnpm 10+ + +### Run the frontend + +```bash +cd frontend/web +pnpm install +pnpm dev +``` + +Then open [http://localhost:3000](http://localhost:3000). + +## Deployment + +Production deploys run via GitHub Actions (`.github/workflows/deploy.yml`) on pushes to `main`. +The workflow syncs the repo to `/var/www/polymer/`, builds `frontend/web`, and restarts the `polymer` PM2 process. + +## License + +MIT (see `LICENSE`). From 2ff75db7e4d6c31cc007953549d031633159ffa4 Mon Sep 17 00:00:00 2001 From: culpen0 Date: Sun, 22 Feb 2026 13:13:55 -0500 Subject: [PATCH 2/2] docs: update project plan and status with a detailed overview, goals, and milestones. --- README.md | 83 ++++++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 64 insertions(+), 19 deletions(-) diff --git a/README.md b/README.md index f542c44..ec8b442 100644 --- a/README.md +++ b/README.md @@ -1,34 +1,79 @@ # Polymer Polymer is the ongoing digital rebuild of **The Polytechnic** web presence. -This repository currently contains the alpha web app, Payload CMS integration, and deployment automation. -## Current Status +## Overview -- Phase: early alpha -- Focus: frontend experience, content modeling, and editorial platform readiness -- Target launch window: **March 2026** +A technical and stylistic revamp of RPI’s Newspaper, The Polytechnic, improving the webpage’s UX/UI and SEO. -## Project Plan +## Goals -### Phase 1: Foundation and Alpha Experience (in progress) +### Frontend -- Set up a unified Next.js + Payload CMS application -- Build a responsive newspaper-style frontend experience -- Establish initial collections and migration baseline -- Establish CI-driven deployment workflow +Rebuild the frontend from scratch using React ([Next.js](https://nextjs.org/)). -### Phase 2: Core Content Experience (planned) +**General Poly Landing Page/Sections:** -- Replace placeholder front page modules with real content data -- Implement section pages (News, Features, Opinion, Sports, etc.) -- Add search and archive browsing paths +- Design landing page structure (take note from [The Harvard Crimson](https://www.thecrimson.com/); fix obsolete newsletter subscription; take note from [Stanford Daily's email digests](https://stanforddaily.com/email-digests/)). +- Add Date & Volume. +- Top News gets a dedicated section (like [Stanford Daily](https://stanforddaily.com/)), as do Opinion and Sports. +- Improve section structures to include a featured/top article for each section. +- Add a "Most Read" / "Opinions Choice" section. +- Add access to visual copies of past papers (either [link to archive](https://chicagomaroon.com/archive/) or have a [print issues section](https://dailybruin.com/category/print)). +- Add a "by | date" format next to articles (like [Chicago Maroon](https://chicagomaroon.com/) or [Stanford Daily](https://stanforddaily.com/category/opinions/)). -### Phase 3: Editorial and Platform Readiness (planned) +**Opinions Section:** -- Add content publishing/editorial workflows -- Improve accessibility, performance, and SEO -- Finalize analytics/observability and release hardening +- Add a drop-down menu on hover (Editorial, Columns, Op-Ed, Letter to the Editor) - similar to [Daily Princetonian](https://www.dailyprincetonian.com/). +- Include pictures/graphics with opinion pieces to elevate the section (standard for collegiate newspapers). +- Opinions section will have an ["Opinion's Choice"](https://www.thecrimson.com/section/opinion/) highlighted section. +- Dedicated section for Columns! + +### Backend & Analytics + +- **CMS:** [Payload CMS](https://payloadcms.com/) +- **Diagnostics/Analytics:** Implement an analytics tool to measure website traffic. +- **Migration:** Database copy and migration from the old Poly website backend. +- **Deployment:** Deploy the new site on our RPI server (with VMware). + +## Milestones + +### Done on February 15th - Visual Mockup + +- Receive formal and cohesive opinions from the Polytechnic Executive Board regarding complaints and suggestions for improvements. +- Visualize and finalize a new web design and a list of features/improvements that we’d like to instill on our new website (using Figma or whiteboards). + +### Done on February 23 - Backend + +- Picking and finalizing which backend we’re using (likely Payload, but doing more research is part of this phase). +- Locally test the backend, and plan how it will interface with our Frontend site. +- Test the migration of articles and photos from our old website to our new one, or choose to keep the old one running. + +### Done on March 28 - Frontend + +- Building the Frontend and implementing all of the previous design choices that were agreed on. +- Address General Poly Landing Page Issues: + - Our landing pages newsletter subscription is obsolete. + - No structure to our landing page. + - Date & Volume. + - Top News gets a section and so does Opinion, Sports. +- Address Section structures: + - Add a featured/top for each section. + - Add a Most Read/ Opinions Choice. + - Access to visual copies of past papers. + - Add a by | date next to our articles. +- Address Opinions page: + - Would like a drop down menu when you hover over opinions. + - Drop down includes editorial, columns, op-ed, letter to the editor. + - Pictures/graphics with opinion pieces will elevate the section. + - Opinions section will have an “Opinion’s Choice”. + - Columns! + +### April 15th - Deployment and Feedback + +- Deploy the site to our RPI vmware server. +- Migrate the old database to the new website. +- Implement an analytics tool to measure website traffic. ## Repository Structure