Consistent, scalable UI system
Built with Tailwind CSS and a component kit approach (shadcn/ui-style primitives) to keep spacing/typography/interaction patterns consistent across the product.
Portfolio case study
Lawbee
Developed with zero AI assistance
Built Lawbee to allow issues focused NGOs regularly track legislation around core fundraising issues in minutes.
Captures from the live product at www.lawbee.org: marketing home, login, on-page search with the term "industry", and the /mybills view in desktop and mobile widths (anonymous session—shows sign-in if not logged in).
www.lawbee.org - home (desktop)
1/8
Project Snapshot
Role: Product Designer & Developer
Project Type: Client-facing web platform
Primary Goal: Build trust and generate qualified inquiries
Focus Areas: UX, content architecture, performance, SEO
What I Built
- Built a legislation tracking product aimed at issue-focused NGOs to monitor bills tied to fundraising and advocacy priorities.
- Implemented a responsive UI with reusable sections and consistent styling for fast iteration and maintainability.
- Structured content and UX flows to support discoverability, clarity, and quick scanning of legislative information.
Industry-Standard Practices
Secure authentication and per-user data access
Integrated Supabase authentication (OAuth + email/password) and enforced per-user access at the database layer using Supabase’s security model (RLS/policies) rather than trusting the client.
Server-side middleware for protected routes
Used middleware/route protection patterns to keep authenticated pages private and ensure sensitive user/session data is never exposed unintentionally.
Trusted legislative data source
Integrated the LegiScan API to ingest standardized legislative data used by NGOs across the U.S., with frequent refresh cadence (e.g. hourly updates) to keep bill status current.
Technical Decisions
Lean visual system with reusable sections
Why: Keeps the experience consistent across pages while making future edits quicker.
Tradeoff: Reduced one-off styling freedom in exchange for stronger maintainability.
Conversion-first page hierarchy
Why: Guides users from trust signals to service details and finally to contact actions.
Tradeoff: Reduced space for secondary details in exchange for faster scanning and clearer next steps.
SEO-aware content structure
Why: Supports organic discovery by aligning headings, copy, and page intent.
Tradeoff: Content structure needed stricter consistency, which required extra editorial discipline.
Results & Next Iteration
Current results are strongest in qualitative feedback and clearer user flow. Next, I would layer in direct measurement to quantify conversion and retention impact.
- Add analytics-backed conversion funnel tracking for inquiry and consultation events.
- Introduce a lightweight CMS workflow for faster non-technical content edits.
- Run targeted accessibility audits and improve contrast, focus states, and form affordances.