clients.alai.no — Hosted Proposal Page
clients.alai.no — Hosted Proposal Page
Type: Vercel static site
Target URL: https://clients.alai.no
Source: ~/business/ALAI-Holding-AS/products/clients-alai-no/
MC task: #9410
Purpose
Minimal, single-purpose hosted proposal landing page. One CTA hands off to ALAI Documenso for signing (https://sign.alai.no/signin). No framework, no JS, no build step — hand-written HTML5 + vanilla CSS, deployed via vercel --prod.
Design
- ALAI dark theme:
--bg:#09090b,--surface:#111113,--accent:#00E5A0,color-scheme: dark. - Mobile-first: single-column layout under 720px, 3-column feature grid + horizontal CTA row above 720px (
@media (min-width: 720px)). - Exactly one interactive element on the page: the CTA anchor.
robots.txt=Disallow: /(private proposal link, not for search indexing).
Verified state (2026-08-08)
curl -sI https://clients.alai.no→HTTP/2 200, served by Vercel,content-length: 6885(byte-for-byte match with localindex.html).- Live HTML has exactly one
<a>tag →href="https://sign.alai.no/signin". https://sign.alai.no/signin→HTTP 200(Documenso reachable, not a dead link).- Vercel project linked:
prj_2Qzvszx7qg4pnzsRf3ZqhddUMaam. robots.txtserved correctly at/robots.txt.
Known gap
The products/clients-alai-no/ directory is untracked in the ALAI-Holding-AS git repo — it was deployed straight via vercel --prod, not through git-triggered CI. Non-blocking (the live deploy works), but a follow-up commit would close the hygiene gap. Not done in this pass because the parent checkout was mid-way on an unrelated feature branch (feat/oauth-metrics-reader-103888).
Local verification
cd ~/business/ALAI-Holding-AS/products/clients-alai-no
python3 -m http.server 8765
curl -s http://localhost:8765 | grep -c "Proceed to secure signing"
Deploy
vercel --prod
vercel domains add clients.alai.no
No comments to display
No comments to display