Trevor Provencio
Build sheet · web work pulled from GitHub on Nov 17, 2026
Ten repositories · two full-stack Next.js products · eight sites and prototypes

Ten web builds, one page.

Everything on my GitHub as of November 17, 2026. Two full-stack Next.js products with their own databases, workers and payment integrations, four production sites that each ship through their own deploy pipeline, three design-led static builds, and one research prototype. Each entry lists what it runs on, where it is hosted, and the reasoning behind how it was built.

10repositories
2Next.js 16 applications
~65klines of TypeScript across the two apps
6hosting setups in production
4GitHub Actions pipelines
9live URLs

Frameworks

Next.js 16React 19Astro 7Vite 6Medusa 2.22Mercur 2.4Tailwind 3 / 4Motion

Data

PostgreSQL 18Drizzle ORMRow-level securitySQLite + FTSS3Cache tags / ISR

Hosting

RenderVercelMedusa CloudHostingerGitHub PagesWordPress on cPanel

Delivery

GitHub ActionsRender BlueprintsTurborepoYarn 4Headless Chrome prerenderlftp over FTPSSentry

Payments and services

CardPointe (Fiserv)SquareTaxJarEasyPostTwilioSendGridClaude APIGoogle / Apple sign-in

Languages

TypeScriptPythonPHPSwiftSQLBash
How I work

The same habits show up in every repository.

These are patterns you can check in the code, not a philosophy statement. Each one names where to look.

Rules are written down before the code.

Home Tab's spec defines 29 numbered business rules (days and cycles, claims, payments, pause and cancel, dashboard math). Code comments cite the rule IDs. Every repository carries a README plus a CLAUDE.md with its conventions, open questions and dated decisions, so a new developer or an agent can pick it up cold.

hometab/docs/spec.md · placemade/CLAUDE.md (513 lines) · carlsbad-crossfit-site/CLAUDE.md

Deploys check themselves.

Every pipeline ends by fetching the live page and looking for something specific: the headline on the landing page, the route table on the gym site, every JS asset the shell references. Render runs migrations as a pre-deploy step and health-checks the database before traffic arrives.

deploy-hostinger.yml · deploy.yml · render.yaml

Card data never touches a server I run.

Both products use CardPointe's hosted iframe tokenizer, so only tokens, card brand and last four reach the app. Santosha sells through Square payment links with no cart. Per-shop gateway credentials are designed to be stored encrypted with the key outside the database.

hometab/docs/cardpointe.md · placemade cardpointe module · santosha square-links.js

Isolation is enforced by the database.

Home Tab's tables carry a forced row-level security policy keyed on a transaction-local setting. Composite foreign keys stop one shop's row from pointing at another's. A test builds a throwaway database as an ordinary role and proves two shops cannot read or write each other.

src/db/index.ts · 0002_force_rls.sql · src/db/isolation.test.ts

No invented claims, anywhere.

Content rules in the repos forbid made-up customers, testimonials, metrics and prices. The sample shop on the Home Tab landing page is labelled as made-up numbers. Placemade's copy may only state what the business can back, and consent wording is versioned and recorded with each opt-in.

home-tab-marketing/CLAUDE.md · placemade/src/lib/content

Performance is measured, then changed.

On the gym site, serving pre-rendered pages straight from Apache cut a plain page view from about 1.35 seconds to about 0.2, with the numbers and the rollback path recorded. Placemade caches by tag and lets the backend refresh pages on demand. Assets carry content hashes so updates never load stale files.

c2-static.htaccess · placemade /api/revalidate · hermosa build.py

Privacy by default.

Sentry is configured to send no personal data. The Hermosa statement reader redacts names, addresses and account numbers in the browser before anything leaves the device, and the ads pixel is skipped when a browser sends Global Privacy Control. Placemade's email endpoint answers identically whether or not an address is on the list.

read-statement.php · build.py META_PIXEL · placemade email-signup module

Accessible, with motion that can be turned off.

44px touch targets and 4.5:1 text contrast are written into the build rules. Every animation respects reduced motion, and the portfolio adds a visible Simple view switch that also goes black and white and stops autoplay. Home Tab's token test checks WCAG contrast on every build.

trevor-portfolio/src/lib/still.ts · hometab design-tokens.test.ts
Group 1

Full-stack products on Next.js

Real applications with a database, background work, authentication and money moving through them. Both are built on Next.js 16 with the App Router and React 19, and both are in staging or pre-launch with a dated plan to go live.

