XML-RPC Blog/News Article Service

You ended up here somehow. A list of the features this XML-RPC blogging/news API supports:

• All article information is stored on the XML-RPC server.
• Automatic conversion from the database storage to HTML via XML templates (either server or user defined).
• Multiple sections can be created via the API to sort articles into categories.
• Support for a few extended article attributes (icons, images, reference URLs, etc.)
• Support to retrieve articles as HTML format from specified template, or to retrieve a single article converted
• Retrieving the raw data from the database so that the client side can convert the data into something presentable
• Templates can be stored on the server or sent with each XML-RPC call
• Lots of API documentation
• Allows (at this moment) up to 500 articles to be retrieved per call to the list or conversion functions (multiple calls over multiple ranges can extend this indefinitely)
• PHP client class provided (though may need some work to work with other PHP installations)
• Future: Online maintenance and control of your account, articles, templates and sections (likely via XWT)
• Future: If demand grows, then shared article sources may be provided (so multiple sites can use each others' articles)
• Future: Enhanced sectioning to provide for sub-sections
• Future: Public anonymous or authenticated commenting on articles
• Future: Interface to sign up e-mail accounts (with e-mail verification) to be notified of new posts automatically

Currently, the only real example of this API in use is the main page of Geeks Anonymous. The news at the top of the page is entirely done using this API and a custom XML template.

If you wish to try out using the XML-RPC functions that are explained in the documentation, you will first need to setup an account on the server. Just fill in the blanks below, and off you go (all information required unless otherwise specified, review the privacy policy if you want):

Username:
Password:
Full name:
E-Mail:
Alias (optional):

There is not much else here just yet. Check out the documentation, though.