We are making a static website with HTML, CSS, Bootstrap and javascripts. Later we have to move this static site to AEM. we are asking that will it be as simple as we do it in WordPress or Drupal where you easily move a static site to CMS? Or no, in such CMS it will be very different. What considerations to keep in mind during static site development knowing later it has to move to AEM"
Solved! Go to Solution.
Views
Replies
Total Likes
Hey,
AEM basic concept works with templates and components. As long as you can break you static website content into components which are modular and independent, we can easily move them to AEM.
I wouldn't trying out a new CMS if its a temporary static site, you can easily deploy a HTML CSS/JS in a vercel like container.
AEM Front end is ultimately structured as ui.frontend. You can take a look at the structure at [1] and our archetypes has an option to integrate with storybook. If you manage your UI components with storybook for your temporary solution, the migration is going to be seamless.
Good luck!
Hey,
AEM basic concept works with templates and components. As long as you can break you static website content into components which are modular and independent, we can easily move them to AEM.
I wouldn't trying out a new CMS if its a temporary static site, you can easily deploy a HTML CSS/JS in a vercel like container.
AEM Front end is ultimately structured as ui.frontend. You can take a look at the structure at [1] and our archetypes has an option to integrate with storybook. If you manage your UI components with storybook for your temporary solution, the migration is going to be seamless.
Good luck!