Repository navigation
Add an Evaluate abap2UI5 page for decision makers, and cut In a Nutshell to the technical picture - #382
Merged
Conversation
The site had one front door for two readers. A developer finds the Quickstart from it; the manager, architect or product owner who decides whether abap2UI5 may be used landed on In a Nutshell, a technical page that mixes the roundtrip with licensing, and the material written for them - when to use it and when RAP, what IT governance keeps, the security model - lived only in the framework repository, unlinked from the site. docs/get_started/evaluate.md is that material on one page, in the order a review asks: the problem it answers, when to use it and when not (with the cost-either-way table), what the organization keeps (code, not configuration), where it runs and what Basis does, what it costs and what is not free, the objections a review board raises with an honest answer each, who runs it, and how to evaluate it on one real screen in a week. The front door points at it twice: the hero's second button, which used to open In a Nutshell, and a fourth tile for the reader who builds nothing. The tile row is four columns now, two by two under 1100px. The enterprise card's "More on" link lands on the page's What you keep section, and In a Nutshell links the page from Where It Fits. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KPRYeJhVLkXoHZepaxgpzG
With Evaluate abap2UI5 carrying the decision, In a Nutshell said half of it a second time: Why abap2UI5, Where It Fits, ABAP Cloud and Clean Core, Production Usage, Licensing, Transparency. Every one of those is now on the Evaluate page and nowhere else; In a Nutshell keeps what a developer or an architect comes for - the roundtrip, the architecture, performance, security, the footprint, the systems and UI5 releases it runs on, where an app can appear, the tooling - and points to Evaluate in its second paragraph. Enterprise Ready is Integration now, holding the two sections that survived it. The one poor fit that had no counterpart on Evaluate, a frontend team that should own the frontend, moved there. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KPRYeJhVLkXoHZepaxgpzG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The site had one front door for two readers. A developer finds the Quickstart from it; the manager, architect or product owner who decides whether abap2UI5 may be used landed on In a Nutshell, a technical page that mixed the roundtrip with licensing. The material written for that reader (when to use it and when RAP, what IT governance keeps) lived only in the framework repository and was not linked from the site.
What
get_started/evaluate.md, "Evaluate abap2UI5", in the sidebar after In a Nutshell. One page in the order a review asks: the problem it answers, when to use it and when not (with the cost-either-way table), what the organization keeps (code, not configuration), where it runs and what Basis does, what it costs and what is not free, six objections a review board raises with an honest answer each, who runs it, and how to evaluate it on one real screen in a week.floorplan,worklist) added to the vocabulary list.Checks
npm run checkis green locally exceptcheck:api-reference, which fails onmaintoo: the framework'sz2ui5_if_clientmoved ahead of the committed reference. That is a separatenpm run generate:apicommit, not part of this change.check:samplesskipped locally for lack of a samples checkout; CI has one.Follow-up
abap2UI5/abap2UI5 has a companion branch that turns
docs/when-to-use.mdanddocs/governance.mdinto pointers to this page. Merge this one first, or the pointers lead nowhere until the site deploys.Generated by Claude Code