Framework for handling specs and proposals. #7
Conversation
This file contains hidden or 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
simensen
added a commit
that referenced
this pull request
Jul 30, 2013
Framework for handling specs and proposals.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds the following to the Stack front page below the community middlewares section:
http://d.pr/i/hhKd
Individual proposals end up looking like this:
http://d.pr/i/Vnim
This PR includes proposal 1 which we can use to further flesh out how we want to handle proposals along with 2 (Authentication) and 3 (Authorization) which are based on my gist minus the configuration stuff (firewalls and acls).
I think that this could work for now but I don't know how long it will work. The format is pretty nice (simple markdown files) but Sculpin isn't doing any work for us. I'm anxious to get it going, though, so I wanted to just try and get things rolling "the easy way" for now.
The front page is becoming a burden. I think that very soon we might consider a redesign. Mostly, I think that navigation can be added and start moving a bunch of the content to specific pages ( /toolbox/, /middlewares/, /specs/, etc ) instead of trying to have it all on the front page.