You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accessing a concept page the layout of the content / tiles looks like some space between the end of the page / browser and the content is missing. While the information is correclty displayed, it looks like some CSS is missing.
Root cause — the left-flush padding: these pages are served into the shell's bare <main> with no shared container, so each page body's root element has to supply its own width/padding. Four page types were missing that rule and rendered flush to the browser edge:
concept detail (/concepts/<slug>/)
topic detail (/topics/<slug>/)
channel detail (/channels/<slug>/)
the channels index (/channels/)
Fix 1 — container padding. Added one grouped CSS rule giving all four roots the site-standard container (max-width: 1280px; margin: 0 auto; padding: 1.5rem 2rem 3rem, matching the group/mission catalog pages), plus the matching mobile override. This is what restores the breathing room on the left/right that was missing.
Fix 2 — the "not 100% ready" impression. On hub concepts the relationship sections dumped the entire list onto the page — e.g. sap-btp-fundamentals rendered 235 "Concepts that build on this" tiles. Those sections now cap at 24 visible tiles, with the remainder in a "Show all N" expander (works with JavaScript disabled). Leaf concepts (single-digit lists) are unchanged.
Activation note: the padding fix takes effect on the next deploy. The tile-cap change takes effect after the next concepts content re-publish following that deploy. Both will ride along with the next scheduled deploy.
Covered by unit tests; no change to which tutorials/links are shown — layout only.
Activity
Merge pull request #3106 from sap-tutorials/fix-concept-page-layout-3095
jung-thomas commentedon Nov 11, 2026
Fixed in #3106 (merged to
DEV).Root cause — the left-flush padding: these pages are served into the shell's bare
<main>with no shared container, so each page body's root element has to supply its own width/padding. Four page types were missing that rule and rendered flush to the browser edge:/concepts/<slug>/)/topics/<slug>/)/channels/<slug>/)/channels/)Fix 1 — container padding. Added one grouped CSS rule giving all four roots the site-standard container (
max-width: 1280px; margin: 0 auto; padding: 1.5rem 2rem 3rem, matching the group/mission catalog pages), plus the matching mobile override. This is what restores the breathing room on the left/right that was missing.Fix 2 — the "not 100% ready" impression. On hub concepts the relationship sections dumped the entire list onto the page — e.g.
sap-btp-fundamentalsrendered 235 "Concepts that build on this" tiles. Those sections now cap at 24 visible tiles, with the remainder in a "Show all N" expander (works with JavaScript disabled). Leaf concepts (single-digit lists) are unchanged.Activation note: the padding fix takes effect on the next deploy. The tile-cap change takes effect after the next concepts content re-publish following that deploy. Both will ride along with the next scheduled deploy.
Covered by unit tests; no change to which tutorials/links are shown — layout only.