Introduction
Based on the research, interviews, and ideas, I created a list of functionalities that are most realistic to achieve for this project. Each functionality has also been prioritized using the MoSCoW method.
Abstract
The functionalities list is split into Must Have, Should Have, and Could Have features, which gives a clear overview for the development of the tool. The Must Have features include: generating a theme page based on a prompt, generating images for the theme page, and publishising the theme page to AWS. These are most important for the core functionality of the tool.
The Should Have features improve the tool’s usability. They include the ability to regenerate sections and images based on prompts, generate theme pages based on templates, set a tone of voice for the content, and integrate with Magento and Storyblok.
The Could Have features are nice to have but not essential. They include setting a styling framework (e.g. Tailwind), and the ability to publish theme pages to Magento and Storyblok. These features would further improve the tool's functionality and user experience but are not critical.
Conclusion
By splitting up the functionalities using the MoSCoW method I made sure that there is a good approach to the tool's development, by focussing first on the core features that are most important. The Should Have and Could Have features help to further develop the tool after the core features have been created.