trevorprovencio-bit/hometabprivatelast commit Nov 17, 2026 · PR #20app.joinhometab.com

Home Tab

Staging · pilot shop planned Dec 21, 2026

Membership software for juice bars and other counter shops. Customers join a shop's monthly plan from a QR code on their own phone, then claim their daily drink on a locked-down counter iPad by typing their phone number. Billing runs through each shop's own CardPointe merchant account, so Home Tab never holds card data and members never download an app.

Home Tab counter iPad pairing screen with a pairing code field and a Pair button
The same pairing screen at phone width
The counter iPad's first screen: pair it to a shop with a one-time code from admin. Below: how the pieces fit.
Surfaces
/counteriPad kiosk, PWA, Guided Access
/join/[shop]phone sign-up from the QR code
/m/[link]private texted member link
/ownerrevenue, churn risk, breakage
/adminshop setup, pairing, ledger
App
Render web serviceNext.js 16, Node 22, Oregon
Route Handlerskiosk API that survives deploys
Server Actionsadmin, owner, pair, join forms
Render workerrenewals, heartbeat, SIGTERM-safe
Data
Render Postgres 18private network only
Forced row-level security13 tables keyed by shop_id
Drizzle migrations6 so far, run pre-deploy
Services
Sentryerrors, uptime on /api/health
CardPointehosted tokenizer, billing plans
Twilio A2P 10DLCbrand registered, campaign drafted

Runs on

Framework
Next.js 16.4, App Router, Cache Components, Turbopack · React 19 · TypeScript strict with generated route types · Node 22
Data
PostgreSQL 18 on Render · Drizzle ORM · node-postgres
Hosting
Render Blueprint: web service, worker, managed Postgres · app subdomain via CNAME
Deploy
Auto-deploy on push to main · migrations as the pre-deploy command · health check with a DB ping
Auth
Hand-rolled: scrypt passwords, HMAC-signed httpOnly cookies scoped per surface, hashed device and staff tokens
Styling
Tailwind CSS 4 + CSS variables generated from tokens.json · Geist · 15 hand-built components
Monitoring
Sentry across server, browser and worker, no personal data, uptime check every minute
Testing
Node's built-in test runner · about 146 tests in 12 files · pure functions for timeouts and member state

Why it is built this way

Tenant isolation lives in Postgres, not in app code. Every table except admins carries a shop_id and a row-level security policy that reads a transaction-local setting. The app can only open the database through three helpers: one shop, all shops, or none. Postgres skips RLS for a table's owner, so a dedicated migration forces it, and the app refuses to start in production as a superuser.

The iPad talks to Route Handlers, not Server Actions. A kiosk sits on one page for days. A Server Action ID minted before a deploy would stop working; stable POST URLs keep working. Each handler checks same-origin, requires the paired-device cookie, caps the body at 2 KB and returns no-store. Admin, owner and join forms still use Server Actions.

One claim per shop-local day stays correct under double taps and two iPads. The member row is locked, then the insert runs against a partial unique index that allows one live claim per member per day. "Today" is computed in the shop's own time zone. Every claim and undo lands in an audit log with the device or staff member as the actor.

Launch does not wait on a payment webhook. For the pilot, CardPointe billing plans run the recurring charges and the operator marks declines by hand in an admin ledger, which pauses the member and texts a card-update link. The weekly manual checklist becomes the spec for automating it later.

Render over Hostinger, on paid tiers on purpose. Hostinger has no Postgres and stops idle Node apps. Render's free tier cannot run pre-deploy commands and has no worker, so the smallest paid sizes were chosen and costed out: about $33 a month for the pilot.

Details worth noticing

  • iPad pairing uses a one-time code (three letters from the shop plus four digits, 15 minutes, shown once). Only its SHA-256 hash is stored. Wrong guesses are capped per iPad and overall.
  • Staff PINs are scrypt-hashed and unique within a shop. Lockout is counted on the device row, so clearing cookies does not reset it, and it doubles up to an hour.
  • Offline handling combines navigator.onLine with real request outcomes in a useSyncExternalStore store. A banner appears, claims are blocked, the typed number is kept, and the heartbeat clears it on recovery.
  • The claim chime is Web Audio with no sound file, primed by a silent buffer inside the first tap, because iOS only allows sound after a gesture.
  • Members keep the price and drink count they joined on. Savings lines are computed from the menu price and never typed in.
  • Seven member states (ready, claimed with undo, already claimed, out of drinks, paused for payment, no photo, cancelled with access until a date) come from pure functions the server also uses, so the screen and the rule cannot drift.
  • A phase-2 document lists every deferral with what it needs first: Wallet passes, offline claims, object storage, kitchen tickets on a Star printer.
13 tables · 9 enums · 11 pages · 11 route handlers · ~146 tests · ~13,200 lines of TypeScript · ~1,600 lines of product docs · sprint 3 of 6 finished early on Nov 18
trevorprovencio-bit/placemadeprivatelast commit Nov 15, 2026 · PR #97placemade.shop · staging.placemade.shop

Placemade

Live, pre-launch · pilot April 2027

A curated marketplace for vetted California makers of food and goods. Shoppers see one store, one bag and one checkout. Each maker ships its own box. Placemade is seller of record, collects the payment, and pays makers every two weeks from its own ledger. Everything is organised by place: region, then area, then the town on every product.

staging.placemade.shop
Placemade storefront home page with the headline Made in California, by people you can name
Placemade storefront at phone width
placemade.shop
Placemade founding makers sign-up page with the headline Your town is the label
Until launch the root domain serves the founding-makers sign-up. The full store runs on staging, marked noindex. Same deployment, switched by request host.
9custom Medusa modules
~55API routes
26workflows
19event subscribers
6hourly jobs
35backend spec files
Modules: cardpointe, taxjar, auth-apple, maker-application, email-signup, place, standard, shelf, payout-ledger.
Front ends
Storefront on VercelNext.js 16, three domains, one project
Maker portal /sellerVite + React, Mercur vendor UI, customised
Operator admin /dashboardApplications, Places, Standards, Payouts
Backend
Medusa Clouddeploys main, previews every PR
Medusa 2.22 + Mercur 2.4sellers, offers, order groups, commissions
Workflows with compensationmaker approval, shelf, badges
Data
PostgresMedusa Cloud
S3 file storagelocked to one folder
Cache tagsbackend calls /api/revalidate
Services
CardPointecustom payment provider
TaxJarcustom tax provider + reporting
EasyPostlabels, HMAC webhook
SendGridtransactional + list
Twilioopt-in texts
Google / Apple sign-in
Sentry
Delivery
GitHub Actionstypecheck + unit tests on every PR
Sample-branch syncdemo store always runs live code
Vercel skip-build scriptdiffs against the last deploy

Runs on

Storefront
Next.js 16.4, App Router, Cache Components with tags, standalone output · React 19 · Tailwind 3 over the design system's CSS · Medusa JS SDK called from server components only, never the browser
Backend
Medusa 2.22 + Mercur 2.4 · 9 custom modules · custom fields on Product · Jest + SWC
Panels
Maker portal and operator admin as Vite 6 + React 18 apps, bundled into the backend build and served at /seller and /dashboard
Monorepo
Turborepo 2.7 · Yarn 4 pinned in-repo · TypeScript 5.9 strict with noUncheckedIndexedAccess · ESLint 9 · Prettier
Hosting
Storefront on Vercel · backend, Postgres and S3 on Medusa Cloud · DNS at Hostinger · a separate sample store on its own branch
Payments and tax
CardPointe hosted iframe tokenizer, authorise once, capture once · TaxJar with sale and refund reporting
Logistics and messaging
EasyPost labels and tracking · SendGrid · Twilio under A2P 10DLC · Google and Apple sign-in for shoppers, makers and operator
CI
Backend type-check and unit tests on every PR, because Medusa Cloud only builds after merge · sample branch force-synced to main

Why it is built this way

Medusa plus Mercur instead of a hosted cart. A platform trial on Nov 6, 2026 confirmed that one cart with offers from two sellers becomes one order group with a child order per seller, which is exactly a box per maker. Owning the data model lets regions, areas, standards and badges be operator-edited records. The rule in the repo is "region is data, not code": no page may hard-code California or a town.

A home-built payout ledger instead of Mercur's Stripe Connect payouts. Mercur pays a box's whole total, tax included. Placemade books a sale only when the box is paid, shipped and not cancelled: goods plus shipping, before tax, after discounts, less the 30% commission. Payable 7 days after delivery. Refunds pro rata. Chargebacks deducted from the next run. Biweekly runs export a CSV for the bank, and no maker bank details are stored.

