improvement

The Website Caught Up

Arivu's marketing site now reflects the focused product, current guides, and warm light-only application design.

Website · Documentation · Design

The Arivu website now looks and speaks like the application it documents.

The previous site belonged to an earlier moment. Its sharp brutalist presentation and bookmark-first language were useful historical markers, but they no longer represented a product centered on connected knowledge. The site has now caught up without erasing that history.

One visual language

The website uses the same light-only direction as the application: warm sand, white surfaces, coral emphasis, neutral ink, editorial headings, open lists, dashed rules, and compact controls. Typography has been rebuilt for longer reading, with consistent line spacing and a narrower article measure across guides, Blog, and Chronicle.

Arivu Library showing bookmarks, notes, and other knowledge types in one filtered view
The current website uses real, synthetic-data product views to explain the experience.

Current pages describe the current product

The homepage, Features, About, documentation, and evergreen Blog now lead with the same loop as Arivu: Capture, Connect, Discover, Learn. They explain Home, Library, Notes, Graph, Insights, and global Search / Ask without presenting optional AI as a prerequisite.

Guides now match the single Go binary and SQLite application. Product images use synthetic data. Diagrams explain real flows and include readable alternatives. Metadata and descriptions follow the same focused story.

Chronicle remains history

Chronicle has a different job from the rest of the site. It records what changed when it changed. Older posts keep their original dates, language, claims, and genuine screenshots, even when the current product has moved on. Explanatory diagrams keep their historical labels and flows while using the shared presentation system. A short dated context note appears only where an old statement could otherwise mislead a present-day reader.

This post does not rewrite the first website launch. It adds the next chapter.

What stayed compatible

The site remains Hugo-based and keeps its existing navigation, public content routes, publication dates, taxonomies, feeds, and Cloudflare static deployment contract. Bookmarks to existing articles and guides continue to work.

The website is still the same front door. It now opens into the Arivu that exists today.