Skip to content
rayssarrsilvaPublic

About

Marketplace for Brazilian makers · Next.js, TypeScript, Stripe, Postgres · PageSpeed 100 · A+ security · 337 tests · full QA cycle · PT/EN

Resources

Security policy

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

100 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🏺 Moringa

An online fair for people who make things by hand in Brazil.

Open the live site · English · Português

CI CodeQL Mozilla Observatory: A+ Security headers: A+ License: MIT

Moringa home page: the headline 'Handmade in Brazil, with the story of who made it', a search field, region filters and the week's new pieces.

Why "Moringa"?

A moringa is the handmade clay jar that keeps water cool. In many Brazilian homes, it is where the glass of water offered to every guest comes from. This project carries the same idea: welcome people, and make room for the hands behind each piece.

What it is

A marketplace with two sides, each with its own panel:

  • Buyers find pieces by region, material and price, read the story of who made them, save favorites, pay through Stripe (test mode, card or Pix), follow every step of the order and review what arrived.
  • Makers open a shop with their story, list pieces in a guided form, edit or pause them, see their sales and ship orders. When they add a tracking code, the buyer sees it right away.

Everything works in Portuguese and English, in a light and a dark theme, on a phone or a desktop, with a keyboard or a screen reader.

Built with the Ipê Design System, also mine.

Try it

No sign-up: each demo account is one click, and what you do stays in your browser for 7 days.

Who Where What to try
Marina, buyer /en/conta Orders in every state, the live timeline, "I got my order", reviews
Dona Lúcia, ceramist /en/loja Sales chart (with a table view), ship an order with a tracking code, edit or pause a piece
A new maker /en/loja Open a shop from zero and publish the first piece
Anyone /en/pecas Filter, add to the bag, pay with the test card 4242 4242 4242 4242, any future date and CVC

Quality at a glance

Measured on the live site and on every pull request. Last checked on October 22, 2026.

Area Result How it is checked
Performance Lighthouse 90–100 on mobile (slow 4G simulated) Lighthouse CI, 4 pages × 3 runs, on every PR
Accessibility Lighthouse 100 · 0 axe violations · WCAG 2.2 AA axe on every page in both themes, plus keyboard and focus tests in Playwright; screen reader pass in the QA cycle
SEO Lighthouse 100 hreflang, canonical, Open Graph images, sitemap, Product and Review JSON-LD
Security headers Mozilla Observatory A+ (135/100, 12/12 tests) · securityheaders.com A+ Third-party scanners on the live site
Vulnerability scan OWASP ZAP baseline: 0 high · 0 medium · 0 low ZAP plan on every PR
Code and dependencies CodeQL security-extended · npm audit: 0 vulnerabilities CodeQL, Dependabot
Tests 179 unit and integration · 158 end-to-end (mobile and desktop) · QA cycle Vitest, PGlite (real Postgres), Playwright

Screenshots

Piece page: clay jar with price, stock, shipping, the maker's story and reviews.
Piece page, with the maker's story
Order timeline: paid, preparing, shipped with a tracking code, and delivered still to come.
Order timeline, updated live
Maker panel in the dark theme: orders to ship, sales in 30 days and a weekly revenue chart.
Maker panel, dark theme
Maker orders board in the dark theme, grouped by status.
Orders to ship
Catalog on a phone: filters and a grid of pieces.
Catalog on a phone
Checkout on a phone: name, email and address filled from the CEP.
Checkout on a phone

Discovery

Design

Stack

Layer Tools
App Next.js 16 (App Router, Server Components, Server Actions) · React 19 · TypeScript (strict)
UI Ipê Design System 2.0 · Tailwind CSS 4 · next-intl (pt-BR, en)
Data Postgres on Neon · Drizzle ORM with versioned migrations · TanStack Query · Zustand
Forms React Hook Form · Zod (one schema in the browser and on the server)
Auth and payments Auth.js v5 (JWT) · Stripe Checkout in test mode (card and Pix) with a signed webhook
Quality Vitest · Testing Library · PGlite · Playwright · axe · Lighthouse CI · OWASP ZAP · CodeQL
Delivery GitHub Actions · Dependabot · Vercel

Run it locally

Requires Node.js 22 (see .nvmrc).

npm install
cp .env.example .env.local   # then fill in DATABASE_URL from Neon
npm run db:migrate           # create or update the tables
npm run db:seed              # add the demo makers and pieces
npm run dev                  # http://localhost:3000
Command What it does
npm test Unit and component tests (Vitest + Testing Library)
npm run test:e2e End-to-end and axe accessibility tests in Chromium, mobile and desktop (Playwright)
npm run lint ESLint with zero warnings allowed
npm run typecheck TypeScript in strict mode
npm run build Production build

Without a database

Skip the DATABASE_URL and the app runs on the built-in sample catalog. CI uses this mode, so tests never depend on a live database.

