Landing Pages for Theme & Plugin Developers

From an action item that developed during the Feb 7 marketing meeting:

  • @james and @norske to create landing pages for plugin and theme developers so that we can start approaching them in a more formal way to invite them to support ClassicPress: @BlueSkyPhoenix can assist

Once landing pages are built, marketing can begin to approach theme & plugin developers

3 Likes

@norske and @james, what are our next steps here? How can others assist?

2 Likes

@norske has put the first of these landing pages up as a draft page on our main site. It needs copy revision and then it needs to be added to the site’s menus (we had previously discussed putting it under “Resources” for now).

2 Likes

Thank you! I’ll take a look at it and make any needed changes.

2 Likes

@norske this looks great. I’ve made just minor changes for flow. Do you want to have a last look, or are you ready for me to publish it?

2 Likes

Please publish it any time if you feel it’s production-ready. I don’t see any major bugs in markup for now and wording is yours. I completely trust your opinion here)

3 Likes

This has been added. I’ll send out a tweet about this as well. Thanks for your work on this! Let me know when you’re ready to have me review the landing page for theme developers.

4 Likes

I think “Increase your plugin audience with ClassicPress developers” is a bit long for a page title, menu entry, and URL slug. Here’s a screenshot of the menu entry:

Can we change this to “ClassicPress for Plugin Developers” instead?

1 Like

I hadn’t even noticed that… Could it not be shortened to just “Plugin/Theme Developers”? The extraordinary length of the text makes it seem unconsidered. The page, on the other hand, is a palatable jumping-in point for curious developers. Thanks for putting this together! :+1:

3 Likes

Isn’t that page only about plugins? What about “Opportunities for plugin developers”.

2 Likes

I would probably do it like this:

  • “Resources > For Plugin Developers” in the menu entry
  • www.classicpress.net/for-plugin-developers/ in the URL
  • “ClassicPress for Plugin Developers” in the page title

I think the “For” is important, there is a difference in how “Resources > Plugin Developers” sounds vs “Resources > For Plugin Developers”. classicpress.net/for-plugin-developers also flows pretty nicely.

Then the idea is to have other pages later on. “For Theme Developers”, maybe “For Hosting Providers”, etc.

I think this initiative is a great starting point to help specific audiences get oriented to ClassicPress. I’ve noticed that people often don’t know where to start looking at first, so this will provide a good initial overview focused on specific interests, with some links for further investigation.

2 Likes

These changes have been made. Thanks for your feedback.

1 Like

What about increasing the width of the submenu from 150px?

.nav–toggle-sub ul ul {
width: 180px;
}

(in css/autoptimize.css line 38?)

That makes all sub-menu items on one line. I don’t think it upsets anything else.

3 Likes

Note: That’s a double dash there on the selector .nav--toggle-sub ul ul just in case anyone is testing the code :slight_smile:

3 Likes

Good idea. I bumped this up to 180px. This is enough for everything to fit on one line for me, and we shouldn’t make it much wider or these could start to run off the screen at some resolutions / zoom levels:

1 Like