Starter products and publicly accessible demos
Not every project starts with a full design system purchase or a premium template license. Sometimes a team needs to evaluate a component library in the context of their own stack before committing to anything. Sometimes a solo developer just wants a clean documentation theme to wrap around a side project. The products on this page represent lighter entry points into the Vantage Design catalog, each one built with the same structural principles that drive our full product families.
The term "starter" does not mean incomplete. Every product listed here ships with functional markup, usable component structures, and enough documentation to begin working immediately. The difference between these and the fuller product tiers is scope: starter products cover fewer components, include fewer layout variants, and leave more room for a team to extend or customize on their own. That trade-off is deliberate. A smaller surface area means less to learn, fewer opinions to override, and a faster path from evaluation to integration.
Where a full design system might include forty or fifty component families with exhaustive state coverage, a starter product focuses on the fifteen or twenty components that appear in nearly every project: buttons, form fields, cards, navigation bars, modals, alerts, and a handful of layout primitives. These are not stripped-down versions of the full product. They are standalone kits designed to be useful on their own terms.
The same principle applies to documentation theme starters. Rather than offering every shortcode, every sidebar configuration, and every search integration, the publicly accessible versions focus on clean content rendering, a working navigation structure, and sensible default typography. If the defaults work for your project, you are done. If you need more, the full theme families are available in the catalog.
Starting with Solid
The Solid design system is the most complete product family in the Vantage catalog, and it is also the one with the clearest starter path. The publicly accessible Solid components cover the foundational layer: buttons with full state handling, form controls with validation patterns, card layouts that respond to real content length, and navigation components that work at multiple breakpoints without custom JavaScript.
What makes these components worth evaluating is not the visual polish, it is the structural consistency. Every component follows the same token architecture, the same naming conventions, and the same approach to responsive behavior. If you build a prototype with the starter set and later move to the full Solid system, nothing breaks and nothing needs to be renamed. The transition is additive, not destructive.
Teams evaluating Bootstrap-based tooling will find that Solid does not fight Bootstrap. It extends it with better defaults, more disciplined component states, and a token layer that makes systematic theming possible without rewriting variables by hand every time the brand guidelines change.
Browse by Category
Accessible documentation theme previews
Documentation themes are difficult to evaluate from a product listing alone. A screenshot of a sidebar tells you almost nothing about how the theme handles deep navigation, how it renders code blocks across different languages, or whether its search integration actually surfaces relevant results when your docs grow past fifty pages.
That is why every documentation theme in the Vantage catalog includes a publicly accessible demo. These demos are not mockups. They are working documentation sites running real content through the same rendering pipeline that ships with the theme. You can navigate the sidebar, test search if it is available, check responsive behavior on different viewports, and see how shortcodes render in context.
The Ace theme family is the primary documentation offering, built around Hugo and designed for projects that need more than five pages of docs. Ace handles content chunking, sidebar depth, breadcrumb generation, and table of contents rendering out of the box. The demo environment shows all of this in action, so you can evaluate the theme against your own content requirements before making any decisions.
For teams that do not use Hugo, the structural patterns in Ace are still worth studying. The way it handles navigation hierarchy, content grouping, and page-level metadata applies to documentation themes on any static site generator. We have seen teams adapt Ace patterns to Docusaurus, MkDocs, and custom Next.js documentation setups with minimal friction.
Documentation Resources
Page templates are perhaps the most straightforward products to evaluate through publicly accessible demos. A landing page either communicates its message hierarchy clearly or it does not. The hero section either leads the eye into the content or it stalls at the fold. These are things you can assess in seconds.
The Identity and Exodus templates both maintain publicly accessible demo environments. Identity is the more conventional of the two, designed for product introductions, agency sites, and service pages where clarity is more important than novelty. Exodus takes a more expressive approach with deliberate asymmetry and unconventional section pacing, suited for brands that want to stand out without abandoning usability.
Both templates demonstrate the same core principle: the quality of a page template lives in its layout hierarchy and content flow, not in parallax effects or animated transitions that break on half the devices visitors actually use. A good template makes content look intentional. A bad template makes you fight the layout to get your own message across.
Template Demos
When to stay with starters and when to move up
The answer depends on your project scope, not your budget. A starter product is the right choice when you are building a focused application with a known, limited surface area. If your project needs a card layout, a navigation bar, a set of form controls, and not much else, the starter components will carry you through without unnecessary complexity.
The full product families make sense when your project will grow over time, when multiple teams or contributors will use the same component library, or when you need the expanded layout primitives and documentation patterns that the starter sets intentionally leave out. The transition path is smooth in either direction. Start with the publicly accessible components, build something real, and decide from there.
There is no artificial limitation designed to push you toward a purchase. The starter products are genuinely useful on their own. If they handle everything your project needs, you have the right tool and there is no reason to look for more.