Skip to main content
Try it free

Changelog

Everything we’ve shipped, newest first. You’re currently on FANDEMiQ v1.5.0.

  1. v1.5.0

    Make demo sites without a code change

    A new demo site no longer needs a developer. In Demos → Demo sites you can create a site and upload its files (a whole folder at once), or ask Claude to build it through the FANDEMiQ connector. Then share it from Demos exactly as before, with its own PIN. Because nobody reviews an uploaded site’s code, it runs sealed off from the rest of fandemiq.net: it can’t see your sign-in or act as you, which a real-browser test proves on every build.

    • New Demos → Demo sites page: create a site, upload files or a folder, replace or remove files, delete a site no demo uses.
    • Uploaded sites appear in the demo site list when sharing a demo; “Share this site” starts a demo with it chosen.
    • Uploaded sites are served sealed (a sandboxed page with no access to fandemiq.net cookies, storage or your session); their scripts, styles and pictures load on a short-lived key tied to the demo’s PIN.
    • Claude (through the MCP bridge) can create a site and write, read and remove its files; deleting a site stays a person’s job in the admin.
    • Limits: 2 MB a file, 300 files and 25 MB a site, static file types only.
  2. v1.4.2

    Demos open after the PIN

    Since 1.4.0 a demo’s PIN screen worked, but after the right PIN the demo itself said “Not found” on the live site: the demo’s files were not being shipped with the page that serves them. They are now, and the build checks it every time, so it cannot go out broken again.

    • The demo sites’ files are shipped with the demo route (the setting that should have done it matched nothing).
    • CI checks the build output and fails if the demo route would ship without a demo site’s files.
    • A site’s tests, scripts and README are no longer shipped at all.
  3. v1.4.1

    Shorter demo addresses

    A new demo’s web address is now made from who it’s for alone: “Arsenal” gives /demo/arsenal/, and “Premier League” gives /demo/premier-league/ rather than /demo/premier-league-premier-league/. A second demo for the same name gets -2. You can still type any address you like.

    • A demo’s suggested web address no longer repeats the demo site’s name.
  4. v1.4.0

    Demos move into the admin

    The demos site is now a third card in the admin, next to proposals and the CMS. Each demo is shared with one client at its own address, behind its own PIN, the same way a proposal is: only a hash of the PIN is stored, changing it signs everyone out, and ten wrong tries lock that address out for 15 minutes. Several clients can see the same demo site, each with their own link, opens and closing date. The single shared PIN on demos.fandemiq.net is gone. Proposals and demos can also now be run from Claude through the FANDEMiQ connector, as the person asking, once the platform side is switched on.

    • New Demos card on the admin home, and /admin/demos to share a demo, set its PIN, make it live, archive it or delete it.
    • Demos open at /demo/<address>/. Without the PIN a client sees a PIN screen; a draft is a 404 to everyone but an admin.
    • Signed-in admins skip the PIN and see a note saying so, with “See it as the client”.
    • After an upload, a demo’s fan apps send fans to /demo/return/<site>, which brings each browser back to the demo it last opened.
    • The Premier League demo moved here from demos.fandemiq.net.
    • The admin API can be called by the platform on behalf of a staff member (a key both servers hold, plus that person’s email), so Claude can list, create, generate and edit proposals and demos. Going live, deleting and the PIN stay a click in the admin. Off until the key is set on both sides.
  5. v1.3.0

    MCP, explained, with pictures

    The Connect page now says what MCP actually is, lists the newer things you can ask Claude to do, and shows what the connector puts in the chat: the fan email, every app screen, share pages, what an event made, your brand and your numbers. Typing /mcp lands you there instead of on a 404.

    • New "See it in the chat" section on /connect: seven examples of MCP Apps previews, each with something to ask and what you get back.
    • New "What MCP is" section in plain English.
    • Five more things Claude can do: start from a template, take your brand from your website, words and languages, search what fans said and showed, and paste a Manager link.
    • Three new FAQs: what MCP Apps are, which chat apps show the previews, and whether a preview sends anything to fans.
    • /mcp and /mcp-apps now go to the right part of /connect.
  6. v1.2.2

    A logo you can link to

    The FANDEMiQ logo in the site header is drawn in code, so there was never a file of it to send anyone. It now exists as two SVG files, one for dark backgrounds and one for light, with the lettering converted to outlines so it looks the same wherever it is opened. Nothing on the site itself looks different.

    • New file /images/fandemiq-lockup-white.svg: tile, wordmark and “Passion. Valued.” strap, for dark backgrounds. Matches the header logo.
    • New file /images/fandemiq-lockup-dark.svg: the same lockup for light backgrounds.
  7. v1.2.1

    White paper, version 1.1

    The State of Fan Participation 2026 white paper offered by the home page pop-up is now version 1.1. Same 19 pages and the same six findings; the download and its cover image are both the new edition.

    • White paper PDF replaced with version 1.1 (1.0 MB, 19 pages).
    • Cover image on the white paper page re-rendered from the new edition, so it shows “Version 1.1”.
  8. v1.2.0

    Saying what we actually do

    A line-by-line check of the legal pages against how the platform really works. The privacy policy was rewritten: it used to describe quizzes and polls and say clubs only see anonymised analytics, when fans send photos and videos to the club that runs the activation. The Data Processing Agreement moves to version 2.0, which covers speech transcription and whole-video analysis; version 1.0 stays at its permanent address for customers who signed under it.

    • Privacy policy rewritten: our two roles (controller for this site and our customers, processor for fans on a club’s behalf), what the platform processes, lawful bases, children, real retention periods (90 days by default, contact details cleared 30 days after the last content) in place of “campaign plus 24 months”, rights including objecting to speech transcription, and where data is processed.
    • Data Processing Agreement version 2.0 published at /legal/dpa (version 1.0 kept at /legal/dpa/v1): speech transcripts and video analysis added to the data and purposes, processing locations corrected for Azure OpenAI, two-factor sign-in no longer listed as a gap.
    • Sub-processor register and data protection brief: generative FanMoment pictures run on Microsoft Azure OpenAI’s Global Standard deployment and may be processed in any Azure region; OpenAI only when Azure refuses a picture. Two-factor sign-in is mandatory, not optional.
    • Cookie policy: no more “by continuing you agree”; it names Plausible (no cookies) and Google Analytics (only after you accept), and the Cookie settings link.
  9. v1.1.2

    We wrote down what we write down

    The platform now turns the speech in every fan video into text, under a plain notice shown with the terms, and can analyse whole videos with Microsoft Azure AI Video Indexer. The privacy pages now say so: what happens, why it is allowed (the club’s legitimate interests, with a right to object), where it runs, and how long anything is kept. The proposal mock-ups show the notice instead of the old optional toggle.

    • Data protection brief: new Speech and video section covering transcription, the right to object, whole-video analysis and search; lawful bases, erasure and retention updated.
    • Sub-processor register: Video Indexer purpose rewritten, Microsoft Azure OpenAI given its own row, OpenAI shown as a fallback for text and speech; dated change-log entry.
    • Retention schedule: rows for transcripts, video-analysis results and Video Indexer’s one-day copy, plus a short note on speech.
    • Privacy policy (built-in text): speech transcription described, with its lawful basis and the right to object.
    • Proposal pages: the consent screen shows the speech notice as small print instead of a transcription toggle, and the product copy no longer says transcription needs a tick.
  10. v1.1.1

    The white paper went on a diet

    The State of Fan Participation 2026 now downloads in about a ninth of the size. Same nineteen pages, same words, same pictures to the eye, just without the weight. It lands faster on a phone and clogs fewer inboxes.

    • White paper PDF replaced with a compressed version: 8.9 MB down to 1.0 MB.
    • Page count and text unchanged; the download link and pop-up are untouched.
  11. v1.1.0

    We asked first

    The site now asks before it sets a single analytics cookie. Say yes and Google Tag Manager loads with analytics on and every advertising signal switched off; say no and nothing from Google loads at all. Either answer is one click, and you can change your mind any time from the footer. Plausible, which uses no cookies, carries on counting visits as before.

    • New cookie banner on the public site, with Accept and Reject given equal weight.
    • Google Tag Manager loads only after Accept, with Consent Mode keeping advertising storage and personalisation denied.
    • Cookie settings link in the footer reopens the banner; rejecting later clears Google Analytics cookies.
    • The white paper offer waits until a first-time visitor has answered the banner, so only one card shows at a time.
    • Content Security Policy now lists Google Tag Manager and Google Analytics.
  12. v1.0.0

    A new front door

    We rebuilt the website from a blank page. It now opens on eighty different fans, because that is the whole point: you have millions of them and know almost none. Behind that sit the things people kept asking to see: a campaign set up from one sentence, a keepsake for every fan, a card for every partner, a report on what it earned, and a free launch package for rights holders. The old pages have been tidied away with proper redirects, so nothing you bookmarked has gone missing.

    • New home page, built around the gap between reach and relationship, with the product in the first scroll.
    • New pages: the platform, how it works, for brands, Autopilot, Connect your AI, leagues and networks, trust and pricing.
    • New free launch package: apply at /launch, with a work email on your organisation’s own domain, and a person reviews every application.
    • A separate route for brands, sponsors and agencies at /partners/contact.
    • Our first white paper, The State of Fan Participation 2026: the home page offers it after a few seconds, and it is yours for an email address at /state-of-fan-participation-2026.
    • Legal documents, Insights and this changelog move into the new look, with every address and every published version unchanged.
    • Old addresses (/packages, /features, /ai-agents, /connect-claude, /partners and the rest) now redirect to their new homes.
  13. v0.57.1

    A quiet shelf for the social campaign

    The Buffer campaign needs its post images and carousel PDF at a plain web address it can fetch, so they now live at fandemiq.net/social/<filename>. Buffer is welcome; search engines and AI crawlers are asked to look away: the folder is disallowed in robots.txt and every file in it says noindex.

    • Fifteen post images, the carousel cover (c01.jpg) and FANDEMiQ-how-it-works.pdf are served from /social/.
    • Every /social/ response carries X-Robots-Tag: noindex, nofollow, noimageindex, noai, noimageai.
    • robots.txt disallows /social/ for every crawler.
  14. v0.57.0

    Choose what each sample plays as, on a roomier page

    Approved samples used to take their part on the page from their place in the list: the first a FanMoment, the second a Fan Wall, the third a Story. If the best picture for the wall was the first one, you had to shuffle approvals to get it there. Now each approved sample has a Plays as box: leave it on In order and nothing changes, or pick FanMoment, Fan Wall or Story for that sample. The rest keep their place in the order.

    • Each approved sample card has a Plays as choice: In order (the old rule), FanMoment, Fan Wall or Story.
    • Saved with the other sample settings; existing proposals stay exactly as they were.
    • A page from before sponsored outputs still plays every sample as a FanMoment.
    • Samples are laid out one per row: the picture on the left, staying in view while you scroll; then On the page (caption and sponsor) and The picture (who is in it, your words, and every redraw button in one row). On a phone each card stacks.
  15. v0.56.0

    Set up the next sample without waiting

    Make 1 more used to lock while a sample was being made, so setting up three meant waiting for each one in turn. Now you can set up another straight away: it waits in line and starts the moment the one before it is done, and each sample appears on the page as soon as it is ready. The Make 1 more form is also a proper dialog now, laid out the Material way: the background as a two-way choice, then the fan, then Cancel or Make.

    • Make 1 more stays available while a sample is being made; the banner counts how many are on the way.
    • Samples set up together are made one after another, and each appears as soon as it is done.
    • A sample the platform lost no longer holds up the ones behind it.
    • Make 1 more is a dialog: Background (Generate one or Upload my own), then the fan’s age range, gender and words, then Cancel or Make.
  16. v0.55.0

    Every sample has a fan in it, and you choose who

    Approve samples had three ways to add a sample: Upload your own pictures, Add people to my backgrounds with its own words box, and Make 1 more. Now there is one. Make 1 more opens a small form: draw a background or upload the client’s own, pick the fan’s age range and gender, add any words, and press Make. Every new sample has a fan in it. Each card also has Age range and Gender pickers beside its words, so you can swap in an older man or a younger woman and redraw. The pickers only offer people our stock photos actually have.

    • Make 1 more asks for the background (Generate one or Upload my own), the age range, the gender and optional words.
    • Each sample card has Age range and Gender pickers; changing one turns Redraw into Save and redraw, which puts in a new person who fits.
    • Upload your own pictures, Add people to my backgrounds and the Words for the people in my backgrounds box are gone. Pictures already uploaded as samples stay.
    • Needs platform v10.143.0; on an older platform the pickers show every combination and the choice is ignored.
  17. v0.54.1

    The faint logo you can actually read

    The last fix drew the logo on a coloured page as a solid dark blob, with High Noon’s name lost inside the disc, and the large copy was cropped by the page edge so only a sliver showed. On a coloured page the logo is now drawn in two tones, so the name stays readable inside the disc, and on a wide screen it sits whole beside the text instead of cut off. It is still faint, and the text is still checked against it. Neutral pages, narrow screens and older proposals are unchanged.

    • Coloured pages draw the faint logo in two tones instead of a flat silhouette.
    • On screens 1000px or wider the logo is smaller and whole, not cropped to a sliver.
  18. v0.54.0

    The app can have its own screen colour

    Until now one colour, the page background, painted both the proposal page and the demo app’s screens, so on a strong page colour like High Noon’s sky blue the phones blended straight into the page. Client & brand now has an optional App screen colour. Leave it empty and nothing changes; set it, press Apply to the demo app, and the app’s screens take that colour while the page keeps its own. The phones on the page show the colour the platform really used.

    • New optional App screen colour on Client & brand (empty = the page background, as before).
    • Use the Manager’s version copies a changed app background into the app screen colour when one is set, never over the page background.
    • Changing it marks the demo app as needing Apply, like any other brand change.
  19. v0.53.2

    The faint logo is now a faint logo

    On a strongly coloured page the logo repeated down the page was drawn in its own colours at 12%, and High Noon’s orange disc over its sky blue differs so little from the page that it simply could not be seen. A coloured page now draws it as a one-colour shadow, dark on a light page and light on a dark one, which is also how the text contrast check always assumed it was drawn. Neutral pages and proposals that went live before page version 10 are unchanged.

    • The logo down the page and in the footer is a one-colour ghost on a coloured page (--crest-filter), at the same strength as before.
  20. v0.53.1

    Say who should be in the backgrounds

    Add people to my backgrounds now has a box above it for words about the person, such as the person is under 25 years old. Type them first, choose your images, and each one comes back as a new sample with a person in it, picked to fit what you wrote. Before, the words could only be added to a sample after it was made.

    • New Words for the people in my backgrounds box on Approve samples; its words go with the images and are kept on each new sample.
  21. v0.53.0

    Add people to my backgrounds

    On Approve samples there is now an Add people to my backgrounds button. Choose one to three of the client’s own pictures and each becomes a new sample with a stock person placed into it, ready to approve like any other. Before, Upload your own pictures kept a file exactly as it was, so a background went in with nobody on it, and the only way to put a person on it was one card at a time. Each new sample uses one AI edit and no AI background.

    • New Add people to my backgrounds button on Approve samples: one to three images, one new sample each.
    • Words typed on a card that name an age, such as under 25, are used when picking the person (needs platform v10.142.0).
    • Upload your own pictures is unchanged: it still stores a finished picture as it is.
  22. v0.52.3

    The crest shows up on a coloured page

    The client’s logo repeats large and faint down the proposal page. On a white or grey page 7% is plenty, but on a strong colour like High Noon’s sky blue it all but disappeared. A coloured page now draws it at 12%, still well behind the words, and the text is checked against it at that strength so nothing becomes harder to read. White, cream, grey and black pages, and proposals that went live on an older page version, look exactly as before.

    • The faint logo down the page and in the footer is stronger on a coloured page background.
    • Text is still checked to read on every part of the page, the logo included.
  23. v0.52.2

    Re-run no longer goes round in circles

    When the demo app’s sponsors had been changed by hand in the Manager, pressing Re-run on the Sponsor logos line quietly did nothing: the platform left the Manager’s version alone, the line stayed amber, and Generate gave you no way past it. Generate now shows the same Left alone box as Client & brand, so you can overwrite the Manager’s version from there, and the line goes green once the sponsors are sent.

    • A run on Generate that the Manager held back shows Overwrite the Manager’s version and Keep the Manager’s version.
    • Overwrite on the sponsors line sends just the sponsors again, not the whole brand.
  24. v0.52.1

    Every idea on an activity the app really has

    Reading a brief could come back with an idea on an activity the demo app was never given, and the Brief step showed it as a bare “Activity 24” with no questions. Confirming would then have left that idea out of the demo app without a word. The Brief step now names the activity, says it isn’t in this demo app, and won’t confirm until you add it on the Activities step or pick another. With platform v10.140.1 the brief is read against the demo app’s own activities in the first place, and an idea you’ve already added with + Add activity under the same name is used as it is instead of copied a second time.

    • An idea mapped to an activity the demo app doesn’t have shows that activity’s name with “not in this demo app”, never a bare number.
    • Confirm stops and says which ideas need an activity the demo app has.
    • An added activity the brief uses keeps its own row: no second, empty “Hot Take” on the Activities step.
  25. v0.52.0

    Tweak it in the Manager, the proposal follows

    Once a proposal has made its demo app, you can fine-tune the app in the Manager: a colour, a font, the logo, an activity’s name, its card line or a question’s wording. Then press Use the Manager’s version and the proposal copies exactly what you changed, so its phone mock-ups show what the real app shows, and the two stay in step from then on. If you swapped a FanMoment’s background in the Manager, it tells you which sample pictures stand on the old one and offers to re-make them on the new one. That costs a new AI picture each, so it always asks first.

    • New Use the Manager’s version button on Client & brand, next to Apply to the demo app.
    • Copies only what was changed by hand in the Manager: colours, fonts, the client’s name, the logo, activity names, card lines, shown or hidden, and question wording. Edits you made here and haven’t sent yet stay.
    • The phones on the page take the app’s own skin at the same time.
    • The Left alone box offers Use the Manager’s version for the brand, activities and backgrounds, instead of Keep, which left the proposal and the app apart. Sponsors and the open or closed setting still offer Keep.
    • Samples standing on a background the Manager no longer uses can be re-made on the Manager’s background, after you confirm.
    • Needs platform v10.140.0 or later; an older one says so plainly.
  26. v0.51.2

    A blue page stays blue

    A proposal whose page background is a real colour now shows that colour. Since version 4 the background set on Client & brand is meant to be the page itself, but the depth styling on top kept only how light it was and drained the colour out, so High Noon’s sky blue came out a muddy grey under its yellow hero. The page now keeps the colour as set, with its sections and cards in deeper and lighter shades of the same colour. White, cream, grey and black pages look exactly as before.

    • Page version 10: a coloured page background is kept exactly as set under the depth page; its band and cards are shades of its own colour, not of the accent.
    • Drafts take it straight away. A live proposal keeps the look it went live with until it goes live again.
    • Every text colour is still checked to read at 4.5:1 on the page, the bands and the cards.
  27. v0.51.1

    The web address and email guide, one click from anywhere

    The guide to running FANDEMiQ on a client’s own web address and email was only reachable by link. It is now in the footer under Resources, so it is there on every page when you need to send it.

    • Footer: Resources now links to Web address & email (/setup/web-address-and-email).
  28. v0.51.0

    Paste their website, get their guide

    The web address and email guide no longer needs a hand-built link. Paste a client’s website into the box at the top, in whatever form you have it, add their name if you like, and every address on the page becomes theirs. Copy link gives you something to send. The page also now copes with both kinds of client: those who want fan emails sent through their own mail server, and those who would rather we sent them from their domain. With nothing filled in, the page is a worked FQ Sports example rather than a page of placeholders.

    • New Personalise this guide box on /setup/web-address-and-email: website (any form, e.g. https://www.yourclub.com/tickets) and an optional name.
    • Copy link copies the personalised page, ready to send; Back to the example clears it.
    • A website the box can’t read is refused with a message rather than quietly ignored.
    • With nothing filled in, the page shows FQ Sports and fqsports.app as a worked example.
    • Nothing is fetched from the client’s website: only its address is used.
    • Two ways to send fan email, chosen on the page: through the client’s own mail server (the default) or by FANDEMiQ from their domain. What we ask for, the steps and the checks follow the choice, and the copied link carries it.
  29. v0.50.0

    Your own web address and email, explained once

    Clients who want fans to open the app at their own address, and get fan emails from their own mail server, used to get a bespoke document. There is now one page for it, /setup/web-address-and-email, that says what we need from them and what we set up. Send it with the client’s name and domain on the end of the link and it reads as theirs: their name at the top and their own addresses in every example.

    • New page at /setup/web-address-and-email: what we need from the client, the five steps we take (only the two DNS records are theirs), what their IT team should check about their mail server, and a three-point test.
    • Add ?client=Your%20Club&domain=yourclub.com to the link and the page names the client and shows fans.yourclub.com, fans@yourclub.com and the rest. Without them it reads generically.
    • Anything typed into the link is cleaned first: an unusable name is left out and an unusable domain falls back to yourclub.com.
    • Listed in the sitemap; not linked from the menu, so it is shared by link.
  30. v0.49.0

    New client setup, minus the email ping-pong

    Getting a new client live used to mean a long thread asking for a logo, some colours, the wording, a web address and a sender email, one reply at a time. There is now a public page, /setup, that shows a new client up front what setting up their account involves: logo, colours, fonts, their own words, web address, sender email and where fans land. It comes with live examples (a phone that repaints in their colours, a character counter and the two DNS records) and an “I have a link” box that takes them to their own private setup page on the Manager. That private page runs on the Manager (v10.131.0, live), and the box now leads straight there.

    • New public page at /setup explaining each thing a client will be asked for.
    • Three live examples: a phone that repaints in the colours you pick, a character counter with the real limits, and the two DNS records for a web address.
    • The “I have a link” box only opens an https link on the Manager’s own address; anything else is refused.
    • The page is listed in the sitemap but not linked from the menu yet, so it is shared by link for now.
    • The private setup page runs on the Manager (v10.131.0, live), so the “I have a link” box leads there.
    • Fonts: pick from 30 popular fonts or upload your own font file; the private page asks you to confirm you may use it.
  31. v0.48.1

    The “left alone” choice is where you can see it, and says what it does

    The new “Left alone in the demo app” box, with its Overwrite and Keep buttons, sat at the very bottom of the Samples, Activities and Publish pages, out of sight under the pictures. It now sits at the top of each page, above the samples, where you can’t miss it.

    • The Left alone box now appears at the top of Approve samples, Activities and Publish.
    • The box now says plainly what each button does: Overwrite replaces the Manager’s version and loses its changes; Keep leaves the demo app as it is, and from then on that group on the proposal and in the app are separate until you press Overwrite.
  32. v0.48.0

    The demo app keeps what you changed by hand

    Until now, pressing Apply to the demo app, Save or Re-run on the sponsors sent the whole proposal to the Manager every time, quietly wiping anything staff had tweaked there by hand. The Manager now notices when a group has been changed by hand since we last wrote it, and the Studio leaves that group alone, says exactly what it left, and offers a deliberate “Overwrite the Manager’s version” button if you really do want ours to win.

    • Brand, sponsors, sample backgrounds, open/closed setting and each activity are checked separately: one left alone never holds back the others.
    • Save never overwrites. It only sends what the Manager still agrees we last wrote, and tells you what it skipped.
    • Apply to the demo app now also sends the activities, backgrounds and open/closed setting, all guarded, and lists every group it left alone.
    • Each group left alone gets two deliberate buttons, on Client & brand, Samples, Activities and Publish: “Overwrite the Manager’s version” (with a confirmation) or “Keep the Manager’s version”, which accepts it, sends nothing, and stops Publish waiting on it.
    • The Samples page no longer keeps saying “save again to retry” when the real answer is that the Manager’s backgrounds were changed by hand.
    • Needs Manager v10.130.0 or later; against an older Manager nothing changes.
  33. v0.47.1

    The footer stops running down the page

    The Legal list had grown to nine links, which made it a sixth column that dropped under Platform and stretched the footer into one long ribbon of text. Legal is now a tidy row of its own beneath the other four columns, wrapping neatly on a phone.

    • Platform, Partners, Company and Resources sit side by side on one row.
    • All nine legal links run along a single Legal row instead of a vertical list.
  34. v0.47.0

    The email now says what the fan actually gets

    A fan who made a photo was being emailed about their “personalised video”, and the demo emails never said which activation they came from. Now every kind of result has its own wording, each demo activity’s email names it, and the brief reader writes a friendly opening line for each idea so the email reads as part of the same story as the proposal. The mock email on the page now shows the button and line the real one carries.

    • The brief reader’s ideas carry an email line (up to 160 characters), kept and sent to the demo app with the rest of the brief.
    • The mock delivery email has one button, “See your FanMoment”, and the real email’s own sentence as its default line; the invented “Open your share page” button is gone.
    • Needs Manager v10.129.0: photo, video, mosaic and picture emails each say the right thing, demo emails name the activity, and cloned events keep their email body and button.
  35. v0.46.0

    Sponsors stop waiting for an invitation

    Until now the demo app only heard about sponsors when you ran the Sponsors line on Generate, so a sponsor tweaked on Client & brand stayed put however many times you pressed Apply to the demo app. Now Save and Apply send the sponsors too whenever they have changed, and the frame on the walls, stories and FanMoments finally says what the page says: the sponsor’s own label and name (“Proud to Support Toast Beer”), not a stock “Sponsored by”.

    • Apply to the demo app sends the brand, then the sponsors when they changed since they were last sent. If the sponsors can’t go, it says why; the brand still goes.
    • Saving a sponsor change on Client & brand sends it to the demo app, as a brand change already did.
    • Each sponsor goes with its frame line: its label then its name, up to the platform’s 80 characters.
    • Because the line is new, proposals with sponsors show their sponsors as changed once, so the next Apply redraws their frames.
  36. v0.45.1

    Words back in their lanes

    Two Proposal Studio fixes. The Activities step’s “What saving sends where” note had lost its icon, so its words were squeezed into the icon’s 20-pixel column, one word per line, down the whole page. And a sample’s caption now heads the words beside its Fan Wall or Story on the proposal page, instead of being ignored in favour of the fixed title.

    • Activities: the “What saving sends where” note reads across the box again, and any Studio note without an icon now spans the full width.
    • Samples: a Fan Wall or Story sample’s caption becomes its title on the page; blank keeps “Every fan on one wall” or “A story to post”.
    • The caption hint on the Samples step says where it goes for each kind.
  37. v0.45.0

    A policy that watches before it bites

    Two more security steps from today’s review, both invisible unless you go looking. The site now tells every browser which origins its scripts, styles, fonts and images are allowed to come from, in report-only mode: nothing is blocked yet, but anything that would have been is reported back to us, so the rule can be switched on once the reports go quiet. And the thirty-odd known weaknesses buried inside the libraries we depend on are down to one, by pinning each to its patched release within the same major version.

    • Content-Security-Policy-Report-Only on every page, with the origins the site actually uses: Cloudflare Turnstile, Plausible, jsDelivr (the proposal world map and the admin’s JSON editor) and Google Fonts for proposal typefaces.
    • A /api/csp-report endpoint receives the reports: 16 KB cap, one line per directive and host every ten minutes, bodies never logged.
    • Dependency advisories in production code: 35 high → 1 (the last one needs a major upgrade upstream). Each pin stays inside its current major, so nothing changes behaviour.
    • Linting works inside a nested worktree.
  38. v0.44.4

    Pictures back

    For about an hour after v0.44.3 went live, no image stored in the CMS could be read: site photos, team pictures and every proposal image answered with an error, and the Studio could not save a proposal because it could not check its pictures existed. The upgraded storage library expects a new column on the two image tables, but it only asks for it when the live storage token is present, so the migration written on a laptop without one never created it. The column is added now, and migrations are generated with the storage library switched on so this cannot happen again.

    • Adds the storage library’s _objectKey column to media and proposal-media.
    • Migrations and the schema-drift test now load the storage adapters with placeholder tokens, so the schema they see is the one production runs.
    • No content was lost: the pictures were always in storage, only the lookup failed.
  39. v0.44.3

    Locks changed, and the test run stops counting ghosts

    A security pass over the site. The two libraries it stands on, Payload and Next.js, were twelve and sixteen releases behind, and the gap held fixes for an account takeover and a remote-code-execution hole in image resizing, so they are now current. A few doors were also closed that were open on principle rather than in practice: anyone who knew an admin’s email could lock them out of the Studio with five wrong passwords, the contact form could be bypassed with a plain POST, and a missing CAPTCHA secret would have waved every bot through. Nothing you do day to day changes.

    • Payload 3.79.0 → 3.92.0 and Next.js 15.5.12 → 15.5.28: nine critical advisories gone, including a pre-authentication account takeover and unauthenticated remote code execution in image optimisation. sharp 0.35.5 for the logo clean-up (libvips and librsvg fixes).
    • Admin sign-in can no longer be locked out from outside: Payload’s five-attempts-then-lock rule is off, because the PIN flow sets a fresh random password on every sign-in and nobody ever types one.
    • The public write to contact submissions is closed; the form itself still works, through the server, after Turnstile.
    • If the Turnstile secret is ever missing in production, submissions are refused and an error is logged, instead of every one passing on Cloudflare’s test key.
    • The sign-in response no longer echoes the session token in its body; the HttpOnly cookie is the only copy.
    • Every page now sends X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy headers.
    • For whoever runs the tests: the runner no longer picks up the stale copies of the repo under .claude/worktrees (that was 14,000 extra tests and 1,800 failures that were not ours, four minutes instead of forty seconds). The unused npm lockfile is gone; pnpm is the one.
  40. v0.44.2

    What is that box for?

    On Activities, a fold-out called "Screen wording" held two boxes per phone screen, and nothing said what they changed. They are the caption above and the line under each phone mock-up on the proposal page, and they never reach the demo app. The fold-out now says so, and its name says it too.

    • "Screen wording" is now "Captions under the phones", tagged Page only, with a line saying the demo app never sees them.
    • Every box on an activity says where it goes: Name and One-line intro are "Page + demo app", Description and the captions are "Page only". A box at the top spells out what saving sends where.
    • Character counts under every box. The Name is cut at 40 in the app, and the One-line intro shows up to 160 on the page but only its first 90 in the app (it turns amber past 90).
    • The line also says where the demo app’s questions are set: the Brief step, or when you add an activity.
    • The in-app guide says which activity fields go to the demo app (name, intro, description) and which are page-only.
  41. v0.44.1

    Generate stops saying "Working" for a request that died

    A Generate step on the Cure sat on "Working" and never finished. The page was fine; the server it ran on was not. When the database dropped a connection for a moment, Payload left a rejected promise nobody was listening to, and on Vercel that takes down the whole server, along with every request still running on it, yours included. Nothing logged an error, so the page kept saying Working for six minutes. That connection blip no longer takes anything down, and a step that does die now shows as stopped in about a minute.

    • A failed first database connection no longer crashes the instance (it had done so 139 times since June, each time killing whatever else was running on it).
    • While a Generate step runs it stamps a heartbeat every 15 seconds. No heartbeat for 75 seconds and the line says stopped, with Try again, instead of waiting six minutes.
    • Deleting a proposal uses the same check for "still being made".
    • The sponsor line was never slow: its "2m 03s" is time since the proposal was last saved, not how long it ran.
    • One small migration adds the heartbeat column.
  42. v0.44.0

    The demo app finally uses your backgrounds

    The demo app was standing every FanMoment on one stock backdrop it made on its own, with "stadium and crowd" written into the instructions even for a band. The backgrounds you approved or uploaded on the samples never reached it. Now they do: approve a sample and its background goes to the app, so three activities show three backgrounds, and the app’s emails come from the client’s name instead of FANDEMiQ Admin.

    • Approving samples (or opening the page again) sends their backgrounds to the demo app’s FanMoments, one per FanMoment in turn. Up to three.
    • The page says so on the Samples step if the app is behind, and Publish waits for it, like the brand and the sponsors.
    • The FanMoment instructions no longer ask for a stadium, and sponsor logos go on an advertising board or banner that suits the scene.
    • Fan emails from the demo come from the client’s name (needs platform 10.124.0).
    • Needs the platform at 10.124.0: until then the Samples step says the app can’t use the backgrounds yet.
    • One small migration adds a fingerprint column.
  43. v0.43.1

    A PIN screen you can read

    Two things looked wrong on the access-code screen. The draft warning an admin sees was pale text on cream, so you could not read it, and a dark logo on a dark background (a black crest, a black wordmark) all but disappeared. The warning is dark on cream now, and a logo on a dark screen gets the same soft light halo the proposal page already gives a dark crest.

    • The draft note on the PIN screen uses its own dark text again (the shell’s paragraph colour was overriding it).
    • A logo on a dark canvas gets a light halo, as the hero does, so a dark crest stays visible.
    • The halo goes only where the canvas is dark; a light screen shows the logo as it is.
  44. v0.43.0

    Samples, one at a time

    Samples cost AI credits, so they are no longer made in threes. Generate makes one, Make 1 more makes one more, and before anything is made you can upload the client’s own pictures as samples, which cost nothing. Each card now says what it plays as on the page, every card has an Add to the prompt box for nudging it until it looks right, and a sample you remove stays removed.

    • Make 1 more (it was Make 3 more), and the first Generate makes one sample, not three. It is the smallest set a live proposal needs; add more one at a time.
    • Upload your own pictures on Approve samples, before anything is made or any time after: one or several at once (PNG, JPEG or WebP, at least 400 pixels each side, up to 4 MB). They cost no credits and need no demo account, and can be approved, captioned and removed like the others.
    • Generate no longer makes a sample unasked when the proposal already has some (your own pictures, say).
    • Each card shows Plays as FanMoment, Fan Wall or Story: the approved samples play on the page in that order, then FanMoment again, and a page from before sponsored outputs plays every one as a FanMoment. (There is no Film sample: a film is an activity’s result tile.)
    • Add to the prompt on each made card (up to 300 characters): Save and redraw draws the same picture again with your words; New person, New background and your own background use them too. Needs platform v10.123.0; on an older one it says so and nothing is charged.
    • A removed sample no longer comes back when the poll brings in new or redrawn samples (the poll and your Save now take the proposal’s row lock).
  45. v0.42.0

    The bar tells you when the app is behind

    Edit a colour, swap the logo or change the brief and the page updates at once, but the demo app and the samples are copies the platform made, and they stayed as they were until someone pressed a button nobody knew about. Now the progress bar says so: the step that needs pushing goes amber, says what to press, and Publish refuses to go live until the app has caught up.

    • Client & brand goes amber when the colours, fonts, logo or name differ from what the demo app was last sent. The reason says to press Apply to the demo app.
    • Approve samples goes amber when the brand or the brief changed after the samples were made.
    • Generate goes amber when the sponsors or the brand changed since the sponsor logos were put on the app.
    • Publish & send lists every change that is behind, each linking to its step, and the proposal can’t be set live until none is. A live proposal that falls behind shows the same warning.
    • Proposals made before this release have nothing to compare against, so they show as up to date until their next push.
    • One small migration adds two fingerprint columns.
  46. v0.41.0

    Sponsors, in their own words

    Every sponsor banner used to open with the same two words, "Sponsored by", whoever was paying. Now each sponsor has its own label. Carlsberg can be "Proudly supported by", the shirt maker "Official kit partner", the local bakery "With thanks to", and each banner on the page says so.

    • A "Label before the logo" box on each sponsor (Client & brand). Blank keeps "Sponsored by".
    • It shows wherever the page shows the sponsor: the FanMoment reveal, the Sponsor card, the Fan Wall, the Story and the delivery email mock-up.
    • The default line under a sample ("<label> <name>") follows the label too; a line you write on a sample still wins.
    • One small migration adds the label column to sponsors.
  47. v0.40.1

    A proposal with a name on it

    Every proposal used to open in a tab called "Private proposal · FANDEMiQ", whoever it was for. Now the tab, the browser history and the link preview say who it is for: "Leeds United - A Proposal by FANDEMiQ".

    • The proposal page title is "<Client name> - A Proposal by FANDEMiQ", from the client name on the proposal.
    • A draft keeps a plain "A Proposal by FANDEMiQ" title, so a name never shows before the proposal is published.
    • Search engines are still told to stay away (noindex is unchanged).
  48. v0.40.0

    Sponsors, on the app too

    Sponsors used to be on the page and nowhere else. Now Generate has a Sponsor logos line that puts them in the demo app: a Fan Wall overlay, a Story frame and the FanMoment scene, made from the logos you uploaded. It remembers what it sent, so when you change a sponsor, its logo, the headline or the brand colours, the line says it is out of date and offers a re-run instead of leaving the app quietly wrong.

    • Generate: a Sponsor logos line (only when the proposal has sponsors, or some were sent before), with Add logos, then Re-run
    • It is marked out of date, and the page stops saying everything is generated, when a sponsor, its logo, its tone, the headline, the brand colours or the club logo changes after it ran
    • Removing every sponsor and re-running takes them off the app again
    • Needs Manager 10.121.0: an older platform answers with one plain sentence, not an error
    • A wall or story already made keeps its old look until it is made again; the logo on a FanMoment is drawn by the image model from the reference, not pasted. Both are said on the line
    • One migration: the line’s status, when it last ran, and a fingerprint of what was sent
  49. v0.39.1

    Colour by numbers

    The Brand panel used to hand you five colour swatches and a shrug. Now it says where the colours came from (Wikipedia, their website, the logo, or you), whether the read was sure, and keeps Re-read brand right there. Each swatch has a number, and a little mock of the page wears the same numbers: point at a swatch and its places light up, so “Second club colour” finally means “those lines and the big step numbers”. Logos can be SVG now (we draw them to a PNG and bin the SVG, scripts and all), and a date question gets its own phone instead of pretending to be a text box.

    • Brand: a source line with the confidence and Re-read brand always to hand (it asks first over colours set by hand, which a re-read keeps)
    • Brand: a numbered mock of the page beside the swatches; hovering or focusing a swatch lights where it goes, for a light page, a dark page or a dark hero
    • Brand: plainer hints under each swatch, true to how the page uses them
    • Club and sponsor logos can be SVG, up to 4 MB: drawn to a transparent PNG on upload, never stored or served as SVG, nothing it points at fetched
    • Date questions show a date phone (day / month / year, Next); a date added in the Studio stays a date even before the platform says so
  50. v0.39.0

    Brought to you by…

    Proposals can now carry the client’s sponsors, because nothing says “real partnership deal” like a beer logo on a fan’s proudest moment. Add up to five on Client & brand (one is the headline), and the samples stop being three of the same: the first plays as a FanMoment with a fifth “Sponsored by” step, the second as a Fan Wall that finds the fan and hands the screen to the sponsor, the third as a Story with a title card and a sponsor outro. Each sample can pick its own sponsor and line, white logos land on a dark plate so they never vanish, and a proposal can no longer go live with nothing to show.

    • Sponsors on Client & brand: up to 5, one headline, logos tidied like the club logo (trim, see-through background, Keep the original)
    • Approved samples play as a FanMoment with a Sponsored by step, a Fan Wall and a Story, each with its own sponsor and optional line
    • The activities’ wall, story and film tiles and the delivery email carry the sponsor
    • A proposal needs an approved sample to go live, and a live one can’t lose its last
    • Page version 9: live proposals keep their look until they go live again
  51. v0.38.1

    Added, in one line

    The note that confirms a new activity was squeezed into a sliver of a column, so “Added Celebrate with the Fans” read one word per line, like a very slow telegram. It now sits beside its tick and reads as a sentence.

    • The “Added …” note after adding an activity shows its tick and reads on one line
  52. v0.38.0

    Your activity, your questions

    Add an activity got a proper makeover and a lot more say. Pick a type from four clear cards, describe it in a line or press Start blank to skip the AI altogether, then shape the draft: remove a question, add a photo, selfie, video, upload, text or date one, up to eight, and the Studio stops you only when the type would lose what it needs (a FanMoment without a photo, say). When the AI’s own safety filter takes fright at an innocent line, the Studio now says so and offers Start blank on the spot instead of a hopeless “try again”. Uploaded logos arrive trimmed, with a flat background made see-through and white inside the crest left alone, plus a Keep the original switch; and the samples estimate finally matches cards made side by side.

    • Add an activity redesigned: numbered steps, type cards with an icon and what fans end up with, the draft as a card, other ideas as clear choices
    • Question editor: each question shows its kind; remove any the type can spare (the rest say why they stay); + Add a question from the type’s kinds; eight at most; a new question needs its wording
    • Start blank: no AI, instant, the type’s bare questions (FanMoment a selfie, Fan Wall a photo, Story a photo and a text answer, Film a video) for you to name and word
    • A draft stopped by the AI’s safety filter says so, with Start blank right there
    • Logo upload: margins trimmed, a flat border made transparent (white inside the crest stays), the preview fits any shape, and Keep the original switches back
    • Samples estimate: about 4½ minutes for three cards, made in parallel
  53. v0.37.0

    Describe it, and it’s in the app

    The Activities step has a new button: Add activity. Pick Fan Wall, FanMoment, Story or Film, describe it in a line, and the platform finds the closest idea in its library and words it for the client. Rename it, reword any question or try one of up to three other ideas before anything is made; Add to demo app puts it in the client’s demo app for real, once, however many times the button gets pressed. On the page, a wall, story or film now ends with a Sample of what fans get, made from your approved samples: pause it, or see the finished frame if you prefer less motion. Live proposals keep their layout until they go live again.

    • Add activity on the Activities step: a type, one line, an editable draft from the platform’s idea library, “Check this” on a loose match, up to three other ideas that keep what you typed
    • Added activities are made in the demo app straight away (a retry or double click still makes one), then saved like any other: rename, reword, hide
    • Plain words for every refusal: content check, AI allowance used up, demo app busy, idea withdrawn, no backdrop for a FanMoment
    • Each activity card shows its type; a wall, story or film without approved samples says where to make them
    • Proposal page version 8: Fan Wall, Story and Film end result tiles, labelled Sample, with a Pause button and a still final frame for reduced motion
    • A client brief never renames or hides an activity you added
  54. v0.36.1

    Delete means delete

    Deleting a proposal in the Studio used to leave the client’s demo app sitting in the Manager. Now it goes too: the demo app, its branding and any fan test uploads are erased first, and the proposal is deleted only once the Manager confirms. If the Manager says no (a Microsoft subscription, an account the client now owns, samples still running) or can’t be reached, nothing is deleted and the Studio says why.

    • Delete for good erases the demo account in the Manager before the proposal goes
    • Refusals keep the proposal and explain: subscribed, converted to a client’s own account, busy, or couldn’t reach the Manager
    • An account the Manager says is already gone doesn’t block the delete; an unclear answer does
    • A demo app whose Generate timed out before the Studio saved its id is found by the page address and erased too
    • Delete waits while Generate is still making the demo app, and gives the Manager two minutes to erase it
    • The delete panel’s wording says the demo app goes with it
  55. v0.36.0

    Dollars, euros, rand and rupees

    A proposal can now speak its client’s currency. You still enter every price in pounds; pick US dollars, euros, South African rand or Indian rupees on the Pricing step and the whole page follows, converted at the European Central Bank’s daily rate and always rounded up to a clean number, so a converted price never undercuts the pound price. The rate locks the first time the proposal goes live, so a client never sees a price drift. Each proposal can also set its own pay-as-you-go rate, and the Pricing heading and intro now mention pay as you go and can be rewritten per proposal.

    • Currency per proposal: £, $, €, R or ₹ (rupees in Indian grouping, e.g. ₹21,00,000); prices entered in pounds, converted and rounded up
    • European Central Bank daily rates; locked at first go-live; a non-pound proposal can’t go live if today’s rate is unavailable, so it never freezes in pounds by mistake
    • Pay-as-you-go rate per proposal; the calculators and savings use it
    • Pricing heading and intro: automatic wording that names pay as you go (and follows what you offer), or your own
    • The Studio shows each pound figure as it will appear on the page, and the AI’s answers quote the same converted prices
    • Proposals that went live before this keep their pounds and their wording; Enhanced budget fine print no longer says “£”
  56. v0.35.1

    One button for older demos

    Demo apps built before the venue fix kept their venue-only activities, and a finished demo is never rebuilt. With Manager 10.111.2, pressing Fill any gaps or saving Activities now opens them up too. The handover says so.

    • Handover: NHL and Museums steps updated (Fill any gaps lifts the venue lock on a finished demo)
  57. v0.35.0

    Loose ends, tied

    The last of the sweep: the things left as “low value” got done anyway. A redrawn sample on a live proposal now waits for approval before the client sees it, a treatment changed after the brief was read says the reading is out of date, the copy that only exists in the page’s mock-ups says so, and history stops hoarding pictures nothing uses any more.

    • Live proposal: a redrawn sample is unapproved until you look at it again
    • Client & brand: changing the treatment after a read says to read the brief again
    • Check the copy: the phone and email mock-up fields say they are page-only
    • History: when old versions drop off, the pictures only they used are deleted
    • Home page: a CMS field left empty shows the built-in wording instead of a blank heading or button
  58. v0.34.2

    Packed for the MacBook

    No new features: the handover note is rewritten for working from the MacBook Pro, with everything on GitHub, the local test setup for the Proposal Studio written down, and what is still to do in one table.

    • docs/HANDOVER.md: moving machines, local Studio testing, what shipped 19–20 October, open items
  59. v0.34.1

    Open means open

    A proposal with no expiry date told its demo app to stay open without saying for how long, and the Manager’s idea of “open” is thirty days. Live demo apps would have quietly closed a month after their last save. They now stay open for a year unless the proposal says otherwise.

    • A proposal without an expiry keeps its demo app open for a year after each Publish save
  60. v0.34.0

    The demo app finally hears what the page says

    A full sweep of the Proposal Studio, field by field, from the Studio to the page to the demo app. The big one: the demo app used to hear about a proposal’s activities exactly once, when the brief was confirmed. Now every Activities save, every Generate and every restore sends the page’s titles, card lines, questions and what’s hidden, and archiving or expiring a proposal closes its demo app. Along the way a dozen smaller leaks got plugged, from draft pages quoting yesterday’s prices to a “Spot the fan” button nobody could ever see.

    • Demo app follows the page: activity names, card lines, each question and the line under it, shown or hidden (needs Manager 10.111)
    • Archiving or passing the expiry closes the demo app; removing or replacing the brief takes it out of the app too
    • “Text on club colour” now goes to the app as the buttons’ label colour
    • Draft pages show today’s rate card, the same prices as the Studio and the answers
    • The page address locks once the demo app exists or the proposal has gone live
    • “Spot the fan” appears on sample cards, pointing at the fan
    • Uploading a new logo replaces the old crest everywhere on the page
    • Renaming the client renames them in the page’s copy too (never in text you wrote)
    • Editing one screen caption no longer freezes the other one
    • The contact line always has an address; Studio notes when Answers or Pricing are on but can’t show; the together section shows without steps
    • Source Sans Pro and Source Sans 3 are the same font; the version link is on the Payload admin too
    • Approve samples: a redrawn picture shows straight after a Save
  61. v0.33.0

    Proposals now speak FANDEMiQ

    A proposal whose client has no font we can match used to fall back to Fraunces and Manrope, faces left over from the very first hand-built concept page, which nobody had ever seen on anything else FANDEMiQ. New and draft proposals now fall back to FANDEMiQ’s own Bricolage Grotesque and DM Sans, the same faces as this website. A client font picked on Client & brand still wins, and live proposals keep the fonts they went live with.

    • Default fonts for new and draft proposals: Bricolage Grotesque headings, DM Sans text (page style 6)
    • Live proposals keep Fraunces and Manrope until they next go live or have their copy regenerated
    • Client & brand shows the default this proposal actually uses
  62. v0.32.1

    Blue buttons mean blue buttons

    The demo app was painting a club’s buttons in its second colour, so the NHL’s blue went on the app’s titles and its buttons came out grey, the opposite of the NHL’s own site and of the proposal page. The app now gets the club colour for its buttons, with the second colour kept as the fallback for when the club colour won’t show. And the font boxes stopped claiming the brand read had filled them in when it found nothing, and stopped calling Fraunces a FANDEMiQ font. It is the proposal page’s default, not our brand. Both spotted by David.

    • Apply to the demo app: buttons in the club colour; the second colour only as a fallback
    • Font boxes: when the brand read found no font, they say so and ask for the nearest match
    • The default fonts are labelled “proposal default”, not “FANDEMiQ default”
  63. v0.32.0

    Dark hero, light page: your call

    Some clients look best with the whole proposal dark; others, like the NHL, look best with a dark band across the top, the crest large behind the headline, and a light page underneath. Client & brand now asks which you want whenever the page background is dark, and the NHL proposal is back to its dark hero on a light page. A dark crest on a dark hero also gets a soft light halo now, so a black shield never melts into the background.

    • Client & brand, with a dark background: Dark page throughout, or Dark hero on a light page
    • The NHL proposal is set to Dark hero on a light page
    • A dark hero gives the crest a light halo, behind the headline and next to the eyebrow
    • Changing the layout is not sent to the demo app: its brand is unchanged
  64. v0.31.1

    The crest is back where it belongs

    A proposal on a dark background, like the new NHL one, opened on a plain dark hero: no colour wash, no big crest behind the headline. Since v0.20.0 a dark background stays a dark page, and that change had quietly switched the club hero off whenever there was no second club colour. The hero band is back on dark pages, washed with the second colour or the club colour, the crest large behind the headline, fading into the page. Live proposals keep exactly the look they went live with.

    • Page style 5: a dark background keeps the club hero band, crest and colour wash, fading into the dark page
    • With no second club colour, the wash uses the club colour (NHL: black with cyan)
    • New and draft proposals get it now; a live proposal changes only when it next goes live or has its copy regenerated
  65. v0.31.1

    The news page learns to complain

    The News page has been quietly showing “No news yet” on the live site while Substack sits on twenty perfectly good posts. The feed reader swallowed every failure without a word, so there was nothing to go on. Now it says what went wrong in the server logs, which is step one of fixing it properly.

    • Substack feed failures (bad status, network error, empty parse) are now logged instead of silently returning nothing
  66. v0.31.0

    Some proposals deserve to go

    Test runs, duplicates and the one with the typo in the client’s name can now be deleted from the Studio. It lives at the bottom of Publish & send, asks you to type the client’s name back, and won’t touch a live proposal: archive it first, so the client sees a closed page rather than a missing one. Deleting takes the proposal’s history and images with it, for good.

    • Delete this proposal, at the bottom of Publish & send, once the client’s name is typed back
    • A live proposal can’t be deleted until it is archived
    • Deleting removes the proposal, its history, its brief file and every image it or its versions used; the client’s demo app in the Manager is left as it is
  67. v0.30.1

    One name is enough

    An activity the brief reworded captioned every one of its phone screens with the activity’s own name, so “Where Hockey Found You” turned up three times in a row: once as the heading and again over each step. Each screen is now captioned by what it is, Video or Text answer, like the Permissions, Consent and Thank-you steps beside it. Spotted by David.

    • Screens of an activity the brief maps are captioned by their type, on the page and in the Studio’s Screen wording
    • A caption you typed yourself is kept, and a screen with no question still shows the activity’s name so it never disappears
    • The Studio’s caption box says what shows when it is left blank
  68. v0.30.0

    Undo, for whole proposals

    Every proposal now keeps its own history. Each time its content changes (a save, a Generate, an edit in the advanced editor) the Studio keeps a version, labelled with what changed and who changed it, and the History page puts any of them back in one click. Restoring never touches who can open the page: the status, expiry, address, access code and published prices stay exactly as they are, and the restore is itself a version, so even an undo can be undone.

    • History button on every proposal in the Studio: the last 50 versions, newest first, each with Restore
    • A version only when the content changes: job progress, page views, status and PIN changes leave none
    • Restoring keeps the status, expiry, address, access code, published prices, demo-app link and brief file as they are now; an image that no longer exists keeps the current one
    • Redrawn sample pictures are now kept rather than deleted, so an older version brings its pictures back
    • Deleting a proposal deletes its history; the version link no longer hides behind the Studio’s Save bar
  69. v0.29.1

    The Studio finally knows what version it is

    The Proposal Studio and the proposals themselves have their own pages with no site footer, so the version number that tells you which build you are looking at was nowhere to be seen there. It now sits quietly at the bottom of every Studio page, every proposal, and the access-code and closed screens, linking here.

    • Version link at the foot of every Proposal Studio page and the admin home
    • Version link at the foot of every proposal, even when its footer section is switched off
    • Version link on the proposal access-code and “closed” screens
    • One shared version link component, used by the public site footer too
  70. v0.29.0

    Pick a price, any price (but only the ones you meant)

    Not every client wants to choose between a campaign and a monthly account, so a proposal can now offer one or the other, or both. The monthly plans finally show up in the Studio next to the campaign packages, either quote can be filled from the rate card in one click, and the monthly slider gets its own starting point. Along the way the Studio stopped showing template wording for activities the brief had already reworded, and the brand warning stopped asking for a logo that was sitting right there.

    • Pricing: choose Campaign and monthly, Campaign only or Monthly only; the page shows tabs, the campaign view or the monthly account to match, and the copy writer is only sent the prices the page shows
    • Pricing: the Studio shows the monthly plans from the rate card, and each quote has “Use the rate card” to start from the cheapest package or plan for its Fan Moments
    • Pricing: a starting point for the monthly slider (a monthly quote still sets it when there is one)
    • Activities: the Studio’s screen wording now matches the page, with the brief’s captions and questions, and saving a row no longer freezes captions you didn’t touch
    • Client & brand: with a logo uploaded, the unsure-colours warning offers Re-read brand and Replace the logo instead of asking you to upload it; uploading a logo re-reads the brand straight away; the Re-read result no longer vanishes when the page refreshes
  71. v0.28.0

    Findable, and a lot less to scroll

    Search engines were being told every page was called “Something — FANDEMiQ”, and the home page ran on for longer than most novels. Pages now have titles and descriptions that say what they are, canonical addresses so Google stops guessing, and a new Insights section with six plain answers to the questions buyers actually ask. The home page lost two abstract sections and gained a real day of the Autopilot, and cards across the site now arrive one by one.

    • Keyword titles under 60 characters, tightened descriptions and canonical URLs on home, platform, features, packages, partners, about, contact, news and careers (lib/seo.ts)
    • New /insights: six articles on first-party fan data, ticket versus person, running engagement hands-free, what to ask before buying a platform, sponsor outcomes and running it from an AI agent, with article and FAQ structured data
    • Insights in the sitemap, the footer and llms.txt
    • Home page: removed “Why now” and the “Exchange” quote section (the About page already says it), added the Autopilot run log with real cards; about a third shorter
    • Cards on every public page arrive in turn and lift on hover; home stats count up; lighter text on dark backgrounds made easier to read
  72. v0.27.0

    Autopilot, now with a pulse

    The Autopilot page described a thing that runs itself while sitting very still. It now moves like it means it: the headline arrives word by word, the numbers count up as you reach them, the five steps take it in turns to light up, and the cards on the way down rise into place one after another. Everything is decoration, so anyone who asks their device for less motion gets the calm version.

    • Hero: label, headline words, subtitle and buttons rise in turn; “runs itself” shimmers
    • The hero stage and the dark control cards get a soft light that follows the pointer
    • Proof numbers count up when they scroll into view
    • The loop’s five steps pulse in sequence; every card lifts on hover and its icon tips
    • Cards in each grid now arrive one by one (the old stagger never reached them), and a line draws down the getting-started steps
    • Fixed the run log spilling off the right edge of the hero panel on phones
    • All of it switches off for prefers-reduced-motion
  73. v0.26.0

    Autopilot gets its own page

    FQ Sports has been running its matchdays on its own since 15 October: it picks the games, opens a fan activity for each, posts before the whistle and posts what fans said against what happened afterwards, with nobody pressing a button. That engine is now a FANDEMiQ service, and it has a page that says so. The cards on it are real ones, drawn by the Autopilot itself for a pair of made-up teams, and the claims are only the ones we can stand behind: no fan numbers, no testimonials, no prices.

    • New /autopilot page: the five-step loop, a day running itself, what the Autopilot fits, how it is made yours, how you stay in control and how to start, with FAQ structured data
    • Added to the footer, the sitemap and llms.txt (the header has no room for another link yet)
    • Two real post cards, drawn by the Autopilot, in public/images/autopilot
    • Copy lives in lib/constants/autopilot.ts, not the CMS
  74. v0.25.1

    Slow down, look closer

    The sample reveal was over before you could take it in. It now takes ten seconds, holding on each moment long enough to see what is happening, and the panel beside it tells the story as it plays: four numbered steps, each with a line of explanation, joined by a line that fills as the reveal moves on, with the fan’s original photo underneath. The delivery email on a proposal is also about half the size it was, so it reads as the phone-sized email it is, with what’s live today beside it.

    • The sample reveal runs over ten seconds instead of six
    • A timeline beside the reveal: each step explained, lit as it happens, with the fan’s original photo
    • The delivery email mock-up is about half its old size, with its notes beside it
  75. v0.25.0

    Watch the fan step in

    Sample cards on a proposal used to show the fan’s photo next to their FanMoment and leave the magic to your imagination. Now each new sample plays it: the photo, the background melting away, the fan cut out and gliding into the scene, and the finished FanMoment appearing around them. The scene they glide into is the finished picture with the fan erased, so the last moment changes only the fan and nothing jumps. It plays once when the card scrolls into view, Replay runs it again, Spot the fan still works, and anyone who has turned off motion on their device sees the photo and the FanMoment side by side, as before. Samples made before today keep the side-by-side layout until they are made again.

    • An animated reveal on each new proposal sample: photo, cut-out, into the scene, FanMoment
    • Plays when scrolled into view, with a Replay button; Spot the fan stays
    • Reduced motion, and older samples, keep the photo and FanMoment side by side
    • Make samples (and new person / new background) now copy in the fan’s cut-out, the scene without them and where they stand
  76. v0.24.2

    No more mystery originals

    The sample cards on a proposal had a Show the original button that swapped the fan’s FanMoment for an empty scene, and the scene often wasn’t even the one behind the fan: an Enhanced FanMoment chooses its own place and redraws the fan into it, so the artwork it started from is not the picture you see. The button is gone. The real original, the fan’s own photo, is still right beside every FanMoment, and Spot the fan still works.

    • Removed Show the original from proposal sample cards
    • Spot the fan stays, and the fan’s own photo still sits beside each FanMoment
  77. v0.24.1

    Your colours, your call

    Some brands can’t be read automatically: a black-and-white shield like the NHL’s has no colour in it to find, so the platform says it is unsure and we don’t use its guess. Fine, except the Studio then kept saying so for ever: setting the colours by hand, uploading a new logo or pressing Re-read brand never made the warning go away. Now, the moment you set a colour and save, the brand says Set by hand and the warning goes. Re-reading later keeps your colours and tells you so, instead of raising the warning again. Proposals already stuck like this are fixed on deploy. And the message itself now says plainly what to do.

    • Setting a brand colour by hand clears the unsure-read warning and labels the brand Set by hand
    • An unsure Re-read over colours you set keeps them, with a note, and no warning
    • Proposals already stuck with the warning over hand-set colours are cleared by a one-off migration
    • Plainer wording: set the colours yourself, or upload a logo in colour and Re-read; a black-and-white logo has no colours to read
  78. v0.24.0

    A fan quote that suits the venue

    The mock delivery email on every proposal quoted the same fan under the picture: “Same seats next time”, which is lovely at a football ground and a bit odd at a museum. Nothing in the Studio could change it, so editing a sample’s caption and seeing the email stay put was fair cause for confusion. The quote is now part of the proposal’s copy: the copy writer drafts one that fits the client, and you can change it in Check the copy, under Delivery, as “Fan quote under the email picture”. Proposals without one show a line that works anywhere. The sample caption now says where it actually appears.

    • New editable “Fan quote under the email picture” in the Delivery copy
    • The copy writer drafts the quote for the client’s sector (once the platform update is live)
    • A sector-neutral fallback quote replaces the football one
    • The sample Caption field explains it shows under the sample, not in the email
  79. v0.23.0

    Your price, not just the price list

    Until now the Studio could only show the rate card and hope the client did the maths. The Pricing step now takes your own quote for each way to buy, set separately: a campaign (how many Fan Moments, for how much) and a monthly platform plan (Fan Moments a month and the monthly fee, on a 12-month minimum term). Each quote opens its tab on the proposal in a highlighted card, with the full rate card still below it, and the calculators start at the quoted volume. The Studio shows what the rate card would charge for the same volume so you can price against it. The 12-month minimum is now stated on the Monthly tab of every newly published page, and the copy writer is told the quotes, so “Your questions answered” can quote them. Pages already sent to clients look exactly as they did.

    • Separate campaign and monthly platform quotes (volume and price) in the Studio’s Pricing step
    • Each quote heads its pricing tab, above the rate card; a monthly-only quote opens on the Monthly tab
    • The monthly quote states the 12-month minimum term and its total over the term
    • The Monthly tab states the 12-month minimum on newly published pages
    • The copy writer’s price facts include the quotes and the minimum term
  80. v0.22.1

    Activity copy that follows the client’s idea

    When a brief maps one of the client’s ideas to an activity, the copy writer was still handed that activity’s original template questions (“Call the score. 20 seconds.”), so a regenerated intro or caption described the template, not the idea: “Where Hockey Found You” came back promising a score prediction. The copy now gets the questions exactly as the idea rewords them, which is what fans are really asked. The Studio’s Screen wording also shows that question, says when it comes from the brief, and labels the two boxes as the page’s caption title and caption line, because that is what they change. Intros and captions you wrote yourself are never touched; to refresh the others, regenerate the Activities copy.

    • The copy for a brief-mapped activity is written from the idea’s own questions
    • Screen wording shows what fans are actually asked, and where it comes from
    • The screen boxes are labelled as page captions
  81. v0.22.0

    Crests all the way down

    That faint, tilted crest behind the proposal page used to turn up twice and then leave you alone for most of the scroll. Now it keeps you company the whole way down: four times, swapping sides as you go, and once more tucked into the corner of the footer. It stays out from behind the words, so everything still reads exactly as before. On a phone the footer one bows out, since there is no margin for it to hide in.

    • The faint crest appears four times down the page, alternating left and right
    • A fifth, smaller crest sits in the footer’s right margin (not on phones)
    • Text contrast is unchanged: the crest never sits behind the text column
  82. v0.21.2

    No original beats the wrong original

    The last fix gave every new sample its own original, but samples made before it kept borrowing the proposal’s first AI scene until the Approve samples page was opened. On a sample whose background you had changed, that is simply the wrong picture. Such a sample now hides "Show the original" until its own background has been copied in, which happens the first time the Approve samples page is opened.

    • A sample card without its own background copy shows no "Show the original" instead of the wrong scene
    • Opening Approve samples once copies each card’s background in and brings the button back
  83. v0.21.1

    The original is actually the original

    Swap a sample’s AI background for one of your own and "Show the original" now shows your picture, not the AI scene it replaced: every sample keeps its own backdrop instead of borrowing the first one ever made. The demo app also stops ignoring the colours you set. It used to be built from the platform’s own guess at the brand (often a plain white background), so the app and the phones on the page stayed white until someone remembered to press Apply. Now the Studio brand is sent once the demo build finishes, and again whenever you save a colour, font or logo change on Client & brand.

    • Show the original uses each sample’s own background, including one you uploaded
    • Existing samples pick up their own background the next time the Approve samples page syncs
    • A finished demo build is sent the Client & brand colours automatically (drafts only)
    • Saving a brand change on Client & brand sends it to the demo app; the Apply button stays for a resend
  84. v0.21.0

    One activity, two ideas

    A client’s brief can now use the same FANDEMiQ activity for two of its ideas, when each is a different activation of it: say “Cards to Players” and “Global E-Cards”, both a photo with a message. Before, the second idea was quietly turned into “We’d build this”. Now each idea is its own activity on the proposal page and in the demo app, with its own name, its own card line and its own reworded questions, and you can pick an activity that another idea already uses on the Brief step. Proposals you already have keep their activities and edits exactly as they are. (Needs the platform’s 10.95.0, which makes the extra copy of the activity in the demo app.)

    • Two ideas on one activity become two activities, on the page and in the demo app
    • The Brief step lets you pick an activity another idea already uses (it says which)
    • Each extra activity keeps its own wording, copy and edits
    • If the brief stops using one, its extra activity is hidden, never deleted
  85. v0.20.0

    Your colours, as you set them

    A proposal page now wears the background and text colours set on Client & brand. A dark background with white text stays a dark page with white text, instead of being turned into a band at the top of a light page. Text is only changed where it genuinely would not read, and dark phones on a dark page keep their light rim so they never vanish. Pressing Apply to the demo app now also says plainly if the app ended up with a different background or text colour from the one you set, and why. Live proposals keep their look until they are made live again or their copy is regenerated; drafts show it straight away.

    • The page background and text are the ones on Client & brand, dark or light (page version 4)
    • A dark background is no longer moved into the hero on a light page
    • Apply to the demo app names any background or text the app was given instead of yours
    • Live proposals change only when republished or regenerated
  86. v0.19.0

    Proposals that know their sport

    The proposal tool now asks what the client is: Football, Rugby union, a music festival, a zoo, any of the platform’s 35 sports and categories. That, with their home country, goes to the platform when the demo account is made, so the client gets the starter activities picked for their world rather than the same general set as everyone else. Before you generate you can take the recommended set, or choose your own from the ideas ranked best-first for that client, with anything coming up soon marked. Existing proposals are unchanged.

    • A Sport or category picker on Client & brand, set before you generate
    • The sport and home country go to the platform, which picks the demo account’s starter set from them
    • Activities offers Recommended for the client’s sport, or Choose my own from the ideas ranked for them, with occasions coming up
    • A proposal’s activities are the ones the platform actually copied, not every template
  87. v0.18.0

    Proposal pages with more depth, and a shorter menu

    The proposal page no longer sits on a flat background. The club’s colour at the top now fades gently into the page, the page takes a light tint of the club’s colour, sections alternate between two soft shades of it, and the crest appears twice down the page, large and very faint at the edge. Every piece of text is checked to stay easy to read on each shade. The menu that sticks to the top is now one short row, The app, How it works, Safeguarding, Questions and Pricing, with Try it as a button, and it shows where the reader is. Proposals already live look exactly as before until they are made live again or their copy is regenerated; drafts show the new look straight away.

    • The top of the proposal fades into the page instead of ending at a line
    • The page and its sections take soft tints of the club’s colour, with cards on a near-white surface
    • The crest appears twice down the page, large and faint, only when the proposal has one
    • The section menu is one short row of headings, Try it is the one button, and the current heading is underlined as you scroll
    • Live proposals keep their current look until republished or regenerated
  88. v0.17.1

    Approve samples loads fast again

    Approve samples loaded every sample, fan photo and background at full size, several megabytes each, which could freeze the browser. It now loads small copies made for the screen, and the proposal page asks for an image the right size for the device. A Make 3 more the platform had lost no longer spins for ever.

    • Studio sample cards show small copies of each picture (about 50 times less to download)
    • The proposal page loads samples, crests and logos at the size they are shown; like the originals, they are never kept in the visitor’s browser
    • If the platform loses a set of samples being made, Approve samples says so and you can start again
  89. v0.17.0

    Change one sample at a time, and make more without leaving the page

    On Approve samples each sample is now a card with its own background and person. You can give a card a new person, a new background, or the client’s own background by dropping an image on it, and the new picture replaces the old one when it is ready, keeping its approval. Make 3 more now runs on the same page. Needs platform v10.93.0; on an older platform the samples look and work as before.

    • Each sample card shows its background and the person in it
    • New person, New background, and Use your own background (drop an image on the card, or choose one) on every card
    • The card shows while it is being redrawn; the new picture replaces the old one, and an approved card stays approved
    • Make 3 more runs on Approve samples: progress and finished samples show there, no trip back to Generate
    • Notes from the platform about the samples show at the top of the page
  90. v0.16.1

    Pricing heading for both tabs, and the Rate card in the Website CMS

    When a proposal shows the Campaign and Monthly account tabs, the pricing heading now reads “Pricing: per campaign or monthly”. The Rate card can also be opened from the Website CMS, under Proposals.

    • Pricing heading covers both ways to buy when the tabs show; proposals without them keep the old heading
    • Rate card listed in the Website CMS menu and overview (Proposals), and still linked from the Studio
  91. v0.16.0

    A richer hero, and monthly pricing beside the campaign packages

    Every proposal's opening band now has a fine texture in the client's colours, with their crest large and faint behind the headline, and the page itself a barely-visible grain that never makes text harder to read. Pricing has two tabs: Campaign, as before, and Monthly account, with the Platform Access plans and a slider that finds the cheapest plan for a month's Fan Moments. Proposals already sent keep the page they went live with.

    • Hero: a brand-coloured grain on every proposal, and the crest large and faint behind the headline whenever there is one
    • A very faint grain on the page, chosen so no text loses contrast
    • Pricing: Campaign and Monthly account tabs; Monthly account lists the six Platform Access plans and works out the cheapest for your monthly volume, the 12-month total and the saving against pay as you go
    • Monthly plans are edited in the Rate card and saved with each proposal when it goes live; the copy writer can quote them in Your questions answered
    • Proposals already live keep their page until they are republished or their copy is regenerated
    • The Live today tag is darker on light pages, so it can be read
  92. v0.15.8

    A dark brand fills the hero, not the whole page

    A client whose brand was read as black or a deep navy got an all-dark proposal, with their dark app screens sitting black-on-black. That colour now fills the top band, like a club's colours do, and the rest of the page reads dark on a light background. Phones that would still disappear into the page get a light edge, and starter activity names written in capitals read normally.

    • A dark brand colour becomes the hero band, with the accent as its trim; the page is light with dark text
    • Proposals on a light brand are unchanged
    • Phone mock-ups as dark as the page behind them get a light bezel and a soft glow
    • Starter activity names in capitals (“CELEBRATION CAM”) show as “Celebration Cam”, unless you typed them that way
  93. v0.15.7

    Admins stay signed in for a working day

    Signing in to the website admin lasted two hours, so admins were signed out several times a day. A sign-in now lasts 12 hours and is extended while you use it; it ends after 12 hours left idle. Signing in on another device no longer affects the first.

    • Admin sign-in lasts 12 hours, up from 2
    • While you keep using the Studio or the admin, the 12 hours start again (checked at most once an hour)
    • Signing in on a second device leaves the first signed in
    • The emailed code is still the only way in
  94. v0.15.6

    Samples with a long brief, a friendlier demo app name, and testing a draft’s PIN

    Make samples failed every time for a client with a long About-the-client: the platform takes at most 600 characters to describe the scene. The description is now cut to fit at a sentence, keeping its opening. The Studio names a demo app after the client instead of by its account number. And an admin can now try a draft's PIN from See it as the client and see the page exactly as the client will after it.

    • Make samples: the scene description is cut to the platform’s 600 characters at a sentence or word, keeping the opening and the mood
    • If the platform ever refuses a description as too long, the Studio says so in a plain sentence
    • Generate and the Proposals list show “<client> (Proposal)”, “Demo app, live until <date>” when the platform gives a date, and the account number in small print
    • See it as the client on a draft: the PIN screen says clients can’t open it yet and lets you test the PIN; the right PIN shows the page as the client will see it
    • An admin is never shown a bare “Not found” for an archived or expired proposal; clients and anyone else still get the same 404 for a draft
    • The phones’ fallback app skin follows the platform’s new rule: buttons and titles always stand out from the page, in the club’s own colours
  95. v0.15.5

    Apply to the demo app keeps the club’s second colour

    Applying a club's brand to its demo app sent the page's background as a brand colour and left out the club's second colour, so an app the platform darkens for the crest ended up with navy buttons on a navy page. It now sends the second colour, which the app falls back to for its titles and buttons, and never the page background.

    • Apply to the demo app: the second club colour goes as the secondary and accent colour; the page background is never sent as a brand colour
    • Without a second colour, the brand goes as before, minus the page background as secondary colour
  96. v0.15.4

    A renamed client renames their demo app

    Changing the client's name on Client & brand now renames their demo app too, when the proposal has one, and Apply to the demo app sends the name with the brand. If the demo app can't take it right then, or the brand has no colours yet, the page says so; the save itself always goes through.

    • Client & brand: a new client name goes to the demo app on save (platform v10.92.4), with a note if it couldn’t
    • Apply to the demo app sends the client’s name with the brand
    • An older platform ignores the name, so nothing breaks before it is updated
  97. v0.15.3

    The phones show the app exactly as it is

    The page's phone mock-ups now copy the skin the client's demo app really paints, read from the platform, instead of working it out from the brand. The two could differ: when a club's crest would not show on its page colour, the platform changes the background, so a club read as white and navy has a navy app with sky-blue buttons, and now its phones do too. The app's header band shows when the app has one. Working the colours out from the brand remains the fallback for a demo app without a skin of its own.

    • Phones use the demo app’s stored skin (platform v10.92.3), colour by colour, falling back to the brand-derived colours for anything it leaves unset
    • The app’s header band in the phones, when the app shows one
    • Uploaded button art is listed in the guide’s technical notes (the phones show the filled colour)
    • Same rules as before: opening Generate updates drafts only; Apply to the demo app updates any proposal
  98. v0.15.2

    The page’s phones look like the client’s real app

    From the second check of the first proposal made from a brief. The phone mock-ups now wear the demo app's own skin, read from the platform, so a club whose app is navy with sky-blue buttons shows navy phones with sky-blue buttons on its page. Each activity the brief maps now says what the client's idea is under its heading, the caption under a reworded question follows the question, and each mapped idea has a Description in the app: the line fans see on its card, shown on the page's event list too. On What the brief asks for, the Read again check now sits on its own row.

    • Phone mock-ups take the demo app’s skin (page, text, title, buttons, fields) as the platform plans it from the demo account’s brand; read when Generate opens (drafts only) and when the brand is applied. Proposals without one, and published ones, look as before. Known differences are listed in the guide’s technical notes
    • A mapped activity’s line under its heading is the idea’s summary instead of the template’s, unless you wrote it; removing the brief gives the template’s line back
    • The caption under a reworded question’s phone follows the question (its detail, else the question), unless you wrote it
    • Description in the app per ready or adapted idea (platform 10.92.2): edited on What the brief asks for, sent to the demo app, and shown on the page’s event-list phone
    • What the brief asks for: Read again’s check has its own row, so a long file name no longer squeezes
  99. v0.15.1

    A club’s proposal in its own colours, and the brief’s questions in the app

    Fixes and additions from the first real proposal made from a brief. A proposal now keeps the club's second colour (the sky blue beside a navy accent, say), and with it the page opens on a band in the club's colours with the crest large in the corner; the second colour marks the section numbers, the phones and the cards, and is only ever text where it is easy to read. The crest the brand read finds is brought into the proposal as its logo when it has none. Each ready or adapted idea from a brief now carries the activity's own questions reworded in the client's words: you edit them on What the brief asks for, the demo app asks them, and the page's phones show them, captioned with the activity's name in the client's app. Your questions answered can quote the page's own prices. A step in How it joins up that came back without a title no longer runs into its number, and Check the copy flags it. Samples that finished while you were on another page no longer show as Stopped.

    • Second club colour on Client & brand, read with the brand; with it, a club band hero with the crest, and club-coloured section numbers, phone rings and cards (text only where it reads at 4.5:1); proposals without one look as before
    • The crest found by the brand read comes in once as the logo when the proposal has none (making the demo account, Re-read brand, or opening Generate), by one update that touches nothing else; never over a logo or badge you chose, never on a published proposal or an unsure read, PNG, JPEG or WebP only
    • Re-read brand on an older proposal can switch its opening to the club band: clear the second colour to keep the old look
    • What the brief asks for: the questions fans see, per ready or adapted idea, labelled by type and editable; sent to the demo app and kept with the brief
    • The page’s phones for a mapped activity ask the reworded question, with its detail, and are captioned with the activity’s name in the client’s app
    • The copy receives the page’s rate-card lines, so answers can quote a price the page shows (never your build prices); Check the copy and Publish warn when those prices have changed since, and publishing waits while the answers quote prices that are hidden
    • A reworded question only ever replaces its own question, of the same type, and never one you rewrote
    • How it joins up: a step without a title keeps its number on its own line; Check the copy flags it
    • Generate: samples that ran while you were away say "Checking on the samples…" instead of Stopped, and finish as done when their samples were already imported
  100. v0.15.0

    Proposals shaped by the client’s own brief

    A proposal can now start from the client's brief. On Client & brand, upload their brief as a Word document or PDF, or paste its text, and add a treatment: your steer, such as "lead with the charity angle". A new page, What the brief asks for, reads it once and sets out the campaign (theme, working title, mood, objectives), each of the client's ideas with whether the demo app can do it today (Ready now, Adapted, or We'd build this), the questions they want answered, and their constraints. Anything the reader wasn't sure of is marked Check this for you to look at. You correct it, add your own price for anything we'd build if you know it, and confirm: the demo app then shows only the ideas it can really do, under the client's names. Generate writes the page from the confirmed brief, with a new Your questions answered section, a Built for you list under what's live and what we'd build (your price, or "Scoped and priced with you"), a Build work block under the rate card, and the brief's mood as a second accent and a faint motif. The brief stays private: it is never shown on the page and is deleted with the proposal. Without a brief, everything works exactly as before.

    • Client & brand: upload a brief (Word or PDF, up to 4 MB, checked by name, type and contents) or paste it; Replace and Remove; a treatment box (1,000 characters)
    • New Studio page, What the brief asks for, shown only when there is a brief: one AI read (a few pence, on the demo account, made first if needed), then editable theme, title, mood, objectives, ideas with fit, activity and app name, questions and constraints
    • Ideas the reader wasn't sure of are marked Check this in amber, keeping the fit they were read with; confirming clears every mark; one activity is never two ideas
    • An optional price per idea we'd build, typed by you, never by the AI and never sent to the platform
    • Confirm and apply to the demo app renames the matching activities, hides the rest and themes its welcome; the page's activities follow; your corrections are kept even if applying fails
    • Only the proposal's own activities can be chosen for an idea; when none matches, the page and the app keep the standard set
    • Removing, replacing or reading the brief again gives the page its activities back (your own edits kept); the demo app keeps the last applied brief until you confirm a new one
    • A brief or treatment refused by the content check gets its own message
    • Generate sends the confirmed brief with the copy request and sets the samples in its theme and mood
    • Proposal page: Your questions answered (after Safeguarding), Built for you under Live vs build, a Build work block under the rate card for priced builds (never added to package totals), and a mood accent and motif, contrast-checked
    • The brief file is private (proposal images store), never on the page, read-only in the advanced editor, and removed when replaced, cleared or the proposal is deleted; a Word upload must really be a Word document
    • The proposal page's image route serves images only, and the logo, badge and backdrop fields offer only images; the public proposal routes never read the brief's text or file
    • Works with an older platform: brief reading then says "Brief reading isn't available yet." and everything else is unchanged
  101. v0.14.1

    Large logos no longer stop Generate

    Generate failed at the demo account step with "The platform couldn't use what we sent" when the uploaded logo was larger than 4 megapixels, even if the file itself was small (the NHL logo was 3600 by 2400 pixels at 227 KB). Logos over that size are now shrunk automatically before they are sent.

    • Logos over 4 megapixels are resized to fit before they reach the platform, whatever their file size.
  102. v0.14.0

    The Proposal Studio: proposals made step by step

    The admin now has two clearly separate areas. Signing in takes you to a home page with two big choices: Create a new proposal, or Website CMS. The Website CMS shows only the public website's sections; proposals live in the new Proposal Studio, which walks you through a proposal in eight short pages instead of one long form: Client & brand, Generate, Check the copy, Approve samples, Activities, Pricing, Preview as client, and Publish & send. Each page says what to check, a progress bar along the top shows what is done and what needs a look, and Back and Next take you through. Generate shows a live tick-list as the demo account, brand, copy and samples are made, with each sample appearing as it lands, how long it has taken, what the platform could not do, and a different, plain message for each reason something can go wrong. Fonts are picked from a list with a live preview, activities are chosen by name, and every row is named by its content. On a proposal page, signed-in admins now see a banner explaining why they skipped the PIN, with a link to see it exactly as the client does.

    • Admin home (/admin) offers two choices: Create a new proposal, and Website CMS; the CMS menu no longer lists proposals, proposal images or the rate card
    • New Proposal Studio at /admin/studio: a list of proposals with status, opens, last opened, demo account and what each needs next
    • Eight guided pages per proposal, with a progress bar, "What to check", flags on pages that need attention, and Back/Next that saves first
    • Client & brand: logo upload, colour pickers with a live preview and readability check, font dropdowns from the allowed Google Fonts with a live sample, where the brand was read from and how sure the read was, and Apply to the demo app
    • Generate: one button for everything, plus re-run buttons per line; live progress for the demo account (each part), the brand, the copy and the samples ("Sample 2 of 3", thumbnails as they land), elapsed against expected time, and "taking longer than usual" / "stopped" messages
    • Platform notes shown as plain sentences; distinct messages for AI rate limits, the daily demo account limit, a used-up AI budget, an unsure brand read and more
    • Check the copy: every section as it appears on the page, editable in place, with highlights shown as their own text and per-section Rewrite
    • Activities chosen by name with descriptions (no more template ids); approve samples in a grid; pricing with the rate card; preview as the client; publish with a copyable link and a ready-made email
    • Proposal page: signed-in admins see "You’re seeing this because you’re signed in. Clients are asked for the PIN." and a See it as the client link
    • The advanced (raw) editor stays, behind an "Advanced editor" link, with rows named by their content instead of "Activity 1…7"
    • The guide is rewritten for the Studio (/admin/studio/guide, also docs/proposals-guide.md)
    • New check in CI: the tests fail if the Payload config has a field or collection without a migration, or the migrations no longer build the config’s schema
  103. v0.12.1

    Admin sign-in and the News API work again

    Signing in to the admin and the News API both failed because the live database was missing the News table and two columns the admin needs whenever it saves or deletes anything. The live database had been set up in a way that skipped part of our very first database change, so those pieces were never created. A new, careful database change adds exactly what was missing and touches nothing else, so sign-in, saving, deleting and the News page work again.

    • Live database repaired: the News table and the two missing admin columns are created, with nothing removed or rewritten
    • The repair is safe to run more than once and does nothing on a database that was already correct
    • A test now builds the broken shape and checks the repair restores it exactly
  104. v0.12.0

    Proposals that let the client try it for real

    Every prospective client can now get their own branded proposal at fandemiq.net/proposal/<client>, opened with a PIN we send them. Behind it sits something better than a slide: one press of Generate in the admin sets up a live demo account in the Manager in the client's own colours, with our starter activities ready to play, real sample FanMoments and first-draft copy for the page. The page then invites them to try it themselves on their phone, and we can see when they open it. Copy we edit by hand is never overwritten by a regenerate.

    • Branded client proposals at /proposal/<client>, behind a PIN, with drafts visible only to signed-in admins
    • Generate in the admin: creates a live, branded demo account in the Manager (with you as its owner), copies the starter activities, reads the brand from the client's website or logo, writes the page copy and makes sample FanMoments
    • Text and colours changed by hand are protected from every regenerate; one section can be rewritten on its own
    • Try it yourself: the client's demo app link and a QR code on the page
    • Open tracking: first opened, last opened and number of views, counting only the client (not our previews) and storing nothing about who they are
    • Prices on a proposal are frozen at the rate card in force when it first goes live
  105. v0.11.1

    The announcement stops hiding behind the logo

    Today's shiny new announcement above the homepage headline had a habit of sliding up under the logo on phones and on shorter laptop screens, because the opening section was a fixed height and the extra line had nowhere to go. The section now grows when its content needs the room, so everything sits clear of the menu bar. On taller screens nothing changes. We also checked a reported blank homepage on phones: real iPhone and Android browsers show it fine, so that one was our test browser, not you.

    • Homepage hero grows to fit its content instead of pushing the top under the header (phones and 720–800px tall laptop screens)
    • Hero content always keeps clear of the fixed header
    • Checked the homepage in real iPhone (WebKit) and Android (Chromium) browsers: it renders in full
  106. v0.11.0

    Hand the keys to an AI agent

    FANDEMiQ now has a full MCP stack, so an AI agent can run the whole account: events, FanMoments, fan walls, fan emails and reports. The new AI agents page explains the three ways in (chat with Claude, let an agent run hands-free, or plug in your own systems with a server key) and is straight about the guardrails, including what hands-free mode takes away. The homepage now shouts about it, because building the thing quietly and not telling anyone felt like a waste of a good robot.

    • New /ai-agents page: three ways in, everything an agent can do, a hands-free matchday timeline, guardrails and an FAQ with FAQPage structured data
    • "New" announcement above the homepage headline, linking to the page
    • AI agents added to the main navigation, footer, sitemap and llms.txt
    • The full menu now appears from 1280px wide (the burger menu covers smaller laptops), so seven links no longer squash into each other
    • Connect Claude page now says approvals are the default, with hands-free available on request
    • Unit test for the page; route added to the e2e page-load list
  107. v0.10.3

    A stronger lock on the admin door

    Signing in to the site admin is safer. Login codes are longer, are never stored in a readable form, stop working after a handful of wrong guesses, and can only be requested a few times in a short spell. The behind-the-scenes store of codes can no longer be reached from outside, and the tool for setting up admin accounts now only answers to its secret key.

    • Admin login codes are now six digits, drawn from a secure random source
    • Codes are stored only as a keyed fingerprint, never as the code itself
    • Only a few codes can be requested in a short time, per email and per connection
    • Repeated wrong codes pause sign-in for that email from that connection for a day
    • Five wrong guesses cancel the code; request a new one to try again
    • The login code store is closed to all outside access
    • Admin account set-up requires its secret key on every request
    • The live site refuses to start without its signing secret configured
    • A sign-in code requested while this update was going live may not work: request a new one
  108. v0.10.2

    Packing for the other desk

    Nothing on the site changes. The handover notes are brought up to date so work can pick up cleanly on another machine: what shipped this week, the state of every branch, and the small traps we stepped in so the next session doesn't. The only moving part here is the person.

    • Handover notes updated for v0.10.x: the Connect Claude page and its copy
    • Setup notes for working in a worktree: pnpm only, the lint workaround, running the dev server from the worktree
    • Guidance to work on the local machine rather than continuing old sessions remotely
  109. v0.10.1

    Connect Claude page: clearer data and cost answers

    Two questions people actually ask before connecting Claude now get straight answers. The small print says plainly that what Claude reads from FANDEMiQ goes to Anthropic under your own agreement with them, and the cost answer explains that Claude's AI work comes out of the same monthly allowance as the Manager. No surprise bills, and no surprise lawyers.

    • Data note under the connection steps now names Anthropic as your processor for what Claude reads, and repeats that fan contact details stay hidden
    • "Does it cost extra?" now explains the shared monthly AI allowance, Enhanced AI FanMoment billing and where your Claude plan sits
    • FAQ structured data test now checks answers as well as questions
  110. v0.10.0

    Claude, meet FANDEMiQ

    A new page explains how to connect Claude to your FANDEMiQ account through MCP, so you can ask about your fans, plan a campaign or set up a fan wall in plain English. It also spells out the part that matters most: you sign in with two-factor, you choose what Claude may touch, and anything that reaches fans or costs money waits for your approval. Claude is keen, but it still has to ask.

    • New page at /connect-claude: what you can do, how you stay in control, five steps to connect, and an FAQ
    • FAQ and how-to structured data on the page, so search engines and assistants can read the steps
    • Added to the sitemap, llms.txt and the footer Platform column
  111. v0.9.4

    Green across the board

    Our automated checks had been failing for months, mostly because the tests still expected the template copy the site launched with: free trials, a team of six people who never existed, and nav links we removed long ago. Every test now checks the site as it actually is. Where it can, a test reads its expected text from the same place the page does, so a copy change won't break it again. Nothing visible changed on the site.

    • Unit tests rewritten for the Platform, About, Features and Header components, and the section smoke tests; two duplicate legacy test files removed
    • End-to-end tests rewritten: every live page, header nav, retired-URL redirects, versioned legal pages, the footer version and status links, and real 404s
    • Type check, lint, 343 unit tests and 41 end-to-end tests all pass
    • End-to-end run allows the CI server five minutes to build and start, instead of two
  112. v0.9.3

    Is it up? Now you can check

    The footer now links to status.fandemiq.net, our public status page, so anyone can see whether the Manager, the Camera App and the APIs are working without having to email us. We also cleared out the old page files that stopped being reachable when they were redirected last week. Nobody could see them, but they were still sitting in the code.

    • Footer: "System status" link to status.fandemiq.net, opening in a new tab
    • Deleted the dead legacy routes (platform sub-pages, industries, partner sub-pages, template pricing) and their tests; the redirects stay
  113. v0.9.2

    One rulebook, not two

    The website Terms had their own short list of things you mustn't do with FANDEMiQ, and it had quietly drifted from the Acceptable Use Policy published yesterday. The Terms now point to the policy, make it part of the Terms, and keep a plain-English summary. Where the two differ, the policy wins, so there's one rulebook to keep up to date.

    • Terms "Acceptable use" section now incorporates the Acceptable Use Policy at /legal/acceptable-use
    • Short summary kept, with the policy taking precedence if they differ
  114. v0.9.1

    A 404 that admits it

    Two tidy-ups after the legal pages went live. Any address that doesn't exist now gets a proper 404, with the normal header and footer, instead of a bare grey page. That includes a legal version that was never published, such as /legal/dpa/v2, which previously said 200 OK while showing 'not found'. And the script that turns counsel's approved documents into site pages now lives in the repo, so the next version of the DPA, SLA or Acceptable Use Policy is published the same careful way as the first.

    • Unknown URLs return a real 404 with the site header, footer and version number, and are marked noindex
    • Unpublished legal versions (for example /legal/dpa/v2) return 404 instead of a soft 404 with status 200
    • New npm run legal:publish script: strips counsel drafting notes, stops on anything it can’t safely remove, never overwrites a published version
    • The approved v1 substitutions are recorded in the repo, and the script rebuilds each v1 exactly from counsel’s files
    • CLAUDE.md documents how to publish a new legal version
  115. v0.9.0

    The small print, now with version numbers

    Our Microsoft Marketplace contract points at three documents by URL, so they now exist: a Data Processing Agreement, a Service Level Agreement and an Acceptable Use Policy, word for word as counsel approved them. Each version gets a permanent address that never changes, because a customer is bound by the version in force when they signed. When one is updated, the new version goes up beside the old one rather than on top of it.

    • New pages: /legal/dpa, /legal/sla and /legal/acceptable-use, each at version 1.0, effective 28 September 2026
    • Every version has a permanent address (/legal/dpa/v1 and so on) and the current page lists previous versions
    • A test pins each published version, so editing one fails the build; changes have to go in as a new version
    • Website Terms: availability now points to the SLA instead of promising 99.9%, and Marketplace customers are told the Microsoft Standard Contract governs them
    • Terms now come from the approved text in code only, so the CMS cannot override them
    • Sub-processor register: Sentry (error reporting, EU/Germany) added, with a dated change-log entry
    • The three new documents are linked from the data protection brief and the footer
  116. v0.8.0

    Every page stopped pretending to be the homepage

    A search and AI visibility audit found that every page on the site told Google it was a copy of the homepage, so only the homepage was ever indexed. It also found twelve pages that crashed on every visit, among them the partner application form, and a pricing page full of template prices we never charged. The canonicals are fixed, the partner form works again, the dead pages redirect somewhere real, and assistants now get a plain-language llms.txt plus proper structured data describing who we are.

    • Removed the site-wide canonical that pointed every page at the homepage
    • Partner application form (/partners/register) renders again: it had crashed since June
    • Hero and CTA banner sections render nothing instead of crashing when CMS content is missing
    • Legacy platform, industry and partner sub-pages now redirect to /platform, /features and /partners
    • Template /pricing page redirects to /packages; /careers redirects to /company/careers
    • www.fandemiq.net redirects to fandemiq.net instead of serving a duplicate site
    • Contact page banner no longer promises a free trial or links to a missing demo page
    • Added /llms.txt, richer Organization schema and FAQPage schema on the contact page
    • Sitemap drops the dead URLs and adds /features and /packages
    • The old on-site blog redirects to /news, where the real Substack articles live, and leaves the footer
  117. v0.7.1

    The phone number that never rang

    The contact page listed a London phone number from the range Ofcom keeps for TV and film scripts, so it never connected to anyone, and the page told people with urgent questions to call it. It's gone. Email is now the way to reach us, including for anything urgent.

    • Removed the phone card and its tel: link from the contact page
    • The "How quickly will I hear back?" answer now says to email hello@fandemiq.net with URGENT in the subject line, instead of calling
    • Test added so the contact page can never offer a phone number again by accident
  118. v0.7.0

    The data protection brief catches up with the platform

    The brief now describes the platform as it is after this week's privacy release, and it has moved from /legal/gdpr to /legal/data-protection (the old address redirects). Four of the six gaps it used to confess have been closed and are described as they now work; a new section explains how the consent screen changes with where a fan is standing; and it now says plainly where FANDEMiQ is a controller in its own right.

    • Renamed /legal/gdpr to /legal/data-protection with a permanent redirect; navigation, breadcrumb and sitemap updated
    • Two new public pages the brief refers to: /legal/sub-processors (the register, with transfer mechanism per provider and a dated change log) and /legal/retention-schedule (published in advance, as the Illinois biometric statute requires)
    • New section: the consent screen changes with where the fan is (age floors by jurisdiction, EU AI notice, Illinois release, Texas/Washington consent, location opt-in, strictest-set fallback)
    • Closed gaps removed from the roadmap: IP-address location guessing, automated retention, evidence for anonymous consent, the mood-inference switch
    • Faces and AI: mood inference described as on by default and switched off by policy for EU/EEA, staff/student audiences, unknown locations; face analysis off for China, Russia, Vietnam
    • Consent: exact wording now stored, not just fingerprinted; anonymous participation evidenced against the content
    • Sub-processors: IP geolocation service removed (resolved in-platform), Azure Video Indexer added, Resend metadata location and Google Maps heatmap use stated; 30-day change notice
    • Roles: FANDEMiQ declared controller for security, product improvement and anonymised cross-client benchmarking
    • Formal details: lawful bases per purpose, 24-hour breach notice commitment, complaints acknowledged within 30 days
  119. v0.6.2

    Everything now called the same thing

    Finishing what 0.6.1 started. The Vercel project has been renamed to match the repository, so the site is called fandemiq-website everywhere instead of answering to two names depending on which dashboard you were looking at. No change to the site itself.

    • Renamed the Vercel project from fandemiq-redesign to fandemiq-website
    • Added fandemiq-website.vercel.app; the old fandemiq-redesign.vercel.app still resolves so nothing bookmarked breaks
    • Updated the project name in README, CLAUDE.md and .env.example
  120. v0.6.1

    Housekeeping

    No visible changes. The repository was renamed to fandemiq-website — the old name was doing a good job of pointing everyone at the wrong codebase — and a dead environment-validation helper that listed a variable the site no longer uses has been removed, now that .env.example documents the real list.

    • Removed the unused lib/env.ts helper and its stale JWT_SECRET reference
    • Repository renamed from fandemiq-redesign to fandemiq-website
  121. v0.6.0

    A data protection brief worth reading

    The GDPR page was boilerplate — the kind every site has and nobody reads. It has been replaced with a proper data protection brief written for the person filling in a vendor assessment: what we collect from fans, how consent is actually recorded, exactly what our face analysis does and does not do, which sub-processors see what and where, and — the unusual bit — a straight list of the things we cannot do yet.

    • Replaced /legal/gdpr with the "How we handle fan data" brief
    • Added a sticky contents index and a sub-processor table showing provider, data, region and whether it is core or optional
    • Status tags throughout mark what is in place, what is your configuration decision, and what is still a gap
    • Kept the statutory details — company registration, lawful bases, transfer mechanisms and the ICO complaint route — in a formal section at the end
    • Retired the old GDPR statement constant
    • Added .env.example and a real README so a fresh clone can be set up without guesswork
  122. v0.5.1

    Privacy-friendly analytics

    Added Plausible analytics so we can see traffic and which pages land — cookieless, no personal data, and it only runs on the public site, not the admin.

    • Added the Plausible tracking script to all public pages
    • Excluded the Payload admin from analytics
  123. v0.5.0

    Subscribe on the news page

    You can now subscribe to the FANDEMiQ Substack newsletter directly from the News page — no detour to Substack required. Enter your email, hit Subscribe Now, and Substack sends a confirmation. The form is a proper server-side proxy so your email never passes through the browser.

    • Added Substack subscribe form at the bottom of the News page
    • Server Action proxies the subscription to Substack's API — no client-side API keys exposed
    • Success and error states with inline feedback
    • Email validated before hitting Substack
  124. v0.4.9

    News feed stops double-buffering

    New Substack posts were taking up to 20 minutes to appear on the News page because two independent 10-minute caches were stacked on top of each other. Now there's a single cache layer, so the worst-case wait is a predictable 10 minutes.

    • Removed redundant fetch-level cache from Substack RSS fetcher — unstable_cache already covers it
    • New posts now appear within 10 minutes of publishing instead of up to 20
  125. v0.4.8

    Deterministic database migrations

    Behind the scenes, the site no longer lets the database “auto-sync” its shape on the fly in production — the very thing that quietly lost the contact form’s storage table. Schema changes are now explicit, reviewable migration files that apply on every deploy, so a missing table can’t slip through silently again.

    • Disabled Payload push (auto schema sync) in production; dev still uses it
    • Added a committed baseline migration plus a migrate-on-deploy build step
    • Added db:migrate / db:migrate:status / db:migrate:create scripts and docs
  126. v0.4.7

    Enquiries logged again + a tidy-up

    While fixing the contact form we found its admin storage table had never been created in production, so enquiries were only ever emailed, never saved. That’s now restored — every submission is logged in the admin again. Also swept out some stale logo files and stopped stray downloads cluttering the repo.

    • Restored the contact-submissions table so enquiries are saved in the admin, not just emailed
    • Removed unused legacy logo and favicon assets
    • Stopped local staging files and marketing exports from showing up as repo changes
  127. v0.4.6

    Contact form fixed

    The contact form had quietly stopped emailing us — the Resend API key behind it had expired, so every enquiry failed to send (though it was still saved in the admin). Swapped in a fresh key and tidied up a wrong-domain email address while we were in there.

    • Replaced the expired Resend API key so contact-form emails send again
    • Fixed the public contact email from .com to .net (it pointed at a domain we don’t use)
    • Corrected the privacy-policy contact address to privacy@fandemiq.net
    • Hardened env fallbacks so a blank key can’t silently break the form in future
  128. v0.4.5

    Sharper Newsroom heading

    Retitled the news page hero to “News & Insights” with a short, punchy subtitle in place of the long descriptor line.

    • News hero heading changed to “News & Insights”
    • Subtitle shortened to “The latest from FANDEMiQ”
  129. v0.4.4

    Cleaner news cards

    Removed the source badge from the news cards — it was repetitive when everything came from the same place. The “Read on …” link on the featured story still tells you where each post lives.

    • Removed the source badge (e.g. the orange “Substack” pill) from news cards
  130. v0.4.3

    Now you can see what you’re looking at

    Added a visible version number in the site footer so you can tell at a glance whether you’re looking at the freshly deployed site or a cached old one. Click the version to see the full changelog.

    • Footer now shows the app name and current version (e.g. FANDEMiQ v0.4.3)
    • Version number links to this changelog page
    • New /changelog page listing every release, newest first
  131. v0.4.2

    Heroes that behave themselves

    The blog and news page headers were doing their own thing — a fixed-height banner with floating shapes that overlapped the navigation. They now use the same tidy hero as the rest of the site.

    • Blog and news heroes adopt the standard site-wide hero pattern
    • Removed the floating decorative shapes and fixed 240px height
    • Consistent spacing below the header on every screen size
  132. v0.4.1

    No more headline pile-ups

    On phones and tablets the big page headlines were sliding up under the fixed header. Fixed the spacing so titles always sit comfortably below the navigation.

    • Fixed hero/header overlap on mobile and tablet
    • Made hero headlines responsive (smaller on phones, full size on desktop)
  133. v0.4.0

    Introducing the Newsroom

    A brand-new News page that pulls posts straight from our Substack and lets the team feature articles from LinkedIn, the press and anywhere else worth sharing — all in one magazine-style feed.

    • New /news page combining Substack posts and curated external articles
    • Substack posts pulled in automatically from the RSS feed
    • Admins can add curated posts via the new “News Items” collection
    • Source badges, source filtering and a featured story
    • News added to the main navigation, footer and sitemap

Built by humans. Typed by Claude.