Passionfruit DesignPortsmouth and the South Coast

Technical depth. A human approach.

I’m Dr Matt Dennis, a senior academic with over 20 years of experience. I work with people and teams on infrastructure, web applications, automation, data and governance. Understanding the people who use a system is where the engineering starts.

How I build

Minimal technical debt.

Every dependency, build step and moving part is a future cost to you. I only add one when it pays for itself, and I remove what stops paying. Code is linted, typed or validated at its edges, tested in CI, and documented well enough that someone else could take it over. Everything below follows from that.

  1. Slim servers.

    Small, single-purpose Node services with thin request handlers. No heavyweight runtime, no plugin pile. Several production apps share one 2GB VPS, and some have no npm dependencies at all. You get speed and a small hosting bill.

  2. JSON throughout.

    Content is structured data from a headless or JSON-backed CMS, not pages locked in a theme. Schemas are validated at the boundary with Zod or JSON Schema. The same data feeds your website, a PWA, a dashboard or another system without rework.

  3. Built in the browser.

    The server sends an app skeleton once, then JSON over a REST API. The logic runs on the client, which fills HTML templates and web components with that data. The server never assembles a page, so it does less work and costs less to run. Content goes in through the DOM. No innerHTML, no HTML built from strings, no server-side includes. The markup is semantic elements, not layers of divs hung with ids. No jQuery, no getElementById, no var. Search engines and link previews still get whole pages: on the SGMC sites every public route is rendered once in a headless browser in CI and served as a static snapshot, and an edit in the CMS re-renders the pages it touches within a couple of minutes.

  4. Build in CI or not at all.

    Servers run code. They do not build it. Where a server needs TypeScript, Node runs it directly with type stripping.

  5. Current versions, always.

    Dependencies stay on current releases. They are not left to rot until an upgrade becomes a project.

  6. Standard and portable.

    Nothing proprietary. The same app runs on a VPS, on Vercel, on Cloud Run or on Azure, and you can take it elsewhere.

  7. AI-assisted, engineer-owned.

    I use AI tools to support development and review. I read and test the output, make the engineering decisions and remain responsible for what I deliver.

The lot

