Permalink
Browse files

Final changes, renamed to include date.

  • Loading branch information...
1 parent a71490b commit 32e3f1d54209713db9f59fad77933ea7af68160c @zdne zdne committed Jan 24, 2013
Showing with 6 additions and 6 deletions.
  1. +6 −6 _posts/{New API Blueprint Format.md → 2013-01-25 New API Blueprint Format.md}
View
12 _posts/New API Blueprint Format.md → ...ts/2013-01-25 New API Blueprint Format.md
@@ -1,15 +1,15 @@
---
title: Evolving the API Blueprint Format
-excerpt: As we are growing so are our users needs. We're thinking hard about how to evolve API Blueprint format.
+excerpt: As we are growing so are our users needs. To reflect this, address arising needs as well as simplifying the process of designing your API we are improving Apiary.io API Blueprint Format.
layout: post
published: false
-date: 3013-01-25 09:00:00 +1000
+date: 2013-01-25 09:00:00 +1000
---
# Evolving the API Blueprint Format
Apiary.io is growing and so are our users' needs. We want to fuel the endless possibilities of where your API can go. We want to give you the best tools to design and maintain any REST-based API without boundaries or limits. Yet we must also guide newcomers who are just tapping the API World.
-We are thinking hard about evolving our API Blueprint Format and I would like to share with you our thoughts on how it will evolve in the weeks to come.
+We are constantly improving our API Blueprint Format and I would like to share with you our thoughts on how it will evolve in the weeks to come.
## It is Markdown
We have decided to fully embrace Markdown for documenting your API. With the New API Blueprint Format your API documentation will be completely in pure Markdown excluding few extra [MultiMarkdown](http://fletcherpenney.net/multimarkdown/) features.
@@ -22,7 +22,7 @@ Markdown is supported by virtually every language or IDE in existence. There wil
With the New API Blueprint Format getting on board will be even easier. All in proper structural order, Markdown header specifying your endpoint followed by its discussion.
## HUGE deal for big APIs
-No more bloated API blueprints with lots repetition packed into one document. Let's keep things DRY and introduce more modularity. Here is what is new in API Blueprint Format to deal with large, complex APIs:
+No more bloated API blueprints with lots repetition packed into one document. We will keep things DRY and introduce (more) modularity. Here is what is new in API Blueprint Format to deal with large, complex APIs:
* Data Dictionaries
* Cross-References
@@ -39,6 +39,6 @@ While I understand and have nothing but utmost respect for "pragmatic REST" I wa
## To the future and beyond
We will also deliver (or improve existing) support for **multimedia**, **multiple** **request** and **response** with improved schema support. This should be followed later by support for **authentication** an **pagination**.
-As you can see there are big changes ahead. But we will make sure to make things smooth for you and all our existing users. We'll work hard to make migration painless.
+As you can see there are big changes ahead. We will make sure to make things smooth for you and all our existing users.
-In the upcoming weeks I will be posting more details about format changes including specific examples. In the mean time, if you're excited about the direction API Blueprint is heading, or have comments/wishes, please head over to [New API Blueprint Format](http://support.apiary.io/forums/120125-general/suggestions/2970802-new-api-blueprint-format) and vote or add your comments there. Additionally you can contact me directly at [z@apiary.io](mailto:z@apiary.io).
+In the next weeks I will be posting more details about the upcoming format changes including examples. In the mean time, if you're excited what will the new format bring or just curious about the direction API Blueprint is heading, please head over to [New API Blueprint Format](http://support.apiary.io/forums/120125-general/suggestions/2970802-new-api-blueprint-format). There you can vote for the new format and add your comments and wishes. Additionally you can contact me directly at [z@apiary.io](mailto:z@apiary.io). I would love to hear from you.

0 comments on commit 32e3f1d

Please sign in to comment.