Files
Charles N Wyble 073581f835 feat: convert from mdbook to Grav format
- Rename src/ to pages/
- Add Grav frontmatter to markdown files
- Create numbered folder structure
- Remove mdbook-specific files

Migration from mdbook to Grav CMS.
2026-03-02 16:32:13 -05:00

39 lines
2.0 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: 'STLP — Website Tech Plan (MVP)'
menu: 'STLP — Website Tech Plan (MVP)'
---
# STLP — Website Tech Plan (MVP)
Objective
- Launch fast with a simple, trustworthy online presence that takes orders/payment without waiting on a full site build.
Phase 0 (same day)
- Domain: confirm and point DNS.
- Single-page site: static page (e.g., simple HTML/Bootstrap or lightweight Astro/Vite) deployed on your existing infra.
- Intake: embedded Typeform/Tally (file upload enabled) or simple HTML form to inbox.
- Payments: Hyperswitch (selfhosted) using Stripe as the initial processor. Expose simple “Pay Now” links or a minimal checkout that creates a payment intent via Hyperswitch and redirects to card entry.
- Analytics: Matomo tag + a basic goal (form submitted / checkout start / success).
Phase 1 (week 2)
- Add product tiles (entry/core offers) with price ranges, FAQs, materials allowed/disallowed.
- Add appointment link for consults (Calendly or equivalent).
- Add gallery from portfolio folder.
Phase 2 (weeks 34)
- Migrate to a simple storefront if needed: keep self-hosting; use static site + Hyperswitch checkout or a lightweight headless cart.
- File handling: gated upload after order (order # + file link) to reduce spam.
- CRM: push leads/orders to Dolibarr (optional if it slows us down).
Hyperswitch MVP Architecture
- Host Hyperswitch (Docker) behind your existing reverse proxy. Configure OIDC admin access.
- Processors: start with Stripe credentials; expand to additional PSPs later. Routing stays in Hyperswitch.
- Server endpoint: tiny service to create payment intents via Hyperswitch API for fixed SKUs and custom quotes.
- Client: simple button → calls server → redirects to Hyperswitch-hosted entry or embeds minimal card form.
- Events: record checkout start/success to Matomo with order/quote IDs.
SEO/Local
- Google Business Profile: ensure NAP consistent with site footer; add UTM links.
- On-page basics: title/description, H1 for “Custom laser, embroidery, CNC in Pflugerville, TX”.
- Schema: LocalBusiness JSON-LD (lightweight).