The docs site currently hosts a number of assets for both light and dark theme, but they are embedded in the site itself without a consistent naming convention or management system. As we intend to introduce more technical diagrams, branded graphics, and other related assets, we need to transition to a CMS to better manage these assets.
Problem
The current implementation of the assets on the docs site makes it difficult to manage and organize them efficiently. We lack a consistent naming convention, and this can lead to difficulty finding specific assets. Additionally, with more assets expected to be added to the site in the future, the current approach will become unscalable.
Proposed Solution
We propose leveraging an open-source CMS called Strapi to improve our management of assets for not only the docs site but also for future blogs, websites, and marketing materials.
Benefits
By transitioning to a CMS, we can take advantage of several benefits:
Efficient management of assets
Easy organization and retrieval of assets with a consistent naming convention
Scalability for future growth in assets
Improved consistency and branding across all our marketing materials
Implementation details
To implement this solution, we suggest the following steps:
Create and organize asset collections according to our needs.
Integrate the out-of-the-box API for all assets on the docs site.
Alternative CMS
Although this task outlines the usage of Strapi, we can certainly use an alternative CMS if we find one that better suits our needs. However, based on the research, we have chosen Strapi due to the following factors:
Free for self-hosted version
Open source
Easy integration
Easy content setup and categorization
Easy to follow UI for admins
By implementing a CMS like Strapi, we can ensure that our assets are efficiently managed and organized, leading to more consistent and effective content materials across all projects.
Overview
The docs site currently hosts a number of assets for both light and dark theme, but they are embedded in the site itself without a consistent naming convention or management system. As we intend to introduce more technical diagrams, branded graphics, and other related assets, we need to transition to a CMS to better manage these assets.
Problem
The current implementation of the assets on the docs site makes it difficult to manage and organize them efficiently. We lack a consistent naming convention, and this can lead to difficulty finding specific assets. Additionally, with more assets expected to be added to the site in the future, the current approach will become unscalable.
Proposed Solution
We propose leveraging an open-source CMS called Strapi to improve our management of assets for not only the docs site but also for future blogs, websites, and marketing materials.
Benefits
By transitioning to a CMS, we can take advantage of several benefits:
Implementation details
To implement this solution, we suggest the following steps:
Alternative CMS
Although this task outlines the usage of Strapi, we can certainly use an alternative CMS if we find one that better suits our needs. However, based on the research, we have chosen Strapi due to the following factors:
By implementing a CMS like Strapi, we can ensure that our assets are efficiently managed and organized, leading to more consistent and effective content materials across all projects.