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
Would it be better if the template provides with a functional website from the beginning? Without requiring creating/moving files (e.g. config.toml) and with the initial fake data. So as soon as the repository is created based on this template, the workflow builds the website and it is there.
The text was updated successfully, but these errors were encountered:
I think it is fine to keep the theme within the same repo. I wonder if it would be better to include it in the template as is in the repo, and not like a git sub-module- It can get confusing for more entry-level users, if they want to make some change in the template and they find this link instead of files.
Would it be better if the template provides with a functional website from the beginning? Without requiring creating/moving files (e.g. config.toml) and with the initial fake data. So as soon as the repository is created based on this template, the workflow builds the website and it is there.
The text was updated successfully, but these errors were encountered: