ISSUE-009 — Build Remaining Templates (School, SaaS, Blog) & Vite Arch

[ISONIC0788]

What to build

Our documentation specifies 5 total templates and 3 architectures. We currently only have Portfolio and E-Commerce in Next.js.

We need to build out the base structure for the School Management, SaaS Dashboard, and Blog / Magazine templates. Furthermore, we need to create the Vite + React 18 SPA architectural alternative for the SaaS Dashboard, demonstrating how Opusify generates a purely client-side React app.

Files to create

• templates/school/nextjs-monolith/...
• templates/saas/nextjs-monolith/...
• templates/blog/nextjs-monolith/...
• templates/saas/vite-react/...

Specs

• School Management: Needs a role-based dashboard layout (Admin vs Student).
• SaaS Dashboard: Needs a data-heavy analytics layout (Charts placeholder).
• Blog: Needs an MDX content-first layout.
• Vite Architecture: Must use react-router-dom instead of Next.js App Router, with a standard src/App.tsx entry point.

Acceptance criteria

• Create the package.json for all three new templates using Handlebars {{projectName}}.
• Build the Next.js App Router structure for school, saas, and blog following the established patterns in ISSUE-005.
• Build the Vite + React 18 structure for saas/vite-react, ensuring react-router-dom is configured in src/App.tsx based on the {{navCount}} parameter.
• Ensure all new templates respond to the {{includeSidebar}} CLI parameter by conditionally rendering a Sidebar.tsx component.
• Test by running node index.js, selecting "SaaS Dashboard" and "Vite + React 18", and ensuring npm run dev boots a Vite server successfully.

Dependencies

• None, can be worked on in parallel with ISSUE-008.