Website RSS feed development
A feed needs stable item identity, working addresses and a clear selection policy. A title correction should not accidentally appear to be a new publication.
- Starting condition
A feed needs stable item identity, working addresses and a clear selection policy. A title correction should not accidentally appear to be a new publication.
- Implementation
Select published entries by language. Generate absolute links, XML escaping, dates and stable identifiers from the content source. Exclude private drafts and previews.
- Verification
A corrected article retains its intended identity while a genuinely new article receives a new ID.
- Decision
Use a persistent item ID or a deliberate stable-address model. Plan changes for existing subscribers: a changed guid may already have been imported.
A corrected article retains its intended identity while a genuinely new article receives a new ID.
Which check determines the next step?
Use a persistent item ID or a deliberate stable-address model. Plan changes for existing subscribers: a changed guid may already have been imported.
Scope the development
A feed needs stable item identity, working addresses and a clear selection policy. A title correction should not accidentally appear to be a new publication.
ImbaHub can help with a bounded implementation on your website. We start from the real environment, affected page types and an agreed visitor task.
What the implementation needs
Select published entries by language. Generate absolute links, XML escaping, dates and stable identifiers from the content source. Exclude private drafts and previews.
Delivery covers the agreed components, configuration, test cases and documentation. Start with a representative page. Define languages, devices and external dependencies before extending the work to the rest of the website.
| Check | Expected outcome |
|---|---|
| Starting condition | A feed needs stable item identity, working addresses and a clear selection policy. A title correction should not accidentally appear to be a new publication. |
| Implementation | Select published entries by language. Generate absolute links, XML escaping, dates and stable identifiers from the content source. Exclude private drafts and previews. |
| Verification | A corrected article retains its intended identity while a genuinely new article receives a new ID. |
| Decision | Use a persistent item ID or a deliberate stable-address model. Plan changes for existing subscribers: a changed guid may already have been imported. |
A fictional website example
Fictional example: A knowledge article gets a new title. The feed derives its guid from that title, so the reader treats old and new entries as different articles.
Checks before acceptance
A corrected article retains its intended identity while a genuinely new article receives a new ID.
Save the feed before and after a title change. Compare guid, link and publication date for the same item. Check unique, stable identity even when ordering changes.
Delivery and ongoing ownership
Assign responsibility for changes after handover and document how to restore the previous working version. Scope and pricing follow review of the current solution and access; fixed packages or outcome levels are not assumed.
Sources and further reading
Questions, answered
What should we send to scope the work?
Select published entries by language. Generate absolute links, XML escaping, dates and stable identifiers from the content source. Exclude private drafts and previews.
Which check determines the next step?
Use a persistent item ID or a deliberate stable-address model. Plan changes for existing subscribers: a changed guid may already have been imported.