[ci skip] First draft of guides #189
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are 3 types of people who will want to interact with sprockets, asset processing framework developers, library developers who want to extend sprockets, and end users who will create and modify assets that get compiled using sprockets. The current documentation is all in the README or at the method level. The README does not make a distinction between these roles, so it makes determining what docs are applicable to your specific task. For that purpose I plan on splitting up documentation into different roles, and publishing these in the `guides/` directory.
|
|
schneems
added a commit
that referenced
this pull request
Dec 3, 2015
[ci skip] First draft of guides
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are 3 types of people who will want to interact with sprockets, asset processing framework developers, library developers who want to extend sprockets, and end users who will create and modify assets that get compiled using sprockets. The current documentation is all in the README or at the method level. The README does not make a distinction between these roles, so it makes determining what docs are applicable to your specific task. For that purpose I plan on splitting up documentation into different roles, and publishing these in the
guides/directory.