{
  "site": {
    "name": "Passionfruit Design",
    "area": "Portsmouth and the South Coast",
    "owner": "Dr Matt Dennis",
    "url": "https://passionfruit.design",
    "email": "hello@passionfruit.design",
    "phone": {
      "display": "07385 509278",
      "tel": "+447385509278",
      "whatsapp": "https://wa.me/447385509278"
    },
    "location": {
      "town": "Portsmouth",
      "region": "Hampshire",
      "country": "UK",
      "countryCode": "GB"
    },
    "serviceArea": {
      "radiusMiles": 30,
      "latitude": 50.8198,
      "longitude": -1.088,
      "places": [
        "Portsmouth",
        "Southsea",
        "Gosport",
        "Fareham",
        "Havant",
        "Waterlooville",
        "Chichester",
        "Southampton",
        "Winchester",
        "Isle of Wight"
      ],
      "remote": "United Kingdom"
    },
    "person": {
      "name": "Matt Dennis",
      "prefix": "Dr",
      "jobTitle": "Senior academic and technology consultant",
      "credential": "PhD in human-computer interaction",
      "alumniOf": {
        "text": "University of Aberdeen",
        "href": "https://www.abdn.ac.uk"
      },
      "memberOf": {
        "text": "BCS, The Chartered Institute for IT",
        "href": "https://www.bcs.org"
      }
    },
    "profiles": [
      {
        "text": "GitHub",
        "href": "https://github.com/matt-thepie"
      },
      {
        "text": "LinkedIn",
        "href": "https://www.linkedin.com/in/drmattdennis"
      }
    ],
    "indexNowKey": "26752be6ba04488b94c8dbe957c8f20b",
    "repo": null,
    "title": "Home automation and IT, Portsmouth",
    "description": "Friendly technology help from Dr Matt Dennis: home automation, data, IT and governance for people, charities and businesses in Portsmouth and beyond.",
    "versions": {
      "plain": "Plain English",
      "technical": "For IT people"
    },
    "labels": {
      "home": "Home",
      "questions": "Questions people ask",
      "technical": "For IT people",
      "plain": "In plain English",
      "technicalWork": "All the work, with the tools named",
      "proof": "Work like this",
      "services": "What I did here",
      "specialities": "Specialities",
      "visit": "Visit",
      "sources": "Sources",
      "plan": "The plan for this note",
      "allServices": "All services",
      "allWork": "All the work",
      "facts": "How it is built",
      "moreWork": "See all the work"
    },
    "hero": {
      "headline": "Technology that makes life a little easier.",
      "lede": "Hello, I’m Matt. I help people make their homes more efficient, and charities and businesses make technology work for their people. I listen, explain things in plain English, and help you find a practical way forward. Based in Portsmouth, working along the South Coast and across the UK.",
      "action": "Let’s talk it through"
    },
    "automation": {
      "service": "home-and-business-automation",
      "heading": "A home that works around you",
      "hooks": [
        "Heating that fits your routine.",
        "Lights that help you feel at home.",
        "Everyday tasks taken care of."
      ],
      "answer": "We start with what would make a difference to your day. I help your heating, lights and devices work together, with controls you feel comfortable using. In Portsmouth and along the South Coast.",
      "get": {
        "heading": "From a conversation to a working home",
        "items": [
          "Visit your home or business for a free consultation and quote: on the mainland within 30 miles of Portsmouth. The Isle of Wight costs extra, because of the ferries.",
          "Source the hardware, or advise you on what to buy yourself.",
          "Install the devices and set up your network.",
          "Set up and test your automations with you, and show you how to use them."
        ]
      },
      "control": {
        "heading": "How you control it",
        "items": [
          "A web dashboard",
          "Apple Home",
          "Google Home",
          "Alexa"
        ],
        "note": "Google Home and Alexa need Home Assistant Link, a separate subscription from Nabu Casa at £6.50 a month or £65 a year billed annually, and are cloud services themselves. Apple Home and the dashboard do not need it."
      },
      "support": {
        "heading": "After it is installed",
        "paragraphs": [
          "I take time to show you how everything works. The hardware and code are yours, with the choice to make changes yourself or ask for help.",
          "Or retain me for £15 a month. If an automation stops working, send me a message and I fix it remotely, and I apply the Home Assistant updates for you. Faults caused by your own edits, new automations and changes are quoted separately.",
          "Support is done remotely, over a private link, and only with your permission. It needs Home Assistant on its own computer, such as a Raspberry Pi."
        ]
      },
      "link": "How home automation works",
      "details": "Installation, controls and ongoing support"
    },
    "focus": {
      "heading": "Support for charities and businesses",
      "intro": "I’ve worked with charities throughout my adult life, supporting people with all levels of IT confidence. We can work through the things that matter to your organisation, at a pace that suits your team.",
      "services": [
        "business-data-analysis",
        "it-and-ai-consultancy",
        "web-apps-and-booking"
      ],
      "proof": "See the work",
      "link": {
        "text": "Explore support for charities",
        "href": "/services/charities"
      }
    },
    "what": {
      "heading": "How I work",
      "lead": {
        "title": "A conversation comes first.",
        "text": "I start by listening: what matters to you, what is getting in the way, and what would make things easier. Then we agree a practical plan that fits your people, your budget and the way you work."
      },
      "items": [
        {
          "title": "You can ask anything.",
          "text": "I work with people with all levels of IT experience. You can ask questions, take your time and tell me what you want to do in your own words. I will explain the options in plain English."
        },
        {
          "title": "We work together.",
          "text": "You know your home or organisation. I bring the technical experience. I involve you and the people who will use the result, from the first conversation through to trying it out."
        },
        {
          "title": "Care with your information.",
          "text": "We discuss who needs access, how information is protected and what support is needed. Remote access to your home is only with your permission."
        },
        {
          "title": "Room for everyone.",
          "text": "I consider accessibility from the beginning, so people can use what we build on different devices and with assistive technology."
        },
        {
          "title": "Clear costs and choices.",
          "text": "I explain the setup and running costs before you decide. We choose what is useful for you and keep ongoing maintenance manageable."
        },
        {
          "title": "Confidence to carry on.",
          "text": "I explain how things work and document what you need. You can look after it yourself, work with your team or arrange ongoing support."
        }
      ]
    },
    "technical": {
      "title": "Full-stack developer, Portsmouth",
      "description": "Technical expertise from Dr Matt Dennis in Portsmouth: infrastructure, web apps, automation and data, informed by research and practical experience.",
      "hero": {
        "headline": "Technical depth. A human approach.",
        "lede": "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."
      }
    },
    "principles": {
      "heading": "How I build",
      "lead": {
        "title": "Minimal technical debt.",
        "text": "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."
      },
      "items": [
        {
          "title": "Slim servers.",
          "text": "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."
        },
        {
          "title": "JSON throughout.",
          "text": "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."
        },
        {
          "title": "Built in the browser.",
          "text": "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."
        },
        {
          "title": "Build in CI or not at all.",
          "text": "Servers run code. They do not build it. Where a server needs TypeScript, Node runs it directly with type stripping."
        },
        {
          "title": "Current versions, always.",
          "text": "Dependencies stay on current releases. They are not left to rot until an upgrade becomes a project."
        },
        {
          "title": "Standard and portable.",
          "text": "Nothing proprietary. The same app runs on a VPS, on Vercel, on Cloud Run or on Azure, and you can take it elsewhere."
        },
        {
          "title": "AI-assisted, engineer-owned.",
          "text": "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."
        }
      ]
    },
    "about": {
      "heading": "A little about me",
      "photo": {
        "src": "img/matt.webp",
        "alt": "Matt, smiling with his arms folded, standing outside in front of a tree with yellow leaves.",
        "width": 540,
        "height": 270
      },
      "paragraphs": [
        "I’m Dr Matt Dennis, a senior academic based in Portsmouth with over 20 years of experience in the field. I enjoy making complicated things understandable, and helping people feel confident with technology.",
        "My doctorate at the University of Aberdeen is in human-computer interaction: understanding how technology can work better for the people using it. Listening, research and accessibility shape how I approach every project.",
        "I have taught web technologies for over a decade, published peer-reviewed research and run production systems since 2018. I bring that experience to practical questions, from making sense of data to keeping an organisation’s systems running.",
        "I’ve worked with charities throughout my adult life, supporting people with a wide range of IT skills and confidence. I care about making things that work for them, and taking the time to help them feel comfortable using them.",
        "I’m a charity trustee and a member of the BCS, The Chartered Institute for IT. I have held a senior role covering safeguarding, regulatory compliance and data protection. I bring that experience to helping organisations look after their people, information and systems."
      ],
      "details": "More about my background"
    },
    "contact": {
      "heading": "Let’s talk it through",
      "intro": "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.",
      "link": "Have a conversation",
      "sent": "Thanks. Your message has been sent. I will reply to the address you gave.",
      "failed": "That did not send. Please email me directly instead."
    },
    "legal": "Passionfruit Design is the trading name of Dr Matt Dennis.",
    "welcome": {
      "heading": "Where can I help?",
      "credentials": [
        "Senior academic",
        "Over 20 years of experience",
        "Working with charities throughout my adult life"
      ],
      "choices": [
        {
          "text": "Help with my home",
          "href": "/#automation",
          "description": "Bring your heating, lights and devices together, with everyday routines that make life easier."
        },
        {
          "text": "Help for my charity or business",
          "href": "/#business",
          "description": "Friendly support with IT, data, infrastructure and governance, whatever your level of confidence."
        }
      ],
      "profiles": "More about my experience"
    }
  },
  "stack": {
    "heading": "The lot",
    "intro": "Every layer, from the people using it down to the network. No subcontractors. No gaps.",
    "layers": [
      {
        "name": "Experience",
        "text": "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.",
        "items": [
          "15 years JavaScript",
          "10 years PHP",
          "10 years Apache",
          "3 years JSP",
          "Java",
          "C",
          "MariaDB",
          "MySQL",
          "Postgres",
          "SQLite",
          "Git",
          "Mercurial",
          "GitHub",
          "Vercel",
          "Neon"
        ]
      },
      {
        "name": "Research and design",
        "text": "I find out what people need before I build it, then test it with them.",
        "items": [
          "User research",
          "Interviews",
          "Usability testing",
          "Prototyping",
          "Interaction design",
          "UX",
          "Accessibility to WCAG 2.2 AA"
        ]
      },
      {
        "name": "Research and data analysis",
        "text": "I design the study, run it, analyse the results and report them so a person can read them. Large datasets included.",
        "items": [
          "Study design",
          "Surveys",
          "Data analysis",
          "Large datasets",
          "Python",
          "R",
          "Bespoke analysis tools",
          "Dashboards",
          "Reporting",
          "Peer-reviewed publication"
        ]
      },
      {
        "name": "Architecture",
        "text": "Designed for the job and sized to run fast on modest hardware.",
        "items": [
          "Headless CMS",
          "REST and JSON APIs",
          "Small services",
          "App skeleton",
          "Client-side logic",
          "HTML templates",
          "Web components"
        ]
      },
      {
        "name": "Web apps with a CMS",
        "text": "Your staff edit the content. Nobody phones a developer.",
        "items": [
          "Payload",
          "Directus",
          "A custom CMS written for the job"
        ]
      },
      {
        "name": "Interface",
        "text": "Hand-written where that is enough, a framework where the app warrants it.",
        "items": [
          "HTML",
          "CSS",
          "JavaScript",
          "React",
          "Next.js",
          "TypeScript",
          "Tailwind"
        ]
      },
      {
        "name": "Application and data",
        "text": "APIs, databases, and the data you already have, moved in safely.",
        "items": [
          "Node",
          "Express",
          "Fastify",
          "REST and JSON APIs",
          "Postgres",
          "SQLite",
          "Prisma",
          "Full-text search",
          "Data migrations",
          "Legacy imports",
          "Feeds to and from other systems"
        ]
      },
      {
        "name": "Legacy applications",
        "text": "I know the older frameworks, and move applications from server state to true RESTful APIs.",
        "items": [
          "MVC",
          "PHP",
          "Laravel",
          "CodeIgniter",
          "Ruby on Rails",
          "JSP"
        ]
      },
      {
        "name": "Identity",
        "text": "One sign-in for every app, with roles that match how your organisation works.",
        "items": [
          "Passkeys (WebAuthn)",
          "OIDC",
          "Single sign-on",
          "Google sign-in",
          "Magic links",
          "Role hierarchies",
          "Central identity service"
        ]
      },
      {
        "name": "Payments and ticketing",
        "items": [
          "Stripe",
          "Box office",
          "Events",
          "Bookings"
        ]
      },
      {
        "name": "Integrations",
        "items": [
          "Social media hooks",
          "Webhooks",
          "Media pipelines",
          "Third-party feeds"
        ]
      },
      {
        "name": "AI",
        "text": "LLM features behind a provider you can swap, with privacy designed into the schema.",
        "items": [
          "LLM features",
          "Swappable provider interface",
          "Privacy by schema"
        ]
      },
      {
        "name": "DevSecOps",
        "items": [
          "GitHub Actions",
          "Automated deploys",
          "Dependency patching",
          "Content Security Policy",
          "Security headers",
          "Secrets management",
          "pm2",
          "Docker",
          "Monitoring",
          "Health checks"
        ]
      },
      {
        "name": "Hosting",
        "text": "Several production apps on one small box.",
        "items": [
          "Linux VPS",
          "nginx",
          "Vercel",
          "Neon",
          "Google Cloud",
          "Managed Postgres",
          "Backblaze B2",
          "Object storage behind a CDN"
        ]
      },
      {
        "name": "Cloudflare",
        "items": [
          "DNS",
          "CDN",
          "Caching",
          "TLS",
          "Edge protection"
        ]
      },
      {
        "name": "DNS and email",
        "text": "Your domain cannot be spoofed, and your mail arrives.",
        "items": [
          "DNS management",
          "Domain migrations",
          "SPF",
          "DKIM",
          "DMARC to p=reject",
          "BIMI",
          "MTA-STS",
          "Mail forwarding",
          "Mailing lists",
          "Transactional email"
        ]
      },
      {
        "name": "Home and business automation",
        "text": "Devices from different makers, working together on a small computer you own.",
        "items": [
          "Home Assistant",
          "Docker",
          "Zigbee",
          "MQTT",
          "433 MHz radio",
          "Presence sensors",
          "Heating control",
          "Dashboards"
        ]
      },
      {
        "name": "Network",
        "items": [
          "Reverse proxies",
          "TLS",
          "Private networking",
          "VPN (Tailscale)",
          "Network design"
        ]
      },
      {
        "name": "Policy and governance",
        "text": "I write the policy as well as the code.",
        "items": [
          "Data protection by design",
          "Accessibility",
          "Security policy",
          "Safeguarding",
          "Regulatory compliance"
        ]
      }
    ]
  },
  "services": {
    "index": {
      "name": "Services",
      "title": "Automation, data, IT and web services",
      "description": "What you can hire me for in Portsmouth and the South Coast: home and business automation, data analysis, IT and AI advice, web apps and websites.",
      "lede": "Practical help for your home, charity or business. We start with what you need, then find an approach that fits your people and your budget."
    },
    "headings": {
      "for": "Who it is for",
      "get": "What you get",
      "how": "How it works",
      "cost": "What it costs to run"
    },
    "pricing": "I quote each job up front. Tell me what you need and I will tell you what it costs to build and what it costs to run.",
    "items": [
      {
        "slug": "home-and-business-automation",
        "image": {
          "src": "img/automation.webp",
          "alt": "Illustration of a house and a shop in cross-section, with lights, a radiator and a sensor all linked to one small computer inside.",
          "width": 1200,
          "height": 800
        },
        "name": "Home and business automation",
        "title": "Home automation, Portsmouth",
        "description": "Home Assistant home and business automation in Portsmouth and the South Coast. Local control, hardware you own, installed and supported by me.",
        "lede": "Make your home or workplace more comfortable and efficient, with heating, lights and devices that work around your routine. We choose what would be useful together, and I help you feel confident using it. In Portsmouth and along the South Coast.",
        "for": [
          "Homes and small businesses in Portsmouth and along the South Coast that want their lights, heating and sensors to work together, without depending on one company's app.",
          "It suits you if you want simpler everyday routines, more control over your heating, or help getting the devices you already own to work together."
        ],
        "get": [
          "A free consultation visit and a quote, on the mainland within 30 miles of Portsmouth.",
          "Home Assistant, on a small computer in your building. It is free and open source.",
          "The hardware sourced for you, or advice on what to buy yourself.",
          "Your devices installed and your network set up.",
          "The automations you want, programmed and tested with you.",
          "The controls you want: a web dashboard, Apple Home, Google Home or Alexa."
        ],
        "how": [
          "I visit your home or business, look at what you already have and what you want it to do, and give you a quote. I choose devices that work locally wherever I can, and I tell you which ones do not.",
          "After that, the hardware and the code are yours to change yourself. Or you can retain me for £15 a month. If an automation stops working, send me a message and I fix it remotely, and I apply the Home Assistant updates for you. New automations and changes are quoted separately.",
          "I run all of this in my own house, so I know where it goes wrong."
        ],
        "cost": [
          "The software is free. You pay for the hardware, once, and you choose it on price because it does not have to come from one maker.",
          "Apple Home works locally with no subscription. Google Home and Alexa connect through Home Assistant Link, a separate subscription you pay to its makers, Nabu Casa. It costs £6.50 a month, or £65 a year billed annually. Those two are cloud services themselves, so commands given through them leave your building.",
          "Support is optional, at £15 a month for remote fixes and updates."
        ],
        "extra": [
          {
            "heading": "Why Home Assistant, and when I would suggest Rako",
            "paragraphs": [
              "Home Assistant is free and open source, and it runs on a small computer in your building. The devices can come from any maker and talk over any of the common radios, so you choose them on price and on what they do, not from one catalogue, and what you already own is usually kept rather than thrown away. That is what keeps an installation affordable, and it is why I recommend it for most homes, small businesses and charities.",
              "The computer itself need not be yours already. If you do not have one, a Raspberry Pi does the job and costs less than a single designer light fitting. I will help you order the right one for your home. It is yours from the day it arrives: it runs your home, and if you like, it can run other things too, from a music server to a child's first programming project.",
              "A charity gets the same benefit: a one-off cost for hardware it owns, no licence to renew, and nothing tied to one supplier or to me. When trustees or volunteers change, the system stays understandable and another installer can pick it up.",
              "Rako is a British lighting control system with its own hardware, fitted by trained installers. It costs more, because everything comes from one maker. If you want Rako, I can quote for it. For most people who want an affordable installation, Home Assistant does the job well, and the work I show on this site is built on it."
            ],
            "links": [
              {
                "text": "How smart devices talk to each other, and why it matters",
                "href": "/notes/zigbee-thread-wifi-explained"
              }
            ]
          }
        ],
        "questions": [
          {
            "question": "What does the £15 a month cover?",
            "answer": "Remote fixes when an automation I installed stops working, and applying the Home Assistant updates so that an update does not catch you out. Faults caused by your own edits, new automations, changes and site visits are not included. I quote those separately, so you know the price first."
          },
          {
            "question": "Do I have to replace the devices I already have?",
            "answer": "It works with devices from many makers. I check yours before I start and tell you which can stay."
          },
          {
            "question": "What happens if the internet goes down?",
            "answer": "The computer is in your building, so devices that talk to it directly keep working. Devices that depend on their maker's own service wait until it comes back."
          },
          {
            "question": "What happens if you stop supporting it?",
            "answer": "Nothing stops working. The hardware and the code are yours, the software is widely used and open source, and another installer can pick it up."
          },
          {
            "question": "How do you fix things if the system is local?",
            "answer": "If you retain me, I connect over a private, encrypted link, only with your permission. Nothing is opened to the public internet. It needs Home Assistant on its own computer, such as a Raspberry Pi."
          },
          {
            "question": "Do you cover my area?",
            "answer": "I work across Portsmouth and the South Coast. Consultation visits are free on the mainland within 30 miles of Portsmouth. The Isle of Wight costs extra, because of the ferries. Further along the coast, ask me."
          }
        ],
        "work": [
          "my-own-house"
        ],
        "technical": {
          "paragraphs": [
            "Home Assistant in Docker, with devices over Zigbee, MQTT and 433 MHz radio. Apple Home through the HomeKit Bridge, which stays on your network. Remote support is over SSH or Tailscale, with your permission, and needs Home Assistant on its own computer or a Raspberry Pi."
          ],
          "page": "home-assistant"
        }
      },
      {
        "slug": "business-data-analysis",
        "image": {
          "src": "img/data-analysis.webp",
          "alt": "Illustration of untidy stacks of paper and spreadsheets narrowing down into one clear bar chart.",
          "width": 1200,
          "height": 800
        },
        "name": "Data analysis and research",
        "title": "Business data analysis, Portsmouth",
        "description": "Business data analysis for Portsmouth and South Coast firms. I turn your sales, customer and operations records into plain answers you can act on.",
        "lede": "What would you like your data to help you understand? I work with charities and businesses to turn records, surveys and spreadsheets into clear findings you can use. In Portsmouth, along the South Coast and across the UK.",
        "for": [
          "Businesses and organisations with records nobody has time to read: sales, customers, bookings, stock, staff or survey results.",
          "It suits you if you have a question you keep guessing at, or a monthly report that takes someone days to put together."
        ],
        "get": [
          "Your question turned into something the data can answer.",
          "Your records cleaned up and joined together, however many there are.",
          "Findings in plain English, with the charts and the method there to check.",
          "A dashboard, when you need to keep watching the numbers.",
          "A repeatable process, so next month's report does not take days."
        ],
        "how": [
          "We start with the decision you have to make. I look at what you hold and tell you plainly what it can and cannot answer.",
          "I do the analysis, check the figures a second way and write up what they mean. If you need it again, I turn it into a tool that runs itself."
        ],
        "cost": [
          "A one-off analysis has no running cost. A dashboard is a small web app, and I keep it cheap to run."
        ],
        "questions": [
          {
            "question": "Have you done this before?",
            "answer": "My largest analysis so far covers a whole university's survey results, and it was running within three hours of them being published. Another turned about 6,700 old files into an archive anyone can search. The method is the same for business records."
          },
          {
            "question": "Is our data safe with you?",
            "answer": "I hold only what the job needs and delete it afterwards if you want. Sensitive data can be analysed on my own computer, with no outside AI service involved. I have held a senior role covering data protection."
          },
          {
            "question": "What if our data is a mess?",
            "answer": "It usually is. Cleaning it up is part of the job, and I will tell you what could not be saved."
          }
        ],
        "work": [
          "survey-analysis-dashboard",
          "geraldlarner-com"
        ],
        "technical": {
          "paragraphs": [
            "I work in Python and R, and write bespoke analysis tools when the standard ones do not fit. Figures are recomputed independently by tests before anything goes out."
          ]
        },
        "summary": "Make sense of your records and surveys, with clear findings to help you decide what to do next."
      },
      {
        "slug": "it-and-ai-consultancy",
        "image": {
          "src": "img/advice.webp",
          "alt": "Illustration of a branching path with several routes, one marked in amber and leading to a flag.",
          "width": 1200,
          "height": 800
        },
        "name": "IT, infrastructure and governance",
        "title": "IT and governance, Portsmouth",
        "description": "Friendly IT, infrastructure and governance support for charities and businesses in Portsmouth and the South Coast, with clear advice in plain English.",
        "lede": "A sounding board for the decisions, and practical help with the systems behind your work. I support charities and businesses with IT, infrastructure, data protection and governance, explaining the choices in plain English. In Portsmouth, along the South Coast and remotely across the UK.",
        "for": [
          "Small businesses, charities and schools with nobody whose job is IT, or with someone who would like a second opinion.",
          "It suits you if you are being sold something you cannot judge, or if your staff are already pasting work into AI tools and nobody has decided whether they should."
        ],
        "get": [
          "A plain review of your systems, your network and what they cost you.",
          "Help planning and looking after infrastructure: the servers, hosting and connections your organisation relies on.",
          "Help choosing and buying software, and a second opinion on quotes.",
          "Honest advice on where AI would help you and where it would not.",
          "A clear answer on where your data goes when staff use AI tools.",
          "Support with governance, data protection and regulatory compliance, including policies your team can understand and use."
        ],
        "how": [
          "We talk it through and I look at what you have. You get a short written plan, in order of what matters most, that you can follow with me or without me.",
          "I’ve worked with charities throughout my adult life, supporting people with a wide range of IT skills and confidence. We work at a pace that suits your team, with time for questions and explanations. My experience as a senior academic and charity trustee helps me consider the people, policies and systems together."
        ],
        "cost": [
          "Advice has no running cost. Where I recommend something that does, I tell you what it costs each year before you decide."
        ],
        "questions": [
          {
            "question": "Should we be using AI?",
            "answer": "Sometimes. It is good at drafting, summarising and sorting large amounts of text, and someone still has to check the result. I will tell you where it would save you time and where it would not."
          },
          {
            "question": "Can we use AI without sending our data to another company?",
            "answer": "Often, yes. Some AI can run on a computer you own. It suits some jobs and not others, and I will tell you which yours is."
          },
          {
            "question": "Do you only advise charities?",
            "answer": "No. I'm a charity trustee, so I know how far the money has to go, and I work with businesses and schools as well."
          }
        ],
        "work": [
          "survey-analysis-dashboard",
          "solent-gay-mens-chorus"
        ],
        "technical": {
          "paragraphs": [
            "For private AI work I have used local models through Ollama, with output checked and scanned for personal details."
          ]
        },
        "summary": "Get your systems working reliably, protect your information and put practical policies in place."
      },
      {
        "slug": "web-apps-and-booking",
        "image": {
          "src": "img/web-apps.webp",
          "alt": "Illustration of a booking screen on a laptop and a phone, with one calendar slot picked out in amber.",
          "width": 1200,
          "height": 800
        },
        "name": "Web applications",
        "title": "Web applications, Portsmouth",
        "description": "Bespoke web applications and booking systems for Portsmouth and South Coast organisations. Designed with the people who use them, built and run by me.",
        "lede": "When off-the-shelf software does not fit, I build what does: bookings, sign-ins, records and the screens your staff use to run them. From Portsmouth, for the South Coast and the UK.",
        "for": [
          "Organisations with a job that off-the-shelf software does not fit: a school, a university department, a charity, a small business.",
          "For example a booking system, a members' area, a marking system or a private archive."
        ],
        "get": [
          "A system designed from research with the people who will use it.",
          "Sign-in that matches how your organisation works, with the right access for each role.",
          "Bookings, payments and tickets, when you need them.",
          "The data you already have, moved in safely.",
          "A record of who did what, when the job needs one.",
          "Screens built so that people with disabilities can use them, from the first page."
        ],
        "how": [
          "I talk to the people who will use it and watch how they work. I build an early version, test it with them and change it until it fits.",
          "Then I host it, keep it safe and keep it running."
        ],
        "cost": [
          "The running cost depends on how many people use it and how much it has to store. I size each system to run fast on modest hardware."
        ],
        "questions": [
          {
            "question": "How long does a web app take to build?",
            "answer": "It depends on the size of the job. We agree the scope and priorities together, and I check and test the work before handing it over. Tell me what you need and I will give you a date before I start."
          },
          {
            "question": "Can it work with the systems we already have?",
            "answer": "Usually. I connect new systems to existing ones, bring in old data, and set up sign-in with the accounts your people already use."
          },
          {
            "question": "Who owns the system?",
            "answer": "You do. I use standard, widely used tools. If you ever move on, you take everything with you."
          }
        ],
        "work": [
          "sums",
          "student-feedback-platform",
          "photo-archive-for-a-school",
          "asica"
        ],
        "technical": {
          "paragraphs": [
            "15 years of JavaScript, 10 of PHP, 10 of Apache and 3 of JSP. I support the frameworks I use, and Java and C as well. Databases: MariaDB, MySQL, Postgres and SQLite. Semantic, accessible HTML throughout."
          ],
          "page": "passkeys-and-single-sign-on"
        },
        "summary": "Make bookings, records and everyday tasks easier for your staff and the people you support."
      },
      {
        "slug": "websites-you-can-update",
        "name": "Websites you can update yourself",
        "title": "Small business websites, Portsmouth",
        "description": "A small business website you update yourself, from a simple editing screen. Designed, built and run by me for Portsmouth and the South Coast.",
        "lede": "A website your own team can change. You edit the words and pictures from a simple editing screen. I design it, build it and keep it running.",
        "for": [
          "Small businesses, sole traders, clubs and community groups who want a proper website and want to change it themselves.",
          "It suits you if you are tired of waiting for someone else to make a small change, or if your current site is broken and nobody knows how to fix it."
        ],
        "get": [
          "A website designed around what your customers need to find.",
          "A simple editing screen for the words and pictures.",
          "Pages that work on phones, on slow connections and with screen readers.",
          "Your email set up so nobody can send fakes from your address.",
          "Friendly support when something needs changing or fixing."
        ],
        "how": [
          "I start by talking to you and to the people who will use the site. I design it around what they need, build it and test it with them. Then I show you how to edit it.",
          "After launch I keep the software up to date and the site running."
        ],
        "cost": [
          "A small site is cheap to run. I keep things small, so pages load fast and the hosting bill stays low."
        ],
        "questions": [
          {
            "question": "How do I update the website?",
            "answer": "You sign in and change the words and pictures from an editing screen. You do not need to know any code, and nobody has to phone a developer."
          },
          {
            "question": "Who owns the website?",
            "answer": "You do. I use standard, widely used tools. If you ever move on, you take everything with you."
          },
          {
            "question": "How long does a website take?",
            "answer": "It depends on the size of the job. We agree the scope and priorities together, and I check and test the work before handing it over. Tell me what you need and I will give you a date before I start."
          }
        ],
        "work": [
          "alicedennis-net",
          "morganharnett-tattoo",
          "solent-gay-mens-chorus"
        ]
      },
      {
        "slug": "charities",
        "name": "IT and governance support for charities",
        "title": "Charity IT support, Portsmouth",
        "description": "Friendly charity IT support in Portsmouth and the South Coast: infrastructure, data, governance and websites, from an experienced charity trustee.",
        "lede": "Technology should help your charity do its work. I support staff, volunteers and trustees with IT, infrastructure, data and governance, taking time to explain things in a way that works for your team.",
        "for": [
          "Charities and community groups with staff, volunteers and trustees who have different levels of confidence with IT.",
          "You might need help with unreliable systems, a data question, clearer policies or a website your team can manage. You can also ask for a second opinion before making a decision."
        ],
        "get": [
          "A review of what you have, with a practical plan that fits your people and budget.",
          "Help with IT and infrastructure: hosting, networks, access and keeping systems running.",
          "Data analysis and research to help you understand your work and make decisions.",
          "Support with governance, data protection and policies your team can understand and use.",
          "Accessible websites your staff and volunteers can update, with bookings or ticket sales where needed.",
          "Patient explanations and documentation to help people feel confident using what we put in place."
        ],
        "how": [
          "We start with a conversation about your charity, your people and what is getting in the way. You do not need a technical brief.",
          "I’ve worked with charities throughout my adult life and I’m a charity trustee myself. We agree priorities and costs, involve the people who will use the systems, and work at a pace that suits your team.",
          "You can ask for advice, practical implementation or ongoing care. I explain the options before you decide."
        ],
        "cost": [
          "I keep things small, so running costs stay low. One charity I work with runs its website, ticket sales, members' area and sign-in on a single small server."
        ],
        "questions": [
          {
            "question": "Can you help our charity with IT, even if we do not need a website?",
            "answer": "Yes. I can help with your systems and infrastructure, data analysis, governance and data protection. We start with what you need, whether that is a second opinion, a practical fix or a longer piece of work."
          },
          {
            "question": "Some of our volunteers are not confident with technology. Is that a problem?",
            "answer": "No. I have supported people with a wide range of IT skills throughout my adult life in charity work. I take time to listen, explain and test things with the people who will use them."
          },
          {
            "question": "What does a charity website cost?",
            "answer": "It depends on what it has to do. A few pages of information cost far less than ticket sales and a members' area. I quote each job up front. Tell me what you need and I will give you a price to build it and a price to run it."
          },
          {
            "question": "Can our volunteers update it?",
            "answer": "Yes. They change the words and pictures from a simple editing screen. Nobody has to phone a developer."
          },
          {
            "question": "What happens if you are not available?",
            "answer": "Everything I build is tested and written down well enough for someone else to take over. I use standard, widely used tools, so another developer can pick it up."
          }
        ],
        "work": [
          "solent-gay-mens-chorus"
        ],
        "summary": "Support for your people, systems and trustees, from someone who understands charity life."
      },
      {
        "slug": "payments-and-tickets",
        "name": "Payments and ticket sales",
        "title": "Take payments and sell tickets online",
        "description": "Take card payments, sell tickets and take bookings on your own website. Built for choirs, groups and small businesses in Portsmouth and the South Coast.",
        "lede": "Take card payments, sell tickets and take bookings on your own website, under your own name.",
        "for": [
          "Choirs, theatres, community groups, clubs and small businesses who want to sell on their own site and not send people somewhere else."
        ],
        "get": [
          "Card payments on your own website.",
          "Ticket sales and a box office for your events.",
          "Bookings.",
          "Event pages your team adds and changes themselves."
        ],
        "how": [
          "I set up the payment side with an established card payment company. Card details go to them and not to your website.",
          "I build the pages your customers see and connect them to your events and your records."
        ],
        "cost": [
          "The card payment company takes a fee from each payment, and publishes its fees. On top of that there is the hosting, which I keep low."
        ],
        "questions": [
          {
            "question": "Is it safe to take card payments on our own website?",
            "answer": "Yes. Card details go straight to the card payment company. Your website never sees or stores them."
          },
          {
            "question": "Can we sell tickets for our own events?",
            "answer": "Yes. I built the ticket sales and box office for a choir, on the choir's own website."
          }
        ],
        "work": [
          "solent-gay-mens-chorus"
        ]
      },
      {
        "slug": "research-and-data-analysis",
        "name": "Surveys and research",
        "title": "Survey design and research studies",
        "description": "Survey design and research studies for Portsmouth and South Coast organisations. Findings in plain English you can act on, not another spreadsheet.",
        "lede": "I plan the study, run it, analyse the results and report them plainly. Large amounts of data included. You get answers you can read, not another spreadsheet.",
        "for": [
          "Organisations with a question and the data that could answer it: survey results nobody has had time to read, records that have outgrown a spreadsheet, a service you want to evaluate."
        ],
        "get": [
          "A study or survey designed to answer your question.",
          "The analysis done, however much data there is.",
          "Findings written in plain English, for the people who have to act on them.",
          "A dashboard, when you need to keep watching the numbers.",
          "Analysis tools written for your data, when the usual ones do not fit."
        ],
        "how": [
          "We start with what you need to know. I work out what data would answer it: what you already hold, and what needs collecting. I run the survey or study, analyse the results and write up what they mean.",
          "My own research is peer-reviewed and published."
        ],
        "cost": [
          "A one-off study has no running cost. A dashboard or an analysis tool is a small web app. I host it and keep it running like any other."
        ],
        "questions": [
          {
            "question": "Can you work with data we already have?",
            "answer": "Yes. Send me what you hold and what you want to know. I'll tell you plainly what it can and cannot answer."
          },
          {
            "question": "How much data can you handle?",
            "answer": "Large amounts. One tool I built covers a whole institution's survey results. It was running within three hours of the results being published."
          },
          {
            "question": "What do we get at the end?",
            "answer": "A report in plain English that says what was found. The charts, the numbers and the method are there for anyone who wants to check."
          }
        ],
        "work": [
          "survey-analysis-dashboard",
          "student-feedback-platform",
          "asica"
        ],
        "technical": {
          "paragraphs": [
            "I work in Python and R, and I write bespoke analysis tools when the standard ones do not fit. The output is still something a person can read."
          ]
        }
      },
      {
        "slug": "accessibility-and-user-research",
        "name": "Accessibility and user research",
        "title": "Accessible websites and user research",
        "description": "Accessible websites and user research in Portsmouth and the South Coast, from a designer with a doctorate in how people use software.",
        "lede": "I find out what your people need before I build, and I make sure everyone can use the result. This is what I trained in: my doctorate is in how software should adapt to the person using it.",
        "for": [
          "Organisations whose website or app has to work for everyone: the public, patients, students, staff, and people who use a screen reader or only a keyboard."
        ],
        "get": [
          "Interviews and observation with the people who will use it.",
          "Designs tested with those people, before and after they are built.",
          "Websites and apps built to the recognised accessibility standard from the start.",
          "A plain list of what to fix on a site you already have."
        ],
        "how": [
          "I talk to the people who will use it and watch how they work. I turn what I learn into designs, and test those with the same people. I have done this with students, university staff and NHS patients.",
          "When I build, accessibility is part of the work from the first page. It is not a check at the end."
        ],
        "cost": [
          "Accessibility is part of how I build, not an extra. Research takes time with real people, so its cost depends on how many people and how many rounds of testing."
        ],
        "questions": [
          {
            "question": "What accessibility standard do you build to?",
            "answer": "The current international standard for accessible websites, at the level called AA. Every page is checked by automated tests before it goes live, and I check by hand that it works with a keyboard and a screen reader."
          },
          {
            "question": "What is user research?",
            "answer": "Finding out what people need by asking them and watching them work, before deciding what to build. Then testing what gets built with the same people."
          }
        ],
        "work": [
          "asica",
          "student-feedback-platform"
        ],
        "technical": {
          "paragraphs": [
            "I build to WCAG 2.2 AA. This site is tested against it with axe on every change, with JavaScript off, by keyboard and at 320px."
          ]
        }
      },
      {
        "slug": "email-security",
        "name": "Email security",
        "title": "Stop people faking your email address",
        "description": "Stop people sending fake email from your address. For organisations in Portsmouth, along the South Coast and UK-wide. No new email provider needed.",
        "lede": "Anyone can send an email that claims to come from your address, unless your domain name says otherwise. I set it up so fakes are rejected and your real email still arrives.",
        "for": [
          "Any organisation that sends email from its own domain name: charities, schools, small businesses.",
          "It matters most if you send invoices, appeals for money or anything else a fraudster would like to copy."
        ],
        "get": [
          "A check of how your email is set up today.",
          "Every service that sends email in your name found and set up properly.",
          "Fakes rejected by the systems that receive them, not just marked as suspicious.",
          "Your own email still arriving."
        ],
        "how": [
          "I look up how your domain name is set up today. I find everything that sends email in your name: your mailbox provider, your website, your newsletter tool. I set each one up to sign its messages.",
          "Then I tighten the rules in stages, reading the reports as I go, until fakes are rejected."
        ],
        "cost": [
          "Nothing extra each month. The settings live in the records for your domain name, which you already pay for. The work is done once, then checked whenever you add a new service that sends email."
        ],
        "questions": [
          {
            "question": "How do I know if our email address can be faked?",
            "answer": "Send me your domain name. The settings are public, so I can look them up and tell you what I find."
          },
          {
            "question": "Will it stop our own email arriving?",
            "answer": "No. That is why I do it in stages. I make sure every service that sends for you is set up before fakes are rejected."
          },
          {
            "question": "Do we need to change email provider?",
            "answer": "No. It works with the email provider you already use."
          }
        ],
        "work": [
          "solent-gay-mens-chorus"
        ],
        "technical": {
          "paragraphs": [
            "The standards are SPF, DKIM and DMARC. I take domains to DMARC p=reject with DKIM aligned."
          ],
          "page": "email-authentication"
        }
      },
      {
        "slug": "hosting-and-care",
        "name": "Hosting and care",
        "title": "Website hosting and care",
        "description": "Website hosting and care in Portsmouth and the South Coast, with software kept current and friendly support from someone who knows your setup.",
        "lede": "I host what I build and look after it. The software is kept up to date, everything that does not need to be open is closed, and you have someone familiar with your systems to ask for help.",
        "for": [
          "Organisations that want their website looked after by the person who built it, not passed between a designer, a developer and a hosting company."
        ],
        "get": [
          "Hosting on a server I run, or with a hosting company you choose.",
          "Software kept up to date.",
          "Everything that does not need to be open, closed.",
          "Your domain name and email settings looked after.",
          "Support from someone familiar with your setup when something needs fixing."
        ],
        "how": [
          "I do the design, the building, the hosting and the email myself. Every change is tested before it goes live.",
          "I keep the software underneath on current versions, so an upgrade never grows into a project of its own."
        ],
        "cost": [
          "I keep things small, so the hosting bill stays low. Several of the systems I run share one small server."
        ],
        "questions": [
          {
            "question": "Who owns my website?",
            "answer": "You do. I use standard, widely used tools. If you ever move on, you take everything with you."
          },
          {
            "question": "What happens if you are unavailable?",
            "answer": "Everything I build is tested and written down well enough for someone else to take over. I use standard, widely used tools, so another developer can pick it up."
          },
          {
            "question": "Can I move my website somewhere else later?",
            "answer": "Yes. Nothing I build is tied to one hosting company."
          }
        ],
        "work": [
          "solent-gay-mens-chorus",
          "alicedennis-net",
          "geraldlarner-com"
        ]
      },
      {
        "slug": "moving-off-wordpress",
        "name": "Moving off WordPress",
        "title": "Moving your website off WordPress",
        "description": "Moving your website off WordPress, with content and web addresses kept. A smaller site your team can edit. Portsmouth, the South Coast and UK-wide.",
        "lede": "WordPress is widely used and suits many organisations. If yours has become slow, hard to update or a worry to keep secure, I can move it to something smaller that your team can still edit.",
        "for": [
          "Organisations whose WordPress site has become hard to live with: updates that break things, add-ons nobody remembers installing, pages that load slowly.",
          "If your site works and you are happy with it, stay where you are. I will tell you so."
        ],
        "get": [
          "Your pages, posts and pictures moved across.",
          "A simple editing screen your team can use.",
          "Fewer moving parts, so there is less to update and less to go wrong.",
          "Your web addresses kept or redirected, so existing links still work."
        ],
        "how": [
          "I look at what your site does today and what your team needs from it. I build the new site alongside the old one, move the content across and check it with you.",
          "Then I switch over, with the old addresses pointing to the new pages."
        ],
        "cost": [
          "A smaller site has less to host and less to look after."
        ],
        "questions": [
          {
            "question": "Do we have to leave WordPress?",
            "answer": "No. It is widely used and suits many organisations. Moving makes sense when the site has become slow, hard to update or hard to keep secure. If it has not, I will say so."
          },
          {
            "question": "Will we lose our content?",
            "answer": "No. I move your pages, posts and pictures across and check them with you before the switch."
          },
          {
            "question": "Will our old links still work?",
            "answer": "Yes. I keep your web addresses the same where I can and redirect the old ones where I cannot."
          }
        ],
        "work": [
          "alicedennis-net",
          "geraldlarner-com"
        ],
        "technical": {
          "page": "legacy-app-modernisation"
        }
      }
    ]
  },
  "work": {
    "heading": "Work",
    "intro": "A charity platform, small-business sites on custom CMSs, university systems and a public archive.",
    "plainIntro": "A choir, a music teacher, a tattoo artist and my own home: practical technology shaped around the people using it.",
    "index": {
      "name": "Work",
      "title": "Portfolio: work I have built and run",
      "description": "My portfolio, from Portsmouth: automation in my own house, data analysis, web apps and websites for a charity, businesses, a university and a school.",
      "lede": "Automation, data analysis, web applications and websites. Each one built and run by me, from Portsmouth."
    },
    "projects": [
      {
        "slug": "solent-gay-mens-chorus",
        "name": "Solent Gay Men's Chorus",
        "title": "SGMC: tools that work for volunteers",
        "description": "A website, ticket sales and member tools for Solent Gay Men's Chorus, with shared sign-in and an editing system the committee can use itself.",
        "published": "2026-10-02",
        "url": "https://sgmc.org.uk",
        "kind": "A bespoke website and connected applications for a volunteer-run choir.",
        "plain": "A website the committee can edit, ticket sales and practical tools for members. One connected platform for the people who keep a choir running.",
        "flagship": true,
        "sections": [
          {
            "heading": "Built around the people running the choir",
            "paragraphs": [
              "A choir has several audiences: people thinking of joining, audiences buying tickets, members preparing for rehearsals, and the volunteers keeping everything organised. Each needs a clear way to do their part.",
              "I built a connected set of tools for Solent Gay Men's Chorus, with a public website, an editing system, ticket sales and a members' area."
            ]
          },
          {
            "heading": "A website the committee can look after",
            "paragraphs": [
              "The committee can update pages, share news and advertise concerts through an editing system. Concert pages have their own pictures and descriptions when shared in a message.",
              "Tickets are paid for through a card payment service, which charges its own fees; the application does not add a separate ticketing platform between the chorus and its customers."
            ]
          },
          {
            "heading": "Everyday jobs in one place",
            "paragraphs": [
              "Members can report a rehearsal absence, give their availability for concerts, update their details and request uniform. The choir's music application brings together set lists, scores and learning tracks.",
              "A shared sign-in service supports email links and passkeys. Access depends on the person's role, so member information and committee tools have different permissions."
            ]
          },
          {
            "heading": "What this makes possible",
            "paragraphs": [
              "The platform gives the choir ways to manage its own information and routine tasks, with the website and member tools connected rather than treated as separate jobs.",
              "If you help run a charity, the starting point can be just as practical: one task that takes too much chasing, or information people struggle to find. We can start there."
            ]
          }
        ],
        "facts": [
          "Payload CMS on Next.js, with PostgreSQL and a separate Vite public frontend.",
          "A shared Node.js and SQLite identity service supports magic links, passkeys and role-based access.",
          "The member portal integrates with the identity service and CMS for profiles, absences, availability and uniform requests.",
          "Stripe checkout and signed payment webhooks support ticket orders.",
          "Public content is prerendered for search engines and link previews. GitHub Actions workflows define builds and deployment.",
          "The interfaces include skip navigation, labelled controls and reduced-motion support."
        ]
      },
      {
        "slug": "geraldlarner-com",
        "name": "geraldlarner.com",
        "title": "geraldlarner.com: a public archive",
        "description": "How about 6,700 old word-processor files became geraldlarner.com, a free public archive of programme notes on 445 composers that anyone can search.",
        "published": "2026-10-02",
        "url": "https://geraldlarner.com",
        "kind": "A public, searchable archive, built from a pile of old files.",
        "plain": "About 6,700 old word-processor files, turned into a free public archive that anyone can search. It holds 5,388 programme notes on 445 composers.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "Gerald Larner (1936 to 2018) was a music critic. Over five decades he wrote notes for concert programmes. The archive makes them free to performers, students and listeners."
            ]
          },
          {
            "heading": "What I started with",
            "paragraphs": [
              "About 6,700 old word-processor files, in folders by composer. They were in several old formats, some of which today's software cannot open."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A set of steps that reads every file, whatever its format, and pulls out the writing. It works out which composer and which piece of music each note is about. It sets aside the files that are not notes at all, such as indexes and logs.",
              "Where the steps could not be sure, I decided by hand and recorded the decision. The whole archive can be rebuilt from the files and come out the same.",
              "A report lists every entry that still needs a human eye. It now lists none.",
              "Then the website: a page for each composer and each piece, and a search across every word.",
              "The site is small and quick. The pages are made in advance, so the server has very little to do when someone asks for one."
            ]
          },
          {
            "heading": "What it does",
            "paragraphs": [
              "Writing that sat in old files can now be read and searched by anyone: 5,388 notes on 3,522 pieces of music by 445 composers."
            ]
          },
          {
            "heading": "Where it is now",
            "paragraphs": [
              "It has been public since May 2026."
            ]
          }
        ],
        "facts": [
          "About 6,700 legacy word-processor files: WordPerfect, RTF (including old Nisus RTF) and Word.",
          "A Python pipeline converts them with headless LibreOffice, with its own parser for the files LibreOffice cannot read, then classifies each as a work, an essay or source material.",
          "Manual corrections are keyed by file path, so a rebuild is repeatable.",
          "5,388 notes on 3,522 works by 445 composers.",
          "A thin Express server over one SQLite file of pre-rendered pages, with full-text search and a JSON API."
        ]
      },
      {
        "slug": "alicedennis-net",
        "name": "Alice Dennis",
        "title": "Alice Dennis: a site she looks after",
        "description": "A website for a piano and singing teacher, with clear lesson pages, an enquiry form and an editing area for updating text and photos herself.",
        "published": "2026-10-02",
        "url": "https://alicedennis.net",
        "kind": "A small, bespoke website and editing system for a music teacher.",
        "plain": "Clear lesson pages, a way to enquire and an editing area for changing words and photos. A website built around the needs of a music teacher.",
        "sections": [
          {
            "heading": "Make the next step clear",
            "paragraphs": [
              "For someone looking for piano or singing lessons, a website should answer a few straightforward questions: what is offered, who the teacher is, where lessons happen and how to get in touch.",
              "I built Alice Dennis a site around those questions, with separate lesson pages, a gallery, directions and an enquiry form."
            ]
          },
          {
            "heading": "Routine changes without calling a developer",
            "paragraphs": [
              "An editing area lets Alice change the words, photos and reviews using an approved Google account. Lesson lengths and prices are entered once and reused wherever they appear.",
              "Photos are made smaller before they upload. If a page is changed in two editing windows, the site asks for a reload instead of silently overwriting the earlier change."
            ]
          },
          {
            "heading": "Look after the route to an enquiry",
            "paragraphs": [
              "Known page addresses from the previous site redirect to their replacements, so old links still have somewhere useful to go.",
              "The contact form checks for junk without treating every doubtful message as disposable. By default, a high spam score adds a warning to the email; clear bot signals and submission limits can still block a message."
            ]
          },
          {
            "heading": "The right size for a small business",
            "paragraphs": [
              "The result is a site with its own straightforward editing system and shared information that only needs changing in one place.",
              "If you work for yourself, your website should fit the way you run your business. You should be able to keep the important details up to date without learning a complicated system."
            ]
          }
        ],
        "facts": [
          "Express 5 serves complete HTML pages without a client framework or a build step.",
          "Content is stored in a validated JSON file, with uploaded images kept separately.",
          "Google sign-in is restricted to approved administrator accounts; writes require authentication and check the content revision.",
          "Browser-side WebP resizing reduces uploaded image sizes.",
          "Known page IDs from the previous site redirect to the corresponding new routes.",
          "The contact form combines a honeypot, signed timing cookie, rate limits and configurable spam scoring.",
          "Page templates include labelled form fields and a skip link; styling respects reduced-motion preferences."
        ]
      },
      {
        "slug": "morganharnett-tattoo",
        "name": "morganharnett.tattoo",
        "title": "morganharnett.tattoo: artist's site",
        "description": "morganharnett.tattoo is a tattoo artist's website. Its gallery fills itself from his Instagram, and clients book and pay a deposit on the site.",
        "published": "2026-10-02",
        "url": "https://morganharnett.tattoo",
        "kind": "Site and booking system for a tattoo artist, on a custom CMS written for the job.",
        "plain": "A site for a tattoo artist. It fills itself from his Instagram, so he updates one place. Clients ask for a tattoo, pick a time and pay a deposit on the site.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "A tattoo artist in Southsea, Portsmouth."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A site that fills itself from his Instagram. He posts his work there, and the site checks for new work four times a day and shows it.",
              "A booking system. A client describes the tattoo they want: the idea, where on the body and how big, with up to four reference photos. He reads it, and either declines or makes an offer.",
              "A client with an offer picks a time from the hours he is really free, and pays a deposit by card. The booking goes straight into his own calendar. Both of them get a confirmation, and a reminder goes out 48 hours before.",
              "Every picture has a written description for people who cannot see it. New pictures are described by AI, and he can rewrite any of them. Clients' names are kept out.",
              "It can be installed on a phone like an app."
            ]
          },
          {
            "heading": "What it does for him",
            "paragraphs": [
              "He updates one place. A request arrives with everything he needs to decide, and an accepted booking lands in his calendar without anyone retyping it."
            ]
          },
          {
            "heading": "Where it is now",
            "paragraphs": [
              "It has been live since October 2026."
            ]
          }
        ],
        "facts": [
          "It fills itself from Instagram, so the artist updates one place. The official Instagram API, synced every six hours in its own short-lived process.",
          "Booking flow: apply, offer, pick a slot, pay a deposit through Stripe Checkout. A slot is held for 35 minutes while the client pays.",
          "Availability is his working hours, minus his Apple Calendar over CalDAV, existing bookings and held slots.",
          "A Fastify API in TypeScript, run directly by Node with no server build step. State lives in one SQLite file.",
          "A React front end rendered on the server, so crawlers get real pages, then precached by a service worker as an installable PWA.",
          "Alt text for new images from Claude Haiku. The backlog was described locally with Ollama.",
          "Google sign-in for the admin. Deployed by GitHub Actions after tests."
        ]
      },
      {
        "slug": "my-own-house",
        "name": "My own house",
        "title": "A home that works with what you own",
        "description": "Lights, heating, buttons and sensors from different makers working together at home, with everyday controls and a movement logger built for my dog.",
        "published": "2026-11-01",
        "url": null,
        "kind": "A personal Home Assistant installation, integrating existing devices and bespoke applications.",
        "plain": "Lights, heating and sensors from different makers working together. My own home is also where I try ideas, find the awkward bits and improve them.",
        "sections": [
          {
            "heading": "Start with the home you have",
            "paragraphs": [
              "Useful home automation starts with what would make your day easier, and what equipment is already there.",
              "In my own home I connect lights, heating, buttons, sensors and speakers from different makers. Home Assistant runs on an existing laptop, rather than replacing everything with one brand's system. This is my personal installation, rather than a customer case study."
            ]
          },
          {
            "heading": "Controls that fit everyday life",
            "paragraphs": [
              "Lights respond to presence, daylight and time of day. Radiator valves use room readings from a separate wall thermostat. Away and holiday settings coordinate several devices.",
              "Physical buttons give me another way to control things. Using the home does not have to mean reaching for a phone every time."
            ]
          },
          {
            "heading": "What if nobody sells the thing you want?",
            "paragraphs": [
              "I wanted to see where my dog had been while I was out. Bramble Logger reuses the home's motion sensors, records selected monitoring sessions and lets me replay the activity on a three-dimensional house view.",
              "It shows a probable trail from sensor events. It cannot identify which animal triggered a sensor or guarantee an exact location. It is a useful example of building around a particular question, using hardware already in place."
            ]
          },
          {
            "heading": "Plan for the awkward bits",
            "paragraphs": [
              "The setup includes fault alerts and a rule to bring the old radio doorbell chime back into use when the connected setup loses internet or receiver health. The movement logger can also try to fill gaps from retained sensor history after reconnecting.",
              "Some of my devices still rely on their manufacturers' cloud services. I make that distinction clear: keeping control of your home includes understanding which parts need an internet connection and which parts work locally."
            ]
          },
          {
            "heading": "Make a useful first change",
            "paragraphs": [
              "You do not need a whole-house project to start. We can look at one room, one routine or devices you already own, and agree a practical first step. Any new hardware, subscriptions and ongoing support should be clear before you commit."
            ]
          }
        ],
        "facts": [
          "Home Assistant coordinates devices across Zigbee, radio, MQTT and manufacturer integrations.",
          "Automation rules combine presence, light levels, schedules, physical controls and away settings.",
          "Radiator valves receive temperature readings from a separate thermostat.",
          "Fault-monitoring rules and a backup radio-chime automation address specific failure conditions.",
          "Bramble Logger uses Node.js, Home Assistant events and retained history to record and replay movement sessions.",
          "Some integrations depend on cloud services. Motion-based location is an inference, not identification or precise tracking."
        ]
      },
      {
        "slug": "survey-analysis-dashboard",
        "name": "Survey analysis dashboard",
        "title": "Survey analysis dashboard",
        "description": "A dashboard of a university's National Student Survey results, down to each course. Running within three hours of the results. A faculty adopted it.",
        "published": "2026-10-02",
        "url": null,
        "kind": "National Student Survey analysis for a whole university. Adopted across a faculty. In use since July 2026.",
        "plain": "A dashboard of a whole university's National Student Survey results. It was running within three hours of the results being published. It shows each faculty, school and course what its students scored and what they wrote. A university faculty adopted it.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "A university faculty, which adopted it. It covers every faculty, school and course in the university."
            ]
          },
          {
            "heading": "The problem",
            "paragraphs": [
              "Every year, students across the UK answer the National Student Survey. The results are published as large spreadsheets.",
              "The published results are sorted by subject, not by course, and not by the school or faculty that runs the course. Somebody has to work out which numbers belong to whom before anyone can act on them."
            ]
          },
          {
            "heading": "The people",
            "paragraphs": [
              "Staff at the university who need to know how their own courses did, and what to do about it."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A dashboard that takes the published results and works through all of them. I had it running within three hours of the results being published.",
              "It sorts the results by faculty, school and course, so each person sees their own part. For each one it picks out the three things students rated highest and the three they rated lowest, and names the question behind each.",
              "It compares this year with last year. It flags any course that has fallen well below the university's own figure, or dropped sharply since last year, and says why it was flagged.",
              "It reads what students wrote as well as what they scored. It gathers the comments into themes and counts how many students raised each one. Across nine years of comments it shows which themes come up every year, which are new and which are fading.",
              "Each course, school and faculty gets a short written summary. The outcome is a page a person can read, not another spreadsheet."
            ]
          },
          {
            "heading": "Keeping it right and keeping it private",
            "paragraphs": [
              "Every average on the dashboard is worked out a second time by a separate check before it goes out.",
              "The AI that reads the comments and writes the summaries runs on my own computer. No outside AI service ever saw what students wrote.",
              "Staff sign in with their university account. The dashboard shows summaries and counts. Students' own words are shown only to the senior staff allowed to read them."
            ]
          },
          {
            "heading": "Where it is now",
            "paragraphs": [
              "It has been in use since July 2026, for that year's results. Next year's results go in the same way."
            ]
          }
        ],
        "facts": [
          "Running within three hours of the national results being published.",
          "Reads the Office for Students' National Student Survey workbooks and full-data extract directly.",
          "Rolls up institution, faculty, school and course, with year-on-year comparison when two years are loaded.",
          "Concern flags: five points below the institution's own figure, below 70% overall, or a fall of more than five points in a year.",
          "Nine years of tagged free-text comments (2018 to 2026) analysed deterministically for consistent, new and receding themes.",
          "A local model through Ollama handles the sentiment analysis and writes the per-unit narratives, so no cloud AI service saw student comments. Output is paraphrase and counts only, scanned for personal details.",
          "Node and vanilla JavaScript ES modules, with tokenised CSS. No framework.",
          "Google sign-in limited to the institution's domain, verified server-side, with a signed session cookie. Raw comments sit behind an allowlist of senior staff.",
          "The test suite recomputes every school and faculty mean and standard deviation independently, and renders every view in jsdom.",
          "nginx and pm2 on a VPS."
        ]
      },
      {
        "slug": "sums",
        "name": "SUMS",
        "title": "SUMS: university marking system",
        "description": "SUMS is a marking system for a university. Two markers grade each student project blind and every step is recorded. It has been in use since 2018.",
        "published": "2026-10-02",
        "url": null,
        "kind": "Single-blind double-marking platform for a university, with automated reconciliation.",
        "plain": "A marking system for a university. Two markers grade each student project without seeing each other's marks, and the system reconciles the two marks automatically. In use since 2018, with about 600 projects and 100 markers a year.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "A university, which uses it to mark student projects."
            ]
          },
          {
            "heading": "The people",
            "paragraphs": [
              "About 100 markers a year, and the students whose projects they mark: about 600 projects a year."
            ]
          },
          {
            "heading": "What they needed",
            "paragraphs": [
              "The university requires every student project to be marked twice, by two markers who do not see each other's marks. It also had a new marking scheme for them to follow."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A system where two markers grade each student project without seeing each other's marks. When both marks are in, the system reconciles them automatically.",
              "It handles the allocation of supervisors and moderators to projects.",
              "Marking follows the new scheme. Each marker gets clear steps to follow, so the process is easy to pick up.",
              "Markers sign in with the university accounts they already have. There are no separate accounts to look after, and no extra passwords to become a security hole.",
              "It runs on Google's cloud, so there are no servers for anyone to run. Every step is recorded, so there is a full trail of who did what."
            ]
          },
          {
            "heading": "What it does for them",
            "paragraphs": [
              "It has been in use since 2018. It handles undergraduate and master's projects, resits and two international partner programmes."
            ]
          }
        ],
        "facts": [
          "Single-blind double marking with automated reconciliation, and allocation of supervisors and moderators to projects.",
          "Federated login through the institution's single sign-on: no local accounts to manage or to attack.",
          "In production since 2018 on Google Cloud, with no servers to run and a full audit trail.",
          "About 600 projects a year: 350 undergraduate and 250 master's, plus resits and two international partner programmes. About 100 markers a year.",
          "More than 4,800 projects marked since 2018."
        ]
      },
      {
        "slug": "student-feedback-platform",
        "name": "Student feedback platform",
        "title": "Student feedback platform",
        "description": "A student feedback platform built for a university to replace old survey software. No answer can be traced to a student. It is in testing.",
        "published": "2026-10-02",
        "url": null,
        "kind": "Commissioned by a university, designed from research with students and staff. In testing.",
        "plain": "A university asked me for a way to collect feedback from students, to replace its old survey software. It runs annual surveys and short pulse surveys for each module. Nobody can trace an answer back to the student who gave it. It is in testing.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "A university, which commissioned it."
            ]
          },
          {
            "heading": "What they had before",
            "paragraphs": [
              "The university collected student feedback with Evasys, an old survey product. It could not give a student a direct link to a survey, and it did not connect to the university's other systems."
            ]
          },
          {
            "heading": "The people",
            "paragraphs": [
              "The students who give feedback, and the staff and student reps who read it. I did research with students and staff before I designed anything."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A way to collect feedback from students. It runs the annual surveys, and short pulse surveys for each module.",
              "Nobody can trace an answer back to the student who gave it. That is not a promise in a policy. The system is made so that the link does not exist.",
              "Some features use AI. When a student writes something worrying, it is picked up straight away. The common themes in the answers are gathered together for staff and student reps.",
              "The AI features are built so that the AI provider can be swapped for another."
            ]
          },
          {
            "heading": "Where it is now",
            "paragraphs": [
              "It is in testing."
            ]
          }
        ],
        "facts": [
          "Replaces Evasys, which had no direct links to surveys and no integration with other systems.",
          "Annual surveys and module pulse surveys.",
          "Next.js and TypeScript on Vercel, with Postgres on Neon and Prisma.",
          "Anonymity is enforced by the schema: a response cannot be joined to the student who wrote it.",
          "LLM features flag concerning sentiment immediately and aggregate common themes for staff and reps. They sit behind a swappable provider interface.",
          "In testing."
        ]
      },
      {
        "slug": "photo-archive-for-a-school",
        "name": "Photo archive for a school",
        "title": "Photo archive for a school",
        "description": "A private photo archive for a school. Artists' photographs are kept in one place so that students can learn from them. Built and run by me.",
        "published": "2026-10-02",
        "url": null,
        "kind": "Private. Built on Directus.",
        "plain": "A private archive for a school. Artists' photographs are kept in one place so students can learn from them.",
        "sections": [
          {
            "heading": "Who it is for",
            "paragraphs": [
              "A school. The archive is private, so I do not name it. A teacher runs it, and students use it."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "A private archive where artists' photographs are kept and managed in one place: about 2,100 images.",
              "Each artist has a page with their work, a short biography, videos and a link to their own website. Students browse by genre, such as portraiture, landscape and documentary, or search the whole archive.",
              "The home page features an Artist of the Month, chosen by the teacher as part of the school's work on equality, diversity and inclusion. Every past choice is kept.",
              "The teacher adds artists and photographs from one editing screen, and sets the order of the genres.",
              "Only people the school allows can sign in. Every page carries a notice about copyright and fair dealing."
            ]
          },
          {
            "heading": "What it does for them",
            "paragraphs": [
              "Students can learn from the photographs. The teacher keeps the archive up to date without asking anyone."
            ]
          }
        ],
        "facts": [
          "Artists' photographs managed in one place so students can learn from them. About 2,100 images.",
          "Directus on Postgres for the data and the admin, with a custom interface extension for editing photographs. Schema snapshots are committed.",
          "A Vite and React front end in TypeScript, served as static files by nginx.",
          "Images in S3-compatible object storage.",
          "The whole site sits behind Google sign-in through oauth2-proxy. The Directus API is same-origin and private."
        ]
      },
      {
        "slug": "asica",
        "name": "ASICA",
        "title": "ASICA: a skin self-check research app",
        "description": "ASICA is a research app on a tablet that helps people treated for melanoma check their own skin. I built the prototype for a six-month NHS pilot.",
        "published": "2026-10-02",
        "url": null,
        "kind": "Research tablet app for melanoma self-monitoring. University of Aberdeen, published in BMJ Open in 2015.",
        "plain": "A research app on a tablet that helps people treated for melanoma check their own skin at home. Designed with patients and run in a six-month NHS pilot with twenty of them. I built the working prototype with a colleague.",
        "sections": [
          {
            "heading": "What it is",
            "paragraphs": [
              "A research project at the University of Aberdeen. ASICA is an app on a tablet that helps people who have been treated for melanoma, a skin cancer, to check their own skin at home every month.",
              "People who have had melanoma are asked to check their skin between hospital visits. The research found that they saw the point of it, but did not feel equipped to do it properly or to keep it up."
            ]
          },
          {
            "heading": "The people",
            "paragraphs": [
              "Patients. The app was designed with them. Before anything was built, the research team interviewed 21 people who had been treated for melanoma.",
              "They wanted to be shown how to check, to be reminded when, and to be able to report what they found to a specialist who would answer quickly.",
              "The whole process was then acted out in mock-up rooms by volunteers, a family doctor and a specialist nurse, to find the problems before any patient met them. The main lesson was to use clear, simple words, and the same words in the training as in the app."
            ]
          },
          {
            "heading": "What I built",
            "paragraphs": [
              "With a colleague, I turned the research team's design into a working app.",
              "Each month the patient gets a reminder. The app takes them through the check one part of the body at a time, with a short animated film and a checklist for each part. They can compare what they see with photographs of their own skin taken at the start.",
              "If something has changed, they mark where it is on a diagram, describe it, photograph it and send a report to a specialist nurse. The nurse phones them within 24 hours.",
              "With the same colleague, I wrote the training sessions and materials for patients, and I helped to deliver them. I was one of the four who gathered and analysed the results."
            ]
          },
          {
            "heading": "What happened",
            "paragraphs": [
              "Twenty people who had been treated for melanoma used it at home for six months, supported by their family doctors and a specialist nurse. It was a research pilot, not an NHS service.",
              "Fifteen of the twenty kept to their checks well. Four checked less regularly and one withdrew. Patients were largely positive about using it.",
              "Two people had skin surgery because of something they found during a check. One was a melanoma that had come back. The other was harmless.",
              "It was a small pilot, and it showed what to fix. The photographs patients sent were often not clear enough for the nurse to judge, so advice on taking a good one was added to the app."
            ]
          },
          {
            "heading": "Where it is now",
            "paragraphs": [
              "The pilot was published in the journal BMJ Open in 2015. A Cancer Research UK grant followed, to carry the work on."
            ]
          }
        ],
        "sources": [
          {
            "text": "Murchie P, Allan JL, Brant W, Dennis M and others. Total skin self-examination at home for people treated for cutaneous melanoma: development and pilot of a digital intervention. BMJ Open, 2015.",
            "href": "https://doi.org/10.1136/bmjopen-2015-007993"
          },
          {
            "text": "Cancer Research UK: a study using the ASICA app to help people who have had treatment for melanoma (ASICA Optimization Project).",
            "href": "https://www.cancerresearchuk.org/about-cancer/find-a-clinical-trial/a-study-using-the-asica-app-to-help-people-who-have-had-treatment-for-melanoma-asica-optimization"
          }
        ],
        "facts": [
          "Designed with patients and run in a six-month NHS pilot.",
          "An app for the Google Nexus 7 tablet. Reports, with photographs taken on the tablet, went to a secure remote server for review by a clinical nurse specialist.",
          "Developed under the Medical Research Council framework for complex interventions. Behaviour change techniques are built into the flow: prompts, demonstration, checklists and feedback.",
          "Pilot in NHS Grampian: 20 patients, six general practitioners and one nurse specialist. 15 adhered well. Two had lesions excised, one of them a recurrent melanoma.",
          "Murchie P, et al. BMJ Open 2015;5:e007993. Funded by the RCUK Digital Economy programme through the dot.rural hub at the University of Aberdeen."
        ]
      }
    ],
    "featured": [
      "solent-gay-mens-chorus",
      "alicedennis-net",
      "my-own-house",
      "morganharnett-tattoo"
    ]
  },
  "technical": {
    "intro": "Six parts of the work, each with a page of its own.",
    "items": [
      {
        "slug": "payload-cms",
        "name": "Payload CMS",
        "title": "Payload CMS developer, UK",
        "description": "Payload CMS developer in the UK. I build and run production sites on Payload, including a charity's whole platform of five Node services on one server.",
        "lede": "I build and run production sites on Payload. The largest is a charity's whole platform: five Node services with their content in Payload, edited by the charity itself.",
        "sections": [
          {
            "heading": "What I do with Payload",
            "paragraphs": [
              "I model the content, set up who can edit what, and build the services around it: sign-in, payments, media and email. Editors get an admin they can use without me."
            ]
          },
          {
            "heading": "In production",
            "paragraphs": [
              "Solent Gay Men's Chorus is a registered charity. Everything it has online is built and run by me."
            ],
            "items": [
              "Five Node services: main website, box office, governance, members portal and identity. Content in Payload.",
              "A CMS the chorus edits itself.",
              "One identity service for every app, with passkey sign-in and a role hierarchy.",
              "All five share one 2GB server behind nginx, deployed from GitHub Actions."
            ]
          },
          {
            "heading": "How I build it",
            "paragraphs": [
              "Minimal technical debt. Small services with thin handlers, content as JSON over REST, pages put together in the browser from templates, and no build step on the server."
            ],
            "links": [
              {
                "text": "How I build, in full",
                "href": "/technical#how"
              }
            ]
          }
        ],
        "questions": [
          {
            "question": "Why Payload?",
            "answer": "It is a headless CMS written in TypeScript that keeps its configuration in code and runs in your own Node process. Editors get a clean admin. Developers get typed JSON."
          },
          {
            "question": "Do you work remotely?",
            "answer": "Yes. I work with organisations anywhere in the UK, and meet face to face within about 30 miles of Portsmouth."
          }
        ],
        "work": [
          "solent-gay-mens-chorus"
        ]
      },
      {
        "slug": "directus",
        "name": "Directus",
        "title": "Directus developer, UK",
        "description": "Directus developer in the UK. I build on Directus when the data comes first: a SQL database with a clean editing screen and a JSON API on top.",
        "lede": "I build on Directus when the data comes first: a SQL database that needs a clean editing screen and a JSON API on top.",
        "sections": [
          {
            "heading": "What I do with Directus",
            "paragraphs": [
              "I model the data, set up roles and permissions, handle the files, and build the front end that reads from the API."
            ]
          },
          {
            "heading": "In production",
            "paragraphs": [
              "A private photo archive for a school, built on Directus. Artists' photographs are managed in one place so students can learn from them."
            ]
          },
          {
            "heading": "When I choose it",
            "paragraphs": [
              "Directus sits on top of a SQL database and leaves the tables as they are. That suits collections, archives and records, where the data will outlive the app that shows it."
            ]
          }
        ],
        "questions": [
          {
            "question": "Payload or Directus?",
            "answer": "Payload when the content model belongs in code beside the app. Directus when the database is the thing that matters and it needs an admin and an API."
          }
        ],
        "work": [
          "photo-archive-for-a-school"
        ]
      },
      {
        "slug": "email-authentication",
        "name": "Email authentication",
        "title": "DMARC p=reject setup, SPF and DKIM",
        "description": "DMARC p=reject setup with SPF and DKIM aligned, without losing legitimate mail on the way. In production for a charity and for this domain.",
        "lede": "I take domains to DMARC p=reject with DKIM aligned, without losing legitimate mail on the way.",
        "sections": [
          {
            "heading": "What I set up",
            "paragraphs": [
              "Everything a receiving server checks."
            ],
            "items": [
              "SPF, trimmed to the hosts that really send.",
              "DKIM signing on every sending service, aligned with the From domain.",
              "DMARC with reporting, tightened to p=reject as the reports come clean.",
              "MTA-STS and TLS reporting.",
              "BIMI, once the policy allows it."
            ]
          },
          {
            "heading": "How I do it",
            "paragraphs": [
              "I list every sender first: the mailbox provider, the website, the newsletter tool, anything that sends as the domain. I fix alignment for each one.",
              "I publish DMARC with reporting, read the aggregate reports, and tighten the policy only when every legitimate source passes."
            ]
          },
          {
            "heading": "In production",
            "paragraphs": [
              "The email domain for Solent Gay Men's Chorus is at p=reject with DKIM aligned. So is this one. The policy for passionfruit.design is read live from DNS and shown in the Receipts."
            ],
            "links": [
              {
                "text": "The live DMARC policy, in the Receipts",
                "href": "/technical#receipts"
              }
            ]
          }
        ],
        "questions": [
          {
            "question": "Will p=reject block our own mail?",
            "answer": "Not if every sender is aligned first. That is what the reporting stage is for."
          },
          {
            "question": "What about forwarding and mailing lists?",
            "answer": "Forwarding breaks SPF but not DKIM. That is why I align DKIM on every sender and do not rely on SPF alone."
          }
        ],
        "work": [
          "solent-gay-mens-chorus"
        ]
      },
      {
        "slug": "passkeys-and-single-sign-on",
        "name": "Passkeys and single sign-on",
        "title": "Passkey login and single sign-on",
        "description": "Passkey login and single sign-on: one identity service for every app, with WebAuthn, OIDC and roles that match how the organisation works.",
        "lede": "One sign-in for every app, with passkeys instead of passwords and roles that match how the organisation works.",
        "sections": [
          {
            "heading": "What I build",
            "paragraphs": [
              "Identity as its own small service, shared by every app."
            ],
            "items": [
              "Passkey sign-in with WebAuthn.",
              "A central identity service using OIDC, so every app shares one sign-in.",
              "Role hierarchies that match the organisation.",
              "Google sign-in and magic links, where they fit better.",
              "Single sign-on with the accounts an institution already has."
            ]
          },
          {
            "heading": "In production",
            "paragraphs": [
              "Three systems, three kinds of sign-in."
            ],
            "items": [
              "Solent Gay Men's Chorus: one identity service for every app, with passkey sign-in and a role hierarchy.",
              "SUMS, a university marking platform: single sign-on and a full audit trail, in production since 2018.",
              "alicedennis.net: the owner signs in to her admin page with Google."
            ]
          }
        ],
        "questions": [
          {
            "question": "Why passkeys?",
            "answer": "There is nothing to remember and nothing to phish. The private key never leaves the user's device."
          }
        ],
        "work": [
          "solent-gay-mens-chorus",
          "sums",
          "alicedennis-net"
        ]
      },
      {
        "slug": "legacy-app-modernisation",
        "name": "Legacy apps to REST APIs",
        "title": "Legacy app modernisation to REST APIs",
        "description": "Legacy app modernisation: moving PHP, Laravel, CodeIgniter, Ruby on Rails and JSP applications from server-held state to true RESTful APIs.",
        "lede": "I help companies move applications that keep their state on the server to true RESTful API architectures. I know the frameworks they are moving from.",
        "sections": [
          {
            "heading": "What I know",
            "paragraphs": [
              "MVC applications, and the languages and frameworks they are written in."
            ],
            "items": [
              "PHP.",
              "Laravel.",
              "CodeIgniter.",
              "Ruby on Rails.",
              "JSP."
            ]
          },
          {
            "heading": "From server state to REST",
            "paragraphs": [
              "A server-state application keeps each user's session on the server and sends back whole pages. The interface and the logic are tied together.",
              "A RESTful API holds no session between requests. Each request carries what it needs. Each resource has its own address, and the HTTP methods and status codes mean what they say.",
              "Once the API exists, a website, a mobile app and other systems can all use the same one."
            ]
          },
          {
            "heading": "What I build",
            "paragraphs": [
              "REST and JSON APIs on Node, with Postgres or SQLite underneath."
            ],
            "links": [
              {
                "text": "How I build, in full",
                "href": "/technical#how"
              }
            ]
          }
        ],
        "questions": [
          {
            "question": "What makes an API truly RESTful?",
            "answer": "No session held on the server. Resources at stable addresses. HTTP methods and status codes used as they are defined. Many APIs that are called REST are remote procedure calls sent over HTTP."
          },
          {
            "question": "Can you work with our developers remotely?",
            "answer": "Yes. I work with organisations anywhere in the UK, and meet face to face within about 30 miles of Portsmouth."
          }
        ]
      },
      {
        "slug": "home-assistant",
        "name": "Home Assistant",
        "title": "Home Assistant setup and automation",
        "description": "Home Assistant setup and automation in Docker: Zigbee, MQTT and 433 MHz radio, presence lighting, heating, watchdogs and a nightly config backup.",
        "lede": "I build and run Home Assistant for local, vendor-agnostic automation in homes and businesses across Portsmouth and the South Coast. The proof is my own house.",
        "sections": [
          {
            "heading": "What I do with Home Assistant",
            "paragraphs": [
              "I bring devices from different makers under one local controller, write the automations, and keep the configuration recoverable."
            ]
          },
          {
            "heading": "In production",
            "paragraphs": [
              "My own house runs on it."
            ],
            "items": [
              "Home Assistant, Mosquitto and rtl_433 in Docker on one small home server.",
              "A Zigbee network of bulbs, buttons, switches, radiator valves and presence sensors.",
              "More than 60 automations and more than 60 scripts.",
              "Lighting that follows presence from radar and PIR sensors, gated on the light level in each room.",
              "Radiator valves that follow the wall thermostats.",
              "A doorbell received over 433 MHz radio, with a backup chime for when the internet is down.",
              "Away and holiday modes.",
              "Watchdogs for the radio, the sensors and the database, with alerts.",
              "Dashboards, including an occupancy view on a 3D model of the house."
            ]
          },
          {
            "heading": "Kept recoverable",
            "paragraphs": [
              "The server pushes its configuration to a private Git repository every night. A regression check fails on YAML errors, duplicate ids and calls to scripts that do not exist."
            ]
          },
          {
            "heading": "Why Home Assistant",
            "paragraphs": [
              "It is free and open source, it runs on hardware you own, and it talks to devices from many makers. Nothing is tied to one company's app."
            ]
          }
        ],
        "questions": [
          {
            "question": "How do you support it remotely?",
            "answer": "Over SSH or Tailscale, with the client's permission. Nothing is opened to the public internet. It needs Home Assistant on its own computer or a Raspberry Pi."
          },
          {
            "question": "Does Home Assistant need the cloud?",
            "answer": "Home Assistant itself runs locally. Zigbee, MQTT and 433 MHz devices need no cloud at all. Some makers' devices still go through their own service, and I say which."
          },
          {
            "question": "What does Home Assistant run on?",
            "answer": "A small computer or an old laptop. Mine is a 2018 laptop running Docker."
          },
          {
            "question": "How do Apple Home, Google Home and Alexa connect?",
            "answer": "Apple Home uses the HomeKit Bridge and stays on your network. Google Home and Alexa go through Home Assistant Link, the Nabu Casa subscription, or a manual setup that takes more upkeep. Either way those two are cloud services."
          }
        ],
        "work": [
          "my-own-house"
        ]
      }
    ]
  },
  "notes": {
    "index": {
      "name": "Notes",
      "title": "Notes for small organisations",
      "description": "Short, plain notes for charities and small organisations on websites, email security and accessibility, with a source for every claim.",
      "lede": "Short notes on websites, email and accessibility for people who run small organisations. Every factual or legal claim has a source."
    },
    "feed": {
      "title": "Passionfruit Design notes",
      "subtitle": "Short notes on websites, email and accessibility for small organisations."
    },
    "items": [
      {
        "slug": "zigbee-thread-wifi-explained",
        "name": "Zigbee, Thread and Wi-Fi: how smart devices talk",
        "title": "Zigbee, Thread and Wi-Fi explained",
        "description": "How smart home devices talk over Zigbee, Thread and Wi-Fi, and why a device that works in your building beats one that needs its maker's cloud.",
        "lede": "Every smart light, plug and sensor needs a way to hear instructions. Which radio it uses decides whether your home keeps working when the internet, or the maker, goes away.",
        "published": "2026-11-01",
        "sections": [
          {
            "heading": "Three radios, one job",
            "paragraphs": [
              "A smart device is a switch, sensor or motor with a small radio attached. The radio carries two things: instructions to the device, such as turn on, and reports from it, such as the door opened. Three radios do most of this work in homes and small buildings: Zigbee, Thread and Wi-Fi. All three work inside your building. None of them needs the internet to carry a message from a light switch to a light.",
              "The difference is in what each is good at, and in where the messages go once they leave the device."
            ]
          },
          {
            "heading": "Zigbee",
            "paragraphs": [
              "Zigbee is a low-power radio designed for exactly this job. A battery sensor spends almost all its time asleep, wakes to send a few bytes, and sleeps again, so it runs for years on a couple of AA cells or a coin battery. Mains-powered devices, such as plugs and bulbs, also pass messages on for their neighbours. That makes a mesh: the more devices you fit, the more routes a message has, and the network gets more reliable as it grows rather than less.",
              "Zigbee devices talk to a coordinator, a small radio stick in the computer that runs your home. From there the computer does the rest. Nothing goes outside the building unless you choose to send it. Zigbee has been in homes for over a decade, so there are devices from hundreds of makers at every price."
            ]
          },
          {
            "heading": "Thread",
            "paragraphs": [
              "Thread is the newer of the two low-power radios, and it works on the same kind of mesh as Zigbee: battery devices sleep, mains devices relay. The difference is that Thread speaks the same language as the rest of your network, so a Thread device can be addressed like any other computer in your building. Several border routers can join the mesh to the network, and if one fails another takes over.",
              "Thread is the radio behind Matter, the standard that Apple, Google, Amazon and Samsung agreed so that devices work across their systems. It is the direction the industry is going, and the hardware is arriving at reasonable prices. Home Assistant supports both Zigbee and Thread, so you can mix them and buy whatever is cheapest for the job."
            ]
          },
          {
            "heading": "Wi-Fi",
            "paragraphs": [
              "Wi-Fi is the network you already have. It carries far more data than Zigbee or Thread, so it is right for cameras, speakers and screens, where there is a lot to send and a mains socket to power it. It is wrong for a battery sensor: a Wi-Fi radio drinks power, so the battery lasts weeks rather than years. It also leans on your router. Every device takes a slot, and a cheap router gets slow with sixty smart plugs on it.",
              "Wi-Fi itself is not the problem. The problem is what many Wi-Fi devices do with it."
            ]
          },
          {
            "heading": "The device that only works through its maker",
            "paragraphs": [
              "A great many cheap smart plugs, bulbs and sensors use Wi-Fi to reach their maker's servers, and only those servers. When you tap the app, the tap goes to a data centre, often on another continent, and the instruction comes back the same way. The light turns on a second later, if everything along the way is up.",
              "If the maker's service goes down, the device stops. If your internet drops, the device stops. If the company closes, the device stops for good. In April 2022 a smart home maker called Insteon switched its servers off with no notice, and its customers found their apps dead and their automations gone overnight. Makers also change their minds: in 2024 one platform revoked the access it had granted to other systems, and homes that had relied on it went dark.",
              "There is a privacy cost too. The app knows when you come home, when you go to bed and when the house is empty, and that record sits with a company you have never heard of. The National Cyber Security Centre's advice on smart devices is to ask what the device does with your data and what happens when support ends. Most of these devices do not have a good answer.",
              "Many of them are the same device inside. A handful of platforms supply the radio module, the cloud and the app to anyone who wants to put their own name on the box, so hundreds of brands share one set of servers. The name on the box tells you nothing about who you are depending on."
            ]
          },
          {
            "heading": "Local first",
            "paragraphs": [
              "The alternative is a device that answers to a computer in your building. Zigbee and Thread devices do this by design. Many Wi-Fi devices can do it too if you choose makers that support local control, and I check before I buy.",
              "With local control the light turns on in the time it takes to flick a switch. It keeps working when the broadband is out, and it keeps working if the maker is bought, closes or changes its terms. Devices from different makers mix freely, so you choose on price and on what they do. Nothing about your home leaves your home unless you ask it to. And when you move on from me, or from the computer that runs it, the devices stay yours.",
              "That is what I fit. It costs no more than the cloud alternative and often less, because you are not paying for a service that someone has to keep running."
            ]
          },
          {
            "heading": "You do not have to choose",
            "paragraphs": [
              "The computer that runs your home speaks all three radios at once. Home Assistant has a Zigbee stick on one side, a Thread border router on another and your Wi-Fi on the third, and treats a light as a light whichever way it is connected. So you never pick a camp. Buy Zigbee where it is cheapest, Thread where the new device is better, Wi-Fi where there is data to carry, and run them together as one system.",
              "It also means the devices you already own are not waste. If you have a drawer of smart plugs, a brand's bulbs in every room or a hub that came with the house, I start by seeing what can be kept. Many Wi-Fi devices can be switched to local control. Where one cannot, Home Assistant can usually still drive it through its maker's service, so it keeps working until it wears out and you replace it with something local when the time comes. Nothing goes in the bin because it was the wrong brand.",
              "The computer itself is the cheap part. A Raspberry Pi is enough for most homes, and if you do not have one I will help you order the right one. It is yours, not mine, and it is a general computer: when it is not running your home, it can run whatever else you fancy.",
              "That is the real argument for an open system. It is not that one radio wins. It is that your home can use what it has, add what is cheapest, and outlast every one of the makers."
            ],
            "links": [
              {
                "text": "Home and business automation",
                "href": "/services/home-and-business-automation"
              }
            ]
          }
        ],
        "sources": [
          {
            "text": "Silicon Labs: Zigbee fundamentals, overview",
            "href": "https://docs.silabs.com/zigbee/8.2.2/zigbee-fundamentals/01-overview"
          },
          {
            "text": "Thread Group: What is Thread",
            "href": "https://www.threadgroup.org/What-is-Thread"
          },
          {
            "text": "Home Assistant: Zigbee Home Automation integration",
            "href": "https://www.home-assistant.io/integrations/zha/"
          },
          {
            "text": "Home Assistant: Thread integration",
            "href": "https://www.home-assistant.io/integrations/thread/"
          },
          {
            "text": "The Register: Insteon's cloud shutdown, April 2022",
            "href": "https://www.theregister.com/2022/04/19/insteon_cloud_shutdown/"
          },
          {
            "text": "Homey: Tuya revoked API access",
            "href": "https://homey.app/en-gb/news/official-support-for-tuya/"
          },
          {
            "text": "NCSC: Smart devices in the home",
            "href": "https://www.ncsc.gov.uk/guidance/smart-devices-in-the-home"
          }
        ]
      }
    ]
  },
  "pages": {
    "colophon": {
      "name": "Colophon",
      "title": "Colophon",
      "description": "How passionfruit.design is built, in plain language: one small server, two dependencies, no tracking, and every change tested before it goes live.",
      "lede": "How this site is built. It follows the same rule as the work I do for clients: minimal technical debt.",
      "sections": [
        {
          "heading": "As little as possible",
          "paragraphs": [
            "Every dependency, build step and moving part is a future cost. Each one here has to pay for itself. The rest of this page is what that leaves.",
            "The code is linted. The content and every form field are checked. Each change is tested before it goes live. Dependencies are kept on current releases, with updates proposed automatically every week."
          ]
        },
        {
          "heading": "Words are data",
          "paragraphs": [
            "Every word on this site lives in a few JSON files. The server checks them when it starts and refuses to run if anything is missing.",
            "The same content is published as JSON, so you can read the whole site as data."
          ],
          "links": [
            {
              "text": "This site as JSON",
              "href": "/api/site.json"
            },
            {
              "text": "The live figures as JSON",
              "href": "/api/receipts.json"
            }
          ]
        },
        {
          "heading": "Made on the server",
          "paragraphs": [
            "One small Node process using Express builds each page and sends it complete. There is no framework, no bundler and no build step.",
            "It has two runtime dependencies: Express, and Nodemailer for the contact form. Everything else is a few lines written for the job.",
            "The page works with JavaScript turned off. A few lines of JavaScript make the contact form reply without reloading the page. That is all it does."
          ]
        },
        {
          "heading": "Easy to find, easy to read",
          "paragraphs": [
            "Every page has its own title, description, address and a summary that machines can read. The sitemap, the feed and a plain-text summary for AI tools are all made from the same content as the pages.",
            "Search engines and AI crawlers are welcome."
          ],
          "links": [
            {
              "text": "The sitemap",
              "href": "/sitemap.xml"
            },
            {
              "text": "The plain-text summary",
              "href": "/llms.txt"
            },
            {
              "text": "The feed",
              "href": "/notes/feed.xml"
            }
          ]
        },
        {
          "heading": "Locked down",
          "paragraphs": [
            "The server sets a strict content security policy. The browser may load nothing from anywhere but this domain, so third-party requests are impossible, not just absent.",
            "Other headers stop the site being framed, stop the browser guessing file types, send no referrer and turn off every browser feature the site does not use.",
            "The contact form checks where it was sent from, limits how often one address can use it and catches bots without a CAPTCHA."
          ],
          "links": [
            {
              "text": "Check the headers with Mozilla Observatory",
              "href": "https://developer.mozilla.org/en-US/observatory/analyze?host=passionfruit.design"
            },
            {
              "text": "Check TLS with SSL Labs",
              "href": "https://www.ssllabs.com/ssltest/analyze.html?d=passionfruit.design"
            }
          ]
        },
        {
          "heading": "Hosted on a small box",
          "paragraphs": [
            "The app runs under pm2 on a Linux VPS it shares with other production apps. nginx sits in front of it and handles TLS with a Let's Encrypt certificate.",
            "GitHub Actions lints and tests every change, checks accessibility, page weight and Lighthouse scores, then deploys. Nothing is built on the server."
          ]
        },
        {
          "heading": "AI-assisted, engineer-owned",
          "paragraphs": [
            "I use AI tools to write and review code faster. I read, test and answer for everything that goes live."
          ]
        },
        {
          "heading": "Type and colour",
          "paragraphs": [
            "The type is your device's own system font, so there is nothing to download. The colours come from the fruit: aubergine skin, yellow pulp, pale pith. Every pairing passes WCAG 2.2 AA contrast."
          ]
        }
      ]
    },
    "privacy": {
      "name": "Privacy",
      "title": "Privacy",
      "description": "What passionfruit.design collects, which is very little: no cookies, nothing from other companies, and nothing kept unless you send me a message.",
      "lede": "This site collects nothing unless you send me a message.",
      "sections": [
        {
          "heading": "Who I am",
          "paragraphs": [
            "Passionfruit Design is the trading name of Dr Matt Dennis. I am responsible for this site and for anything you send through it."
          ]
        },
        {
          "heading": "No cookies, no tracking",
          "paragraphs": [
            "This site sets no cookies and loads nothing from any other company. Nothing runs in your browser to watch what you do. That is why there is no cookie banner."
          ]
        },
        {
          "heading": "If you use the contact form",
          "paragraphs": [
            "Your name, email address and message are sent to me by email. The site does not store them.",
            "I use them only to reply and to handle any work that follows. I keep them in my mailbox for as long as that takes, and I never pass them on or add you to a mailing list."
          ]
        },
        {
          "heading": "If you message me on WhatsApp",
          "paragraphs": [
            "WhatsApp is run by Meta, not by me. If you message me there, Meta's privacy policy covers what they do with it. I use your messages only to reply and to handle any work that follows.",
            "The WhatsApp link on this site is an ordinary link. Nothing from WhatsApp or Meta loads unless you click it."
          ]
        },
        {
          "heading": "Server logs and counting visits",
          "paragraphs": [
            "Like every web server, mine records the address each request came from, the page asked for and the time. I use these logs to keep the site running and secure, and to count how many times each page is read.",
            "The counting happens on my own server, from those logs. Nothing is sent to anyone else and I do not follow individual visitors. The logs are deleted automatically within 14 days.",
            "Google and Bing also tell me which searches led people here. They collect that on their own search pages, not on this site."
          ]
        },
        {
          "heading": "Your rights",
          "paragraphs": [
            "You can ask me for a copy of anything I hold about you, or ask me to delete it, by email. If you are unhappy with how I handle your data, you can complain to the Information Commissioner's Office."
          ],
          "links": [
            {
              "text": "Information Commissioner's Office",
              "href": "https://ico.org.uk/make-a-complaint/"
            }
          ]
        }
      ]
    },
    "portsmouth": {
      "name": "Portsmouth",
      "title": "IT and web services in Portsmouth",
      "description": "Home automation, data analysis, IT and AI advice and web apps from Portsmouth. I meet people face to face along the South Coast and work UK-wide.",
      "lede": "Friendly technology help for your home, charity or business. I’m Matt, based in Portsmouth, working face to face along the South Coast and remotely across the UK.",
      "sections": [
        {
          "heading": "Meeting in person",
          "paragraphs": [
            "I meet people face to face within about 30 miles of Portsmouth. That takes in Southsea, Gosport, Fareham, Havant, Waterlooville, Chichester, Southampton and Winchester. I also cover the Isle of Wight, where a visit costs extra because of the ferries.",
            "I can come to you, see how your people work and talk it through across a table. Consultation visits are free on the mainland within that area."
          ]
        },
        {
          "heading": "Further away",
          "paragraphs": [
            "I work with organisations anywhere in the UK by video call, phone and email."
          ]
        },
        {
          "heading": "Who I work with",
          "paragraphs": [
            "I’ve worked with charities throughout my adult life, supporting people with all levels of IT confidence. I work with charities, schools, community groups and small businesses, taking time to understand what works for your people."
          ]
        },
        {
          "heading": "What I do",
          "paragraphs": [
            "Practical help with the things that make a difference to your day."
          ],
          "links": [
            {
              "text": "All services",
              "href": "/services"
            },
            {
              "text": "Work I have built and run",
              "href": "/work"
            }
          ],
          "items": [
            "Home automation that fits your routine.",
            "Data analysis and research to help you make decisions.",
            "IT, infrastructure and governance for your organisation.",
            "Accessible websites, booking systems and ongoing care."
          ]
        }
      ],
      "questions": [
        {
          "question": "Do you only work with organisations near Portsmouth?",
          "answer": "No. I meet people in person within about 30 miles of Portsmouth, and I work with organisations anywhere in the UK."
        },
        {
          "question": "Where are you based?",
          "answer": "Portsmouth, in Hampshire, on the south coast of England."
        }
      ]
    }
  }
}