-
Notifications
You must be signed in to change notification settings - Fork 4
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
Make cmd tutorial for pkg template setup easier to find #21
Comments
My main blocker here is that I felt a tension between having the README as a template for the packages vs having a README talking about packagetemplate itself. I've considered this a bit more and my conclusion is there is no probably problem to talk about packagetemplate in The only small downside is that What do you think? |
I think the (necessary) complexity of packagetemplate now means that it's better to use the 'Use as template' fuctionality than try to implement it all oneself, whether from the command line or otherwise. So I would actually be in favour of documenting the ingredients that have gone into it somewhere, perhaps in a technical appendix to Blueprints, and then actually removing this cli tutorial. As @jamesmbaazam says it's difficult to find anyway. The Edit: I see that the cli steps apart from |
Yes, I see the question more as: is the documentation in the wiki discoverable enough or should it be made more visible on the README? Beyond the specifics of what the documentation contains. |
I suppose having this information in the Readme could help external devs who like the setup of Epiverse packages and want to copy it but are not that familiar with using GH templates. Not sure how applicable that is at the moment. |
The tutorial that @pratikunterwegs kindly wrote to set up the package template using the terminal is very useful but almost invisible and hard to find. Maybe, it might help to add a link in the README for visibility.
The text was updated successfully, but these errors were encountered: