Tiny Support

Is your Ghost knowledge base ready to handle real-world support traffic, long KB articles, and accessibility expectations in 2025? Tiny Support by Kick Wheel Themes promises “everything you need, nothing more” for a self-serve knowledge base, wrapped in a minimal Ghost theme built with Tailwind CSS and Alpine JS.

On paper, it sounds ideal for SaaS support docs, help centers, and internal documentation. In practice, once I dug into the documentation, style guide, demos, and my own performance and accessibility checks, I found a theme that feels more like an early release than a polished support solution.

Kick Wheel Themes positions its work as “timeless, flexible themes designed to make your life simpler,” with a focus on adaptable design and “impeccable quality” code. With Tiny Support, the brand promise is clear—but the execution isn’t quite there yet, especially around accessibility, testing, and long-form documentation UX.

Key takeaways (TL;DR)

• Tiny Support is a documentation-first Ghost theme aimed at knowledge bases, FAQs, and support centers, built with Tailwind CSS and Alpine JS.
• It ships with 9 preset demos, topic-driven navigation, a docs-style homepage, FAQ and contact templates, plus Ghost native search.
• Real-world accessibility and WCAG checks are weak (Accessibility 90 with only 47% WCAG compliance and 23 issues), which is worrying for support sites at scale.
• The table of contents works in basic cases but breaks down for long, complex articles, making deep documentation harder to scan.
• The overall feature set is minimal; there’s no real “wow” feature compared to other documentation and knowledge base themes.
• At USD 69, the price is competitive for a niche docs theme, but I do not recommend Tiny Support in its current form. There are more mature alternatives.

What makes Tiny Support Ghost theme unique?

Tiny Support is a minimal, opinionated knowledge base theme for Ghost that focuses on clean topic pages, a docs-style homepage, and a sidebar table of contents—but with a very small feature set and worrying gaps in accessibility and UX for long, real-world documentation.

Tiny Support Ghost theme overview

Tiny Support is marketed as a “knowledge base & documentation Ghost theme with Tailwind CSS & Alpine JS,” designed specifically for self-serve support sites and documentation hubs.

It’s sold via Gumroad for USD 69 by Kick Wheel Themes, with 9 ready-made presets (Sharp, Friendly, Warm Minimal, Loud, Calm, Corporate, Bold, Dark, Cold Minimal) so you can quickly see how the same layout can be styled for different brands.

From the docs and product page, the core promise is straightforward:

• A Ghost theme for docs and knowledge bases
• Topic-driven navigation (tags as topics)
• Clean KB article layout, with an optional sidebar table of contents
• Built-in FAQ and contact templates
• A homepage focused on search and quick navigation to key topics.

The theme officially supports Ghost 5 and Ghost 6 and passes Ghost’s GScan checks. So from a compatibility standpoint, you’re safe for modern Ghost deployments.

If all you want is a simple help guide template or knowledge base theme with a fairly classic support layout, Tiny Support fits that description. But once I moved beyond the marketing bullets and actually looked at the style guide, the TOC behaviour, and accessibility, the cracks started to show.

Top features of Tiny Support Ghost theme

Knowledge-base structure built on Ghost tags

Tiny Support leans into Ghost’s tagging system and renames the mental model to match knowledge base language:

• Posts = articles
• Tags = topics

The docs explain how each “topic” is just a tag in Ghost, and the theme outputs topic pages listing all articles under that tag.

Key structural pieces:

• Topics page: A dedicated “Topics” page template that lists topics and key articles for each.
• Topic detail pages: For each topic, there’s a page that lists all associated articles.
• Breadcrumbs: The first tag is treated as the “main” topic and used in breadcrumb navigation.

This makes Tiny Support feel like a proper knowledge base theme rather than a generic blog layout with a few docs tweaks.

Docs-first homepage

The homepage combines several documentation-focused blocks:

• A hero area with search, focused on letting users search for answers first.

