Skip to content
New issue

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

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split the API out into its own github repo? #145

Closed
nelsonic opened this issue Apr 22, 2015 · 3 comments
Closed

Split the API out into its own github repo? #145

nelsonic opened this issue Apr 22, 2015 · 3 comments
Labels
API chore a tedious but necessary task often paying technical debt discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! priority-4 Deprioritised until all other higher priority items are complete.

Comments

@nelsonic
Copy link
Member

While we do want to encourage people to have "_full-stack_" skills, we should acknowledge (and embrace) the fact that many of the best developers got their expert status by focussing on one aspect of development. Jeffry Zeldman is not known for his scalable back-end code, nor Pedro Teixeira for his slick UX...

I propose we split out the "Back-end" from the "Front-end" to encourage contributions from people who have Zero interest in building UI or Servers respectively. #discuss
@nelsonic nelsonic added help wanted If you can help make progress with this issue, please comment! discuss Share your constructive thoughts on how to make progress with this issue API chore a tedious but necessary task often paying technical debt NiceToHave labels Apr 22, 2015
@nelsonic
Copy link
Member Author

The (obvious?) side benefit is that people who are only interested in developing front-end are not forced to run the back-end tests on pre-commit...! 👍

@iteles
Copy link
Member

iteles commented Apr 23, 2015

Seems like a sensible idea, we just need to make sure we update the readmes 👍

@nelsonic nelsonic mentioned this issue Apr 25, 2015
Merged
@iteles iteles added priority-4 Deprioritised until all other higher priority items are complete. and removed NiceToHave labels Nov 12, 2019
@nelsonic
Copy link
Member Author

nelsonic commented May 9, 2020

I've changed my mind on this.
I very much want to use Content Negotiation https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation to determine if the request expects HTML or JSON
then have a single render function that does the determining & rendering the data.
See: #273

@nelsonic nelsonic closed this as completed May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API chore a tedious but necessary task often paying technical debt discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! priority-4 Deprioritised until all other higher priority items are complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nelsonic @iteles