Building the next
Coolset website
A clearer expression of our company. Better articles, thoughtful design, useful motion, and a simpler way to publish.
This review space lets us develop the website and editor together. The current website stays live throughout the work.
Built
A separate space to review the website.
A shared design language for fonts, controls, motion, and customer evidence.
A proposed company-wide brand direction and three article design options.
214 imported public Academy articles with a shared article layout.
Documented content access for agents.
In progress
The visual direction and reusable page components.
Our editor, with Preview and Publish as the intended everyday workflow.
Content, imagery, and feature reconciliation.
Before launch
Complete content and media migration.
Verified publishing, forms, attribution, performance, and recovery.
Customer and team review, followed by an approved website domain switch.
What to look at first
- Open the homepage. Assess whether the design represents Coolset clearly.
- Review the design language. Try the tabs, customer cards, and form states. Compare the examples for reports, presentations, and social content.
- Read an Academy article on a phone and a larger screen. Check the text, tables, images, and navigation. Compare the three reading treatments.
- Tell us where you lose context, cannot find an answer, or expect a different next step.
- For copy feedback, record the words that a customer would use to explain the same idea.
Record the page address and what you tried to do. A screenshot helps when the issue concerns layout.
The path to launch
Prove the design and publishing workflow
Refine the homepage, product pages, and article layout through shared components. Use motion where it helps explain a change.
Preview will save a change and open its tested website version. Publish will release that version with an accurate status.
Test failed builds, simultaneous edits, private drafts, and recovery. An editor must complete the real workflow before we call it ready.
Move the complete content and media library
Cover all content collections, static pages, campaigns, redirects, and relationships. Preserve published revisions separately from drafts.
Move public images and downloads to dedicated website storage. Retain private files and original artwork separately.
Check each file, link, caption, and publication state. Preserve URLs that customers and search engines already use.
Connect the editor and business journeys
Bring the editor into the existing revenue application. Reuse its research, content workflow, review history, and access controls.
Verify demo requests, newsletters, webinar registration, downloads, calendars, consent, and lead attribution with isolated test services.
Prove correct routing, useful errors, and one expected outcome per submission.
Refine the copy through the customer's voice
After the prototype, study authorized Grain transcripts and customer emails. Find how customers describe their problems, our products, and our way of working.
Compare themes by product, audience, and buying stage. Include objections and expectations that we did not meet.
Propose clearer positioning and copy with traceable evidence. Keep private material out of the website. Obtain permission for attributed quotes.
This research is planned. It did not supply the current prototype copy.
Measure quality, speed, and agent access
Compare loading speed under the same conditions. Check mobile layouts, keyboard access, reduced motion, and the full content build.
Target a measured 100/100 on is-agentic.com. Also test whether agents can find, read, compare, and cite the correct content.
The first scan scored 74/100 on 15 September 2026. Later fixes need a new scan. The preview's noindex setting remains in place.
Review with customers and the team
Ask selected customers and colleagues to complete real tasks on the review site. Ask editors to publish and recover a change.
Close significant defects. Agree the final design, copy, business behavior, and recovery procedure before launch.
Approve the website switch and keep a recovery path
Reconcile final content changes. Review the exact website domains and configuration that a cutover would affect.
Keep production application infrastructure outside that change. Keep Webflow published and unchanged during the switch and recovery period.
Monitor pages, media, forms, bookings, and attribution after launch. Restore the previous website target if the agreed checks fail.
A careful route off Webflow
We only read from Webflow during this work. Development does not change Cloudflare or the production application.
The final website switch requires a tested destination, customer and team review, and approval of the exact changes.
Project roadmap updated 15 September 2026. This page describes the current prototype and the remaining release gates.