Update endpoint ideas

[rmccue]

From the readme:

The JSON API is also an important component so we can use this data elsewhere, and I imagine would have endpoints somethign like:

GET /api/time/now

Returns a list of users with their timezones and working hours

The reason I put "now" is if in the future we were to integrate vacatios etc, this endpoint would just reflect the people who are curently working, where as /api/time may return all the users and data with working schedules etc.

The Extending the API guide is a good reference here.

Here's what I'd envision it looking more like:

• GET /timezones: Gives a list of objects, looking something like this:

[
    {
        "author": {
            "ID": 1,
            ...
        },
        "timezone": "Australia/Brisbane",
        "current_time": "2013-06-02T05:28:00+10:00"
    },
    ...
]

Where:

• user: User entity, similar to the author attributes on posts.
• timezone: Standard timezone identifier
• current_time: Current time in the user's local time. (Helpers for this in WP-API core)
• GET /timezones/<id>: Same as above, but for singular user. i.e. /timezones/1
• PUT /timezones/<id>: Change timezone for user. Only allow changing the timezone key
• POST /timezones/<id>: Create a timezone for a user

That's my cursory thinking, just looking at this quickly. :)

[joehoyle]

@rmccue thanks for the feedback - @missjwo will hopefully be tackling this, so the above will be of use to her I imagine.

[rmccue]

Also, if you do it with this format, creating the same widget as currently exists is pretty simple. :)

Using Mustache syntax, individual items are something like:

<li class="zone">
    <span class="clock">{{ current_time }}</span>
    <span class="humans"><img width="24" title="{{ author.name }} - {{ timezone }}" alt="{{ author.name }}" src="{{ author.avatar }}"></span>
</li>