Adds a feed post at /who-is-data-controller-for/ - a role-by-role answer to "who is this for?".
Structure
One short intro paragraph, then a section per persona - Data Administrators, Data Auditors, Data Managers, Data Owners, Purchasers. Each opens with the question that role actually asks, followed by a couple of lines on how the product answers it. Closes with the product summary and the usual Discovery Call CTA.
Source
Adapted from a Data Controller post. The original text (hashtags included) is preserved verbatim in the trailing Source LinkedIn post: comment, and the site body carries no hashtags.
Copy notes
The auditor section says "any associated Excel file is retained alongside it" - not every submission carries an Excel.
The data owner section mentions rollback: the restore is packaged as a new, reviewable change, so the audit trail keeps both the mistake and the correction.
Cover
previewImg points at who-is-data-controller-for.jpeg in the post folder - the generated illustration (five role figures connected to a dashboard panel with one row highlighted, no text), normalised from the delivered PNG to JPEG at its native 1024x768.
One thing to flag: the delivered image is 4:3, not the 1.91:1 the recorded prompt asked for. Nothing is clipped on the site - the template constrains it and it renders on both the post page and the feed card - but a 1.91:1 crop of a 4:3 image trims the top of the dashboard and the figures' feet, so a wide link preview may look tight. Happy to reword the prompt for a wide format, or pad the existing image with background, if you want the ratio right.
Verified
clean rebuild (rm -rf .cache public && npm run build); the post appears in /feed/, /feed/2026/ and at the top of /rss.xml, and its cover renders on the post page and in the feed card
og:image resolves to a real JPG (1024x768), not the site logo SVG
npm run typecheck clean; npm run lint warns on the same 8 pre-existing files only
no src changes - the diff is the post folder
Adds a feed post at `/who-is-data-controller-for/` - a role-by-role answer to "who is this for?".
### Structure
One short intro paragraph, then a section per persona - Data Administrators, Data Auditors, Data Managers, Data Owners, Purchasers. Each opens with the question that role actually asks, followed by a couple of lines on how the product answers it. Closes with the product summary and the usual Discovery Call CTA.
### Source
Adapted from a Data Controller post. The original text (hashtags included) is preserved verbatim in the trailing `Source LinkedIn post:` comment, and the site body carries no hashtags.
### Copy notes
- The auditor section says "any associated Excel file is retained alongside it" - not every submission carries an Excel.
- The data owner section mentions rollback: the restore is packaged as a new, reviewable change, so the audit trail keeps both the mistake and the correction.
### Cover
`previewImg` points at `who-is-data-controller-for.jpeg` in the post folder - the generated illustration (five role figures connected to a dashboard panel with one row highlighted, no text), normalised from the delivered PNG to JPEG at its native 1024x768.
One thing to flag: the delivered image is **4:3**, not the 1.91:1 the recorded prompt asked for. Nothing is clipped on the site - the template constrains it and it renders on both the post page and the feed card - but a 1.91:1 crop of a 4:3 image trims the top of the dashboard and the figures' feet, so a wide link preview may look tight. Happy to reword the prompt for a wide format, or pad the existing image with background, if you want the ratio right.
### Verified
- clean rebuild (`rm -rf .cache public && npm run build`); the post appears in `/feed/`, `/feed/2026/` and at the top of `/rss.xml`, and its cover renders on the post page and in the feed card
- `og:image` resolves to a real JPG (1024x768), not the site logo SVG
- `npm run typecheck` clean; `npm run lint` warns on the same 8 pre-existing files only
- no `src` changes - the diff is the post folder
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a feed post at
/who-is-data-controller-for/- a role-by-role answer to "who is this for?".Structure
One short intro paragraph, then a section per persona - Data Administrators, Data Auditors, Data Managers, Data Owners, Purchasers. Each opens with the question that role actually asks, followed by a couple of lines on how the product answers it. Closes with the product summary and the usual Discovery Call CTA.
Source
Adapted from a Data Controller post. The original text (hashtags included) is preserved verbatim in the trailing
Source LinkedIn post:comment, and the site body carries no hashtags.Copy notes
Cover
previewImgpoints atwho-is-data-controller-for.jpegin the post folder - the generated illustration (five role figures connected to a dashboard panel with one row highlighted, no text), normalised from the delivered PNG to JPEG at its native 1024x768.One thing to flag: the delivered image is 4:3, not the 1.91:1 the recorded prompt asked for. Nothing is clipped on the site - the template constrains it and it renders on both the post page and the feed card - but a 1.91:1 crop of a 4:3 image trims the top of the dashboard and the figures' feet, so a wide link preview may look tight. Happy to reword the prompt for a wide format, or pad the existing image with background, if you want the ratio right.
Verified
rm -rf .cache public && npm run build); the post appears in/feed/,/feed/2026/and at the top of/rss.xml, and its cover renders on the post page and in the feed cardog:imageresolves to a real JPG (1024x768), not the site logo SVGnpm run typecheckclean;npm run lintwarns on the same 8 pre-existing files onlysrcchanges - the diff is the post folder