You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless it's for setting up the SWA config file (per #20) I feel like the implementation effort would greatly outweigh the user value.
We have a lot of permutations that we'd need to support, first there's the client framework (React, Vue, Angular, Svelte, Vanilla JS, Blazor), then whether you want an API, and if so, what's the API written in (JS, TypeScript, C#, F#, Python). Then there's static site generators (VuePress, Gatsby, Hugo, Jekyll, Nuxt) that would also be options.
Thinking about this - would it be possible to use the GitHub repo templates to generate a project? That would make it easier to have the permutations handled (just create a new template)
We need to think about what problem this addresses. Is the goal to prescribe an opinionated folder structure? GitHub templates might be a good idea but there's a maintenance overhead to them. How many people would find them useful?
We'll be doing some research studies in the next few months around the CLI. We'll include the getting started experience. /cc Reshmi Sriram (@Reshmi-Sriram)
We need to think about what problem this addresses. Is the goal to prescribe an opinionated folder structure? GitHub templates might be a good idea but there's a maintenance overhead to them.
The goal would be to give people a starting point for creating a project, whether they are experienced with SWA or it's their first time. I think of it in a similar manner to someone using func init to setup the starting point for a Functions app.
Activity
aaronpowell commentedon Nov 5, 2020
Unless it's for setting up the SWA config file (per #20) I feel like the implementation effort would greatly outweigh the user value.
We have a lot of permutations that we'd need to support, first there's the client framework (React, Vue, Angular, Svelte, Vanilla JS, Blazor), then whether you want an API, and if so, what's the API written in (JS, TypeScript, C#, F#, Python). Then there's static site generators (VuePress, Gatsby, Hugo, Jekyll, Nuxt) that would also be options.
aaronpowell commentedon Aug 18, 2021
Thinking about this - would it be possible to use the GitHub repo templates to generate a project? That would make it easier to have the permutations handled (just create a new template)
manekinekko commentedon Aug 18, 2021
I am in favor of this 👍
anthonychu commentedon Aug 21, 2021
We need to think about what problem this addresses. Is the goal to prescribe an opinionated folder structure? GitHub templates might be a good idea but there's a maintenance overhead to them. How many people would find them useful?
We'll be doing some research studies in the next few months around the CLI. We'll include the getting started experience. /cc Reshmi Sriram (@Reshmi-Sriram)
aaronpowell commentedon Aug 23, 2021
The goal would be to give people a starting point for creating a project, whether they are experienced with SWA or it's their first time. I think of it in a similar manner to someone using
func initto setup the starting point for a Functions app.aaronpowell commentedon Nov 16, 2021
btw, I created a standalone tool to do this - https://dev.to/azure/scaffolding-static-web-apps-4p97