What kind of themes is the Ghost marketplace in the market for?


#1

I have made four Ghost themes, two open-source and two premium. I’m about to start work on my fifth theme. But first, I’d like to find out what it takes to get a theme in the official Marketplace.

Making Ghost theme development an economically viable activity is hard even when you have a best-selling premium theme. When Ghost pivoted to be more magazine-oriented, and the marketplace was relaunched, and the listings for my first two themes were taken down, downloads declined.

I soon discovered that selling enough copies of a theme that isn’t in the marketplace takes a lot of work, due to the comparatively small market for Ghost themes. Whether your theme makes it into the official marketplace has a huge effect on whether being a Ghost theme developer is economically sustainable.

So I decided it would be worth asking, before starting my next theme: what are you looking for when you’re reviewing themes for the marketplace?

I have read the guidelines, but other than the obvious things like ‘quality over quantity’ and ‘follow the guidelines’, they’re a bit vague. I don’t know whether Laminim was rejected due to quality issues, lack of uniqueness (my themes tend to be solid and pragmatic, but not terribly trendy), or because I didn’t follow of the rules in some way, so I’m not sure what area I need to improve on with my next theme.

The marketplace is currently dominated by fairly slick, modern, masonry layout magazine themes, Casper foremost among them. That seems like a pretty crowded space. Here are some ideas I’ve come up with for my next theme:

  1. A theme for longform literary magazines. Clean and typographic, ala The Paris Review, McSweeney’s, or Granta.

  2. A theme that is entirely composed of text that could be typed on a manual typewriter, set in a genuine typewriter font.

  3. A theme for the ‘lite’ versions of news sites, ala text.npr.org or ite.cnn.com

  4. A more “retro” styled blog / magazine theme. (Closest examples I can find to what I have in mind is HTML5Up’s Strongly Typed template, Retro portfolio WP theme, or the Extinct WP theme)

Do any of the Marketplace reviewers have a hunch about which if any of these would be most likely to fit in the marketplace, assuming the execution was up to Marketplace’s high standards?

In addition, do you have any suggestions of what I could improve about my existing themes:

  1. MNML,
  2. Laminim,
  3. Undefined
  4. Weblog (I have a feeling this one may be … a bit too unique, shall we say :nerd_face: )

… to increase their chances of qualifying for the marketplace?

Thanks in advance :innocent:


#2

Hello!

Could you send me a link to your themes?

I am looking for a solid, well supported theme. I am not happy with a lot of what I’ve seen in Marketplace because a lot of these ‘professional’ themes, when you look into it, are running on version 1 still. Furthermore, many link to Themeforest, have few sales and the comments from support dried up a good while ago, which doesn’t give me any confidence that they are being supported.

So maybe getting into Marketplace either isn’t that difficult or shouldn’t be a focus for you?

The more I look into Ghost, the more it reminds me of the WordPress market pre-StudioPress.

There are ripe pickings for a StudioPress-type business to run a pro Ghost theme platform. I’ve had to spend some serious time on Google to find what I deem to be professional Ghost themes.

Absolute minefield.

:weary:


#3

@schnooks I have two premium themes, Laminim and Weblog, on CreativeMarket, and two free, open-source themes, MNML and Undefined, on GitHub.

If I were to recommend one, it would be Laminim. It has the most features, and has been quite popular on CreativeMarket. I do my best to provide good support for all of them, of course, but my premium themes tend to get priority.

I know what you mean about it feeling like you’re in pioneer country when you move from WordPress to Ghost. It’s a newer platform, and right now a lot of the people using it are developers and larger publications, so theme customizations for Ghost involve rolling up your sleeves and getting into the code more often than theme customizations for WordPress.

Like I mentioned in my previous post, it’s hard to make it economically viable building themes for Ghost, which is probably why there are only a handful of us managing to make it work. I know of about half a dozen professional Ghost theme developers (individuals or companies with multiple actively-maintained premium themes). That said, there are quite a few nice themes out there by more casual developers — many of them free.

From what I’ve seen, the quality, quantity, and variety of available Ghost themes available is steadily getting better, though. And as far as I know all the themes in the official Marketplace — and all of my themes — are compatible with the latest version of Ghost.


#4

Thanks. @curiositry! Good to know!

I see you don’t use Ghosthunter (neither does Casper), which a lot of the other premium themes do, and wondered why?

Just goes back to my previous point about users finding content.

Thanks!

Jayke


#5

@schnooks

The short version: More features = complexity = headache. Complexity makes a theme slower, more work to maintain, harder for users to customize, and creates places for bugs to hide.

Having too many “features”, is, in my opinion, a bug. So before adding a new feature, I ask myself:

  1. How many people will actually use it, and how much value will it add for them?

  2. If I implement it, will the benefit for the people use it outweigh the negative impact on the people who don’t?

If benefit to those who will use it minus cost to those who won’t > energy required to implement and maintain feature, I add it.

Example: Not too long ago, I added i18n localization support to Laminim because a customer asked for it. It made at least one person happy, and it didn’t take too long — but it also increased the complexity of the theme, both for me to maintain, and for other users to edit. The jury is still out on whether I made the right choice.

My reasoning regarding search in specific is based on two pieces of data:

  1. None of my customers have asked for search.

  2. I can’t remember the last time I used the search bar on a blog. If it’s something I’ve seen before, I search my bookmarks / history. If I’m looking articles on some specific topic, I search Google, or a topical aggregator like HN. And in the rare instances when I want to find a particular article on a blog with a lot of posts, I type QUERY site:theblog.com in my address bar, which saves a few seconds and often gets better results.

When Ghost adds native search support I’ll use it to my themes. Until then, I don’t think the benefit search provides warrants the additional complexity, development and maintenance time, page weight, and potential for security vulnerabilities of a 3rd party JS library.

That said, this is a strong opinion weakly held, which could easily be changed by a sufficiently persuasive argument :slight_smile:


#6

Hi @curiositry.

These are all very fair points.

I guess I get frustrated with the fact that a lot of themes do not allow any function for the reader to find previously written content (i.e. not the most recent content), on the basis that my blog (as with many other blogs) is not a personal journal (for example) and therefore chronologically ordered posts are not required, as the content is instructional and therefore all posts are of equal importance.

Having a tag page to show post categories at least allows the reader to navigate to the category of post.

Basically, the exact same functionality as this forum, with categories.

Because this forum, as with my blog, is extensive, navigating by category alone will not be sufficient, given the volume of content. I use the search function on this forum to narrow my search. As it happens, I can’t find many of the answers to my questions, to I create a topic. Sorry about that!

So I guess it depends on the type of blog being constructed using Ghost and the volume of information that blog holds. In the early days of developing my blog, search will not be required and would indeed be quite ridiculous as the reader could flick through all of the the posts at a glance because there will not be many.

Maybe by the time I really do need search, the Ghost search function will be baked in anyway!

:smile:


#7

@schnooks Although there isn’t a definitive timeline yet, native search is indeed planned: