[oXygen-user] oXygen to WordPress

[Oxygen XML Editor Support (Radu Coravu)]

Hi Ben,

We have not (yet) implemented such a "Publish To WordPress" feature.
And also right now this is not on our todo list.
Oxygen has lots of API so hypothetically speaking an Oxygen plugin could 
be built for this.
Or you can just publish to XHTML and then upload that XHTML content to 
the WordPress web site.
A problem would be with referenced images. Usually when I blog, I blog 
in DITA and I embed the images in the XHTML content using base 64 
encoding, thus the XHTML which I paste in the uploaded blog content 
contains all the information inside it.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/5/2016 12:33 AM, Ben McGinnes wrote:
> Hello,
> 	So I stumbled across this post from a couple of years ago:
>
> https://www.oxygenxml.com/pipermail/oxygen-user/2013-August/004754.html
>
> Basically just asking for a feature to update a WordPress blog and
> said request being forwarded along.  I've got two questions:
>
> 1) Did it become a feature?
>
> 2) If not, now that WordPress supplies an optional JSON based REST
>     API, could the request be revisited since it ought to make it
>     easier to make the two things play nicely together?
>
> WordPress API documentation:
>
> http://v2.wp-api.org/
>
> I've only looked at it briefly, but it's REST so it can't be that
> hard, not as far as communicating with the server is concerned, at any
> rate.  I've done a few client-side interaction things like this at
> times; mainly grabbing Bitcoin and/or currency live data and playing
> with the Twitter API so from my perspective the worst case scenario is
> making the right HTML template to play nicely at the other end and
> adding a few Python scripts (well, of course, by now everyone saw
> *that* language preference coming).  Still, there's a lot to be said
> for "point and click" if it just works.
>
> Although the Github repositories also include command line tools and a
> console for the thing, so chances are integration could be reduced to
> calling the relevant commands to do whatever.  The rough edges at the
> moment appear to be limited to generating the OAuth credentials, but
> that's not a huge chore for most WordPress admins.
>
>
> Regards,
> Ben
>