Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Merge in Connect Middleware documentation #13

Closed
ForbesLindesay opened this Issue Aug 1, 2012 · 5 comments

Comments

Projects
None yet
3 participants
Contributor

ForbesLindesay commented Aug 1, 2012

Would it be OK to merge in the Middleware documentation for Connect into the API Docs as an extra section?

Owner

tj commented Aug 1, 2012

I plan on adding some of that to the guide part, the connect docs definitely suck right now, we could always duplicate this site and make the connect one better

Contributor

ForbesLindesay commented Aug 1, 2012

I personally would much prefer all the api docs I need to be in one place (on expressjs). With the old site I always used expressjs whenever I needed to know the exact name of body parser, static etc. middleware.

The guide part definitely needs some more content. I also think we should have something more obvious on the home page as to what to do next. A big link to guide and another to api would be nice. perhaps even include the hello world sample (we used to do that on the old site?)

Also, github link should be really prominent on every page, so should probably go in the main nav.

Owner

tj commented Aug 1, 2012

yeah im down, it would make a bit more sense to have the api reference for connect as its own site, but the guide for express can have pretty much whatever we want

Contributor

ForbesLindesay commented Aug 1, 2012

I think the best bet would be to duplicate the same content on express and consolidate docs. When I was new to express and connect, I would've much preferred not to think about the difference between what comes from express and what comes from connect, much easier to see everything as being from express. We should think about writing the docs so it would be easy to share docs between the two sites though.

Member

jonathanong commented Dec 10, 2013

how about "Connect Middleware" and "Express API" sections? i'd very much like to move connect middleware here. i don't really see the point of having two documentation sites.

@hacksparrow hacksparrow pushed a commit that referenced this issue Nov 5, 2015

@alanhoff alanhoff Merge pull request #13 from gidenilson/gh-pages
Translation into Brazilian Portuguese
8afe543
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment