Document project plan and setup in README

[cp89cyber]

Summary

• Add an initial README covering project mission, current alpha focus, planned phases, repo structure, tech stack, and deployment process
• Outline local development prerequisites and commands so contributors can run the frontend locally
• Fixes #<ISSUE_NUMBER>

Testing

• Not run
  fixes issue Add initial README based on project plan #2

[RonanHevenor]

This needs to better reflect the following:

Overview
A technical and stylistic revamp of RPI’s Newspaper, The Polytechnic, improving the webpage’s UX/UI and SEO.

Goals
Rebuild the frontend from scratch
React (Next.js)
General Poly Landing Page/Sections
Design landing page structure
Section structures
Add a featured/top for each section
Add a Most Read/ Opinions Choice
Can we get access to visual copies of past papers?
Can either do a link to archive(The Chicago Maroon) or have a print issues section (The Daily Bruin)
Add a by | date next to our articles (chicago, stanford)
Opinions
Opinions section will have a “Opinion’s Choice”
See The Harvard Crimson
Columns!
Backend
Payload CMS
https://payloadcms.com/
Analytics
Deploy the new site on our RPI server (with vmware).
Database copy and migration from the old poly website backend.

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
General Poly Landing Page Issues
Our landing pages newsletter subscription is obsolete
Take note from The Stanford Daily
No structure to our landing page
Take note from the Harvard Crimson
Date & Volume
Top News gets a section (Stanford) and so does Opinion, Sports
Our Section structures are lazy
Add a featured/top for each section
Add a Most Read/ Opinions Choice
Access to visual copies of past papers
Can either do a link to archive (The Chicago Maroon) or have a print issues section (The Daily Bruin)
Add a by | date next to our articles (chicago, stanford)
Opinions
Would like a drop down menu when you hover over opinions (The Princetonian)
Drop down includes editorial, columns, op-ed, letter to the editor
Pictures/graphics with opinion pieces will elevate the section (every collegiate newspaper)
Opinions section will have a “Opinion’s Choice”
See The Harvard Crimson
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.