|
|
|
|
|
|
by diegogcouto
5016 days ago
|
|
|
Your feedback was really important to make me think about which kind of user I should focus initially. First, I was thinking how to get attention of the regular user, but you made me think about how it could be a lot more useful to developers and designers in a first moment. Your idea is awesome, I'm very grateful for your help! |
|
|
In all seriousness, the trick to this kind of platform is the following. You have to make it very, very easy to work with. Using confusing API calls will just make people run away from it. I've seen a lot of APIs that are over engineerd with wacky syntax. Try and keep it as simple as possible, as if the developer was writing HTML itself.
The only problem with wordpress is the platform itself. In order to build something with it, you are accepting a lot of engineering overhead from past versions. This technical baggage makes it a pain to work it, though not as bad as joomla. By going with the API route, you can change the back end as much as you'd like, but the developers would just see the same API calls. Its like an interface in OOP programming.
The last API I did for a client took calls like this:
host/category/products/product/id/get
to this:
host/get/id
See how easier it is to develop with that? You dont need to know what category the product belongs to, because that data is passed as a JSON string to you. Once you get it, on your side you just go through the results and display it accordingly.
Same with a blog API. I dont need to know the title, just the post ID. So do host/get/id and then in the front end do {% post.title %} {% post.author %}{% post.date_published %} {% post.content %}
and so on.