• Signposts: three highlighted topics, configured via theme settings by entering tag slugs; these pull in tag images, colours and descriptions.
• Featured articles: pulls articles marked as “featured” in Ghost Admin.
• Popular topics: topic cards with up to six posts each, again configured via comma-separated tag slugs.
• FAQs block: shows up to six FAQ posts tagged with #faq on the homepage.
• Call to action: a CTA block at the bottom of most pages, configured via theme settings (heading, text, button).

For a minimal Ghost theme, this is a sensible, purpose-built layout for a knowledge base theme or KB article theme.

Article layout with optional table of contents

Each article can be rendered in one of two templates:

• A standard single-column article
• A “Post – Sidebar” template that adds a right-hand sidebar with a table of contents that auto-links to H2 and H3 headings in the article.

This is one of the key features of Tiny Support. In simple articles, it works fine. But when I started testing it against long documentation with many headings and sub-headings, the TOC implementation becomes clumsy:

• The list gets too long and visually overwhelming.
• It’s harder to scan and jump around when you have deep hierarchies.

For a theme that markets itself as a minimal Ghost theme for documentation, that’s a big red flag.

FAQ and contact templates

Tiny Support gives you two important support-site building blocks:

• FAQ flow
  • You create FAQ posts, tag them as #faq (internal tag), and the theme pulls them into a dedicated FAQs page and into a block on the homepage.
• Contact / support ticket page
  • There’s a contact page template that connects to an external form endpoint like Getform, Formspree, Kwes or Formkeep.
  • You paste the form endpoint into the theme settings, then create a “Contact” or “New support ticket” page using the Contact template.

This makes Tiny Support usable as a basic theme for support and help centers where you want users to first self-serve via docs and then create a ticket when they’re stuck.

Ghost native search

The theme doesn’t bolt on a custom search solution; it leans on Ghost’s native search, integrated into the homepage hero and navigation.

For a small to medium knowledge base, this is fine and keeps things simple. If you need advanced search analytics or multi-index search, you’ll need external tooling anyway.

Customization options & presets

In Ghost Admin under Settings → Design & branding → Customize, Tiny Support exposes around 20 theme-specific options, split across the Brand and Theme tabs:

• Accent color via Ghost’s standard Brand tab
• Warm/Cool gray palettes for the overall feel
• Header layout: full-width vs contained
• Header background color and image, plus a “header is dark” toggle to switch text to white for legibility
• Font options via Ghost’s standard fonts plus curated additional fonts.

The 9 demo presets (Sharp, Warm, Corporate, Dark, etc.) are essentially different combinations of these options, giving you a starting point for your own knowledge base theme.

Pros and cons of Tiny Support

Pros

• Clean, focused layout for documentation
  It feels like a docs theme from the first glance: search at the top, topics, articles, FAQs, and a clear reading experience that doesn’t get in the way of the content.
• Simple mental model (topics & articles)
  Using tags as “topics” and posts as “articles” is intuitive if you already know Ghost. The dedicated topics page, topic detail pages and breadcrumb behaviour make it easy to group content.
• Multiple preset styles for different brands
  The 9 demo presets give you a quick way to see how Tiny Support can look for different use cases (sharp, warm, corporate, dark, etc.), which is handy if you’re not a designer but still want your support docs to feel on-brand.
• Clear documentation and setup steps
  The official Tiny Support documentation walks you through uploading the theme, setting up routes, configuring topics, FAQs, CTAs, and the contact form. It’s concise but covers what you need to get from “fresh Ghost install” to “working knowledge base.”
• Designed specifically as a knowledge base theme
  This isn’t a generic blog theme repurposed for docs. It’s marketed, structured and documented as a Ghost theme for docs and support content from day one.

Cons

• Released without enough real-world testing
  On paper, Tiny Support claims accessible, semantic SEO-friendly code, 99–100 Lighthouse scores and that it “meets all common WCAG accessibility recommendations.” In practice, my own tests showed:
  • Google PageSpeed Insights Accessibility score: 90
  • WCAG/ADA score: 47%, with 23 issues
    
    For a theme that explicitly leans on accessibility as a selling point, that gap is hard to ignore.
