Using the SAAS template, I want to manage the blog and docs in a "CMS" like an admin screen, how?
Unless I'm missing something, the only way to create blogs right now is saving md files in the directories, and then also needing to change the schema/ structure in the config file each time. Is there a CMS tool that does this anyone has used or has any tldr on? I tried using netlify identity because that's where my blog/docs are deployed, but I'm stuck getting the login to work. Anyone done this yet?
7 Replies
Hi @Cubs. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information available, it seems that the OpenSaas template currently does not have a built-in CMS-like admin screen for managing blog and docs. The current method involves saving markdown files in the directories and updating the schema/structure in the config file each time.
However, there are discussions about integrating a blog into the main stack to simplify the process. The community has also considered using Astro, a framework that provides a structure for both docs and blogs, but it adds another layer of complexity during deployment.
For deployment, the current recommendation is to deploy the SaaS portion to Fly and the static blog/docs portion to Netlify. If you're having trouble with Netlify identity, it might be helpful to ask for assistance in the Wasp community or Netlify's support channels.
As for a CMS tool, there's no specific recommendation in the provided sources. However, you might want to explore headless CMS options like Contentful, Strapi, or even Netlify CMS, which can work with static site generators. These tools allow you to manage content through an admin interface and then pull that content into your application.
Remember to check the official Wasp documentation and the OpenSaas template for any updates or changes in this area.
Sources:
- Discord support thread: OpenSaas Blog deployment > Answers Part 5 (https://discord.com/channels/686873244791210014/1204929776272281641)
- Discord support thread: OpenSaas Blog deployment > Answers Part 4 (https://discord.com/channels/686873244791210014/1204929776272281641)
- Discord support thread: OpenSaas Blog deployment > Original post (https://discord.com/channels/686873244791210014/1204929776272281641)
- Discord support thread: Data Storage & CMS for Beginners? > Original post (https://discord.com/channels/686873244791210014/1206149808327364628)
- Discord support thread: Data Storage & CMS for Beginners? > Answers Part 2 (https://discord.com/channels/686873244791210014/1206149808327364628)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Cubs, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@Vinny (@Wasp) one for you
@Cubs the blog is using Astro, so this is a relevant bit of docs: https://docs.astro.build/en/guides/cms/
Thanks I will read that. I just started asking GPT to code me a custom streamlit CMS lol that connectes to my repo via github personal access token I have stored in streamlit secrets. I'll share the repo when it's done might be useful for others if it works nicely. I'll likely integrate openAI api too to help manage it 🙂
Yep. Like Miho said, the blog is a totally separate app that you can choose to use or not. you can just delete that section of the template entirely if you're not using it 🙂
yeah definitely want to use it on this first like personal/influencer page. I will create new SAAS apps now next that I will point to using this blog but the new forks I will not use the blog on I don't think. What's ur thoughts though, if you launch multiple SAAS apps, are you also managing multiple blogs/ docs for each of them? I can see docs maybe but blog too or is that overkill? I guess the posts can mostly be automated now days anyways tho
Wohooo @Cubs, you just became a Waspeteer level 3!
Ha it depends more about the brand than the app itself. Are all these apps logical part of the same brand? Imagine Google having Gmail and GDrive. Makes probably sense to have one blog for both. Unless the audiences are very different -> then you will probably want to have two blogs. But then it might not be under the same brand even. But for Gmail and GDrive, you kind of want to cross-polinate, so having a shared blog makes sense.
On the other hand, if apps are not connect in any way and audience is different, the only fact connecting tham is that you are the person that made both of them, then yeah, I think two blogs are the way to go.
Not an expert btw :D, so take this with a grain of salt.