In case you haven't noticed, over the last couple of years we've been making huge strides in the depth and breadth of the content offered by ProgrammableWeb. ProgrammableWeb.com has always been regarded as the world's finest directory of APIs and our traffic logs reflect the increasing extent to which developers rely on that directory to research APIs for inclusion in their next apps. But, what was once a relatively basic blog that rode side-car to ProgrammableWeb's directories is now a full-blown media offering with articles of different types ranging from news stories about the latest goings-ons in the API economy to in-depth tutorials and prescriptive advice for those seeking guidance for their API strategies to a variety of other forms of contributed content. After all, when TechCrunch called ProgrammableWeb The Journal of The API Economy, it gave us a tagline to live up to.
Judging by our traffic, the ProgrammableWeb community is appreciating these strides. With each month comes new traffic records and, in our view, that constantly improving visitorship is an acknowledgment of the ever increasing utility of our content. But we prefer not to rest on our laurels. Not only do we have more improvements in store for our directories -- changes that will improve their utility as well -- our plan is to vastly improve the quantity and quality of our educational content; the content that proverbially answers all the questions about APIs that developers, API providers and the API-curious are afraid to ask.
But to do that, we need you. We are constantly on the lookout for both developers and master provisioners of APIs to share their expertise with the ProgrammableWeb community. So, what sorts of articles are we after?
Tutorials for both API developers and API providers are at the top of our list. Have you mastered some special technique for consuming APIs? Or securing APIs? Something that you believe would be of benefit to your fellow ProgrammableWeb community members? For example, on the developer side, check out Doron Katz's tutorial on how to implement deep linking on iOS or Chris Wood's "Hello World" of Twitter using Python to get an idea of the sorts of how-to's were after. But for API providers, click over to Patricio Robles' tutorial on how to create a RESTful API using PHP and Laravel.
In fact, Robles' tutorial is an excellent example of the endless possibilities when it comes to the software stacks as well as the APIs or apps that can be provisioned and developed with them. Likewise, Angelina Fomina's tutorial on How to Build an Events Database Using the ParseHub API, Python & Flask is another example of how myriad technologies can intersect with your creativity to produce highly unique tutorials. Though the use cases within them can be extremely specific, the lessons learned are easily projected to other situations. The resulting orders of magnitude mean that the opportunities for ProgrammableWeb to publish such tutorials about expert consumption and provisioning of API are nearly limitless. We just need you, the experts, to help us address all of those use cases, real or fictitious. Best of all, depending on the article, it's an opportunity to put a little extra spending cash in your pocket.
We are also not shy about accepting such tutorials from technology providers so long as the tutorial is non-hyperbolic; in other words, it's just the facts and not an advertorial that passes judgement on the virtues of the provider or its solutions. For example, check out Joe Chow's How to turn your predictive models into APIs Using Domino. "R" is one of those programming languages that has a nearly cult-like following among data scientists and other aficionados of predictive modeling. In the context of what we here at ProgrammableWeb call PhD APIs (the sort of APIs that obviate the need to hire a team of PhDs), we've been seeing R show up in more and more conversations. So much so that we added R to the taxonomy that cuts across all of ProgrammableWeb's content assets. So, when we ran into Nick Elprin and Anna Anisin from Domino Data Lab in San Francisco and they told us how they can turn R-based predictive models into RESTful APIs, we thought it was so cool that we couldn't wait to have the tutorial on how to do it.
Such submissions are of course subject to our editorial process because we're always on the lookout for tutorials that look to take advantage of the opportunity with too much hyperbole. But the same goes for all contributed content from the community, with the exception of sponsored content.
Sponsored content is exactly what it implies -- articles that are published to ProgrammableWeb.com as a part of a sponsorship arrangement between ProgrammableWeb and the sponsor of the article. A good example is Phillip Shipley's writeup (sponsored by Nexmo) on End-User Verification Even Your Grandma Can Use. When sponsored content is published on ProgrammableWeb as the result of such an arrangement, the rules about what can be written are significantly relaxed when compared to those for contributed content. In both cases however, the content is labeled for what it is (contributed or sponsored content) and the articles include disclosures that make it clear that the views expressed within them are not necessarily the views or opinions of the ProgrammableWeb editorial team.
Finally, thought-leading (and provoking) analysis as well as other interesting API considerations are also at the top of our list. For example, check out Netflix vice president Daniel Jacobson's most excellent treatise on how important it is to your API strategy to “separate concerns.” Or SmartBear CTO Ole Lensmar’s contemplation as to whether REST is losing its flair. We gladly accept thought-leading vendor-neutral contributions like these that promote the best interests and healthy development of the API economy while at the same time not advancing any specific commercial agenda.
If any of these opportunities sound interesting to you, or you have an idea for some form of contributed content that's not covered here, please do not hesitate to reach out to me (email@example.com) or ProgrammableWeb's editorial team (firstname.lastname@example.org). Be sure to give us some idea of what you think you're qualified to write about or even pitch us on a specific story, and we'll get back to you as soon as we can.