Skip to content

Commit 72936ab

Browse files
committed
new api creation resources
1 parent 0670005 commit 72936ab

File tree

6 files changed

+57
-37
lines changed

6 files changed

+57
-37
lines changed

all.html

Lines changed: 20 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3065,19 +3065,6 @@ <h2>Hosted API testing services</h2>
30653065
<h2>API creation resources</h2>
30663066
<ul>
30673067
<li>
3068-
<p><a href="http://www.narwhl.com/">NARWHL</a> is a practical API design site for
3069-
developers confused about what is appropriate for RESTful APIs.</p>
3070-
</li>
3071-
<li>
3072-
<p>This <a href="https://github.com/interagent/http-api-design">API Design Guide</a>
3073-
is based on Heroku's best practices for the platform's API.</p>
3074-
</li>
3075-
<li>
3076-
<p><a href="https://18f.gsa.gov/">18F</a>'s
3077-
<a href="https://github.com/18f/api-standards">API standards</a> explains the details
3078-
behind their design decisions on creating modern RESTful APIs.</p>
3079-
</li>
3080-
<li>
30813068
<p><a href="http://pydanny.com/choosing-an-api-framework-for-django.html">Choosing an API framework for Django</a>
30823069
by <a href="https://twitter.com/pydanny">PyDanny</a> contains questions and insight
30833070
into what makes a good API framework and which one you should currently
@@ -3094,6 +3081,25 @@ <h2>API creation resources</h2>
30943081
traps.</p>
30953082
</li>
30963083
<li>
3084+
<p>Versioning of RESTful APIs is a difficult and contentious topic in the
3085+
web API community. This two-part series covers
3086+
<a href="http://urthen.github.io/2013/05/09/ways-to-version-your-api/">various ways to version your API</a>
3087+
and <a href="http://urthen.github.io/2013/05/16/ways-to-version-your-api-part-2/">how to architect a version-less API</a>.</p>
3088+
</li>
3089+
<li>
3090+
<p><a href="http://www.narwhl.com/">NARWHL</a> is a practical API design site for
3091+
developers confused about what is appropriate for RESTful APIs.</p>
3092+
</li>
3093+
<li>
3094+
<p>This <a href="https://github.com/interagent/http-api-design">API Design Guide</a>
3095+
is based on Heroku's best practices for the platform's API.</p>
3096+
</li>
3097+
<li>
3098+
<p><a href="https://18f.gsa.gov/">18F</a>'s
3099+
<a href="https://github.com/18f/api-standards">API standards</a> explains the details
3100+
behind their design decisions on creating modern RESTful APIs.</p>
3101+
</li>
3102+
<li>
30973103
<p>"<a href="https://medium.com/@zwacky/design-a-beautiful-rest-api-901c73489458">Design a beautiful REST API</a>"
30983104
reviews common design decisions regarding endpoints, versioning, errors and
30993105
pagination. There is also a
@@ -3829,6 +3835,7 @@ <h1>Change Log</h1>
38293835
<h2>2014</h2>
38303836
<h3>October</h3>
38313837
<ul>
3838+
<li>More API creation resources.</li>
38323839
<li>Merged a bunch of pull requests that cleaned up spelling and grammar
38333840
errors. Thank you contributors!</li>
38343841
<li>Adding new Django 1.7-specific resources section on the Django page.</li>

api-creation.html

Lines changed: 19 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -104,19 +104,6 @@ <h2>Hosted API testing services</h2>
104104
<h2>API creation resources</h2>
105105
<ul>
106106
<li>
107-
<p><a href="http://www.narwhl.com/">NARWHL</a> is a practical API design site for
108-
developers confused about what is appropriate for RESTful APIs.</p>
109-
</li>
110-
<li>
111-
<p>This <a href="https://github.com/interagent/http-api-design">API Design Guide</a>
112-
is based on Heroku's best practices for the platform's API.</p>
113-
</li>
114-
<li>
115-
<p><a href="https://18f.gsa.gov/">18F</a>'s
116-
<a href="https://github.com/18f/api-standards">API standards</a> explains the details
117-
behind their design decisions on creating modern RESTful APIs.</p>
118-
</li>
119-
<li>
120107
<p><a href="http://pydanny.com/choosing-an-api-framework-for-django.html">Choosing an API framework for Django</a>
121108
by <a href="https://twitter.com/pydanny">PyDanny</a> contains questions and insight
122109
into what makes a good API framework and which one you should currently
@@ -133,6 +120,25 @@ <h2>API creation resources</h2>
133120
traps.</p>
134121
</li>
135122
<li>
123+
<p>Versioning of RESTful APIs is a difficult and contentious topic in the
124+
web API community. This two-part series covers
125+
<a href="http://urthen.github.io/2013/05/09/ways-to-version-your-api/">various ways to version your API</a>
126+
and <a href="http://urthen.github.io/2013/05/16/ways-to-version-your-api-part-2/">how to architect a version-less API</a>.</p>
127+
</li>
128+
<li>
129+
<p><a href="http://www.narwhl.com/">NARWHL</a> is a practical API design site for
130+
developers confused about what is appropriate for RESTful APIs.</p>
131+
</li>
132+
<li>
133+
<p>This <a href="https://github.com/interagent/http-api-design">API Design Guide</a>
134+
is based on Heroku's best practices for the platform's API.</p>
135+
</li>
136+
<li>
137+
<p><a href="https://18f.gsa.gov/">18F</a>'s
138+
<a href="https://github.com/18f/api-standards">API standards</a> explains the details
139+
behind their design decisions on creating modern RESTful APIs.</p>
140+
</li>
141+
<li>
136142
<p>"<a href="https://medium.com/@zwacky/design-a-beautiful-rest-api-901c73489458">Design a beautiful REST API</a>"
137143
reviews common design decisions regarding endpoints, versioning, errors and
138144
pagination. There is also a

change-log.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,7 @@ <h1>Change Log</h1>
4646
<h2>2014</h2>
4747
<h3>October</h3>
4848
<ul>
49+
<li>More API creation resources.</li>
4950
<li>Merged a bunch of pull requests that cleaned up spelling and grammar
5051
errors. Thank you contributors!</li>
5152
<li>Adding new Django 1.7-specific resources section on the Django page.</li>

feeds/all.atom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-10-13T20:13:57Z</updated></feed>
2+
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-10-14T06:23:43Z</updated></feed>

source/content/pages/08-apis/0803-api-creation.markdown

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -73,16 +73,6 @@ equivalent of browser testing in the web application world.
7373

7474

7575
## API creation resources
76-
* [NARWHL](http://www.narwhl.com/) is a practical API design site for
77-
developers confused about what is appropriate for RESTful APIs.
78-
79-
* This [API Design Guide](https://github.com/interagent/http-api-design)
80-
is based on Heroku's best practices for the platform's API.
81-
82-
* [18F](https://18f.gsa.gov/)'s
83-
[API standards](https://github.com/18f/api-standards) explains the details
84-
behind their design decisions on creating modern RESTful APIs.
85-
8676
* [Choosing an API framework for Django](http://pydanny.com/choosing-an-api-framework-for-django.html)
8777
by [PyDanny](https://twitter.com/pydanny) contains questions and insight
8878
into what makes a good API framework and which one you should currently
@@ -96,6 +86,21 @@ equivalent of browser testing in the web application world.
9686
working with APIs and how you can avoid your API falling into the same
9787
traps.
9888

89+
* Versioning of RESTful APIs is a difficult and contentious topic in the
90+
web API community. This two-part series covers
91+
[various ways to version your API](http://urthen.github.io/2013/05/09/ways-to-version-your-api/)
92+
and [how to architect a version-less API](http://urthen.github.io/2013/05/16/ways-to-version-your-api-part-2/).
93+
94+
* [NARWHL](http://www.narwhl.com/) is a practical API design site for
95+
developers confused about what is appropriate for RESTful APIs.
96+
97+
* This [API Design Guide](https://github.com/interagent/http-api-design)
98+
is based on Heroku's best practices for the platform's API.
99+
100+
* [18F](https://18f.gsa.gov/)'s
101+
[API standards](https://github.com/18f/api-standards) explains the details
102+
behind their design decisions on creating modern RESTful APIs.
103+
99104
* "[Design a beautiful REST API](https://medium.com/@zwacky/design-a-beautiful-rest-api-901c73489458)"
100105
reviews common design decisions regarding endpoints, versioning, errors and
101106
pagination. There is also a

source/content/pages/11-misc/1103-change-log.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ the
2424

2525
## 2014
2626
### October
27+
* More API creation resources.
2728
* Merged a bunch of pull requests that cleaned up spelling and grammar
2829
errors. Thank you contributors!
2930
* Adding new Django 1.7-specific resources section on the Django page.

0 commit comments

Comments
 (0)