Way back in the pre-Internet days, magazines often had little classified ads sections in the back. There was nearly always a couple of businesses that almost said they would send you pornography, usually for scientific and educational purposes; an offer to sell you a weather balloon or information on ham radio clubs or telescope kits; and at least one ad like this:<p>Make money at home stuffing envelopes! Send SASE and enclose $2.50 for our guide on how you can make money in your spare time!<p>And if you were foolish enough to send them the money and a SASE -- a self-addressed stamped envelope, the equivalent of an HTTP GET -- you would get a sheet of instructions, which began: "Take out an ad in a magazine telling people to send you a SASE and money. Make copies of this sheet and stuff them in the SASEs..."
I’d suggest this one instead:<p><a href="http://www.mrmoneymustache.com/2012/03/16/get-rich-with-blogging/" rel="nofollow">http://www.mrmoneymustache.com/2012/03/16/get-rich-with-blog...</a>
In section 4 (Creating an Online Course), the author links to her other article[1] about creating a WordPress membership site using plugins but specifically states these are free registrations that do not handle payments. I wish the author did explore payments more because there are WordPress plugins[2] that do provide subscription payment and reoccurring billing services integrated with payment gateways that truly allow a CMS to be monetized. The issue I see is that WordPress is the only CMS platform that offers such easy membership, payment and content restriction integrations. Have others seen this kind of functionality in other CMS platforms?<p>[1] <a href="https://www.codeinwp.com/blog/build-a-membership-site-on-wordpress/" rel="nofollow">https://www.codeinwp.com/blog/build-a-membership-site-on-wor...</a><p>[2] <a href="https://www.paidmembershipspro.com" rel="nofollow">https://www.paidmembershipspro.com</a>, <a href="https://docs.restrictcontentpro.com/article/1593-restricting-post-and-page-content#restricting-portions" rel="nofollow">https://docs.restrictcontentpro.com/article/1593-restricting...</a>