What Makes a Good Ghost Theme? A Practical Checklist
A polished homepage is the easiest part of a Ghost theme to sell.
It is also one of the least reliable ways to judge one.
The homepage in a demo has been arranged under ideal conditions: the right number of posts, carefully cropped images, agreeable headline lengths, complete author profiles, and tags that happen to suit the navigation. Your publication will eventually supply the opposite. A contributor will submit a 14-word title. An article will have no image. One section will publish every day while another remains untouched for a month.
A good Ghost theme does not merely survive those conditions. It keeps the publication understandable when they occur.
The checklist below is the one we would use before buying a theme, commissioning one, or approving it for release. It begins with the pages readers actually use and ends with the less visible details that determine whether the theme is still pleasant to own a year later.
1. Read a complete article before judging the homepage
Open the demo's longest post. Read it on a laptop and then on your phone.
That single exercise reveals more than a row of feature icons. Look at the measure of the text: long lines make the eye work to find the next one, while very narrow columns turn every sentence into a stack of fragments. Body type should remain comfortable without browser zoom. Headings need enough contrast to organize the argument without overwhelming it. Captions, links, quotations, lists, and code should look like parts of the same publication.
Keep scrolling. Does the theme maintain a readable rhythm after the opening screen, or was most of its attention spent on the title treatment? Is the author, publication date, and post access level clear? Can a reader tell what to do after reaching the end?
Article design is the product. The homepage is its cover.
2. Inspect the awkward editorial states
Theme demos usually show complete content because complete content photographs well. Publishing systems have to handle incomplete content too.
Try to find, or ask the seller to demonstrate:
- A post without a feature image
- A very long title beside a very short one
- An author with no profile image or biography
- A tag archive containing only one post
- A post assigned to several tags
- Navigation with enough items to wrap or collapse
- A gallery that mixes portrait and landscape images
- A members-only article viewed while signed out
These are not obscure edge cases. They are an ordinary month of publishing.
Pay particular attention to fallbacks. Removing an image should not leave a blank frame. A missing excerpt should not create a hole in a post grid. A long author name should not push controls outside the viewport. Ghost's own marketplace requirements ask theme developers to account for unavailable images, biographies, and tags because resilient defaults are part of theme quality, not optional polish.
3. Check whether it uses Ghost, or fights it
Ghost already provides the machinery for a modern publication: posts and pages, authors and tags, native search, newsletters, memberships, paid access, comments, recommendations, and Portal. A theme should provide a considered interface for those systems.
It should not force the publisher to recreate them through fragile snippets or a parallel collection of third-party widgets.
Search is a useful example. Ghost's native search can be opened from a theme with a helper or a data-ghost-search attribute. Membership links can open Portal directly, while custom signup forms can use Ghost's members attributes. Supporting those features is usually more dependable than bundling substitutes that have their own accounts, scripts, styling, and update cycles.
There is room for custom behavior, especially when a publication has an unusual editorial model. But ask what the customization is replacing. If the answer is a stable Ghost feature that already solves the problem, added code may be buying complexity rather than capability.
4. Look at archives, not only individual posts
A publication becomes an archive surprisingly quickly.
Visit a tag page and an author page. Both should identify where the reader has arrived, provide enough context, and make older work easy to scan. Pagination must be visible. Dates, excerpts, and images should follow a consistent hierarchy rather than changing shape unpredictably from one page to another.
This matters even if most visitors arrive through search or social links. An article earns the click; the archive helps a new reader understand the body of work around it.
5. Test the reader states that affect revenue
If memberships matter to the publication, one screenshot of a subscribe button is not evidence of membership support.
Ghost exposes different states to a theme: a signed-out visitor, a logged-in free member, and a member with an active paid subscription. Post access can also change according to the visibility selected in Admin. The interface should respond coherently to those combinations.
Start with a public article. Sign up, confirm access, open the account view, and sign out again. Then repeat the journey with a restricted post. Check the free preview, the content boundary, the invitation to join, and the return to the site after authentication. Ghost provides a default paid-content call to action and lets a theme replace it with a custom partial; either approach can work, but the language and visual treatment should feel native to the publication.
The decisive question is simple: does the theme help the reader understand their current access and next step without making them think about the underlying system?
6. Resize it slowly
Do not test responsiveness by checking one desktop width and one phone preset. Drag the browser window slowly between them.
Awkward widths expose navigation collisions, cards that become too narrow before the layout changes, controls stranded on their own line, and headings that escape their containers. Rotate a phone. Increase the browser's text size. Open the menu with a keyboard and make sure focus remains visible.
A responsive theme is not a desktop composition squeezed into fewer columns. It is a layout that keeps its hierarchy as space changes.
7. Treat accessibility as observable behavior
You do not need a specialist audit to notice the first set of problems.
Use the site without a mouse. Can you reach navigation, search, account controls, galleries, and forms in a sensible order? Is there a visible focus state? Do menus close predictably? Are form fields labelled? Does text remain legible against both the default background and the accent colours available in the settings?
Then inspect images. Decorative images should not be announced as content, while meaningful images need useful alternative text. Valid HTML, keyboard navigation, image alternatives, and reasonable colour contrast are also part of Ghost's published marketplace criteria.
Passing these checks does not certify a theme as fully accessible. Failing them does show that basic reader needs were left untested.
8. Measure performance with representative content
Fast demo hosting can make a heavy theme feel light for one page view. Test several routes and use your browser's network panel or Lighthouse to see what is actually loaded.
Look for oversized images, several font families with many unused weights, JavaScript shipped to pages that do not need it, and third-party scripts that block the first render. Repeat the test on an article with a gallery or embed. Performance should not collapse as soon as the editor uses the content cards the theme claims to support.
Do not reduce the decision to one score. A laboratory result is useful evidence, not a guarantee. What matters is whether the theme has a disciplined asset strategy and remains responsive under realistic content.
9. Count useful settings, not total settings
Ghost currently allows a theme to expose up to 20 custom settings. The limit encourages choices.
A typography option, accent colour, logo treatment, homepage introduction, or feed style may let a publisher establish a clear identity without editing code. A panel full of controls for individual margins, border radii, and isolated buttons transfers the designer's work to the buyer.
Before purchase, ask to see the theme settings in Ghost Admin. For each control, consider three things:
- Is its effect clear from the label and description?
- Does every option look intentionally designed?
- Can the setting be changed without breaking another part of the site?
Strong defaults matter more than a large control panel. You should be customizing a finished system, not completing one.
10. Ask what happens when Ghost changes
Every uploaded theme is checked for fatal compatibility problems, and developers can run GScan for a fuller report during development. Passing GScan is essential. It is not the same as promising maintenance.
Look for a version number, changelog, stated compatibility range, and an update process you can understand. The documentation should identify any required routes, integrations, or content setup. If an update replaces the theme ZIP, find out whether your configuration survives and which custom edits would need to be reapplied.
This is where a theme with fewer tricks often ages better. Clear Handlebars templates, sensible partials, scoped CSS, and restrained JavaScript are easier to inspect and maintain than a theme whose homepage depends on a chain of hidden assumptions.
11. Read the support policy before you need support
“Support included” can mean anything from help installing the ZIP to unlimited customization. A credible seller defines it.
You should be able to learn which Ghost versions are covered, how updates are delivered, where bugs are reported, and whether support includes help with third-party services. The license should be equally plain about the number of sites, client work, redistribution, and refunds.
Good documentation reduces the number of support conversations. A good policy makes the remaining ones less disappointing.
12. Run a 20-minute publication test
If a demo and documentation have passed the earlier checks, use this final sequence before committing:
- Open the homepage, a post, a page, a tag archive, and an author archive on a phone.
- Search for a post and navigate the result using a keyboard.
- Find examples with missing images, long titles, galleries, embeds, lists, and quotations.
- Follow the signup or membership journey from invitation to account access.
- Inspect the theme settings and identify which changes would actually be necessary for launch.
- Confirm the current theme version, Ghost compatibility, update terms, support scope, and license.
That short test will not reveal every defect. It will tell you whether the theme was designed as a publishing system or prepared mainly as a sales page.
The checklist should end with your publication
There is no universally best Ghost theme. A sparse essay site and a daily multi-author magazine should not pass the same design test in exactly the same way.
The standard that carries across both is fitness for real work. The theme should make articles comfortable to read, archives useful, native Ghost features coherent, routine publishing predictable, and future maintenance understandable. It should remain composed when content is absent, excessive, or inconvenient.
That is what you are looking for when you browse the Visioun theme collection, too. Not the greatest number of features, and not the most theatrical demo. The right theme is the one whose decisions still make sense after your own content replaces ours.