<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body> <ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[
Zend_Service_Wordpress
<p>This page has been created from a template that uses "zones." To proceed:</p>
<ol>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.
<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.</p></ac:rich-text-body></ac:macro></li>
</ol>
</ac:rich-text-body></ac:macro>
<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[
Zend Framework: Zend_Service_Wordpress Component Proposal
Proposed Component Name
Zend_Service_Wordpress
Developer Notes
http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Wordpress
Proposers
Eric Clemmons
Zend Liaison
TBD
Revision
1.0 - 2 September 2009: Initial Draft. (wiki revision: 8)
Table of Contents
1. Overview
Zend_Service_Wordpress allows you to easily consume a WordPress blog's content via WordPress' XML-RPC gateway via a fluent interface.2. References
3. Component Requirements, Constraints, and Acceptance Criteria
4. Dependencies on Other Framework Components
- Zend_Service_Exception
5. Theory of Operation
- Application Developer instantiates Zend_Service_Wordpress
6. Milestones / Tasks
Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.
- Milestone 1: design notes will be published here
- Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
- Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
- Milestone 4: Unit tests exist, work, and are checked into SVN.
- Milestone 5: Initial documentation exists.
If a milestone is already done, begin the description with "[DONE]", like this:
- Milestone #: [DONE] Unit tests ...
7. Class Index
- Zend_Magic_Exception
- Zend_Magic (factory class)
- Zend_Magic_MindProbe
- Zend_Magic_MindProbe_Intent
- Zend_Magic_Action
- Zend_Magic_CodeGen
8. Use Cases
| UC-01 |
|---|
Connect to your blog
| UC-02 |
|---|
Get various blog information
| UC-03 |
|---|
List all tags
| UC-04 |
|---|
List all categories
| UC-05 |
|---|
Get recent posts
| UC-06 |
|---|
Get post information
2 Comments
comments.show.hideOct 08, 2009
Eric Clemmons
<p>Perhaps this should be Zend_Service_Blog with a Zend_Service_Blog_Adapter_Wordpress class, like Zend_Db and Zend_Db_Adapter_Mysql</p>
Feb 17, 2011
Nikko Bautista
<p>If we were to follow the Zend_Service convention, then the name should remain Zend_Service_Wordpress IMO, since each component of Zend_Service is a different service - though I agree, it would be much better to have separate blog adapters to accomodate for different blogging platforms.</p>
<p>Is anybody working on this now? I want to continue this component if possible <ac:emoticon ac:name="smile" /></p>