AICTPO AI Coding Agents Knowledge Module
AICTPO AI Coding Agents Home — Knowledge Module
AICTPO AI Coding Agents knowledge module — UI selectors, data model, and page states documenting Home.
sidebutton install aictpo Home
Marketing landing page at /. Anchors all of the site's top-level sections — hero, mobile app showcase, FAQ, pricing, plus the global header and footer that wrap every other page.
Sections (top to bottom)
| Section | Anchor | Purpose |
|---|---|---|
| Global nav | top of viewport | Logo, primary nav links, account/CTA |
| Hero | top of <main> | Headline "Your AI Engineering Department", subhead, primary CTA |
| Mobile app showcase | #mobile-app | "Your Fleet In Your Pocket" carousel |
| FAQ | #faq | 9-question accordion |
| Pricing | #pricing | Pricing tiers |
| Footer | bottom | Imprint / Privacy / Terms / contact links |
The global header and footer also appear on /imprint, /privacy, /terms, and any other route — they are not unique to home.
Hero
The hero is the first paint above the fold. It contains:
- H1 headline: "Your AI Engineering Department"
- A short subheading explaining the value prop
- A primary CTA button (typically routing to a contact / signup target)
Selector hints: main > section:first-of-type h1, primary CTA via [data-cta] or by visible text.
Navigation
Nav links scroll to in-page anchors (#mobile-app, #faq, #pricing) rather than navigating between pages. Clicking a nav link should trigger a smooth scroll. The mobile menu collapses behind a hamburger toggle below the breakpoint.
Common tasks
Verify hero render: navigate to /, snapshot the first <section>, assert the H1 text and that the CTA is visible and clickable.
Test in-page navigation: click each nav link, verify the URL hash updates and the corresponding section scrolls into view.
Check global chrome: assert the header and footer render with the expected link set on every page (/, /imprint, /privacy, /terms).
Gotchas
- Smooth scroll can race with page-load layout shifts — wait until DOMContentLoaded plus a short settle period before measuring scroll positions.
- The hero CTA may be an anchor link, a router link, or an external URL depending on campaign config; do not hardcode the target in tests.
- Hash-based deep links (
/#faq) only work after the page hydrates; navigating directly to the anchor before hydration can land at the top of the page. - The mobile breakpoint hamburger menu uses a different DOM than the desktop nav — selectors must branch on viewport width.