nsaspy/starintel-tmp-website

Draft and design the new `starintel.actor` main site #1

New issue

Open

opened 2026-08-25 09:27:45 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-25 09:27:45 +00:00

(Migrated from github.com)

Goal

Produce a strong, usable first design and implementation draft for the new starintel.actor front door. Treat this as an exploration-quality production skeleton: coherent enough to deploy and test, but easy to replace or iterate aggressively.

Context / dependencies

Deployment/hosting contract: starintel-infra #47 and #48
Blog: blog.starintel.actor / starintel-social-presence #12
Self-hosted analytics: starintel-infra #66
SEO audit service: starintel-infra #67

Information architecture

Design clear routes/navigation for at least:

home / what StarIntel is
intelligence/search capabilities
Quasar/app entry
API + MCP
docs/research
blog
pricing/account placeholder
login
security/privacy
status/contact/about as appropriate

Design requirements

Establish a reusable StarIntel web design system: typography, spacing, layout, nav, buttons, cards, forms, data/status primitives, icon/symbol usage, responsive breakpoints, focus/hover states, and light motion rules.
Strong technical/cybernetic identity without sacrificing readability or turning every screen into decorative noise.
Mobile-first/responsive and keyboard accessible.
Semantic HTML and sensible progressive enhancement.
Build reusable components rather than a one-page visual mock with no implementation path.
Keep the homepage fast: explicit JS/image/font budgets and no unnecessary framework weight.
No fake metrics/customer claims/testimonials.

SEO / telemetry

Canonical metadata, per-page title/description, OpenGraph/social cards, sitemap/robots inputs, structured data, stable slugs, and internal-link structure.
Integrate the shared Umami hook without exposing analytics.star.intel to clients.
Make the output auditable by the SEO service from infra #67.

Auth boundary

Design login/account UI around the canonical StarIntel OAuth service; do not implement a second password database in this website repo.

Deliverables

short design rationale/brief
reusable component/theme foundation
responsive homepage + key route skeletons
realistic content placeholders clearly marked where copy is unfinished
social/SEO metadata
build/test/deploy documentation compatible with infra #48

Acceptance

Site builds reproducibly from a fresh checkout.
Core routes are usable on mobile and desktop.
Keyboard navigation/focus and basic accessibility checks pass.
Lighthouse/performance regressions are bounded/documented.
No private .star.intel names, private IPs, credentials, or internal-only service details enter the client bundle/generated pages.
Infra can deploy the artifact without manual production edits.

Execution mode — AUTO-RAGE

Run the full ADARD/ADADR loop autonomously: inspect repo/current StarIntel public surfaces and available design assets; research comparable technical product IA patterns; create the design direction and architecture; adversarial UX/accessibility/security review; autonomous decision gate; test-first implementation where practical; exact-head build/accessibility/metadata verification; push a focused branch and open/update a PR targeting main. Do not stop for subjective design approval—the draft is intentionally disposable/iterable. Stop only for a genuinely unresolved requirement/security blocker, inaccessible dependency, or failed verification gate.

## Goal Produce a strong, usable first design and implementation draft for the new `starintel.actor` front door. Treat this as an exploration-quality production skeleton: coherent enough to deploy and test, but easy to replace or iterate aggressively. ## Context / dependencies - Deployment/hosting contract: `starintel-infra` #47 and #48 - Blog: `blog.starintel.actor` / `starintel-social-presence` #12 - Self-hosted analytics: `starintel-infra` #66 - SEO audit service: `starintel-infra` #67 ## Information architecture Design clear routes/navigation for at least: - home / what StarIntel is - intelligence/search capabilities - Quasar/app entry - API + MCP - docs/research - blog - pricing/account placeholder - login - security/privacy - status/contact/about as appropriate ## Design requirements - Establish a reusable StarIntel web design system: typography, spacing, layout, nav, buttons, cards, forms, data/status primitives, icon/symbol usage, responsive breakpoints, focus/hover states, and light motion rules. - Strong technical/cybernetic identity without sacrificing readability or turning every screen into decorative noise. - Mobile-first/responsive and keyboard accessible. - Semantic HTML and sensible progressive enhancement. - Build reusable components rather than a one-page visual mock with no implementation path. - Keep the homepage fast: explicit JS/image/font budgets and no unnecessary framework weight. - No fake metrics/customer claims/testimonials. ## SEO / telemetry - Canonical metadata, per-page title/description, OpenGraph/social cards, sitemap/robots inputs, structured data, stable slugs, and internal-link structure. - Integrate the shared Umami hook without exposing `analytics.star.intel` to clients. - Make the output auditable by the SEO service from infra #67. ## Auth boundary Design login/account UI around the canonical StarIntel OAuth service; do not implement a second password database in this website repo. ## Deliverables - short design rationale/brief - reusable component/theme foundation - responsive homepage + key route skeletons - realistic content placeholders clearly marked where copy is unfinished - social/SEO metadata - build/test/deploy documentation compatible with infra #48 ## Acceptance - Site builds reproducibly from a fresh checkout. - Core routes are usable on mobile and desktop. - Keyboard navigation/focus and basic accessibility checks pass. - Lighthouse/performance regressions are bounded/documented. - No private `.star.intel` names, private IPs, credentials, or internal-only service details enter the client bundle/generated pages. - Infra can deploy the artifact without manual production edits. ## Execution mode — AUTO-RAGE Run the full ADARD/ADADR loop autonomously: inspect repo/current StarIntel public surfaces and available design assets; research comparable technical product IA patterns; create the design direction and architecture; adversarial UX/accessibility/security review; autonomous decision gate; test-first implementation where practical; exact-head build/accessibility/metadata verification; push a focused branch and open/update a PR targeting `main`. Do not stop for subjective design approval—the draft is intentionally disposable/iterable. Stop only for a genuinely unresolved requirement/security blocker, inaccessible dependency, or failed verification gate.