Testing with a non-wordpress.com server

[scripting]

Yesterday I wrote on my blog --

Just added to my todo list -- add the option to use the WordPress REST interface in place of the WPCOM interface, this will give "WordLand" the ability to edit WordPress sites anywhere, not just on wordpress.com. When I made the choice to go with WPCOM I didn't have ChatGPT to look at the other options, I was surprised to find that WordPress actually had a good JavaScript API. It doesn't look like the conversion will be too bad. It's obviously better to be able to work with all WordPress sites.

I was then informed that this would not be necessary.

The good news is, self-hosted WordPress site owners should already be able to use WordLand. The Jetpack plugin allows you to use the WordPress.com REST API from a self-hosted site. Anyone can install the plugin and start using WordLand, even if their site is not hosted on WordPress.com.

I want to get on this asap. Will explain in next comment.

[scripting]

The details on the server.

I wrote a Node package called wpIdentity. It handles all communication with WordPress for WordLand.

If we can get a simple app running on wpIdentity to publish to a WordPress site that's not on wordpress.com, that will provide all the info we need to get WordLand to do it.

[scripting]

And for the final step -- this is the wpcom Node.js package.

https://github.com/Automattic/wp-calypso/tree/trunk/packages/wpcom.js

It seems to me somewhere in here there must be a place where we provide the URL of the non-wordpress.com site.

[jeherve]

The good news is, self-hosted WordPress site owners should already be able to use WordLand. The Jetpack plugin allows you to use the WordPress.com REST API from a self-hosted site. Anyone can install the plugin and start using WordLand, even if their site is not hosted on WordPress.com.

I can confirm it works well! I just tested and was able to publish to a self-hosted site with no issues.

It seems to me somewhere in here there must be a place where we provide the URL of the non-wordpress.com site.

After you authenticate with WordPress.com, wpIdentity makes a call to return all the sites managed by your WordPress.com account (that is your wordpressgetusersites call). That call will not only return WordPress.com sites ; it will return any site currently associated with your WordPress.com account, including self-hosted sites you've linked to your WordPress.com account via the Jetpack plugin.

That means that when I hit Publish and pick where I want to publish, I can pick one of my self-hosted sites there and publish there.

The only caveat is that you must have enabled the "JSON API" feature in the Jetpack plugin settings on your site. The feature is what allows managing your site via a third-party application like WordLand. The feature is activated by default so it will be active for most folks trying to use the app.

[scripting]

@jeherve -- you all do good work. i was very pleased to see the API in wpcom, it was consistently designed, worked more or less the way i would have designed my api, in fact it's pretty much the same as the manila api we did for our blogging system at userland in the late 90s early 00s.

what i'm doing here is providing the writer's interface i want for wordpress, a 2024 version of the one we did when blogging was first booting up.

but i didn't expect that wordpress.com would act as glue that tied all wordpress sites together, even ones that were hosted elsewhere.

[drf5n]

That means that when I hit Publish and pick where I want to publish, I can pick one of my self-hosted sites there and publish there.

Ah, I see, when you hit Publish, the lower left corner of the window has a "Choose site." button that lists the jetpack-registered sites, and after you chose one for the post, that button changes to "Site: blog name"