Authorise once at checkout, capture once. The capture happens when every open box has shipped or on day 6, because CardPointe allows one capture per authorisation and authorisations last about seven days. A box cancelled before capture is simply left out. Refunds that arrive before settlement are held as pending and retried hourly.

Maker onboarding is a compensating workflow. Approval creates the seller, pricing regions, area link, stock location and a flat shipping option, then sends the invite. Each step undoes itself on failure, so there is never a half-made store, and the invite only goes out when everything succeeded.

No programmatic SEO pages, on purpose. With one maker per town, generated town-by-department pages would duplicate maker pages and split their ranking. Instead there are four real page types with indexing thresholds in one tested helper; pages below them are marked noindex, follow.

Medusa Cloud has no shell. One-off data fixes are written as idempotent migration scripts that run on deploy and are safe on an empty database. There are 14. Scripts that write catalog data also flag the search index for a rebuild, because writes made outside the running server never reach it.

Details worth noticing

  • Shelf stock: Placemade can buy and hold inventory and sell it through a hidden house seller at 0% commission. The storefront picks which offer each line uses. PR #97 reworded every claim that "each box ships from its maker" because that had stopped being true.
  • Fraud holds on AVS or CVV mismatch, a first order over $300, or three orders in 24 hours. A held order gets no maker email, no timers and no capture.
  • Box timers: accept within 24 hours, ship by the promised days, first carrier scan within 72 hours. Late boxes email the operator and appear in a Needs attention queue.
  • Cottage-food items can only ship within the maker's state. This is enforced in the cart-completion hook, not just in the UI.
  • The email list endpoint answers the same way whether or not an address exists, has a honeypot field, and only re-adds an unsubscribed person through an HMAC-signed link.
  • Image remote patterns are locked to one S3 folder because bucket names can be registered by anyone.
  • Video clips are re-encoded as silent H.264 with poster frames, load only near the viewport and play only while visible. Every video except the footer's has a pause control.
~550 TypeScript files · ~51,700 lines · 35 backend spec files · 97 pull requests · 14 deploy-time data scripts · documented work from Nov 6 to Nov 17, 2026 against a 15-sprint plan
Group 2

Production sites with their own pipelines

Live marketing sites for real businesses. None of them use a page builder. Each has a build step suited to its host and a deploy that verifies itself, and two of them carry server-side features that go well beyond a brochure.

trevorprovencio-bit/carlsbad-crossfit-siteprivatelast commit Nov 12, 2026carlsbadcrossfit.com

Carlsbad CrossFit

Live since Nov 4, 2026

A full redesign of a gym's website, delivered inside the WordPress install the gym already pays for. The new site is a static app shell plus pre-rendered pages, served by Apache rules that a small PHP snippet manages, so a plain page view answers in about 0.2 seconds instead of 1.2 to 1.8.

carlsbadcrossfit.com
Carlsbad CrossFit home page with a workout timer and the headline about North County's most fun CrossFit gym
Carlsbad CrossFit home page at phone width
Build
One master HTML file58 numbered patch scripts applied in order
Launch builderpages + content-hashed assets
Headless Chrome prerender12 routes with meta, OG and JSON-LD
Deploy
GitHub Actions, macOS runnerneeds Chrome and sips
POST zip to /wp-json/c2/v1/deploytoken checked by SHA-256 fingerprint
Post-deploy checkthree pages and every JS asset
Serve
WordPress on GoDaddy cPanelPorto parent, child theme untouched
functions.php snippetroutes, redirects, 410s, sitemap, llms.txt
Apache rewrite rulesstatic pages for logged-out visitors

Runs on

Build
Python toolchain, 72 scripts: patch series, launch builder, prerender, crawl and audit tools · a Swift helper for image flattening
Hosting
The gym's existing WordPress on GoDaddy cPanel · DNS at GoDaddy · no new hosting bill
Deploy
GitHub Actions on macos-15-intel · custom WP REST endpoint · deploy key can only install a launch zip · Wordfence keeps Application Passwords off
Performance
Pre-rendered pages served by Apache for plain visits · admin toggle writes an .htaccess backup first · app shell fetched with no-cache so updates show at once
Integrations
Ninja Forms (free trial, drop-in) with nonce bootstrap · BTWB workout widget with a 24-hour localStorage cache · Google Tag Manager · Search Console
Design system
Tokens, components, fonts and logo extracted from the site into source/design-system

Why it is built this way

Keep the host, replace the experience. No migration, no new bill, and the old theme stays underneath. A single flag flips between the new site and the old pages. With it off, only logged-in editors see the new site, after opening a page with a query key.

