Rework the entry path: landing page, depth pages out of onboarding, one AI page, and docs for the three tools

[oblomov-dev]

Four changes to the same problem: the way in. What a newcomer meets first was carrying things they do not need yet, while the things they do need were reachable only through menus — or not written at all.

1. Landing page

The front page spent two of its three cards (GitHub, LinkedIn) duplicating the social icons that are always visible in the nav bar, and claimed "Keep it ABAP" without showing a line of it.

• Hero actions by reader intent: Get Started (→ quickstart), Introduction (→ about), Live Demo (→ the browser build — the strongest argument for the undecided, previously buried in a tip on the quickstart page). "What's new?" leaves the hero; the changelog stays in the version dropdown.
• Six cards, one per reader journey, in the order a reader meets them: Quickstart → Cookbook → Samples → Configuration → Technical Insight → Community. Every main section is now one click from the front page.
• The nine-line hello-world class under the cards, centered at the site's reading width (the home layout would otherwise give it the full feature-grid width, where code reads as a banner).

2. Depth pages out of Getting Started

Two pages answered questions a newcomer does not have yet, and there they read as required steps. Both move under Advanced Topic:

• Use Cases (the on-stack/side-by-side extensibility tiers) as-is.
• Your Project → Working Off-Stack, which is what the page is actually about: developing the app repository off the SAP stack, with git, the gates and CI.

3. All AI material on one page

It lived in three places. Building with AI is now the one page: the Tooling page loses its ai-mcp section and its llms.txt tip (both restated what that page already said) and points there instead, and the paste-ahead prompt from the framework README — the only AI content that existed nowhere in this documentation — moves in as the zero-effort first rung. (The framework README is shortened to match in abap2UI5/abap2UI5#[companion PR].)

4. A documentation page per tool repository

The linter, the MCP server and the VS Code extension are this project's own tools, and the only thing describing any of them was a README written for somebody already standing in the repository — 843 and 991 lines of it. Nothing on this site said what an MCP server even is, and the extension appeared as one paragraph.

Advanced Topic → Tools now has a page per repository, written for somebody who has not decided to use the tool yet: what it is, the problem it solves, setup in levels, and every feature explained rather than listed.

• /advanced/linter — moved here from Technical Insight, where it sat among the tools this project borrows, and expanded to the same depth. The entry in that list now points here.
• /advanced/mcp_server — new.
• /advanced/vscode — new.

The three READMEs are shortened to their quick start plus development/packaging/releasing and point at these pages, so there is one copy to maintain instead of two that drift (abap2UI5/linter, abap2UI5/mcp-server and abap2UI5/vscode-extension each have a companion PR).

Also corrects the MCP server's repository name throughout: ai-mcp was renamed to mcp-server, and every link here still said the old one.

Verified

• npm test, check:version, docs:build (no dead links, no orphan pages) and check:examples all green; check:samples / check:counts skip without a samples checkout, as documented — this change touches neither samples blocks nor counts
• All three new pages appear in the generated llms.txt
• Landing page screenshotted in light, dark and mobile

🤖 Generated with Claude Code

https://claude.ai/code/session_01YM2A6eh3sX7ssGDuagbSGG

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.