Our AEM client is having maven project which is not using the AEM Archetype setup. The project structure is different from aem archetype and they have plan in future to refactor the project to match with aem archetype project. We have requirement to integrate react application with AEM SPA editor. We are following the steps mentioned in wknd tutorial (where this tutorial used aem archetype) https://experienceleague.adobe.com/docs/experience-manager-learn/spa-react-tutorial/create-project.h... , and following the steps to map the aem components from react but we are not able to achieve it. So I wanted to get confirmation, if the SPA editor setup will work only for aem archetype project?
AEM Project Archetype - simple starting point or basis for starting an aem project. And it will be provided with good best practices and basic standards to easily start your implementation. The archetype is very flexible and can be customized to your needs using several options. All modules created are to organize dependencies in better way and have clean separation of package deployment.
Coming to your question- Do we need AEM Archtype project as mandatory - Answer - No.
But - can you please give more details about - what you are not able to achieve with Archtype?
following the steps to map the aem components from react but we are not able to achieve it. - are you getting any errors? what functionality you are not able to achieve ? - These details will help to resolve the issue