Requests that are not plain page views fall through to WordPress. Query keys other than the campaign and cache keys reach the old site, so search, plugin endpoints and member login keep working. The schedule page still reads the workout widget key from the old WOD page, which is why that page stays up with noindex.

Launch-day SEO rules live in the snippet, dated. Staff URLs redirect to the coaches page, author archives and feeds go home, the robots file is served from the deploy because the physical one listed 13 dead sitemaps, and the app shell carries an X-Robots-Tag so crawlers index the pre-rendered pages instead.

Details worth noticing

  • Body links are written as data attributes and filled from routes.json; the prerender fails the build if any placeholder link is left unfilled.
  • Launch zips are stored, never deflated, because the host's loader cannot read compressed entries. The note explains it bit once and shows the fix.
  • A phone-side debug panel logs each step of the workout widget load with timings, never the key, so a slow page can be diagnosed on the device itself.
  • Host limits (responses of about 3.7 MB, non-file bodies over 1 MB) and the Nov 5, 2026 switch to Intel runners are recorded with dates and reasons.
  • Seven audit documents sit alongside the code: SEO audits for launch, the main pages and the free-trial page, a copy review, a design audit and a site-health report.
12 routes · 72 build and audit scripts · 19 HTML sources · 1 deploy workflow · 1 launch snippet · live-site response time cut from about 1.35 s to about 0.2 s
trevorprovencio-bit/hermosa-payments-siteprivatelast commit Nov 1, 2026hermosapayments.com

Hermosa Payments

Live

Marketing site for a local card-processing company, with a free statement checker that reads a merchant's monthly processing statement and sorts every fee line. The site is flat HTML written by one Python script. The checker parses the PDF in the browser and sends only redacted text to a PHP endpoint, which asks Claude for the breakdown.

hermosapayments.com
Hermosa Payments home page with the headline Lower card fees, a local team that answers
Hermosa Payments home page at phone width
hermosapayments.com/statement-check
The free statement checker page with a drop zone for a PDF statement
The statement checker. The PDF is read on the visitor's device with a self-hosted pdf.js; names, addresses and long account numbers are removed before any text is sent.
In the browser
pdf.js 4.10, self-hostedno outside script near the statement
Redactionnames, addresses, account numbers
Fallback readerruns if the server answers 503
On the host
Hostinger PHP60-second request limit
POST returns a job idpage polls every few seconds
Claude via raw HTTPSno Composer on the host, so no SDK
Temp file, self-deletingnothing saved or logged

Runs on

Build
One Python generator: page bodies, industries, counties, FAQs and Markdown posts in; about 40 HTML pages, sitemap and robots out · photos resized to 700 and 1400 px
Hosting
Hostinger shared PHP hosting with Git deploy · .htaccess maps clean URLs, 301s the first launch's addresses, hides the build folders
Forms
PHP handlers email quotes, support tickets and call bookings through the domain's own mailbox, so no password is stored · SMS consent kept with time and IP
AI reader
Browser-side parsing and redaction · async job pattern around the host's 60-second cut-off · API key kept outside the web root
Front end
Vanilla JS · theme chosen before first paint (query, saved choice, then device) · entrance motion with a 2.5-second fallback · content-hashed asset URLs
Privacy
Ads pixel skipped when the browser sends Global Privacy Control · statement results deleted after display

Why it is built this way

A generator instead of a CMS. The owner's content lives in JSON and Markdown. A build is one command. The host serves flat files, so there is nothing to patch and nothing to break into. Industry and county pages come from data, with the service area wired into the footer and the structured data.

The statement checker is built to never see a whole statement. Parsing and redaction happen on the visitor's device. The model receives redacted text and returns JSON. Results are deleted right after they are shown, and if the key is missing the page falls back to an in-browser reader rather than failing.

An async job around a shared-host limit. A careful read can take over a minute and the front server cuts requests at 60 seconds, so the POST answers at once with a job id and keeps working. The finished answer waits in a temp file and deletes itself after 30 seconds if the page has gone.

Details worth noticing

  • Nine industry pages and three county pages generated from data files, plus eight articles written in a small Markdown dialect the build parses itself.
  • The old quote-form endpoint is kept alive so pages cached in a visitor's browser still submit.
  • Light and dark themes, a hero video with a pause control, and a brand voice guide with claims the business can back.
  • The fee analysis page explains the anatomy of a statement for people who would rather enter two numbers than upload a PDF.
24 top-level pages · 9 industry pages · 3 county pages · 8 articles · 6 JS modules · 3 PHP handlers · 1 build script
trevorprovencio-bit/home-tab-marketingprivatelast commit Nov 16, 2026 · PR #12joinhometab.com

Home Tab landing page

Live

The public page that sells Home Tab to shop owners and takes applications for the pilot. One HTML page, one stylesheet, one script, no build step, and a deploy pipeline that verifies the live page after every upload.

joinhometab.com
Home Tab landing page with the headline Memberships that live at the counter and a sample owner report
Home Tab landing page at phone width
The owner report on the page is a sample shop with made-up numbers, and says so next to the figures. No pilot pricing is shown because pricing is set per shop.

Runs on

Front end
Static HTML, CSS and JS · layout responds to the page root with container queries at 1080, 920 and 640 px · tokens copied from the Home Tab design system · Geist self-hosted
Forms
Validation, chips, JSON POST to an endpoint attribute · without an endpoint it only "sends" on localhost or ?preview, and tells real visitors applications are not open yet
Hosting
Hostinger static hosting · DNS at GoDaddy · SSL and the HTTPS redirect from the host
Deploy
GitHub Actions on push to main · lftp over FTPS, mirror with delete, hidden files left alone · then six attempts to find the headline on the live page
Legal
/privacy and /terms kept in step with the app repo's drafts, including the text-message section Twilio's review checks
Accessibility
Real buttons and links, labelled inputs, alt text that says what each screenshot shows, 4.5:1 text contrast, 44 px touch targets

Why it is built this way

lftp instead of a Node FTP client. The host requires each transfer to reuse the login's TLS session, which lftp does reliably. The workflow comment says exactly that, so nobody swaps it out later.

The pipeline refuses politely. Until the three secrets exist, a run does nothing and posts a warning naming the file to read. Only the site's own files are uploaded; the README, the notes and the docs folder never reach the server.

Nothing invented. No customers, testimonials, results or prices exist yet, so none appear. One acid-green fill per screen, on the one button that matters.

3 HTML files · 1 workflow · 8 product screenshots at 2x · 3 container-query breakpoints · 12 pull requests
trevorprovencio-bit/trevor-portfolioprivatelast commit Nov 2, 2026trevorprovencio.com

trevorprovencio.com

Live

My design portfolio, rebuilt from a Squarespace export into an Astro static site. One JSON file per project, images resized at build time, a WebGL tape-signal effect on the hero and the closing card, and a visible switch that turns all of it off.

trevorprovencio.com
Portfolio home page with a client ticker, a script logo and a product video
Portfolio home page at phone width

Runs on

Framework
Astro 7, static output, sitemap integration · content collection of typed JSON, one file per project · Motion 14 for animation CSS cannot do · sharp for build-time image resizing
Content
15 project files · a services module ties six services to real projects · llms.txt and JSON-LD generated from the same data · 172 images tracked in a manifest
Hosting
Hostinger · .htaccess handles HTTPS and www, the old Squarespace project URLs, the 404 page and caching
Media
Self-hosted clips with poster frames · Vimeo embeds with the site's own play and mute controls · GIFs kept as originals so they stay animated
Tooling
A Chrome-driven script renders each project's social share image · Formspree for the contact form · fonts via @fontsource
Accessibility
Simple view switch remembered in the browser · every effect checks reduced motion and data saver first · content stays visible without JavaScript

Why it is built this way

The build fails on bad content. Every project's sections must reference each image and video exactly once, and a self-hosted video without a poster stops the build. Copy fields stay empty until approved; the rule is never to invent project copy or client claims.

Simple view is a real feature, not a media query. A switch in the top bar turns off motion, autoplay and effects, goes black and white while keeping project work in colour, and swaps posters for still photos. Every effect checks one helper that also covers reduced motion and data saver.

The tape effect repaints real text onto a canvas. The type underneath stays real, selectable and indexable; the shader only distorts a copy of it.

15 projects · 10 Astro pages and components · 10 TypeScript modules · 60 video links by host · migrated from Squarespace with redirects for every old URL
Group 3

Design-led static builds

Sites built straight from design comps, published on GitHub Pages as working previews. No frameworks to maintain, forms that degrade to email until a backend is chosen, and a written list of everything still waiting on the client.

trevorprovencio-bit/santosha-sitepubliclast commit Nov 12, 2026GitHub Pages preview

Santosha Nutrition

Design preview · noindex

A clickable preview of the new site for a plant-based chef's cooking classes, catering and events. Eight pages, a component library written in React 18, and Square payment links for the cookbook and gift certificates, so there is no cart and no payment code on the site at all.

trevorprovencio-bit.github.io/santosha-site
Santosha Nutrition home page with a garden-party video and the headline Plant-based cooking for a happier, healthier you
Santosha Nutrition home page at phone width

Runs on

Front end
Plain HTML pages, each holding its layout in a template of custom import tags · a 129-line runtime turns the template into React elements and re-renders on state change
Components
Header, hero, cards, testimonials, FAQ, forms and footer in one React file · tokens.css with light and dark themes · Aleo and Sofia Sans Semi Condensed self-hosted
Checkout
Square payment links, one per product, redirecting to a thank-you page · until a link is pasted in, the Buy button goes to the contact page and says so
Hosting
GitHub Pages · every page marked noindex while it is a preview · the contact form sends nothing yet by design

Why it is built this way

The preview and the eventual build share one source. The component markup comes straight from the design canvas, so what the client clicks through is what gets shipped, not a mock-up to be rebuilt later.

Payments stay entirely on Square's side. The owner turns checkout on by creating three payment links in her Square dashboard and pasting them into one small file. Larger cookbook orders route to the contact page because Square's checkout cannot change quantity.

8 pages · 1 component library · 2 themes · credits and font licences recorded in the README
trevorprovencio-bit/greenhouse-sitepubliclast commit Nov 9, 2026GitHub Pages preview

Greenhouse

Preview · awaiting client answers

The website for a tattoo shop, hair salon and art space in Asheville. Thirteen pages moved over from design comps, with a booking panel that sends hair clients to each stylist's own booking page and tattoo requests to the right artist.

trevorprovencio-bit.github.io/greenhouse-site
Greenhouse home page with the headline Tattoo, hair and art in a little Asheville greenhouse and two portraits
Greenhouse home page at phone width

Runs on

Front end
Static HTML and CSS, no build step · one shared stylesheet · the booking panel is namespaced so page styles cannot leak into it
Booking
Any element with a data-book attribute opens the panel for hair, tattoo or a named artist · a hash on any page opens it on load · the link keeps working without JavaScript
Forms
Contact, guest-spot and newsletter forms validate and show status · with no backend they open the visitor's mail app, or post JSON to a form service once an endpoint is set
Responsive
Below 900 px the nav collapses to a details panel and a sticky bottom bar shows Book and Text the shop · artist grids go two across on phones
Hosting
GitHub Pages · every page has its own title and meta description
Brand
Eight named colours and three typefaces fixed in the notes · one button class with four variants · copy voice: plain, warm and specific

Why it is built this way

Ship the whole site before the shop has answered every question. The repo keeps a dated list of what is waiting on the owners: hours, walk-in policy, which name an artist goes by, how pricing works. Those links are left as placeholders instead of guesses.

One button system, four variants, fixed brand palette. The colours, fonts and copy voice are written down so new pages match without a style audit.

13 pages · 1 booking panel · 3 forms · fonts and colours fixed in the project notes
trevorprovencio-bit/builders-lessonspubliclast commit Nov 8, 2026GitHub Pages

Builders

Live

A seven-lesson study series for a church, with a group format and a glossary. The lesson pages and the glossary are generated from one JSON file by a Node script, so the content can be edited by the team without touching HTML.

trevorprovencio-bit.github.io/builders-lessons
Builders landing page with the headline Bible lessons for home, work and church
Builders landing page at phone width

Runs on

Build
A Node script reads data/builders.json and writes one reading page per lesson plus the glossary, with previous and next links and reading time
Images
A small Swift tool crops the photographs for phone sizes · lighter versions served on the landing page
Design kit
An MIT-licensed kit for styles, scripts and motion · only the files the pages load are published
Hosting
GitHub Pages

Why it is built this way

Content as data for a non-technical team. Lesson text, questions and the weekly practice live in one file. Regenerating the site is one command, and the structure of every lesson page stays identical.

7 lessons · 9 HTML pages · 94 photographs · share image and phone crops prepared ahead of time
Group 4

Research and prototypes

Work done to win and shape a project before anything is built for production. The sample pages run only on one computer, so they appear here as screenshots. The photography in them belongs to Stone Source.

trevorprovencio-bit/stone-sourceprivatelast commit Nov 8, 2026runs locally only

Stone Source

Local prototype · not hosted by design

A pitch to a national tile and stone retailer: a site audit with before-and-after sample pages, a design system checked against their identity guide, and a prototype sales assistant where a rep describes a project and Claude drafts a product deck from a library built out of all 219 of the company's brochures.

site-sample/after · served locally, not the live site
Proposed Stone Source home page with a catalog search bar, a photo hero and the headline Tile and natural stone for memorable spaces
The proposed Stone Source home page at phone width
The proposed home page. Every sample page carries a banner saying it is not the live site, with a link to the original it replaces.
site-sample/before · saved Nov 1, 2026
The live Stone Source home page as saved on November 1, 2026, with a boxed headline over the photo
Before: the live home page, kept as a faithful copy so every proposed change can be compared side by side.
site-sample/after/porcelain-tile
Proposed porcelain category page with a full-bleed photo, a breadcrumb and an introduction
After: the porcelain category page with the proposed heading, the new address and the warm text colour from the style guide.
site-sample/after/mutina-puzzle-steel
Proposed product page for Mutina Puzzle Steel with a large swatch, suitable-for icons and a colour grid
Product page: a shorter title and new alt text over the same catalog data.
pitch · sales assistant, a proposal
The sales assistant proposal page with the headline Project decks in about two minutes, checked against stonesource.com
The proposal site for the sales assistant and the new-rep kit. Its own test line reads 8 decks, 61 products, every product matched the website.
localhost:8770 · sales assistant prototype
The prototype's draft view showing a 19-slide project deck with a cover slide and a strip of slide thumbnails
The prototype's draft view: a 19-slide deck drafted from a rep's brief, with every spec read from the live product page before the slides are rendered.

Brochure library pipeline (the script numbers are real)

  1. 01_download_brochures.pyDownloadevery brochure PDF on the site
  2. 02_crawl_collections.pyCrawlcollection and SKU data from product pages
  3. 03_extract_pdfs.pyExtractpage text and page images
  4. 04_ocr_pages.py + ocr.swiftOCRimage-only pages through Apple's Vision framework
  5. 05_build_database.pyBuild the databaseSQLite with full-text search
  6. 06_export_photos.pyExport photoseach image from each PDF as its own file
  7. 07_link_photos.pyLink photos to colourswith the reason each link was made
  8. 08_label_photos.pyLabel photoswhat it shows, which room, one-line summary
219brochure PDFs
4,261pages
9,155photos exported
2,538colours
11,262SKUs
10database tables
Claude does
Searches the librarypicks 3 to 6 products, at most 12
Writes the reasonsdeck title, fit per product, overview, a note to the rep
Code does
Opens each live product pagethe website is the source of truth
Fills every specsizes, thickness, DCOF, finishes
Checks the wordingrejects price, stock, lead time, guarantees and any spec that does not match
Renders PDF and PowerPointpython-pptx, with a before-you-send checklist

Runs on

Library
Python, PyMuPDF, a Swift OCR helper · SQLite with FTS tables · CSV and JSON exports for people and code
Assistant
Flask · Anthropic SDK · python-pptx · Pillow · drafts saved to disk with their own address, revisions, search and filters · rep profiles kept out of git
Design system
Tokens and a dozen components (site header, hero banner, search field, tag, product specs, form field) with contrast checked against the brand's warm neutrals
Samples
Before and after pages for the home page, a category page, a product page and the contact form · the before pages stay faithful copies of the live site
Cost control
Each draft's API cost is recorded; test runs cost $0.08 to $0.21 and a request stops at $1.50
Status
Runs on one computer with no logins · email drafts switched off · the README lists what a pilot would need first

Why it is built this way

Let the model choose and explain; let code be exact. Claude is good at picking products for a brief and saying why. It is not allowed to state a size, a thickness or a slip rating. Those come from the live page, and any claim about price, stock, lead time or guarantees is sent back for rewriting.

Every draft is auditable. A result file keeps the request, the deck, each product's website check, the notes and the cost. Revisions link back to the draft they came from.

Open questions are written down, not papered over. The font licence, the twelve missing pages of the style guide, two brand colours that fail contrast at small sizes, the photo rights and every line of draft copy that needs approval are listed in the README with dates.

8 pipeline scripts · 10 database tables · 12+ components · 4 before-and-after sample pairs · audit deck, design-system deck and sales-assistant pitch page