I was thinking "how if the content is moved to cms?", It is because this website is still using static content data that written directly into *.vue files. If there's a things to be editted, I must be openning code editor, searching for the file, formatting file, and make a new commit into master branch. However, this cycle is complicated. I just thinking if should I move any contents in this website to CMS?
Moving to CMS gives you lot adventages. It allows us to edit content directly in the CMS and any published changes will be applied to the website automatically, without any changes with source code. This is because our website consumes and fetch the content from the CMS.
And this is a more-useful adventage, It allows authenticated user to make changes to the contents. I think it will be great if Choco (herself) can make changes to the contents too. So it's like a "Editor" role that allowed to make any changes to contents.
What CMS? I don't know. There's a lot CMS-provider out there. I'm just thinking about it right now.
I have 2 experiences in using CMS
-
Using Strapi's CMS
It allows us to self-host the CMS on our local machine or our cloud. But some troubles in using this CMS is limitance in cloud usage. This requires a node-server to be running 24/7, and I am a free user of any services here. When I'm using Railway, I have an limit 20 days free quota. So this CMS will be shutted down when it reached it's limit and the client will stopped working too. I have to wait until 1st day in month to have it cycle resetted and running again.
-
Using Sanity's CMS
It allows us to edit the content in Studio-separated application and the whole contents in their clouds. These things eliminates previous problems in using Strapi's but, I don't know if this CMS does have and allows us to create multiple user and roles. I will have to check it later, and any updates will be announced here. Thanks.
I was thinking "how if the content is moved to cms?", It is because this website is still using static content data that written directly into
*.vuefiles. If there's a things to be editted, I must be openning code editor, searching for the file, formatting file, and make a new commit intomasterbranch. However, this cycle is complicated. I just thinking if should I move any contents in this website to CMS?Moving to CMS gives you lot adventages. It allows us to edit content directly in the CMS and any published changes will be applied to the website automatically, without any changes with source code. This is because our website consumes and fetch the content from the CMS.
And this is a more-useful adventage, It allows authenticated user to make changes to the contents. I think it will be great if Choco (herself) can make changes to the contents too. So it's like a "Editor" role that allowed to make any changes to contents.
What CMS? I don't know. There's a lot CMS-provider out there. I'm just thinking about it right now.
I have 2 experiences in using CMS
Using Strapi's CMS
It allows us to self-host the CMS on our local machine or our cloud. But some troubles in using this CMS is limitance in cloud usage. This requires a node-server to be running 24/7, and I am a free user of any services here. When I'm using Railway, I have an limit
20 days freequota. So this CMS will be shutted down when it reached it's limit and the client will stopped working too. I have to wait until 1st day in month to have it cycle resetted and running again.Using Sanity's CMS
It allows us to edit the content in Studio-separated application and the whole contents in their clouds. These things eliminates previous problems in using Strapi's but, I don't know if this CMS does have and allows us to create multiple user and roles. I will have to check it later, and any updates will be announced here. Thanks.