[Task] Create an azd template for setup of Strapi resources about contoso-real-estate HOT 2 CLOSED

Now that scenario 3 has been implemented, I've pondered how a template could be made for it.

Strapi has a template feature for setting up new projects, but it works on a specific structure of what files exist where. The other alternative is that Strapi has starters, which use templates but are more complete applications (so combine something like Next.js + Strapi).

On the other hand you have azd templates, which are really just taking an existing GitHub repo, cloning it and pushing to Azure using azd up. These need to be more structured like a standard repo, so could be similar to the starters concept from the Strapi CLI.

Then there's the idea proposed in the initial description, don't have Strapi in the azd template repo, just the infra/azure.yaml/etc. files so you can azd-ify an existing repo. This would essentially be using the Make your project azd compatible approach, but some how make it easier to import the various files needed, rather than copy/paste them from docs/online.

Here's my pro/con list for the approaches:

• Create a Strapi template or starter
  • Pros: integrate with the standard Strapi workflow, working application immediately
  • Cons: Requires shipping Strapi "in the box", thus having to worry about upgrade/maintenance of packages
• Create an azd template
  • Pros: Clearer ties to azd and that workflow, working application immediately
  • Cons: Foreign to someone who's familiar with Strapi and bootstrapping projects, requires shipping Strapi in the box
• azd-only files template
  • Pros: Don't have to maintain the Strapi instance in the template, allows adding it into existing project
  • Cons: Doesn't appear that azd has direct support for this workflow at present

from contoso-real-estate.

It looks like the template for azd and Strapi has already been created. Can we close this issue? cc @sinedied

from contoso-real-estate.