Skip to content
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

Documentation: Add quickstart guide to the yaml #91

Open
sils opened this issue Aug 25, 2018 · 3 comments
Open

Documentation: Add quickstart guide to the yaml #91

sils opened this issue Aug 25, 2018 · 3 comments

Comments

@sils
Copy link

sils commented Aug 25, 2018

The docs give an intro to the command line and then immediately talk about inheritance of yamls without introducing them or the most important keys first, I think that'd help me and others a lot.

@chfw
Copy link
Member

chfw commented Aug 25, 2018

Your feedback is appreciated. I will write down more docs. Stay tuned. I will request your review on my docs commit.

@chfw
Copy link
Member

chfw commented Aug 25, 2018

instead of putting you on wait, here is a brief info:

moban itself has requirements on the keys in the yaml file. The principle: keys in yaml file serve the data dict, with which jinja2 renders the templates. So, the keys are buried and scattered inside the templates. No reference in templates, No keys.

The keys in yaml file become compulsory when templates uses them. As of now, pypi-mobans are the default templates for python packages, hence it does require compulsory keys so it would function. And I should outline them for reference. But if we step back once, if you do not use pypi-mobans, you are not obliged to declare the keywords. And if you write your own templates(mobans), such as "My first {{thing}}", you may want to put thing in your yaml file.

Why would one need to override? The use case: in an organisation, there are more than one repo and all of them share similar texts: organisation, mission, but differ in details: such as author, description, version, copyright. So in the default yaml file, the organisation may want to put all initial values and each repo can override the default yaml file.

@PrajwalM2212
Copy link
Collaborator

@sils Thanks for requesting this.
@chfw Thanks for explaining this in the comment. I too think that more documentation would surely benefit anybody viewing the project.

@jayvdb jayvdb added this to the 0.5.0 milestone Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants