@dcarter1 wrote:
That sounded like a subset of Hubspot CMS rather than the whole thing to me, but I can't find any references to the name Hubspot Blog I assumed it was a reference to the CMS Blog API which sits inside Hubspot CMS.
Well yes.... and no.... The blog is cetainly a subset of the CMS. A CMS is just a management system and I'd certainly hope people could manage their blogs. Yes, there's an API which is precisely why there are plugins possible 🙂
Whenever people pipe these things through a JAMStack app / SSG they are typically doing so in a headless setting where content edtiors just come in and write things and have nothing else to worry about. A dev does the rest. So, it's a separation of concerns (which never really works imo, but anyways....) that people have back-filled into real / heavier CMS' like HubSpot, WordPress, etc since they expose an API (data stream) from which this sourcing can be performed.
Whether it's real REST APIs, GraphQL, or higher level meshes.
@dcarter1 wrote:
I could find so little how to's on Google, it sounds like a not very well worn one and I'd need to reflect this in costings. Also, it possibly indicates it is not a particularly good idea (as the sales staff suggested, the CMS is more for marketing people than anything - whatever that means).
Right... but there aren't really "how tos" for this type of stuff. It's just a plugin. If you're a developer doing this... you don't need a how to you already have the dev chops to do so. And if you don't.... Don't try it not worth it.
Same process whether you are sourcing from contentful, strapi, or any other headless CMS.... or a real CMS with a data stream exposed. It's a generic process that is unchanging. Your only difference is maybe a different plugin piping things for the source and changing how the GraphQL / querying of data within these posts is structured for them to be spitout via in a SSG / JAMStack app. You just need to know if an API exists or not and if someone has already done the hard work for you (a plugin). If not comfortable with this.... then yes you may be giving yourself more overhead than you'd like.
@dcarter1 wrote:
now much of an untrodden path
Not an untrodden path... It's just that nobody uses HubSpot, because per this comment:
@dcarter1 wrote:
more for marketing people than anything - whatever that means
It's meant to be friendly for people to edit with user-friendly text-editors - marketers - who don't do anything technical.... So the most technical thing you get in HubSpot are workflow "automations" and half-baked themes / websites made by similar people. Very rarely, unless you're building an integraiton or custom app, do you do any semblance of real development in HubSpot.
So, in that sense maybe it's "untrodden", but not impossible. You'd effectively being offering a service that says:
"Hey pay $$$$ a month for fancy editing priveleges you could just use a better headless CMS for, then pay me to build loads of extra tech on top of that, then maintenance fees and complications, hoting / extra dev to setup a JSx to display it via JAMStack for better metrics presumng I have the development chops to make that happen".
Not a great sale. A better sale would be "I can make a JSx app inside HubSpot"