Plugged Into Programming - From WordPress Plugins To Micro SaaS
By Jamie Robe
Plugged Into Programming - From WordPress Plugins To Micro SaaSJul 06, 2023
The sexy topic all developers love to talk about...documentation!
I talk about a log-based type vs system-based type, and how I use both in a typical Wordpress micro- saas.
And I am finding documentation important as I continue to test building with crocoblock plugins like jetengine.
Day 8 - Emotional Milestones are important when developing
I am celebrating the rebuild of it using jetengine, jetformbuilder, and other crocoblock plugins. All no code!
I also reached episode 30 and gave 1000 all times listens. Thank you all very much!
Day 7 - Are no-code projects harder to start and stop than code?
Day 6 - Taking the micro-SaaS bull by the PayPal horns!
I was just listening to another podcast yesterday that had Seth Godin on as a guest. He has a new book out called "The song of significance". Anyway, Seth gave some advice to help people focus on creative projects. I am qupting him from what I jotted down while at a stop light yesterday: "What is the very very hard thing, that if it happens, your project will work better?". In other words, figure out the part that maybe you don;t know as much about (or down-right do not enjoy as much) and hit it first.
So I took the bull by the horns and selected the payment gateway and membership level/user registration part. Not as flashy as the other parts of the micro-SaaS I am redoing in this ongoing test - but critically important for so many reasons.
In this pod I will talk about my 11 hour saga today (on my vaca day off from J1) ... Ok I did eat a few meals at home... but it was a solid focused day. I am very happy :)
- Some gotchas on having to create a new business level paypal - they would not let my old paypal create APIs any more.
- How to get the pro version of jetformbuilder - the crocoblock super advanced form builder that I get with my license level. Turns out you get the free plugin from the WP repo and the pro parts are add-on that I get with my license.
- Building the form was the easy part
- Created a CCT using jetengine - to store some buyer info
- Learned about the post submit actions on the jetform settings on Gutenberg.
- A few gotchas due to even 1 year old youtube videos and other docs being outdated - crocoblock is modernizing everything all the time - which is great.
- Got some help from the cocoblock chat support - excellent and fast info
- Got some help from a youtube chat with some random user helping my with a 5 month old chat
- Completed the tests - finally getting a user registered, CCT record on the order inserted, an email to the admin sent, and a jetformbuilder form record being saved into a sort of form log
All very cool. I learned a lot and it is full steam ahead.
Thank you Seth Godin for inspiring my direction today - as now I can get to the fun parts :)
Day 5 - Thinking about options if using CPT or CCT to store and display my microSaaS data
Burnout and how to move past it
Day 4 - Some fun successes with JetProductGallery and a CPT
I have been able to have some fun today, and I believe a light bulb went off in my head about the templating features. I will try to summarize what I have found.
As I talk about today's findings, I started off wanting to make an artist portfolio system. So first I used jetengine to create a new CPT (custom post type), called artworks. These are the records that will hold a title and featured image of a painting, followed by some meta fields I created called price, description, notes, and so on. I did not use the content field or area of the default post, just the title and featured image. I also used one of the special media field that allows you to upload multiple images into one field. You will see how I use this later.
So far I have found 3 main crocoblock things related to templates. The first is the Jetengine - Listings, which are really templates. In the context of the grid listing features, you first create a listing item. This looks like you are on a page or post, with gutenberg and all its blocks and features. But this "page" is actually a template. I made one for a test called Artwork listing template.
So I then added a regular WP page called portfolio, and I edited that in gutenberg. I pulled in the jetengine block called listing grid. This is then set to the template I made above and magically all my artworks appear - each following the layout I did above. Very cool and easy.
Since I want to also allow the user to click on any artwork image and go to a single page with all the fields of data displayed, I needed to make a single page template just for this. This is where the crocoblock menu item in the admin dashboard comes in - it has 2 theme related sub menus. They botgh sort of work together. They are theme builder and theme templates. I used the theme templates sub menu item to add what is called a theme part. In my case I am creating a single. This will end up displaying the layout for any of the artwork cpt single pages. I won't go into details here, but you create the layout in gutenberg, with any blocks including the dynamic blocks supplied by crocoblock.
You also have to use the theme builder menu item to create a full template - one that allows (optionally) to change the header, body, and footer of any page. In my case I set the condition to be singular, cpt single - artwork. And I left the header and footer untouched, since my portfolio page is part of the rest of the WP site. In other words, I am using the theme templates laid out above in the middle body part only. Works!
Now comes the crocoblock magic! I want the single cpt - artwork template to also use the cool features of the JetProductGallery plugin. It can make a page look like some cool interactive product page - with image gallery, sliders, zoom, sharing, you name it! I dropped the block called gallery modern (there are others too), and I set it to use that meta field in my CPT where I upload multiple images. It also had a cool setting that allowed me to also use the featured image in with the rest. It looked 1000% better than anything I have made before.
In summary, just having worked on this for a few days, I have already learned enough to make an artwork porfolio system that would have taken me a LONG time using code and PODS. So far so good. No code needed yet :)
Day 3 - Thoughts on Elementor vs Gutenberg and CPT vs CCT
Got a little confused again with a template that was needed as I began testing the Profile Builder. That is a system they made that can create a frontend dashboard with subpages under a vertical or horizontal menu. This is for your users who log in and need to edit profile or content or other forms you build.
My confusion was with making a Listing template using a jetengine listing item. Had earlier used that for listing my CPT about pets. However, in this profile context I was confused if it was a different crocoblock template or maybe gutenberg.
Once I got thru that issue I was able to make the frontend user dash. Very cool.
CPT is a custom post type. These are used to build upon the data structures Wordpress uses for all post types.
CCT is a custom content type. Crocoblock makes this available when you have data that would be more effectively stored in its own individual DB table. Very powerful for the micro-SaaS developer.
My problem is mainly one caused by the side hustle nature of my project. I can only dedicate a limited amount of hours toward doing my side project. So far crocoblock has bern fun to learn and to use. I have a new idea for a web app or site or micro-SaaS every time I try a new feature lol.
Day 2 - First experiences with getting support from Crocoblock
This is Day 2 of this series exploring how far I can push crocoblock's ecosystem of plugins to build a micro-SaaS app.
I really like the ease of working on Custom Post Types or CPTs using Jetengine. Jetengine seems to be the original crocoblock plugin and it handles a lot of things, and its interface for building CPTs is pretty easy to use. I have made CPTs for years with code and also with PODS.
I did get a reply to my questions I submitted on Day 1 (late in day), using the support ticket system. I am in Florida (UTC-5) and they seem to be in Ukraine (UTC+3), and I had a reply waiting for me around 6:30am or so on Day 2. Very fast turnaround and the ticket was helpful. Giving me 2 links.
The crocoblock knowledge base is extensive with documents, tutorials, and a huge video collection. Tons of YouTube videos are made by crocoblock staff, and there are lots of good ones from independent people too.
I also decided to do the dreaded deed and join Facebook. I had a Facebook account MANY years ago and cancelled it after 24 hours. I just don't like the feed system, people trying to friend you, etc. But crocoblocks has a private Facebook community group, and I joined to get into it. You have to wait for a few hours so they vet you. I used the same email I used to register my license of crocoblock.
One my first day I posted a hello to everyone and got some responses :). There are 23.7k members! It does seem very active. On my first day while I was reading I decided to reply with an answer to someone's question - it was clearly about using AJAX so I felt I could answer them about using javascript to make the live updates in the client. They said it was helpful.
That was about it. Day 2 was a J1 day as well, so I have limited time to put on this on weekdays (just like many of you). But I am able to use my time wisely and I will keep pushing forward! Till next time - keep on it.
Day 1 - First successes building CPTs using Crocoblock's Jetengine plugin
Day 0 was basically purchase and install, while in this Day 1 episode I talk about setting up an smtp service for the dev site, as well as starting to actually build out part of the specialized content structure of the dev site.
This app was previously developed using PODS and custom PHP code, so I am basically starting on one CPT called pets. Pets holds a title, featured image and a bunch of meta fields. Jetengine has a very nice interface allowing no code construction of the Custom Post Type, as well as allow creation and editing of the data itself in the admin backend.
I am learning as I go, so I spent some time watching the crocoblock videos and reading tutorials. I did get some questions together and created a support ticket to see how long it takes to get help. More on that in Day 2.
This episode is part of a 30 day test I am doing to crash-learn how to use the crocoblock ecosystem of plugins. I am building or should I say rebuilding one of my micro-SaaS apps that I previously developed using PODS, and lots of custom code. I want to see how far I can push crocoblocks :) I will save any coding for my secret sauce of the functionality of the application.
Day 0 - Purchase and setup
I am doing a 30 day series on my real life evaluation of the crocoblock framework. It is a series of plugins designed for no code development of wordpress sites. I am trying it out as a RAD for one of my own micro-SaaS projects. I called this Day 0, since it was my wedding anniversary and I only had about an hour or so free to purchase it and install on a basic cloudways dev site.
Before installing crocoblocks, I did a WP install, adding mainwp (which I use for monitoring and managing all my sites and micro-SaaS apps), and updraftplus (my backup plugin of choice). I then used the crocoblock wizard to get things going.
The wizard allowed me to easily install the free version of the GeneratePress theme. I happen to have a premium license of GP so I downloaded the plugin .zip from GP's wensite, so now I have the full premium version running. crocoblock claims 100% compatibility with GP (and a half dozen other good plugin choices).
This episode is part of a 30 day test I am doing to crash-learn how to use the crocoblock ecosystem of plugins. I am building or should I say rebuilding one of my micro-SaaS apps that I previously developed using PODS, and lots of custom code. I want to see how far I can push crocoblocks :) I will save any coding for my secret sauce of the functionality of the application.
Celebrating endings and new beginnings
Facing the Stormy Seas of the Unknown
Wrap your mind around Beta Testing
Making a decision on your development framework...to use WordPress or not?
Overcoming Complexity
Focus on Impact
You are in control so do not stop!
Stop thinking about your Micro SaaS and just start doing it
A paper and pencil hack that might help you create some creativity and thinking space
Finding your micro SaaS customers using time, money, or audience.
How customers perceive the value in your micro SaaS products
Pivoting like a ballerina or a bull in a china factory?
You might get to a point in your project where you ask yourself this: How and when should I change course on my micro SaaS project?
Are you pivoting like a ballerina or a bull in a china factory?
Yes,change to a complex online business or software product can be scary. But you can make a rational decision and execute a pivot. And it just might save your project.
Concepts - pivoting, why I did it a few weeks ago, changing my whole website and branding - from the old wpplugincollege.com to the new pluggedintoprogramming.com. I did it to save confusion of the audience of my podcast and YouTube channels. Why was I promoting 2 different brands? I decided the new domain name made much more sense to my target audience, who were responding well to the podcasts. And even google was ranking my podcasts very highly, right away. That surprised me. So I acted.
What to watch out for - pivoting...
- Too soon
- Too late
Tips on how to execute
- Think things thru - write or graph it out
- It can take time
- Recover and reuse as much as you can from old to new
Coaching
- Don't be afraid to keep trying
- Don't be afraid to change
- At an early stage You are probably the only one who will notice
- At a later stage, you might have to talk to customers / users and explain changes, refund money, even shutdown something
- Have confidence in yourself and your creative decisions - there is no right or wrong - as long as you keep motivated
- Main thing is to keep in motion and keep spread out your opportunity surface area
So visit me at pluggedintoprogramming.com and take a look at the changes - and good luck with your project - I know you can do it :)
The biggest advantage of building a microSaaS using WordPress
There are many factors to consider when choosing the framework or platform you are going to use to build your microSaaS product. Solo-founders-programmers who are considering to use WordPress often ask the question: What is the biggest advantage of building a microSaaS using WP? Answer: You will 100% own and control your platform.
In this episode I look at some objective factors to demonstrate what an advantage this ownership is for an entrepreneur.
If you are interested in learning more and WordPress, plugins programming, and microSaaS, join us at wpPluginCollege.com
Leveraging WordPress as a Development FrameworkWe have already discussed this in detail in a previous article, but to summarize, here are 3 big advantages to using WP:
- #1 – Robust, Flexible, Reliable Tech-Stack
- #2 – Benefits of Open-Source
- #3 – The Gigantic WP Ecosystem = Thousands of plugins / themes / consultants / companies generating $600 billion
But when you talk to successful solo-founders / solo-programmers, they will often reply that the number one thing they value the most is ownership and control - both of their online products and businesses, as well as their time and attention.
So does WordPress offer this advantage? Yes it does!
To demonstrate how WP enables this ownership, let’s look at 4 factors we can use to evaluate this objectively:
- Startup-ability
- Scalability
- Sustainability
- Sale-ability
By startup-ability I mean the difficulty level of getting a microSaaS project up and running as a bootstrapped startup.
- With 100% control, you can run your SaaS virtually anywhere (shared, server, VPS, cloud)
- Theoretically the lowest possible startup costs (mostly hosting)
- Contrast with bubble.io (hundreds $/month)
This relates to the number of users you will have, the amount of content/data stored, the number of visitors, etc.
- With lower recurring costs, WP allows you to keep scaled down and still be profitable
- Also allows you to easily scale up with cloud servers
- WP is demonstrated to be able to handle incredibly large projects (wordpress.com)
This means the long term stability of the product / business you are creating. The main thing you need to watch is risk caused by your development choices. WordPress offers a huge advanatge in that you control everything and can move the entire system to any server or system.
- Reduced risk from the platform (like bubble.io) from:going out of business
- flagging your usage, users, content
- raising prices
Even though we are focusing most of our energy at developing long-term, sustainable, micro-scaled businesses, we also should look at possible end-games. One of the rip-cords you can pull is the sale of your microSaaS. Developing it in WordPress gives you some real advantages.
- You own a tangible propertyyour configurations
- your custom plugin code
- your domain and intellectual property
- You can easily backup, export everything
An update on the learning design and community structure of the wpPluginCollege.com
In this episode, Professor Jamie talks about the project that he has been developing for the past several years, and has evolved into the wpPluginCollege.com. This is a learning platform/community for solo-founder-programmers who want to make new streams of income from plugin products or SaaS applications.
The project is getting closer to launch, and Jamie shows off the structure for the curriculum. Everything is divided into learning centers. Most centers will have courses, forums, and live online events. Those centers, such as Plugin Programming, will also have the hands-on learning lab that he has been developing. This helps get the student into learning mode almost instantly.
He will release more information as the material is built out and we get closer to launch. For now, if you are interest I highly suggest you visit https://wpPluginCollege.com and sign-up for the Free Subscription to the newsletter.
A data driven web app created using WordPress
As part of our series from https://wpPluginCollege.com on 7 different products that can be created using the WordPress plugin programming framework, we are looking at a type of web app. Data-driven, web applications are software that helps businesses, corporations, non-profits, and government organizations collect, store, and analyze data. These are usually complex in terms of data storage and customer requirements. The programmer that has the right skill set can develop these applications for clients, and this can be a very lucrative business.
I have built many of these data-driven web apps for use by large organizations. The beauty of using WordPress is that you can make the app mobile friendly very easily. You also have access to a lot of useful database functions for storing and accessing any type of data.
I finish off the episode with a short coaching section where I talk about thinking outside of the product box.
Please visit the website to get the visuals.
The pro and cons of building a microSaaS product
MicroSaaS is a type of Software-as-a-Service product, and today's show looks at the pros and cons of creating one as your business model. This is part of a series looking at 7 different types of products that can be built using the WordPress Plugin Programming Framework. This is what we focus on at wpPluginCollege.com with our shows and courses.
MicroSaaS are specifically engineered to be built and operated by a solo-founder or perhaps a tiny team. It is often the choice for those seeking to build a sustainable, lifestyle business. They can also be scaled larger if circumstances dictate. I feel that this presents a lot of cool opportunities to programmers and founders who are bootstrapping and need to go after a tightly niche market.
We use SWOT analysis to take an objective look from the solo-programmer or solo-founder's perspective.
Creating and Selling a WordPress Plugin as a Software Product
At wpPluginCollege.com we are exploring 7 different ways for solo-programmers to develop income producing products and businesses using WordPress as the development framework. This is the first in a series covering a detailed SWOT analysis of each idea.
Selling or licensing plugins is what I call the "traditional" business model in the world of WordPress programming. There are over 50,000 free plugins found in the WordPress.org/plugins repository, all open source. Many of those have up-sells to paid, premium versions. There are also hundreds of premium plugins sold directly from websites and other commercial marketplaces.
To some, this would sound like a "saturated" market, but that is not a correct way of looking at how the plugin market functions.
Many of the plugins that exist are outdated or aging rapidly. New features in WordPress and other technologies (like APIs) now enable more feature-rich and advanced plugins to be developed.
- The so-called "Bread-and-butter" plugins, like form builders, are not 100% locked in by the existing products. There is always room for the brand new approach, especially since there are so many new businesses and users coming online every day.
- Inventive and creative programmers can find new ways of doing the same thing faster, easier, cheaper... or just plain more fun.
- The WordPress admins and developers are constantly seeking new features and capabilities that will help make what they provide or sell more interesting and desirable to their users.
What is the DOM? From code to eyeballs :)
In this episode we are exploring an important part of web programming that is hidden in plain sight to most of us - it is called the DOM. This stands for the Document Object Model, and it is created to represent the html document in the web browser every time code is sent from a web server. The DOM also has a programming interface called an API, which can be manipulated with languages such as JavaScript. I will be going over these concepts, as well as showing what it all really looks like using php and js in the pluggedintoprogramming.com hands-on learning lab. At the end, I will give you some coaching about dealing with the complexity of learning how to code.
When Working Backward Can Actually Move Your Software Product or Business Forward
It is very easy for a solo-programmer and solo-founder to get overwhelmed or side-tracked when developing a software product/business, such as a WordPress plugin or a micro-Saas (Software as a Service). In this episode we will looking at a planning technique called backward planning or reverse planning. I originally learned it from a professional business coach many years ago, and it really gave me some "aha" moments. I will be giving you some concepts, with real-world examples how it has helped me with my side-hustle projects, such as wpPluginCollege.com.
Even the best laid plans can sometimes unravel. Everyone who has ever created a software product or business has gotten "stuck". I have a segment of coaching in this podcast where I give you strategies to get yourself focused on what is really important. Remember, done is better than perfect. You can do it! Enjoy.
Be sure to visit us at https://wpPluginCollege.com to get show notes, join in the discussion, and to register for our free mini-course on 7 ways to make money using the WordPress Plugin Programming Framework.
Concepts, Creativity, Code, and Coaching - Laying the groundwork for learning to create programming products.
I have seen a lot of changes in technology and computer languages. I found 4 elements that have helped me in my journey and evolution as a solo-programmer and solo-founder, now concentrating on micro-SaaS and other products using the WordPress framework. In this episode, I want to lay the groundwork for all my future shows and online courses. I will always incorporate as many of these 4 elements... concepts, creativity, code, and coaching into everything I make for you.