Lawsy

Lawsy turns a newsletter idea into a real publishing workflow. Readers can subscribe, browse published dispatches, open individual articles, and follow the RSS feed. Behind the scenes, an admin can create issues, write in Markdown, upload cover images, schedule articles, and trigger email delivery.

The problem

Newsletter projects often stop at a landing page plus an embedded form. That is not enough for a real editorial product. The editor needs content operations: drafts, issue numbers, scheduled publishing, image storage, subscriber status, unsubscribe sync, RSS, and a clean admin space.

What I built

• Public homepage with hero subscription form, current issue signal, and article feed
• Article archive with pagination, categories, read time, and cover images
• Individual article pages rendered from Markdown with SEO and Open Graph metadata
• Subscription flow with email capture, optional subscriber details, and a reactivation path for previously unsubscribed readers
• Admin dashboard with article list, mobile cards, desktop table, and preview/edit/delete actions
• Article editor with title, slug, excerpt, Markdown editor, cover image upload, issue number, category, and draft/publish/schedule modes
• Admin settings area for profile fields, password change, and session sign-out
• Supabase database schema for articles, subscribers, user profiles, roles, storage, and RLS policies
• Scheduled publishing and newsletter delivery through Brevo campaigns
• RSS feed served through a Supabase edge function

Design decisions

The visual identity deliberately avoids the conservative legal-tech default. Lawsy uses bold editorial typography, high-contrast surfaces, cyan/yellow accents, and issue-number language to make legal content feel current and energetic. The public experience is reader-first: subscribe quickly, see the latest issue, then move into a clean archive. The admin experience is denser and more operational, with tables, forms, and publishing metadata placed where an editor would expect them.

Under the hood

The frontend is a React application built with TanStack Router/Start and Vite. Supabase provides auth, Postgres, RLS, storage, and scheduled jobs. Brevo handles mailing list contact sync, campaign creation, and unsubscribe feedback through webhook events.

Why it matters

This project signals:

• Building a real publishing product, not just a static newsletter landing page
• Understanding admin workflows, editorial metadata, and reader-facing content UX
• Connecting frontend, database, auth, storage, scheduled jobs, RSS, and email delivery into one coherent system
• Giving a niche brand a sharper visual identity without losing usability

Final positioning line

A full-stack legal newsletter platform with a bold editorial frontend, a custom admin CMS, scheduled publishing, RSS, subscriber management, and Brevo-powered email delivery.