Page Route Stubs for All Public Pages

[calebyhan]

Motivation

Creating all route stubs upfront means every nav link resolves without 404s, and devs can pick up any page to build out independently. This also documents the full site map in code.

Deliverables

• Create Next.js app router pages for every public route:
  • / (home)
  • /news and /news/[id]
  • /senators/leadership
  • /senators/roster
  • /senators/contact
  • /senators/previous-leadership
  • /committees and /committees/[id]
  • /legislation (search)
  • /legislation/[id]
  • /legislation/recent
  • /legislation/nominations
  • /legislation/rules
  • /legislation/disclosure
  • /about/staff
  • /about/powers
  • /about/bill-process
  • /elections
  • /meetings
  • /funding/apply
  • /funding/budget-process
  • /funding/budget
• Each page should render a heading (<h1>) with the page name and a placeholder paragraph describing what will go there
• Create /admin stub page with "Admin Dashboard" message

Important Notes

• Depends on Shadcn Setup + Global Layout Shell + Navbar #7 (still create all the files, but may be broken until layout file is merged in)
• Use Next.js App Router file conventions (page.tsx in each route directory)
• Static content pages (Powers, Bill Process, Disclosure, Elections, How to Apply, Budget Process, Rules) will eventually fetch from the StaticPageContent API — for now just use placeholder text
• Do NOT build any page UI beyond the heading and placeholder — other tickets handle that