This set builds vocabulary for building structured, no-code websites with a visual CMS.
0 / 5 completed
1 / 5
At standup, a dev mentions designing a website visually with a drag-and-drop interface that generates clean, production-ready HTML and CSS underneath. What is this type of tool called?
A visual, no-code website builder like Webflow lets a designer construct a site through a drag-and-drop interface while the tool generates clean, production-ready HTML and CSS underneath, bridging the gap between visual design tools and hand-written code. This gives non-developers meaningful control over a site's structure and styling without needing to write markup directly. It differs from a purely visual mockup tool by producing an actually deployable website.
2 / 5
During a design review, the team wants to define a reusable, structured content type, like a blog post with a title, author, and body field, that non-technical editors can populate. Which capability supports this?
A CMS collection defines a reusable, structured content type, like a blog post with fields for title, author, and body, that a non-technical editor can populate through a form-like interface without touching the underlying page design. New entries automatically inherit the collection's defined template layout. This structure is what separates a true content management system from a page-by-page static site builder.
3 / 5
In a code review, a dev notices a reusable visual component, like a navigation bar, is defined once and automatically updates everywhere it's used across the site. What does this represent?
A reusable symbol, or component, is defined once and instanced across multiple pages, so an edit made to the original automatically propagates everywhere it's used, rather than requiring the same manual change repeated on every individual page. This consistency mechanism mirrors component reuse in code-based frontend development, applied within a visual design tool. It significantly reduces the maintenance burden of keeping shared elements, like a navigation bar, consistent site-wide.
4 / 5
An incident report shows a non-technical editor accidentally broke a page's layout while trying to update text content. What practice would prevent this?
Restricting a non-technical editor to structured CMS fields, like a title or body text box, rather than giving them direct access to layout-level design controls, prevents an accidental change from breaking the page's visual structure. This separation lets content updates happen safely and frequently without requiring design expertise from every contributor. It's a deliberate permission design choice available in most visual website builders with a CMS layer.
5 / 5
During a PR review, a teammate asks why the team uses a CMS collection for blog posts instead of manually building each post as its own separate static page. What is the reasoning?
Manually building each blog post as its own separate static page means every new post requires rebuilding the layout from scratch and risks visual inconsistency between posts, while a CMS collection applies one consistent template automatically and lets a non-technical editor add content without touching the page structure at all. This approach scales far better as the number of posts grows. A one-off static page might still make sense for genuinely unique content that doesn't fit a repeatable structure.