OutSystems Front-End Developer Specialist study guide
OutSystems Front-End Developer Specialist · Work through your exam, one topic at a time.
The Front-end Developer Specialist (O11 and ODC) is a Specialization exam in the OutSystems certification program. OutSystems describes Specializations as shorter exams focused on a specific topic or area, able to serve as the final outcome for a role or experience level, or as a path toward a new certification. This particular exam, per the certification page, focuses on the fundamentals of OutSystems front-end development and is targeted at front-end developers who are fairly autonomous in creating UI designs and stylings to achieve pixel-perfect web and mobile applications in both ODC and O11. Because it spans both platform generations, candidates should be comfortable with the styling and layout tooling available in each. The exam runs 90 minutes and costs $100 US. It is delivered in English, Español, 日本語, and Português (BR); note that the language selection applies only to exam content, since proctoring and support are provided in English. Topics on this exam: OutSystems Front-end development fundamentals (UI design and styling for pixel-perfect web and mobile applications in ODC and O11). The OutSystems Front-End Developer Specialist study guide has 1 section and about 509 words.
01Front-end Fundamentals: UI Design and Styling for Pixel-Perfect Web and Mobile Apps (ODC and O11)
This domain tests whether you can turn a design specification into maintainable UI in OutSystems instead of one-off CSS. It covers the styling stack shared by ODC and O11 Reactive Web apps, the extra rules that apply to Traditional Web modules, and the concrete widgets, theme settings and extended properties an assessor expects you to name. Every decision should sit as high in this stack as it can: Theme - colours, typography, spacing and border radius are edited in the Theme Editor and generated into CSS; the theme's Style Sheet holds CSS that must apply app-wide. Layout - Layouts and Placeholders define the chrome (header, side menu, content area) that Screens and Blocks reuse.
509 words, about 3 minMore study resources for OutSystems Front-End Developer Specialist
- Practice questionsIn OutSystems, which element should you use to apply a reusable visual style such as a brand color or font to multiple widgets without repeating the CSS on each screen?
- FlashcardsLayout block. A reusable Block that defines the page shell (header, menu, footer, content placeholders).
- Cheat sheetScreen composition: a Screen references a Layout block (Layouts/BaseLayout, Layouts/SideMenu, Layouts/Blank) plus Blocks; the Layout renders placeholders (Title, MainContent, Breadcrumbs) that the Screen fills - styling a Layout changes every Screen that uses it.
- Key termsTheme. A global styling layer in OutSystems that defines colors, fonts, spacing, and component appearance across an entire module or app, applied through CSS variables and generated stylesheets.
- Study planMap the full OutSystems UI stack (Screen, Block, Web Block, Layout, Theme, Style Sheet) and state in one sentence what each layer controls for styling.
- Common mistakesInline styles are the fastest way to see a visual change in Service Studio's TrueChange preview, so candidates under time pressure default to them and never revisit.
- Exam-day guideBring the exact ID name that matches your registration.