This was a great discussion, and worked well just as audio too when I was tabbed out. API stuff IS daunting for us non-coders, but utlising some plugins to achieve what we want to do with it is so close. Nice to hear other Designers /Creators have the same obstacles.
The concept of using an API or any dynamic content is to leverage dynamic site facets over static. Build a site with as little pages while using dynamic content/posts/api calls to fill posts that appear as pages. On the back end using plugin developer tools to do this so you don’t use a plugin you don’t need to. I’ll give you an example I’m building a RV campground site. In research I discovered most have a 7 day forecast widget. Makes sense if you are on vacation in an unfamiliar area in your RV, right? I can go the plug-in route which is built and calls up a popular weather API. Or I could create my own CPT that taps into the same weather api, using 75% less code bloat, determine control over the calls and data needed and ultimately have just the right amount of power from the same source the plug-in uses minus the extra intrusion, and injection and security risks if the plug-in isn’t using standard practice. Although the biggest advantage is scalability and maintainability . Why? The reason why is because who knows if that plug-in will ever be maintained in the future although if you structure this into this site project, it will always be maintained so long as it’s calling up the API and the API is still being maintained. Developers abandon Plug-ins all the time, rarely do you see an api get ignored. If it does, all you have to do is change to a different API.
Yea, if I'm understanding your approach, I agree with you. I'm releasing videos this week where I build my own lightweight custom plugins so I don't need any extra bloat.
If you look into CornerStone or CS with Pro-Theme, you can do all of this even tapping into any API, THEMCO’s API, or even WordPress Rest API all within the builder UI. So, yes, it can be done.
@@BrendanOConnellWP I think their tutorials could use a huge overhaul. They have remained almost invisible because their best content remains behind a paywall. It’s unfortunate because their builder passes the 20 things you need in a builder. They need to take a content creator approach to their branding and leverage this tool’s power to the general public. I’ve been a fan of Themeco since X. I was there when they pivoted to Pro. Since those humble beginnings, they have strayed off message and from their original roots from a great origin story to a corporate brand that has zero personality. I still love what they’ve built but anyone who accidentally stumbles on them now doesn’t get the support or the love they once had built into their core values.
![Chris Langan - The Interview THEY Didn't Want You To See - CTMU [Full Version; Timestamps]](/img/n.gif)
This was a great discussion, and worked well just as audio too when I was tabbed out. API stuff IS daunting for us non-coders, but utlising some plugins to achieve what we want to do with it is so close. Nice to hear other Designers /Creators have the same obstacles.
100% 🙌 we're all navigating it together 😅 thanks for watching!!
The concept of using an API or any dynamic content is to leverage dynamic site facets over static. Build a site with as little pages while using dynamic content/posts/api calls to fill posts that appear as pages. On the back end using plugin developer tools to do this so you don’t use a plugin you don’t need to.
I’ll give you an example I’m building a RV campground site. In research I discovered most have a 7 day forecast widget. Makes sense if you are on vacation in an unfamiliar area in your RV, right?
I can go the plug-in route which is built and calls up a popular weather API. Or I could create my own CPT that taps into the same weather api, using 75% less code bloat, determine control over the calls and data needed and ultimately have just the right amount of power from the same source the plug-in uses minus the extra intrusion, and injection and security risks if the plug-in isn’t using standard practice.
Although the biggest advantage is scalability and maintainability . Why? The reason why is because who knows if that plug-in will ever be maintained in the future although if you structure this into this site project, it will always be maintained so long as it’s calling up the API and the API is still being maintained. Developers abandon Plug-ins all the time, rarely do you see an api get ignored. If it does, all you have to do is change to a different API.
Yea, if I'm understanding your approach, I agree with you. I'm releasing videos this week where I build my own lightweight custom plugins so I don't need any extra bloat.
If you look into CornerStone or CS with Pro-Theme, you can do all of this even tapping into any API, THEMCO’s API, or even WordPress Rest API all within the builder UI. So, yes, it can be done.
I'll have to check it out, thanks!
Yep good point! ThemeCo is doing some great stuff with API in their builder natively, lots of good docs and tutorials on their site
@@BrendanOConnellWP I think their tutorials could use a huge overhaul. They have remained almost invisible because their best content remains behind a paywall. It’s unfortunate because their builder passes the 20 things you need in a builder. They need to take a content creator approach to their branding and leverage this tool’s power to the general public. I’ve been a fan of Themeco since X. I was there when they pivoted to Pro. Since those humble beginnings, they have strayed off message and from their original roots from a great origin story to a corporate brand that has zero personality. I still love what they’ve built but anyone who accidentally stumbles on them now doesn’t get the support or the love they once had built into their core values.
Loved this :)
Thank you for watching!!!
this should be goooood!!!
You know it 🙌
'should' being the important operative word here