Endpoint Guide

[lancehalvorsen]

We certainly need one.

[gjaldon]

I'd like to help out with this too, @lancehalvorsen. Just let me know which one you prefer I take on.

[lancehalvorsen]

Thanks for this as well, @gjaldon! Much appreciated.

This guide would be fine to work on, if it interests you. A Heroku deployment guide would be great as well. This would be a new file.

[willykaram]

@gjaldon @lancehalvorsen I just wanted to check on the status of the Endpoint Guide. It looks like the Heroku Deployment Guide is done, but we didn't tackle the endpoint guide yet. I can create a proposed draft this week if helpful, but don't want to duplicate any other work if others or @gjaldon are already working on it.

[lancehalvorsen]

As far as I know, nobody is currently working on this. It would be fabulous if you wanted to take this on @willykaram!

[dmitrinesterenko]

I'm taking this one on.

[willykaram]

@dmitrinesterenko thx, that would rock!! As discussed, ideally we can incorporate some of that into the the diagram for #118 and an accompanying guide.

[dmitrinesterenko]

What would be the appropriate name for this guide? I.e. C_controllers. E_endpoints? There is an implied order in the selection of the title letters and I'm interested in where the endpoints would fall.

[willykaram]

@dmitrinesterenko I wasn't sure of which letter to use for the naming either, so for this issue #365 & related PR #465 I just used "X" as the alpha prefix. That could likely work for now, and then @lancehalvorsen for @jeregrine could rename it appropriately.

If there's a clear strategy/approach for the naming, then perhaps we could update the Contributing to the Phoenix Guides and the root READ.me file

[jeregrine]

I think the numbers are sort of an informal ordering, I wasn't around for there creation.

[xuebingli]

@dmitrinesterenko has created the guide #567

[chrismccord]

We can work the endpoint discussion when talking about routing and the plug pipeline