This does make for a clunky workflow (joining is still required before subscription), and it only suits sites which have a very simple ‘a few categories’ structure.
The core problem when attempting to use Discourse as a membership site (with paid members) is that the two processes (joining and subscribing) are separate at present. I’ve tackled this by either embracing it, or trying to work around it:
Embracing the Join / Subscribe separation
Having a public component of the site, so that people already have a reason to join it - and ‘financial membership’ is simply taking it to the next level. Example site:
Working around it
Being login-only, and using the Custom Wizard Plugin 🧙 to force people to the subscription page as part of the joining workflow.
Unfortunately, they can still crash out of it if determined. If they do, they get a quite restricted experience, but this must be carefully configured. Example site:
The way forwards
Having the option to connect the two in a single workflow would be brilliant, especially for membership organisations which want to use Discourse for their member website.
Personally I’d do it like this as a first pass:
- Have a setting in the Plugin which turns on Subscriptions during joining
- OFF: as current functionality (default)
- OPTIONAL: directs people to subscription page at end of joining (but allows them to navigate away)
- FORCED: directs to subscription page, and does not allow access to any other parts of the site unless subscription granted
Would of course need some messaging and polish as part of that.