MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 9 · Fragments, components and reuse

Theming and staying consistent

Lesson 96 of 176 · 3 min

Looking like it BELONGS BESIDE FUSION, and the difference between MATCHING A BRAND AND REBUILDING ONE. An application here sits beside Oracle's own screens, and a user moving between them notices inconsistency far more than they notice styling. THE DEFAULT THEME IS ALREADY THE RIGHT ANSWER FOR MOST OF THIS, AND THAT IS WORTH SAYING PLAINLY. It matches the ecosystem, it has been tested for contrast and readability, and it carries right-to-left and accessibility work you would otherwise redo. An application that looks like the rest of the estate reads as part of the estate, which is usually exactly what is wanted. MATCHING A BRAND MEANS ADJUSTING THE THEME'S OWN VALUES: COLOURS, FONTS, SPACING. The components keep their structure and behaviour and take your palette. That is cheap, it survives platform updates, and it gets most of what anybody actually asked for when they said "make it look like ours".

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 9 · Fragments, components and reuse

  1. 1The component library you already have
  2. 2Fragments: a piece of page you reuse
  3. 3When to make one
  4. 4Custom components
  5. 5Sharing across applications
  6. 6Theming and staying consistent
  7. 7What breaks: two reuse failures
  8. 8Lab briefing · Extract a fragment properly
Theming and staying consistent — Oracle Visual Builder: Applications That Outlive Their First Release — MSAMM