This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add project scaffolding #21
Comments
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) |
I am in favor of this 👍 |
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 |
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 |
btw, I created a standalone tool to do this - https://dev.to/azure/scaffolding-static-web-apps-4p97 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the solution you'd like
As a user I'd like to be able to use
swa
to scaffold a new project structure.Example: running
swa init
should produce the following project structure:Other options/questions:
api
folder?The text was updated successfully, but these errors were encountered: