-
-
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
Reword many fields, add explanations, move fields into different sections. #5
Conversation
<div id="install_fields"> | ||
<ol> | ||
<ol> If this mod requires other mods to be installed alongside it, use Relationships.<b>Do not use install instructions to install multiple mods.</b> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line in particular probably needs an edit since I imagine this text should be inside some kind of element.
edited to #9 |
# Conflicts: # static/index.html
@@ -147,42 +147,48 @@ | |||
</li> | |||
<li> | |||
<label>KSP-Version<br /><input type="text" id="ksp_version" size="40" /></label> examples: <code>==1.0</code> or <code><=1.1>=1.0.3</code> | |||
<br /> | |||
<small>While not technically mandatory, not providing this field is considered bad practice.</small> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth noting that if/when KSP-CKAN/CKAN#1742 is merged this will be technically mandatory.
A lousy title and commit message, this is just a bunch of cosmetic changes. Some things reworded to use CKAN nomenclature (like relationships). Many fields have increased explanation of what's expected. "KSP_version" moved up into "mandatory" (KSP-CKAN/CKAN#1742 for more). Strict version matching moved into "advanced". And much more.
Closes #9