expand_less








Some of this will be changing. See [[RESTful Web API]].

we need to get rid of this hideous card and make sure all the key points are covered in [[RESTful Web API]] or elsewhere.
--[[Ethan McCutchen]].....2013-08-08 20:27:56 +0000


"RESTful Web API" - just the name, and the way that page is now - seems likely to scare off some non-techies who are perfectly capable of constructing URLs. Are you okay with keeping a page like this, and if so what kinds of changes (to name and/or content) would you like to see?
--[[John Abbe]].....2013-08-08 22:12:07 +0000


Well, DRY doesn't mean we can't have multiple names for the same thing. We can just include the RESTful Web API stuff in a card with a less wonky name (but a wieldier name than this one).
 
I cleaned it up and corrected it so that it's not a huge liablility, but in general we want one canonical page for a given concept.
--[[Ethan McCutchen]].....2013-08-09 15:40:53 +0000


I'm fine with one page, just want it to be named, and content to start with, stuff that will be approachable by less-geekier folks.
--[[John Abbe]].....2013-08-09 17:08:25 +0000


What do you think of merging the two into a card simply named "web addresses" ? Start with the stuff telling non-geeks how to construct addresses, and later get into REST, POST, PUT, DELETE, etc.?
--[[John Abbe]].....2013-09-15 09:45:31
+0000