Layout and UI

Goal

This snapshot advances Meridian Notes by teaching you to build a shared responsive interface with Tailwind CSS.

Every numbered folder is a complete application. Run this stage on its own, then compare it with the previous snapshot to isolate the new responsibility.

Prerequisites

Use Node.js 20 or newer, npm, and a terminal. You should be comfortable with JavaScript functions, objects, modules, and basic HTML forms.

The development server uses port 3000. Data-backed snapshots use PostgreSQL on host port 5433 and keep their data in a database unique to that folder.

• Node.js and npm installed
• A code editor and terminal
• Docker from part 4 onward

Concepts

Layouts persist around child routes. Tailwind utility classes make spacing, type, color, and responsive states explicit without a page-specific stylesheet.

Keep the server boundary visible: Server Components may read trusted data directly, while Server Actions and route handlers must validate all incoming values and re-check authorization.

Walkthrough

Create the Meridian Notes shell, reusable card treatment, sample note list, readable form controls, and consistent focus and hover states.

Trace the example from request to rendered result, then inspect the matching snapshot for its surrounding types, validation, error handling, and configuration.

<article className="rounded-xl border border-slate-700 p-6">
  <h2>{note.title}</h2>
</article>

Run and verify

Enter 03-Layout-And-UI, install its dependencies, and copy .env.example when the snapshot includes one.

Open http://localhost:3000. Keep the terminal visible so framework, Prisma, and authentication errors can be matched to the browser action that caused them.

git clone https://github.com/michaeldunga1/fcc-nextjs-blog.git
cd fcc-nextjs-blog/03-Layout-And-UI
npm install
npm run dev

Troubleshooting

If styles are missing, verify the Tailwind content glob includes every App Router file and that the global stylesheet is imported only by the root layout.

A missing-module error usually means npm ran in another snapshot. Database errors often mean Docker is stopped, the environment file is missing, or this folder points at the wrong numbered database.

• Read the first error first
• Restart after environment changes
• Never commit .env or node_modules

Try this

Add an empty-state card and test the layout at a narrow viewport.

Test one expected path and one invalid or unauthorized path. A production-minded app gives useful feedback without exposing secrets or stack traces.

• Make one focused change
• Verify it in the browser
• Continue only after this snapshot works