The weeks you'd rather not spend twice.

Classic & Modern — a site theme

For developers who can build anything and would rather not design it

Most template libraries offer you the same flat sans-serif SaaS look, and using one quietly announces that nobody paid for design. This is the other thing: a warm, editorial treatment built on serif type and a deep gradient masthead — closer to a well-set book than a dashboard. It's the design running behind ThaiBridge AI, which you can open and scroll right now.

Why it’s worth paying for

• A look you couldn't have produced yourself. Most developers know their design is the weak part and can't fix it by trying harder. This is taste you can buy, not a grid you still have to make attractive.
• Never writing column CSS again. The layout detects what each page contains and becomes one, two or three columns on its own. Add a sidebar and it reflows. Remove it and it reflows back. You write no media queries for it.
• The mobile work already done. Every component has been through real use on real phones, including the sticky sidebar and the menu — the two things that usually break first.
• Rebranding in minutes, not a weekend. Every colour comes from one file. Change a handful of values and the whole site follows, including hover, focus and border states you'd otherwise hunt down one by one.

See it before you buy it

Open the live demo → Five pages, four different layouts, and a second colourway — all of it the theme with nothing custom added. Click through it properly; that is what you are buying.

What is in the download

• Five HTML pages, each showing a different layout
• theme.css — the whole theme, one file, 33 colour tokens
• colourway-slate.css — a second identity as a worked example
• theme.js — menus and collapsible sections, keyboard accessible
• A START-HERE guide, README, changelog and licence

How to use it — the ten steps

The first three have nothing to do with the theme, and they are half the job.

How the job goes

1. Decide what the site is for — who it is for, and what you want a visitor to do.
2. Plan your pages. Five or six is plenty. That list becomes your menu.
3. Gather your content first — the words for each page, your photos, your logo, two or three brand colours.
4. Open index.html and click through the demo. Notice which layout suits each of your pages.
5. Copy the folder and rename it after your site. Leave the original untouched.
6. Keep the pages you need, delete the rest, duplicate one for any extra.
7. Swap the words and pictures, one page at a time. Home first.
8. Change the site name and the colours. One block at the top of theme.css controls the colours for every page.
9. Open every page, click every link, try it on your phone.
10. Upload the folder to any web host. Nothing to install.

Stuck on any step? Email support is included for 60 days. And if you would rather not do steps 5 to 10 at all, installation on your domain starts at £150.

The engine — a Flask SaaS starter

For anyone building something they intend to charge money for

Accounts and billing are the part of a paid product that nobody enjoys building and everybody has to. They're also the part where a small mistake is expensive rather than embarrassing. This is that machinery, taken out of a working application and stripped back to a foundation you build your own product on.

The mistakes it stops you making

• Paid features unlocking for free. Anything the browser holds, a user can edit. Here the database is the only thing that decides who has paid, and only a signed message from Stripe is allowed to write to it. A tampered cookie unlocks nothing.
• A customer who paid and can't get in. The worst billing bug there is: the money leaves, the upgrade doesn't happen, and you hear about it from an angry email days later. The webhook path here is the one that has already been run end to end.
• An AI bill you find out about at month end. Connect a language model without limits and one loop or one abusive user writes you an invoice. Usage caps are built in rather than added after the first scare.
• Accounts that vanish on deploy. A classic first-product disaster. This has been confirmed to survive redeployment with user data intact.
• Changes that quietly break payments. 1,523 automated tests run on every change, so the billing path can't rot while you're busy building features.