• Table of contents struggles with long, complex docs
  The sidebar TOC is fine for short articles. But with long KB content, many headings and nested sections, the current implementation becomes messy and hard to work with. It doesn’t feel robust enough for serious, multi-level documentation.
  
  TOC is fixed and you cannot navigate to bottom sections from TOC as they are hidden. You need to scroll the whole page to access those sections and TOC becomes useless in this case.
  
  Ref: https://tinysupport.kickwheelthemes.com/style-guide/

• Style guide page reveals rough edges
  The style guide is supposed to showcase all Ghost cards, code blocks, links and typography. Instead, it exposes multiple issues and rough spots that reinforce the feeling that Tiny Support shipped a bit too early, especially when it comes to layout consistency and fine-tuning.

• Minimal feature set compared to other docs themes
  The theme’s own tagline is “Everything you need, nothing more,” and that’s exactly what you get—nothing more. There’s no built-in changelog page, roadmap, multi-docs hub, advanced navigation patterns, memberships-focused layouts, or structured multi-product docs like you’ll see in more mature documentation themes.
• Accessibility is not where it needs to be
  For WCAG/ADA, anything below a very high score is risky if you operate in regulated markets or have users who rely on assistive tech. With a 47% score and 23 issues in my checks, Tiny Support is not something I’d use for an accessibility-sensitive help center without significant extra work.

Use cases: who is Tiny Support for (and not for)?

Good fit

• Very small teams needing a simple public docs site
  If you’re a tiny SaaS or side-project founder who just wants a basic knowledge base theme with native Ghost search, topic pages and a contact form, Tiny Support can do the job at a low price.
• Internal or low-risk docs
  For internal documentation where accessibility lawsuits, strict WCAG policies or very high UX demands aren’t a concern, Tiny Support’s minimal feature set might be “good enough.”

Not a good fit

• Serious SaaS and enterprise support centers
  If you’re running high-traffic, business-critical documentation, I’d expect stronger accessibility guarantees, better long-form TOC handling, and richer support features like changelogs, multi-product docs, or member-only areas. Tiny Support simply doesn’t offer that today.
• Accessibility-sensitive organisations
  With WCAG scores as low as 47% in my own tests, I wouldn’t feel comfortable deploying this as the front-line support experience for a company that takes accessibility or legal risk seriously.
• Teams needing powerful docs navigation
  For complex documentation sets with many sections, versions or products, the simplistic TOC and topic structure will likely feel limiting quite fast.

Performance, accessibility & SEO

The developer’s own marketing leans heavily on performance and accessibility:

• “Accessible, semantic SEO-friendly code – 99/100 Lighthouse score”
• “Perfect support for Ghost 5 and Ghost 6 – 100% on GScan”
• “Meets all common WCAG accessibility recommendations”

From a performance and SEO perspective, this mostly aligns with my experience:

• Google PageSpeed Insights Best Practices: 100
• Google PageSpeed Insights SEO: 100

The theme uses semantic HTML, supports all of Ghost’s editor cards, and is built with Tailwind CSS and Alpine JS, which generally lead to lean front-end bundles when used well.

Where the story breaks is accessibility:

• Accessibility score: 90 (already below the ideal 95+ for comfort)
• ADA/WCAG: 47%, with 23 issues flagged

For a theme that markets itself as “meeting all common WCAG recommendations,” that delta is too big to gloss over. If you’re in the US, UK or EU and care about accessibility risk, this is a serious downside, especially for a support site where users arrive precisely when they’re stuck and vulnerable.

In short:

• Speed & SEO: Strong.
• Accessibility: Not good enough right now for compliance-driven documentation.

Installation & customization

Basic installation

The setup follows standard Ghost theme practice:

• Upload the tiny-support.zip file in Settings → Design & Branding → Customize → Change theme → Upload theme.
• Activate the theme.

Routes (required)

Tiny Support requires a custom routes.yaml file for its documentation structure to work:

• Go to Settings → Labs → Routes in Ghost Admin.
• Download your existing routes as a backup.
• Upload the included routes.yaml file from the theme package.

Without this step, the topics and KB layouts won’t function correctly.

Topics & articles

To get the knowledge base structure working:

