7 Replies
Hi @ArDev. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The OpenSaas blog is currently built with Starlight, an Astro template. To change the style of the blog, you would need to modify the Starlight template. However, the specific details on how to do this are not provided in the knowledge sources.
There is an ongoing discussion on GitHub about revamping the blog, possibly moving it out of Docusaurus and into a headless CMS, which would provide more flexibility for styling and posting articles. You can follow this discussion here (https://github.com/wasp-lang/wasp/issues/855).
For more specific guidance on styling, you may want to refer to the Astro or Starlight documentation, or ask for help in the Wasp community on Discord.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, 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 how to change the style of the blog?
Let me check the knowledge base for you. One moment! :books:
----------------------
To change the style of the blog in a Wasp project, you would typically modify the CSS associated with the blog components. However, the exact details on how to do this are not provided in the knowledge sources.
There is a closed GitHub issue that suggests putting a contrasting box around the blog intro/CTA part to distinguish it visually from the content. This would involve modifying the CSS of the blog component. You can see this issue here (https://github.com/wasp-lang/wasp/issues/462).
There is also an open GitHub issue discussing the possibility of rearranging the blog in Docusaurus or revamping it to a headless CMS. This could potentially involve significant changes to the blog's style. You can see this issue here (https://github.com/wasp-lang/wasp/issues/855).
For more specific guidance on styling, you may want to refer to the Wasp documentation or ask for help in the Wasp community on Discord.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, 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?
ok cool done
@kapa.ai when deploying to netlify, should i create a new site for my blog? then how can i connect with my og website? through subdomain?
Let me check the knowledge base for you. One moment! :books:
----------------------
Yes, when deploying your blog to Netlify, you can create a new site specifically for your blog. This is because Netlify excels at hosting static sites, which is what your blog would be if it's built with Astro, as suggested in the OpenSaas Discord thread (https://discord.com/channels/686873244791210014/1204929776272281641).
To connect your blog with your original website, you can indeed use a subdomain. For example, if your main website is at
<https://example.com
,> you could host your blog at <https://blog.example.com
.>
To do this, you would need to configure your DNS settings to point the subdomain to your Netlify site. You can find more information on how to do this in the Netlify documentation (https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/#configure-a-subdomain).
Once your blog is deployed and the DNS is configured, you should also set the baseDir
option in your Wasp app's configuration to the path of your blog, and make sure the WASP_WEB_CLIENT_URL
environment variable includes that base directory. This is explained in the Wasp documentation (https://wasp-lang.dev/docs/project/client-config#base-directory).
Here's an example of how to set the baseDir
option:
And here's how to set the WASP_WEB_CLIENT_URL
environment variable:
Remember to replace "blog"
and "<https://example.com/blog"
> with your actual blog path and URL.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, 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 how to get blogs indexxed on google? i already have one property for my main domain but how do i do it for subdomain and add that?
Let me check the knowledge base for you. One moment! :books:
----------------------
To get your blog indexed on Google, you need to submit your blog's sitemap to Google Search Console. Here are the steps:
1. Create a new property in Google Search Console for your blog's subdomain. For example, if your blog is at
blog.example.com
, you would create a new property for blog.example.com
.
2. Generate a sitemap for your blog. If your blog is built with Astro, it might not generate a sitemap automatically. You might need to use a plugin or a third-party service, or create the sitemap manually.
3. Submit the sitemap to Google Search Console. In the new property you created for your blog, go to 'Sitemaps' and enter the URL of your sitemap, then click 'Submit'.
4. Google will start crawling your blog based on the sitemap. It might take some time for your blog to appear in search results.
Remember, having a sitemap and submitting it to Google Search Console doesn't guarantee that your blog will be indexed or rank high in search results. There are many factors that Google's algorithm takes into account, such as the quality of the content, the structure of the website, and the number and quality of other websites linking to it.
For more information on how to get your website indexed by Google, you can refer to Google's Search Console Help (https://support.google.com/webmasters/answer/6259634?hl=en).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, 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?