reinvent the contribution section #3
Closed
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
I teamed up with ermouth <[email protected]> (@ermouth) and Nolan Lawson <[email protected]> (@nolanlawson) to highlight the many different ways you can get involved with CouchDB. The new section gives a quick overview where and how you can get involved with CouchDB.
|
the workflow so far was building the site on the local machine and the committing everything. Maybe the new git toolchain can automate things for us, but don’t worry about it for now. LGTM, feel free to merge! :) |
|
merged as f750d15 |
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.
I teamed up with ermouth [email protected] (@ermouth) and
Nolan Lawson [email protected] (@nolanlawson) to highlight
the many different ways you can get involved with CouchDB.
The new section gives a quick overview where and how you can get
involved with CouchDB.
PS: unsure if we have to checking the generated CSS (as you see it is currently since the git migration) - this is a leftover after the svn -> git migration and I will ask how the deployment works now