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
New "getting started" and reorganization of README.md #26
Conversation
fhocutt
commented
Aug 1, 2014
- Reorganized to put important information at the top
- Added more information about dependencies and repositories
- Added a "getting started" section with information on Maven
- Miscellaneous rewording, typo fixes, etc.
* Reorganized to put important information at the top * Added more information about dependencies and repositories * Added a "getting started" section with information on Maven * Miscellaneous rewording, typo fixes, etc.
Hmm do you think it is realy more important to know about the inner design goals and where to downloand binaries of jwbf as a code sample? I tried to organize the README.md more like an product page you can find in eCommerce: Amazon: ## Name of Product >>> author/manufacturer/... - [product image] product details README.md ## Name of Product >>> short description / status badges - [code sample] product details ... Dependecies/Binaries, API details, JavaDocs, Refs., ... |
@eldur: I am approaching the README structure from the perspective of someone who is not sure if or how they want to use this framework instead of another. If it is confusing, they will probably give up and go find something that appears more likely to work for them. So, the structure I aimed for without the design goals:
Does that make sense? |
* Revised initial "about jwbf"-type statement with more detail and reason to use jwbf * Removed design goals; these will be added to developerDocs * Removed links to maven-metadata.xml files * Clarifications in Getting started and Dependencies
TODO: add a table of contents as at the beginning of this document: https://raw.githubusercontent.com/zachallaun/datomic-cljs/master/README.md |
My structure design is written from a perspective of an experienced developer. Someone with an idea to work or to change mediawiki based content automatically. The most interesting part for such a person, is IMHO, partially the point you've named "Code uses idioms appropriate to the language the library is written in" so I would prefer a code example at the begining, like a teaser. Dependecy managment, remote respositories, where to download binaries ... are details, because they are optional to check api readbility. Your structure makes sense, if someone desides that the code example looks interesting and want to know more details. Compare with: http://junit.org/ What do you think about?:
|
* Added table of contents with internal links * Removed Scala section (may add it to developerDoc.md) * Simplified some wording * Readability tweaks * Moved code sample earlier
I think I've addressed all comments--how does it look now? |
Fine. I'll squash merge your 3 changes to one (like gerrit code review) and trim the trailing whitespaces. I'll use this squashed commit message. ok?
|
Sounds good. Thanks very much! On Tue, Aug 5, 2014 at 12:21 PM, Loki notifications@github.com wrote:
|
~ Reorganized to put important information at the top + Added more information about dependencies and repositories + Added a "getting started" section with information on Maven ~ Revised initial "about jwbf"-type statement with more detail and reason to use jwbf - Removed design goals; these will be added to developerDocs ~ Clarifications in Getting started and Dependencies + Added table of contents with internal links - Removed Scala section (may add it to developerDoc.md) ~ Miscellaneous rewording, typo fixes, etc. ~ Simplified some wording ~ Readability tweaks Task: #26
merged |
Thanks! |