The Toolbox
Okay, here's the whole toolbox.
You asked. This is the full range of architecture, technology, standards and practices I draw on — not everything gets used on every project, but this is what's available when a project needs it.
Architecture & Development Approaches
Static websites & static-site generationServer-rendered & hybrid web applicationsReact component-based architectureNext.js App RouterHeadless architectureAPI-first integrationsServerless architectureJAMstack-style deploymentsEdge/CDN deliveryRelational database-backed applicationsAuthentication & role-based accessCustomer/member portalsCMS-driven websitesE-commerce architectureForm & lead-generation workflowsBooking & scheduling integrationsThird-party API integrationsWebhooks & automationFile/media storageStaging → review → production workflowCI/CD deployment pipelinesSource-controlled developmentResponsive/mobile-first designProgressive enhancement where appropriate
Front-End Technologies
HTML5CSSJavaScriptTypeScriptReactNext.jsTailwind CSSResponsive CSS / Grid / FlexboxSemantic HTMLModern browser APIs
Hosting & Deployment
VercelNetlifyGitHubGitHub ActionsCDN/edge hostingCustom domains & DNSHTTPS/SSLPreview deploymentsBranch deploymentsStaging environmentsProduction environments
Backend, Database & Application Services
SupabasePostgreSQLSupabase AuthSupabase StorageRow Level SecurityServerless functionsREST APIsWebhooksAuthenticationRole-based permissionsDatabase-driven forms & applications
CMS & Traditional Website Platforms
WordPressJoomlaDrupalSquarespaceWixHeadless CMS options when appropriate
E-Commerce
ShopifyBigCommerceMagento / Adobe Commerce experienceStripeProduct/catalog integrationsCheckout integrationsPayment linksSubscription billingCustomer accounts
Forms, Email & Communications
Netlify FormsSupabase-backed formsResendTransactional emailContact formsLead formsAutomated confirmationsForm spam protectionCAPTCHA where warrantedCRM/API handoffs
Analytics, SEO & Marketing
Google Analytics / GA4Google Search ConsoleConversion trackingEvent trackingTechnical SEOOn-page SEO foundationsXML sitemapsrobots.txtCanonical URLsRedirect managementOpen Graph metadataSocial sharing metadataSchema.org structured dataLocal-business structured dataSearch-engine indexing controlsCore Web Vitals monitoringPerformance auditingLighthouseSEO tooling (e.g. SEMrush) when appropriate
Design & UX
FigmaResponsive layoutsMobile-first designDesign systemsReusable componentsAccessible navigationClear calls to actionConversion-oriented page structureInformation architectureUser flowsLanding pagesBrand integrationImage optimizationResponsive images
Development & Project Tools
GitGitHubGitHub Issues / pull requestsFigmaVS CodeAutomated buildsAutomated QA checksDependency management with npmPreview/review environments
Web Standards
HTML5 standardsSemantic HTMLModern CSS standardsECMAScript / modern JavaScript standardsStandards-based browser renderingProper document hierarchyValid metadataProgressive enhancementResponsive web designDevice-independent layouts
Accessibility Standards & Practices
WCAG 2.2Targeting WCAG 2.2 AA practicesSemantic landmarksKeyboard navigationVisible focus statesSufficient color contrastForm labelsAlternative textReduced-motion preferencesLogical heading hierarchyAccessible link/button treatmentARIA only where semantic HTML is insufficientTouch-target sizingScreen-reader-conscious markup
Performance Standards
Google Core Web VitalsLargest Contentful Paint (LCP)Interaction to Next Paint (INP)Cumulative Layout Shift (CLS)Image compressionModern formats such as WebP/AVIF where appropriateResponsive image sizingLazy loadingCode splittingMinimal unnecessary JavaScriptCDN cachingFont optimizationAsset optimizationLighthouse performance testing
Security Practices
HTTPS/TLSSecure headers where appropriateOWASP-informed development practicesInput validationOutput escapingProtected authentication flowsLeast-privilege permissionsRole-based access controlRow Level Security for Supabase applicationsSecret/environment-variable managementDependency security checksSpam/bot protectionSecure form handlingMinimal exposure of customer dataNo secrets committed to repositories
Privacy & Data Practices
Privacy-by-design mindsetData minimizationCookie/consent controls when actually requiredClear privacy policiesPIPEDA considerations for Canadian businessesGDPR considerations where applicableCCPA/CPRA considerations where applicableNo unnecessary analytics or trackingAppropriate retention of form/customer data
SEO Standards
Crawlable semantic HTMLDescriptive title tagsMeta descriptionsCorrect heading structuresitemap.xmlrobots.txtCanonical URLsStructured dataLocal SEO markup where relevantProper redirectsFast page performanceMobile usabilityAccessible content structureSearch-friendly URLs
Quality & Maintainability
Git version controlPull-request reviewStaging before productionReusable componentsConsistent naming/conventionsTypeScript where appropriateResponsive QABrowser testingAccessibility checksPerformance checksBroken-link checksForm testingProduction smoke testingDocumented architecture for larger projectsClean handoff & maintainable code
Still Reading?
Not sure if what you need is on this list?
That's exactly what the contact form is for. Tell me what you're trying to do and I'll tell you honestly whether it's a fit.
