5 ms·
No worries. I just wanted to make it clear this is not a toe in the water. :-) > My understanding is this can be used as an interface to all WordPress blogs.
by rralian 11y ago
No worries. I just wanted to make it clear this is not a toe in the water. :-)
> My understanding is this can be used as an interface to all WordPress blogs.
Yes, that's correct. It works for WordPress.com blogs of course. But self-hosted blogs can also make use of Calypso by installing our Jetpack plugin (https://wordpress.org/plugins/jetpack/ https://wordpress.org/plugins/jetpack/) which adds some API endpoints that allow Calypso to communicate with the self-hosted site.
> it is only steps away from peeling out the whole PHP layer for these interfaces
I don't think I would go that far exactly. The php codebase is still there, and users can still use "wp-admin" if they prefer. And the API is also powered by PHP. But now that Calypso only communicates with a site through the API it allows us to separate the view logic and focus on making those endpoints as efficient as possible. I think it's possible the API could be written in a language other than PHP. But that hasn't happened yet and would be a significant task.
I should probably mention I am one of the authors, if that wasn't obvious. :-)
- rralian 11y agoOh yeah, there's also the whole "every page a reader sees" on the front-end of the site.
- lloydde 11y ago> We still have a ton to figure out around plugins, extensibility, contributions, Windows and Linux releases, API speed, localization, and harmonizing the WordPress.com API and WP-API so it can work with core WordPress. Thousands more PHP developers will need to become fluent with JavaScript to recreate their admin interfaces in this fashion. I'm also really excited to revisit and redesign many more screens now that we have this first version out the door. http://ma.tt/2015/11/dance-to-calypso/ http://ma.tt/2015/11/dance-to-calypso/