Standard features line now reads Data Rollback, Data Catalog and Data Viewer come as standard.
Cross-post copy (the trailing Source LinkedIn post: comment) uses UTF-8 punctuation - -> replaced by an arrow on the five role leads, plus bolt on the installation line and a tick on the closing Data Control. Kept restrained per .agents/docs/linkedin.md, which says to avoid emoji walls.
Note: this drops Data Lineage from the standard-features list. The site's own meta description still leads with it ("A zero code approach with Data Lineage, Catalog, Dictionary, Validation, Workflow, Alerts and more") - say the word if that should follow.
Verification: clean rebuild (rm -rf .cache public && npm run build), npm run typecheck clean, npm run lint warns only on the 8 pre-existing files. Rendered page checked: body shows the new line, no Lineage remains visible, the arrows/emoji survive verbatim in the comment, og:image resolves to the JPG.
The latest feed post gets two copy changes.
**Standard features line** now reads `Data Rollback, Data Catalog and Data Viewer come as standard.`
**Cross-post copy** (the trailing `Source LinkedIn post:` comment) uses UTF-8 punctuation - `->` replaced by an arrow on the five role leads, plus `bolt` on the installation line and a tick on the closing `Data Control.` Kept restrained per `.agents/docs/linkedin.md`, which says to avoid emoji walls.
Note: this drops Data Lineage from the standard-features list. The site's own meta description still leads with it ("A zero code approach with Data Lineage, Catalog, Dictionary, Validation, Workflow, Alerts and more") - say the word if that should follow.
Verification: clean rebuild (`rm -rf .cache public && npm run build`), `npm run typecheck` clean, `npm run lint` warns only on the 8 pre-existing files. Rendered page checked: body shows the new line, no Lineage remains visible, the arrows/emoji survive verbatim in the comment, `og:image` resolves to the JPG.
Spice up the Source LinkedIn post comment with typographic arrows and a
couple of emoji (per .agents/docs/linkedin.md), and swap Data Lineage for
Data Rollback in the standard-features line.
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.
The latest feed post gets two copy changes.
Standard features line now reads
Data Rollback, Data Catalog and Data Viewer come as standard.Cross-post copy (the trailing
Source LinkedIn post:comment) uses UTF-8 punctuation -->replaced by an arrow on the five role leads, plusbolton the installation line and a tick on the closingData Control.Kept restrained per.agents/docs/linkedin.md, which says to avoid emoji walls.Note: this drops Data Lineage from the standard-features list. The site's own meta description still leads with it ("A zero code approach with Data Lineage, Catalog, Dictionary, Validation, Workflow, Alerts and more") - say the word if that should follow.
Verification: clean rebuild (
rm -rf .cache public && npm run build),npm run typecheckclean,npm run lintwarns only on the 8 pre-existing files. Rendered page checked: body shows the new line, no Lineage remains visible, the arrows/emoji survive verbatim in the comment,og:imageresolves to the JPG.