Oracle Visual Builder: Applications That Outlive Their First Release · Module 3 · Pages, flows and navigation
Layouts, and the page that grew
Lesson 28 of 176 · 2 min
Structuring a page so that ADDING A FIELD LATER DOES NOT MEAN REBUILDING IT. Every page you build will be asked to hold one more field, and how you laid it out decides whether that is a minute or an afternoon. THE MISTAKE IS POSITIONING RATHER THAN STRUCTURING. Components dragged where they look right, sized to suit the content that exists today. It looks perfect and it is a picture rather than a layout — because nothing describes the RELATIONSHIP between the pieces, so a new field has no place to go and everything around it has to be moved by hand. STRUCTURING MEANS SAYING WHAT GOES WITH WHAT, AND LETTING THE LAYOUT PLACE IT. These fields are a group, this group flows in a column, this column adapts to the width available. Then a new field joins a group and everything else moves itself — which is the whole…
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