• Create tags for each topic (e.g. “Getting Started”, “Billing”).
• Assign exactly one primary tag to each article for clean breadcrumbs.
• Create a Topics page and set its template to “Topics Page,” and URL slug to topics.
• Add the Topics page to your primary navigation.

FAQs

For FAQs:

• Create FAQ posts where the title is the question and the body is the answer.
• Tag them with #faq (an internal tag).
• Create an FAQ page using the “FAQs Page” template.
• Add it to your navigation.
• The homepage will automatically show a block of up to six FAQ entries.

Contact / support ticket form

To collect support requests:

• Create a form endpoint in a service like Getform or Formspree.
• Paste the endpoint into Settings → Design & branding → Customize → Site-wide → Contact form endpoint.
• Create a new page (e.g. “Contact” or “New support ticket”) and choose the Contact Page template.
• Optionally, set the last nav item to be a button for extra prominence.

Customizing look and feel

Finally, tweak the design:

• Accent color in the Brand tab.
• Warm vs Cool gray palette in the Theme tab.
• Header layout (full-width or contained), background color or image, and a “header is dark” toggle.
• Optionally model your site after one of the 9 demo presets by matching colours and layout choices.

The customization experience is straightforward, but again, it’s very much in the “minimal ghost theme” category—manageable, but not particularly deep.

Rating & recommendation

My rating: ★★★☆☆ (3/5)

Even with the clean layout and sensible docs-first structure, I can’t ignore the issues:

• Weak real-world accessibility despite strong marketing claims
• A table of contents that doesn’t scale well to serious documentation
• A style guide page that exposes rough edges instead of inspiring confidence
• A feature set that feels bare-bones when you compare it with other documentation themes

At USD 69, Tiny Support is priced competitively for a niche documentation / knowledge base theme, especially from a boutique developer like Kick Wheel Themes. But price alone doesn’t make up for the gaps I’ve seen.

Do I recommend this theme?

Right now, no. Tiny Support needs more work—especially around accessibility, TOC behaviour, and general polish—before I’d feel comfortable recommending it, even to small teams.

FAQs about Tiny Support Ghost theme

Tiny Support alternatives (better documentation Ghost themes)

If you like the idea of a Ghost theme for docs but want something more mature, here are better-rounded alternatives, all listed on Theme My Blog:

• Doks is a full-featured documentation and help center theme by Spiritix with multi-documentation support, built-in changelog timeline, roadmap pages, blog integration and a showcase area for case studies. It’s a better fit if you manage docs for multiple products or modules and need more structured navigation than Tiny Support offers.
• Docslab, by Electron Themes, focuses on high-performance docs with light and dark modes, RTL support, translation readiness and native Ghost membership/subscription support, plus strong search and code syntax highlighting. It’s ideal for international SaaS documentation and global knowledge bases.
• Array by Bright Themes is a vibrant, category-driven Ghost theme with a dynamic tag feed, multiple grid layouts, versatile post templates (including TOC layouts) and strong accessibility and performance practices such as WCAG-aware design and lazy-loaded WEBP images. If you want docs plus blog/newsletter or content marketing, Array is much more flexible than Tiny Support.
• DigiDocs from GBJ Solution is a minimal documentation and knowledge base theme with features such as automatic table of contents, FAQ and changelog pages, breadcrumb navigation, full membership support and strongly documented performance metrics (GScan 100/100, PageSpeed ~99/99). It’s a better pick if you want a minimal Ghost theme for docs that already has a more reliable accessibility and performance profile.

All four feel more battle-tested and feature-complete than Tiny Support right now.

Conclusion

Tiny Support tries to be a focused, minimal Ghost theme for documentation, knowledge bases and support sites—and to a point, it succeeds. The layout is clean, the docs structure is sensible, and the price is attractive.

But when I look at the poor accessibility results, the fragile table of contents for long content, and the lack of standout features compared to other documentation themes, I simply can’t recommend it yet. If you’re serious about your support experience, I’d test Tiny Support very carefully—or skip it in favour of Doks, Docslab, Array or DigiDocs until Tiny Support has addressed its current issues.