Rolling window or fixed editorial week?
The seven-day option is relative to execution time, not a fixed calendar week. Review dates manually for the issue boundaries and quarantine undated or future-dated entries.
Elysia Tools
Navigation
Workflow Playbook
Turn selected RSS and Atom feeds into a reviewed weekly digest with explicit dates, cross-source deduplication, traceable summaries and verified HTML or PDF delivery.
Hubs
This workflow is for an editor preparing one weekly technical or team digest, not an unattended news monitor. Record the period, timezone, capture time and feed list. A rolling seven-day filter changes with each run; for a fixed Monday-to-Sunday issue, review exact boundaries against a saved snapshot. Unparseable dates are retained by the feed tool, and Atom can fall back from published to updated. A recent update does not necessarily mean a new article. Future-dated candidates also need review rather than automatic inclusion.
Keep date and source link fields visible and record each feed's cap. If the limit hides relevant entries, inspect a larger candidate set instead of calling the truncated output complete. An unavailable feed is missing evidence, not proof that its author published nothing. Feed descriptions may be shortened or promotional; the formatter does not independently establish truth.
Open selected originals and use authorized page conversion to help reading where appropriate. A successful fetch may omit client-rendered content or figures, so compare the actual page. Write a short note about why the item matters to this audience and retain source and author attribution. Do not merge full converted articles into the public digest merely because they were fetchable.
Merge candidate drafts in a recorded order, then review heading changes and any generated navigation. A merger combines text; it does not make editorial choices. URL deduplication can miss alternate links, while title matching can confuse distinct posts. Keep one primary entry when several sources repeat the same story, retaining complementary attribution when it matters. Maintain a small ledger of included items, excluded duplicates and date exceptions so the final count is explainable.
Run style and reference checks after the edit. The link inventory helps spot missing sources and tracking variants but does not decide which canonical URL is correct. Do not strip query parameters blindly: some identify the article. The link checker is static, so visit external destinations separately and note paywalls or authentication.
Export website HTML or a PDF proof only if the recipient needs it. Compare the issue date, entry count, headings, summaries and source links against the approved Markdown; inspect PDF page breaks and website rendering rather than trusting conversion success. If a source changes after review, record a new snapshot and update all required copies together. HTML export does not test mail clients or send a newsletter. Use the general documentation workflow for manuals, the source audit for broader reuse questions and Markdown utilities for isolated edits; this page's result is one attributable, reviewed digest.
Workflow playbook
Process each feed, retain date and link fields, record the rolling window and cap, and separately assess missing dates, Atom updated fallbacks and items outside the fixed issue interval.
Open the original articles, use webpage conversion for authorized readable source material where useful, and verify titles, authors and substantive claims without assuming a fetch contains all dynamic content.
Merge source drafts in a deliberate order, review adjusted headings, manually reconcile cross-source duplicates and write topic-grouped notes with attribution and an inclusion ledger.
Review Markdown findings and the extracted link inventory, check internal anchors and references statically, and separately test external destinations and access conditions.
The seven-day option is relative to execution time, not a fixed calendar week. Review dates manually for the issue boundaries and quarantine undated or future-dated entries.
Feed deduplication uses title or URL within a run, not semantic comparison across feeds. Review merged candidates so identical headlines do not erase distinct articles.
Treat feed descriptions as source-provided text, not fact-checked summaries. Consult the original for important claims, write a concise attributed note and publish only content you can reuse.
Generate only the required HTML or themed PDF from the approved master, inspect rendering and compare item count, dates and source links before handing off; conversion does not send email.