We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How can we standardize the /source/wp-content/... folder structure?
/source/wp-content/...
Could it be something that's automated, instead of manually setup? If not, maybe have a README describe the process, and enforce it w/ a linter?
README
Otherwise I worry we'll end up in a few years with inconsistent folder structures, etc. Maybe it's not worth it, though?
The text was updated successfully, but these errors were encountered:
Documenting the desired folder structure in the readme for this repo sounds like a good idea. Enforcing with a linter seems a bit overkill to me.
Sorry, something went wrong.
That's fair. I'd worry that folks (or our future selves) won't think to look in the readme, but I don't feel strongly.
No branches or pull requests
How can we standardize the
/source/wp-content/...
folder structure?Could it be something that's automated, instead of manually setup? If not, maybe have a
README
describe the process, and enforce it w/ a linter?Otherwise I worry we'll end up in a few years with inconsistent folder structures, etc. Maybe it's not worth it, though?
The text was updated successfully, but these errors were encountered: