Layout and UI

Goal

This snapshot advances Cobblecart Market by teaching you to build a shared Tailwind layout and product card shell.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Ruby 3.2+, Bundler, Node.js 20+, and Docker for Postgres stages.

Port 3010 must be free. Copy .env.example before database stages.

• Ruby and Bundler
• Node.js and npm
• Docker from part 4 onward

Concepts

One layout owns navigation, flash banners, and the cart badge.

Turbo keeps interactive UI on the server; Tailwind styles the storefront; Active Record owns persistence and authorization checks.

Walkthrough

Compose the storefront chrome with sample product cards before persistence exists.

Read the example, then open the matching snapshot. The repository includes validation, CSRF, and the surrounding structure.

<%= render "shared/product_card", product: sample %>

Run and verify

Enter 03-Layout-And-UI, bundle install, copy .env.example, migrate, seed, and boot Puma on port 3010.

Open http://127.0.0.1:3010. From data lessons onward, Ada and Grace use password123.

git clone https://github.com/michaeldunga1/fcc-rails-ecommerce.git
cd fcc-rails-ecommerce/03-Layout-And-UI
bundle install
npm install
cp .env.example .env
bin/rails db:prepare
bin/rails server -b 0.0.0.0 -p 3010

Troubleshooting

Missing Tailwind classes after edits usually mean assets were not rebuilt.

For database failures, confirm Docker and the cobble_NN name. Never commit .env, vendor/bundle, or node_modules.

• Read the first exception first
• Rebuild assets after Tailwind class changes
• Never commit secrets

Try this

Add an empty-state message when the sample product list is empty.

Test a happy path and one invalid or unauthorized request.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works