Use Astro for Docs (but other thing for Blog)
I am trying to understand how I can use something “extra” (excuse some non-tech terms), some other library or similar to not use what is Astro for Blog. I will use Astro for Docs because the layout is ideal but I would like to be able to use it as a different “layout” from the blog frontend.
Any recommendations?
Can you modify in Astro things as if it were a “Theme Builder” like Divi, Astra, etc... For wordpress?
For example Railway has Docs similar to Astro: https://docs.railway.app/
And their blog is "different", so I assume they are using other "thing, library, dependency": https://blog.railway.app/
17 Replies
Hi @NEROX. 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 provided in the knowledge sources, it seems that you can indeed use different libraries or frameworks for different parts of your application when working with Wasp. However, the specific details on how to achieve this are not provided in the knowledge sources.
In one of the Discord threads (https://discord.com/channels/686873244791210014/1204929776272281641), a community member mentioned using Astro for their blog and docs, but also noted that it added an extra layer of complexity during deployment. They also mentioned the possibility of integrating a blog into the main stack, but didn't provide specific details on how to do this.
It's worth noting that while Astro is a powerful tool for building fast, modern websites and can be used to create both blogs and docs, it's not the only option out there. There are many other libraries and frameworks you could consider for your blog, depending on your specific needs and preferences.
As for the Railway example you provided, it's possible that they're using different tools for their docs and blog, but without more information, it's hard to say for sure what they're using.
If you're looking for a more detailed guide on how to use different libraries or frameworks for different parts of your Wasp application, I would recommend checking out the Wasp documentation (https://wasp-lang.dev/docs) or asking in the Wasp community for more specific advice.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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?
@kapa.ai Thank you very much for your response. Don’t worry, as you have answered me very correctly. In this case, as you yourself mentioned that Astro has its own blog and documentation, but they have something complex during the deployment process and do not provide too many details about it, I wanted to ask you several other things. If I'm not mistaken about what you’re telling me, you are referring to frameworks or libraries with which I can run an npm command, possibly from a GitHub repository, and install them in the same way that I installed and am running Wasp on one side and on a port. In the end, I will deploy both of those things on the domain, as well as the blog, the documentation, etc. So, I want you to look for some of those options for blogs. Don’t worry, you’re not going to do it wrong. And lastly, I wanted to ask if it's possible to use a WordPress base solely as a CMS or article manager, categories, thumbnails, etc., and somehow use something I believe is called GraphQL to use React, since that's what Prisma uses to create a kind of headless blog based on React but with Wasp. In this case, you just understood an idea that I just told you, but I know this has already been done. That is, there is something that I don't know how to express, and you simply have to tell me.
Let me check the knowledge base for you. One moment! :books:
----------------------
Based on the knowledge sources provided, it seems you're interested in using a different library or framework for your blog, separate from Astro, and you're also considering using WordPress as a headless CMS with GraphQL.
While the knowledge sources don't provide specific recommendations for alternative blog libraries or frameworks, there are many options available in the JavaScript ecosystem. Some popular choices include Next.js, Gatsby, and Nuxt.js. These frameworks all support server-side rendering and static site generation, which can be beneficial for blog sites.
As for using WordPress as a headless CMS, this is indeed possible. WordPress exposes a REST API that you can use to fetch your posts, categories, and other data. However, if you prefer to use GraphQL, you might want to look into WPGraphQL, which is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site.
Regarding integrating this with Wasp and Prisma, the knowledge sources don't provide specific details. However, Wasp does use Prisma under the hood for database interactions, and Prisma supports a wide range of databases including PostgreSQL, MySQL, SQLite, and SQL Server. If you're planning to use WordPress as a headless CMS, you might need to find a way to integrate the WordPress data with your Prisma setup.
For more detailed guidance on these topics, I would recommend checking out the Wasp documentation (https://wasp-lang.dev/docs), the Prisma documentation (https://www.prisma.io/docs/), and the WPGraphQL documentation (https://www.wpgraphql.com/docs/). You might also find it helpful to ask for advice in the Wasp community.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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?
@kapa.ai Once again, thank you very much for your response. You are correct in suggesting the use of another library or framework for the blog. In this case, let’s stop talking about WordPress. I’m familiar with Next and have worked with it a bit. I’ve handled its code. In this case, I know I have the option to download, search for, buy, or acquire certain programs or applications made with Next.js, through which I can have my blog. But here, a question arises where you should provide me with the information. In this case, on one side, as far as I know, I am running Wasp for the application. On the other side, I’m running Prisma for the database, although it’s not particularly related to what I’m telling you. I’m also running Astro for documentation and the blog. And in this case, I know that Wasp deploys in a very easy way. If, for example, I add something to my Wasp project that’s related to Next.js, which really has no relation to it—just as it doesn’t with Astro—will I still be able to follow the same steps to deploy it?
Let me check the knowledge base for you. One moment! :books:
----------------------
Based on the knowledge sources provided, Wasp does offer a single-command deployment through the Wasp CLI, which makes deploying your Wasp app quite straightforward. However, the sources do not provide specific information on how to deploy a Next.js app alongside a Wasp app.
In general, deploying a Next.js app would involve building the app into a production-ready format and then deploying it to a hosting provider that supports Node.js apps. This could be done separately from your Wasp app.
However, it's important to note that Wasp and Next.js are both high-level frameworks that are not typically used together. As mentioned in one of the Discord threads (https://discord.com/channels/686873244791210014/1221301825462866022), these frameworks sit on the same level and are not meant to be used together. You would typically choose one or the other for a given project.
If you're considering using Next.js for your blog and Wasp for the rest of your app, you might want to consider deploying them as separate apps. This would likely involve separate deployment processes for each app.
For more detailed guidance on deploying Next.js apps, you might find the Next.js deployment documentation (https://nextjs.org/docs/deployment) helpful. For deploying Wasp apps, you can refer to the Wasp deployment documentation (https://wasp-lang.dev/docs/advanced/deployment/overview).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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?
@kapa.ai Once again, thank you very much for your response. I feel like you’re becoming less shy each time, so please continue. If you don’t have the necessary documentation or knowledge base, feel free to give your own opinion. I’m just looking for ideas and not a definitive answer. With this in mind, I would like you to once again provide me with links, Discord channels, Twitter things, forums, or similar places where I could learn more about Astro to understand how it works and see if they have a community. If they do, please share it with me. I want to look for information, as I am a person very open to ideas and I like to gather all kinds of information. Thank you very much.
Let me check the knowledge base for you. One moment! :books:
----------------------
Based on the knowledge sources provided, you can find more information about Wasp and interact with its community through the following channels:
1. Wasp Documentation (https://wasp-lang.dev/docs): This is the official documentation for Wasp. It provides a comprehensive guide on how to use Wasp, from getting started to advanced topics.
2. Wasp Discord (https://discord.gg/rzdnErX): This is the official Discord server for Wasp. It's a great place to ask questions, share your experiences, and connect with other Wasp users.
3. Wasp Github (https://github.com/wasp-lang/wasp): This is the official Github repository for Wasp. You can find the source code, report issues, and contribute to the project here.
As for Astro, while the knowledge sources don't provide specific links to Astro's community or documentation, you can generally find these resources on the official Astro website or by doing a quick web search. Astro has a vibrant community and extensive documentation that can help you understand how it works and how to use it effectively.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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?
@kapa.ai
Thank you again for your information, and I wanted to mention that maybe I didn’t explain myself very well, and we might not have fully understood each other on my part. When I was asking about other data sources or knowledge bases regarding Astro, I wasn’t asking for specific external personal links. A few messages ago, you mentioned a Discord thread about something related to blogs and Astro documentation. That’s why I want you to gather and return to me that series of threads that might be related to the topics I’m mentioning to you.
Let me check the knowledge base for you. One moment! :books:
Wohooo @NEROX, you just became a Waspeteer level 2!
----------------------
Based on the knowledge sources provided, here are the relevant Discord threads that discuss Astro, blogs, and documentation:
1. OpenSaas Blog deployment > Answers Part 1 (https://discord.com/channels/686873244791210014/1204929776272281641): This thread discusses the deployment of a blog for OpenSaas, which is a template for Wasp. The discussion includes deploying the blog part of OpenSaas, which is a separate app, and the challenges encountered during the process.
2. OpenSaas Blog deployment > Answers Part 2 (https://discord.com/channels/686873244791210014/1204929776272281641): This thread continues the discussion on deploying the blog part of OpenSaas. It also discusses the integration of Google Analytics with Astro/Starlight.
3. OpenSaas Blog deployment > Answers Part 3 (https://discord.com/channels/686873244791210014/1204929776272281641): This thread further discusses the deployment of the blog part of OpenSaas and the integration of Google Analytics. It also mentions the addition of deployment docs for the blog.
4. OpenSaas Blog deployment > Answers Part 4 (https://discord.com/channels/686873244791210014/1204929776272281641): This thread discusses the integration of a blog into the main stack and the use of Astro for both docs and blogs.
5. OpenSaas Blog deployment > Answers Part 5 (https://discord.com/channels/686873244791210014/1204929776272281641): This thread confirms the recommendation of deploying the SaaS portion to Fly and the static blog/docs portion to Netlify.
6. Node version conflict between wasp and astro > Answers (https://discord.com/channels/686873244791210014/1209461309171830846): This thread discusses a node version conflict between Wasp and Astro during development.
7. seo and ssr > Answers Part 2 (https://discord.com/channels/686873244791210014/1219684155072184440): This thread discusses the use of Astro for docs and the possibility of using a different library or framework for the blog.
These threads provide a wealth of information on using Astro with Wasp, particularly for blogs and documentation. They also discuss some of the challenges and considerations when deploying these parts of an application.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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?
@kapa.ai Thank you again for your response. Don’t worry at all. Right now, this last response you’ve given me has just solved all my doubts related to this ticket. So, please close it yourself, or let me know, if you don’t have the ability to do so, how I should go about closing it.
Let me check the knowledge base for you. One moment! :books:
----------------------
I'm glad to hear that your questions have been answered! As an AI, I don't have the ability to close this ticket for you. However, you should be able to close it yourself. The exact steps may vary depending on the platform you're using, but generally, there should be an option to close or resolve the ticket somewhere on the page. If you're having trouble finding it, you might want to check the platform's help center or support resources for more information.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, 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 sir
Sorry to ask very strange things
Wohooo @NEROX, you just became a Waspeteer level 3!
It's totally up to you which blog you'd like to use. As you can see, it's just a separate app.
maybe nextjs would be a good fit for this. they have a bunch of blog templates you can choose from https://vercel.com/templates?type=blog