- landing.css is layout only and uses tokens (colors, fonts, hero, nav)
- palettes live in css/landing-<theme>.css; Robotex gets its own dark
theme, MyPointVPN sets the same tokens
- theme defaults to the project folder name; the build fails if the
theme file is missing, so a landing can't ship without styles
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- how it works: async POST /v2/tasks + polling, window held between tasks,
/v1/solve stays synchronous; example uses an http proxy and native Linux UA
- new "Architecture" section (api, RabbitMQ, worker, Redis) via the optional
engine block; base engine styles moved into landing.css
- features: window between tasks, inner_text; limits: open window takes a slot
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Landings get per-project themes (params.theme, params.fonts) and optional
chat/start/note/engine sections, so they don't look like clones.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- projects section: standalone landing template and styles, served on a
subdomain by the ingress Caddy (project) snippet
- Robotex landing in RU/EN, links to Redmine forum/issues
- blog post: Robotex is now a free service
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