Every layer, from the people using it down to the network. No subcontractors. No gaps.

  1. Experience

    Years on the web, and what I support. That includes every framework on this page. Semantic, accessible HTML, so people with disabilities can use what you ship.

    • 15 years JavaScript
    • 10 years PHP
    • 10 years Apache
    • 3 years JSP
    • Java
    • C
    • MariaDB
    • MySQL
    • Postgres
    • SQLite
    • Git
    • Mercurial
    • GitHub
    • Vercel
    • Neon
  2. Research and design

    I find out what people need before I build it, then test it with them.

    • User research
    • Interviews
    • Usability testing
    • Prototyping
    • Interaction design
    • UX
    • Accessibility to WCAG 2.2 AA
  3. Research and data analysis

    I design the study, run it, analyse the results and report them so a person can read them. Large datasets included.

    • Study design
    • Surveys
    • Data analysis
    • Large datasets
    • Python
    • R
    • Bespoke analysis tools
    • Dashboards
    • Reporting
    • Peer-reviewed publication
  4. Architecture

    Designed for the job and sized to run fast on modest hardware.

    • Headless CMS
    • REST and JSON APIs
    • Small services
    • App skeleton
    • Client-side logic
    • HTML templates
    • Web components
  5. Web apps with a CMS

    Your staff edit the content. Nobody phones a developer.

    • Payload
    • Directus
    • A custom CMS written for the job
  6. Interface

    Hand-written where that is enough, a framework where the app warrants it.

    • HTML
    • CSS
    • JavaScript
    • React
    • Next.js
    • TypeScript
    • Tailwind
  7. Application and data

    APIs, databases, and the data you already have, moved in safely.

    • Node
    • Express
    • Fastify
    • REST and JSON APIs
    • Postgres
    • SQLite
    • Prisma
    • Full-text search
    • Data migrations
    • Legacy imports
    • Feeds to and from other systems
  8. Legacy applications

    I know the older frameworks, and move applications from server state to true RESTful APIs.

    • MVC
    • PHP
    • Laravel
    • CodeIgniter
    • Ruby on Rails
    • JSP
  9. Identity

    One sign-in for every app, with roles that match how your organisation works.

    • Passkeys (WebAuthn)
    • OIDC
    • Single sign-on
    • Google sign-in
    • Magic links
    • Role hierarchies
    • Central identity service
  10. Payments and ticketing

    • Stripe
    • Box office
    • Events
    • Bookings
  11. Integrations

    • Social media hooks
    • Webhooks
    • Media pipelines
    • Third-party feeds
  12. AI

    LLM features behind a provider you can swap, with privacy designed into the schema.

    • LLM features
    • Swappable provider interface
    • Privacy by schema
  13. DevSecOps

    • GitHub Actions
    • Automated deploys
    • Dependency patching
    • Content Security Policy
    • Security headers
    • Secrets management
    • pm2
    • Docker
    • Monitoring
    • Health checks
  14. Hosting

    Several production apps on one small box.

    • Linux VPS
    • nginx
    • Vercel
    • Neon
    • Google Cloud
    • Managed Postgres
    • Backblaze B2
    • Object storage behind a CDN
  15. Cloudflare

    • DNS
    • CDN
    • Caching
    • TLS
    • Edge protection
  16. DNS and email

    Your domain cannot be spoofed, and your mail arrives.

    • DNS management
    • Domain migrations
    • SPF
    • DKIM
    • DMARC to p=reject
    • BIMI
    • MTA-STS
    • Mail forwarding
    • Mailing lists
    • Transactional email
  17. Home and business automation

    Devices from different makers, working together on a small computer you own.

    • Home Assistant
    • Docker
    • Zigbee
    • MQTT
    • 433 MHz radio
    • Presence sensors
    • Heating control
    • Dashboards
  18. Network

    • Reverse proxies
    • TLS
    • Private networking
    • VPN (Tailscale)
    • Network design
  19. Policy and governance

    I write the policy as well as the code.

    • Data protection by design
    • Accessibility
    • Security policy
    • Safeguarding
    • Regulatory compliance

Specialities

Six parts of the work, each with a page of its own.

Work

A charity platform, small-business sites on custom CMSs, university systems and a public archive.

Receipts

Figures about this page, measured by the server that sent it. None of them are typed in by hand.

Page weight
19.1 KB Everything this page downloads, compressed, in 4 requests. Check it yourself: page weight
Server render
0.88 ms Median of the last 47 renders. 95% took under 10.77 ms. Check it yourself: Server-Timing response header (browser dev tools, Network tab)
Server memory
35.1 MB What this server holds on its own, right now. Node's shared program code is not counted. Check it yourself: server memory
Third-party requests
0 The content security policy lets the browser load from this domain only. Check it yourself: third-party requests
Runtime dependencies
2 66 packages installed in total, counted from the lockfile. Check it yourself: runtime dependencies
Cookies set
0 Out of 6,288 responses since the server started. Check it yourself: Application tab in your browser's dev tools
Version
4d8e820 Deployed . Check it yourself: version
DMARC policy
p=reject Read live from DNS for passionfruit.design. Check it yourself: dmarc policy
Security headers
This response was served with:
  • Content-Security-Policy
  • Strict-Transport-Security
  • X-Content-Type-Options
  • X-Frame-Options
  • Referrer-Policy
  • Permissions-Policy
  • Cross-Origin-Opener-Policy
  • Cross-Origin-Resource-Policy
  • Cross-Origin-Embedder-Policy
  • Origin-Agent-Cluster
Check it yourself: security headers

All of this as JSON

Let’s talk it through

Tell me what you would like to make easier. It is fine if you are still working out what you need. We can start with a conversation, in person around Portsmouth and the South Coast, or by video call anywhere in the UK. Or email hello@passionfruit.design, or call or WhatsApp 07385 509278 (open WhatsApp).