For newsletter creators
Publish your archive on the web, run the newsletter from your own list, and open a community for readers who reply: BuddyNext or Jetonomy for subscriber discussion, gated spaces for paid readers, and the issues as searchable pages. Add the community when readers are already replying to you with things others would like to see. Reign makes it all feel like your publication.
Newsletter writers want their own community and courses, but a hosted newsletter platform takes a share of paid subscriptions and its community tools are basic.
Reign + BuddyNext for a self-hosted home for a paid newsletter: public archive, subscriber community and gated spaces on your own domain. BuddyNext installs free, and its Pro plan adds paid plans and broadcast email.
Subscriber community and discussion spaces, free to install. You buy the Reign theme; BuddyNext and Jetonomy are ours and install free.
Screens from the live demos, with sample content. Open any of them and click around.
A public archive of past issues that search engines can find.
BuddyNext community, free to install, for subscriber-only discussion.
Own the email list and the domain, with no platform share of subscriptions.
You launch with a web archive of past issues, a members area for paid subscribers, and a discussion space. The archive is the part people underestimate: newsletters that live only in inboxes are invisible to search, and publishing them as pages turns years of writing into something that brings in new readers continuously.
A reader finds an old issue through search, subscribes, and receives the next one by email. Paid conversion happens when there is something extra: the archive, a community, subscriber-only issues. Readers who join the discussion renew at noticeably higher rates than those who only read, which is the argument for having a community at all.
Paid subscriptions billed monthly or yearly, gated by paid plans on the site, with the free list as the funnel. Running the CRM on your own site means segmenting by tier or engagement without an integration. Sponsorship of the free edition is usually the second line once the list is substantial.
Hiding the archive. Past issues are the only part of a newsletter that search engines can find, and keeping years of writing locked in inboxes means the list only ever grows through promotion. Publish the archive; the fear that it cannibalises subscriptions is almost always wrong.
Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. A newsletter writer needs the publishing side and a lightly used community.
Past issues go on the site as posts, with Reign providing a readable layout. BuddyNext supplies the reader profiles, feed and spaces, and its Pro plan adds paid plans and gated spaces plus broadcast email. Jetonomy adds threaded discussions for readers who want to respond to an issue. Learnomy, also free, can turn your best series into a course if you want one.
On BuddyPress, the BuddyPress Community Bundle kit is the packaged route and the membership site build guide covers gated content. The plugins page has the free and Pro split, and Reign is a flat theme licence with no share of subscriptions.
Publish first, build community later. The archive does the early work.
Install WordPress with Reign. Import or republish your past issues as posts, keeping the original titles and dates.
Add a clear subscribe form to the top of every issue page, with a sentence on what readers get and how often.
Decide which issues stay public and which are paid. Gate recent issues or specific formats if you want a paid hook, and keep older ones open.
Set up paid plans for readers who want the full set. BuddyNext Pro adds the plans and gated spaces; check the plan structure before you launch.
Open a discussion space when readers start replying by email. Post a question from each issue and answer the first replies yourself.
Import your existing list into your email tool and ask readers to re-confirm if needed. Tell them where to find the archive and the discussion.
Readers meet you in their inbox on a set day. Some open the email and read it there. Others click through to the web version, where they can comment, share and see related issues. A reader who found you through an old issue on a search subscribes and then goes through the archive.
Paid readers get something extra: the full archive, subscriber-only issues, or a discussion space. The ones who join the discussion tend to reply under each issue, and those replies show other readers what the paid tier feels like.
Your week follows the publishing day. You send the issue, reply to comments, pin the best reader response and note questions for the next issue. Because the archive sits on your site, each issue also adds a page that can bring in readers for years.
A newsletter grows through its archive. Each issue is a page that can rank, and the subscribe form on each page turns searchers into readers. Writers who treat the archive as a product, with tags, series pages and a best-of list, see steady inflow.
Paid conversion depends on what is behind the wall. Keep the free issue valuable and make the paid layer clearly different: earlier access, longer pieces, a members' discussion or a private Q and A. Test one change at a time.
Sponsorship of the free edition is usually the second revenue line once the list is substantial. Running the sign-up and member list on your own site means you can segment by tier or engagement without a separate integration.
An archive that is just a long list of dates is hard to use, and search engines struggle with it too. Organising it takes a weekend and turns years of writing into a resource. Readers who find an organised archive stay longer and subscribe more often.
Group issues into series. If you have written on the same theme several times, give it a page that lists the issues in order with a short introduction. These series pages can also rank for broad searches that single issues do not.
Tag by topic, not by date. Use a small set of clear tags, such as hiring, pricing or tools, and show them on each issue. Keep the list short enough that every tag has real depth.
Pick a few best-of pages. A page of the ten issues you would send to a new reader is the kindest introduction you can offer, and it works as a landing page from social posts.
Link between issues. When a new issue builds on an old one, link to it. The links help readers and search engines see how the work connects, and they keep people moving through the archive.
Hiding the archive is the main one. Years of writing locked in inboxes means the list only grows through promotion. Publish the archive.
Adding a community too early is the second. An empty forum looks abandoned. Wait for the replies.
Third, do not move the list in a rush. Send a clear message about the change, ask for re-confirmation if your rules require it and keep sending as normal while you switch.
If you also record a podcast, the podcast community page shows how to give both formats one home. If you are mainly a video creator, see the YouTube creator page.
If you only need to send email and have no wish to build a site around it, a hosted newsletter tool is simpler.
Usually yes. Export your subscriber list as a CSV from your current platform and import it into whichever email tool you use on the new site. Ask subscribers to re-confirm, and check the consent rules that apply to your list.
Yes, with a CRM running inside WordPress, so your subscriber list and your member list are the same records. Connect a proper sending service for deliverability. The alternative is a hosted platform plus a sync, which works but adds a moving part.
Mostly yes. Public archives are how new readers find you, and the fear that free archives cannibalise paid is usually wrong. Gate recent issues or specific formats if you need a paid hook, but keeping years of writing invisible costs more than it protects.
Not necessarily, and a dead forum is worse than none. Add one when readers are already replying to you with things other readers would want to see. That is the signal, and before it arrives a community is usually an empty room.
Yes, with the site as the archive and the membership layer, though it means a sync. Running the CRM on the site removes that, and lets you segment by subscription tier directly, which is usually the reason people move.
Offer annual with a monthly option, and price it against what a reader would happily pay without thinking about it. Charging more needs the archive and the community to justify it, so earn the higher price before you ask for it.
BuddyNext and Jetonomy cost nothing to install, and each has its own Pro plan for later. Running the third-party stack instead? The BuddyPress Community Bundle kit is the packaged route. Or have the Wbcom team set either one up for you.
One theme, the whole site
Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. Start with one, add the others when you need them, and keep one login for every member. Open a live demo, or launch a sandbox and get a fresh WordPress site to click through in about a minute.
Profiles, activity feed, spaces, messages and moderation on your own domain. Powered by BuddyNext.
Lessons, quizzes, certificates and memberships, on the same login as the community. Powered by Learnomy.
Listings, search, maps and reviews that members can add themselves. Powered by Listora.
Sell services or products from many sellers, with orders, reviews and commissions. Powered by WP Sell Services.
Employers post jobs, members apply, and you run the board from one dashboard. Powered by WP Career Board.
Reign with BuddyPress, ready in one click, or browse every demo by site type.
Add more when you need it
Tell us what you want members to do on your site. We will tell you which Reign setup, plugins and kit fit, before you buy anything.
I only have positive experience with wbcom. My journey started a lot of years back with the free buddyx theme. during my learning of wordpress and futher websites ideas I found a match with their Reign job mate theme. Always there to help, always open to explore ideas, always kind replyes even if I…
Swift and expert coding by Kerit to apply a personalised display adjustment on the Reign Theme for a media plugin that was not fully supported at the moment.
I purchased Reign theme from Wbcom Designs, the support team was very helpful and I got the perfect website what I was looking for. Good work Wbcom Designs
WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth. The recently launched BuddyNext Pro and MediaShield Pro are…
Love this company. Loved the REIGN product. They were there the entire time helping me set things up; and when things went wrong? They were quick to take action and help find a solution.
I am using the REIGN theme and several plugins from Wbcom Designs on my website. The theme is beautifully designed, and the plugins are user-friendly. Everything works smoothly, and the features are perfect for building professional websites and communities. What impressed me most is their…
We’ve hosted a number of Wbcom Designs clients on Levamo, and our experience with their products has been very positive. Their plugins and themes are well built, their support has been reliable, and they seem to be very innovative and constantly launching cool new products.
I have worked with Wbcom Designs on several custom development requests for my WordPress platform, and my experience has been excellent.
After 16 years of buying WordPress themes and plugins, I know exactly what bad support looks like and Wbcom Designs is the polar opposite. My setup was a nightmare: multiple tools, deep integrations, custom configurations that required real back-and-forth. Most vendors would've pointed me to a…
I was using an excellent plugin created by Wbcom Designs and had both an error and discovered a slight bug in one aspect of the plugin. After creating a support ticket - I got a super-quick response and discovered the error was on my part and was fixed right away. Regarding the bug - I was thanked…
