Task #3284
closedAdd conceptual introduction to plugin writing guide
100%
Description
Add a conceptual introduction to the plugin writer guide. This would help motivate and offer perspectives on some of the most important questions a plugin writer has to answer before coding:
Defining a content type to manage
What is the content called?
What attributes make each piece of content unique?
How will this content get into Pulp?
Upload?
Sync from a remote source?
- what kind of tools can be used to sync from remote?
- download API
- storage API
How does the content need to be published?
Is there metadata that needs to be generated at publish time?
What tools will be used to consume the content?
- does the tool expect static files served by a web server
- does the tool use a protocol other than HTTP to consume content?
Updated by dkliban@redhat.com almost 7 years ago
- Sprint/Milestone set to 53
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Updated by bmbouter almost 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Added by bmbouter almost 7 years ago
Added by bmbouter almost 7 years ago
Revision 23110be3 | View on GitHub
Adds a plugin planning guide
closes #3284
Updated by bmbouter almost 7 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|23110be3dbd43a30dfd2577a95ee46bdbf687b16.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Adds a plugin planning guide
closes #3284