Catalog API

GET /api/pieces takes the same params as the catalog page, for example /api/pieces?regiao=nordeste&material=palha&preco_max=150&ordem=menor-preco. GET /api/pieces/{slug} returns one piece, or a JSON 404.

Demo account

The buyer area at /pt/conta has a one-click demo login as Marina, with orders in every state (paid, shipped with a tracking code, delivered). There are no passwords: a demo login only sees demo data. On Vercel, set AUTH_SECRET (run npx auth secret to generate one).

Database migrations

The schema lives in src/db/schema.ts. After changing it, run npm run db:generate and commit the new file in drizzle/. CI fails if the schema and the migrations disagree (npm run db:check).

Every Vercel build runs npm run db:migrate before next build, so the database always matches the code being deployed. Migrations are additive (add first, remove in a later release), so the live site keeps working during a deploy. The first databases were created with db:push; the migrate script detects that and records the baseline instead of recreating tables.

Tests

  • npm test runs unit, component and database integration tests. The integration tests start a real Postgres in memory with PGlite, create the schema from src/db/schema.ts and run the same Drizzle queries the app sends to Neon.
  • npm run test:e2e runs Playwright on mobile and desktop, with axe accessibility checks in both themes.
  • npm run lhci builds the site and runs Lighthouse CI three times on four pages (home, catalog, piece, shop in English). The pull request fails below these scores (latest results in Quality at a glance):
Performance Accessibility Best practices SEO
≥ 90 100 ≥ 95 100

Payments (Stripe test mode)

Without STRIPE_SECRET_KEY, checkout runs as a demo and goes straight to the confirmation page. To try the real flow:

  1. Create a Stripe account, stay in test mode, and copy the secret key (sk_test_…) into .env.local. Live keys are refused on purpose.
  2. In Dashboard → Settings → Payment methods, turn on Cards and Pix.
  3. Run stripe listen --forward-to localhost:3000/api/stripe/webhook and copy the whsec_… secret into STRIPE_WEBHOOK_SECRET.
  4. Pay with the test card 4242 4242 4242 4242, any future date and any CVC. Use 4000 0000 0000 0002 to see a declined card.

Each maker gets their own order. Orders start as pending and the webhook moves them to paid (card right away, Pix when the bank confirms) or canceled (Pix expired), following the order lifecycle in FigJam.

Workflow

  • Every change goes through a branch and a pull request. CI runs lint, types, unit tests, build, E2E, Lighthouse, the ZAP scan, npm audit and CodeQL on each one.
  • Commit messages follow Conventional Commits and are checked by commitlint.
  • Work is planned on the project board in one-week sprints.

Quality assurance

A full QA cycle ran before release: a test plan based on ISO/IEC/IEEE 29119-3, 58 test cases traced to the user stories, 8 exploratory sessions, bug reports and a summary against the exit criteria.

The exploratory sessions found BUG-001 (severity High): after a maker edited a price, a bag opened earlier still showed the old price on the pay button. It is fixed in two layers, the bag updates itself and the server refuses to charge a price the buyer did not see, and four regression tests keep it from coming back.

The pipeline is built to stay fast as the suite grows: one production build shared by the E2E, Lighthouse and ZAP jobs, caches for the Next.js build and the Playwright browser, and the E2E suite split into two shards that run at the same time and merge into one report.

Security

Built against the OWASP Top 10 and ASVS level 2. The threat model lists each risk, what stops it and where in the code.

  • Content Security Policy with a fresh nonce on every request. Only this response's scripts run: no inline script, no eval, no other origins, no framing.
  • HSTS (preload), nosniff, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy on every page, API route and file.
  • Rate limits on sign-in, checkout, guest order tracking and every write, stored in Postgres so they hold across serverless instances. The client is a salted hash of the IP, never the IP itself.
  • Origin checks on every POST route, on top of SameSite cookies and the built-in check of Server Actions.
  • Server-side rules: prices re-calculated, ownership checked in every query, one order state machine, signed and idempotent Stripe webhook.
  • Supply chain: CodeQL, Dependabot, npm audit gate, GitHub Actions pinned by commit, read-only workflow token.
  • Found a problem? See SECURITY.md or /.well-known/security.txt.
Check Result
Mozilla HTTP Observatory, live site A+ · 135/100 · 12 of 12 tests passed
securityheaders.com, live site A+
OWASP ZAP baseline scan, every pull request 0 high · 0 medium · 0 low
npm audit (production dependencies) 0 vulnerabilities
CSP violations in the browser (Playwright) 0

Author

Made with care by Rayssa Roberta · LinkedIn · Portfolio

License

MIT

About

Marketplace for Brazilian makers · Next.js, TypeScript, Stripe, Postgres · PageSpeed 100 · A+ security · 337 tests · full QA cycle · PT/EN

Resources

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages