Structured work
Tasks, docs and decisions in one record type, so a search returns the decision as readily as the ticket that prompted it.
Work platform
Kinetic is a marketing theme for a multi-product SaaS: a hero, a tabbed platform tour, a feature grid and a pricing table — all of it static, all of it usable without JavaScript.
Each surface is a full page of content on its own. The tab strip is an enhancement, not the structure.
Break an objective into work that fits in a week. Dependencies are declared once and drawn everywhere, so a slipped date shows up on the plan it affects rather than in someone's inbox.
Boards, lists and a calendar over the same records. Changing the view never changes the data, so two teams can look at one backlog through the lens each prefers.
Comments resolve against a revision rather than floating free, and an approval records who approved what, not merely that somebody did.
Dashboards read from the same records the work lives in. There is no export step, so a number on a dashboard is never a fortnight behind the thing it describes.
Tasks, docs and decisions in one record type, so a search returns the decision as readily as the ticket that prompted it.
Filter, group and sort are independent. Any combination is a URL, which means a view is something you can send to a colleague.
Rules are stated as sentences and shown in full before they run. An automation nobody can read is an outage waiting for a quiet afternoon.
Every field keeps its previous values. Reverting is reading the record, not restoring a backup.
A workspace starts closed. Sharing is a deliberate act with an audit line attached to it.
What you export imports again. Leaving is supported rather than merely permitted.
Roadmaps that survive contact with a shipping date.
Campaign calendars with the assets attached to the dates.
Recurring work that does not depend on anyone remembering it.
Kinetic is the marketing front of a fictional work platform. The product, the customers and the figures are illustrative: they exist to exercise the components, not to describe a real company.
The category it belongs to — multi-product SaaS marketing — usually reaches for saturated gradients and large type. Kinetic keeps both, but confines the gradients to decoration. Nothing legible is ever placed on one, because a gradient cannot be contrast-checked, and every colour that carries meaning comes from a token gated at AAA.
Two components here are progressive enhancements rather than components that require JavaScript. The platform tour is four ordinary sections that a small module turns into a tab strip; the pricing table is a complete monthly table that a module teaches to show annual rates. In both cases the version without scripting is the whole answer, not a fallback.
That constraint is also why the tab markup carries no role="tab" in the HTML. ARIA tab roles promise arrow-key navigation that only the script can deliver — announcing it statically and then not honouring it is worse than a plain stack of sections.