Oracle Visual Builder: Applications That Outlive Their First Release · Module 3 · Pages, flows and navigation
The shell page and what belongs on it
Lesson 26 of 176 · 3 min
Header, navigation and the things EVERY PAGE NEEDS. What to put here and WHAT TO LEAVE TO EACH PAGE. The shell is the frame around every page — and it is where a small mistake is multiplied by the number of pages you will ever build. WHAT BELONGS ON IT IS EVERYTHING IDENTICAL ON EVERY PAGE. The header, the application name, the navigation, the signed-in user, a global message area. Anything a user expects to stay put while they move around — and putting it here means it is written once and cannot drift between pages. WHAT DOES NOT BELONG IS ANYTHING CONDITIONAL, AND THAT IS THE LINE PEOPLE CROSS. A control shown on most pages is not a shell control; it is a page control that most pages have. Put it in the shell and you inherit a growing list of conditions — hidden here, relabelled there — until…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 3 · Pages, flows and navigation
- 1Flows: the unit that decides your structure
- 2Navigating between pages
- 3Passing data when you navigate
- 4The shell page and what belongs on it
- 5Deep links and the URL
- 6Layouts, and the page that grew
- 7Building for somebody who did not build it
- 8Accessibility, from the start
- 9What breaks: three navigation failures
- 10Lab briefing · Four pages that hang together