The site felt old, unfocused and bloated: 11 pages, a features page of 171
bullets, a homepage of 830 words in card grids around seven mockup-style
screenshots, and no single thing it wanted a visitor to understand.
- Message: control instead of drift. Audience: IT departments in small and
mid-sized companies. Goal: buy a licence — netOrk itself is free, the
licence adds vulnerability data and image updates.
- Home is under 400 words: the drift comparison of a real access point, three
steps, the hardware it runs on, vulnerabilities with a licence, what else is
in the box, one closing band. Features, Drivers and Roadmap are gone; their
URLs redirect (router and nginx 301).
- New Pricing page: the free core, Starter / Pro / Enterprise on request with
the plan differences from the licence server, four questions; buttons go to
the licence portal. The unit-less KB request limit is left out.
- Persona pages are one template; NIS2 and Plugins are cut to half or less.
Impressum and Datenschutz exist as marked placeholders; the unsupported
"MIT licence" claim is gone from the footer.
- Look: light paper and ink, the dark product on a stage, Inter self-hosted,
split sections and ruled lists instead of cards. Four real, cropped
screenshots replace eight full-window ones.
- Language follows the browser until someone chooses; <html lang> is set.
Scroll-to-top on navigation, a catch-all route, no dead /docs/architecture.
- CLAUDE.md, DESIGN.md, PAGES.md and PRODUCT.md describe the new rules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diese Anwendung teilt sich Netz, Datenbankcluster, öffentlichen Eingang und
Backup mit anderen Projekten. Wer dort etwas ändert, ändert es für alle, und
dem eigenen Repo sieht man es nicht an.
Die Regel steht vollständig in christianmanivong/infrastructure; hier nur der
Verweis, damit sie dort gelesen wird, wo gearbeitet wird.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Establishes the documentation foundation for the netOrk website:
- CLAUDE.md — tech stack (React 18/Vite/Tailwind), design rules, tone of
voice, and file structure guidance for the implementation instance
- docs/PRODUCT.md — one-liner, elevator pitch, target audience, value props,
full feature list, driver table, architecture summary
- docs/DESIGN.md — exact Tailwind classes for colors, typography, spacing,
and all reusable component patterns (cards, buttons, screenshot frames,
badges, nav) lifted directly from the product UI
- docs/PAGES.md — page-by-page content plan with route, purpose, section
structure, and draft copy for every page
No code yet — that follows in a separate instance.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
christianmanivongandClaude Opus 5