Phase 2: Build the Feed and Content Engine
Days 6-14. By the end of this phase you will have a configured feed, a working content process, and a starting collection worth browsing.
Phase 1 gave you a feed idea and a strategy sheet. Phase 2 is where that becomes a real, browsable feed: named, branded, categorized, stocked with sources, and running on a repeatable process for turning raw material into published posts.
Day 6: Create and name the feed
Today's outcome: the feed exists, with a public title and description you're comfortable with.
Why this matters: the name and description are the first thing a new visitor judges the feed by.
What to do: create the feed and confirm its public title and description. Make the topic obvious, use language your audience already uses, avoid clever names that hide the purpose, and include the place or audience when it helps.
You're done when: the feed name and working public link are recorded.
Day 7: Configure branding and basic settings
Today's outcome: a feed that looks finished, not a bare default template.
Why this matters: a feed that looks unfinished undercuts the content inside it, even when the content is good.
What to do:
- Logo or brand identity added where applicable.
- Colors and theme reviewed.
- Public description checked.
- Sharing information reviewed.
- Feed behavior settings reviewed.
- Default links checked.
- Custom domain decision recorded. A custom domain can wait, don't let it delay launch.
Quality check: ask someone unfamiliar with the setup to open the feed and answer, "What is this feed about?"
You're done when: they could answer without help from you.
Day 8: Create the category structure
Today's outcome: three to six categories that help a reader decide what to click.
Why this matters: categories should help a reader make a decision, not just mirror your internal content labels.
What to do: start with three to six categories. For an events feed, that might be This Weekend, Family, Food and Drink, Live Music, Free. For a deals feed, that might be Food and Drink, Shopping, Family, Health and Wellness, Limited Time. Avoid creating so many categories that most hold a single post.
You're done when: categories are created and recorded on the Feed Strategy Sheet.
Day 9: Build the Content Source Planner
Today's outcome: a short, honest list of where your content will actually come from.
Why this matters: a plan for where content comes from keeps you from scrambling for posts every week.
What to do: list your sources below. Possible types include RSS, webpage, Meetup, Eventbrite, direct business contribution, manual research, and your own original content. Start with a few reliable sources rather than connecting everything you can find. Remember: imported content always goes into review, a source won't automatically catch every change or cancellation, and you remain responsible for accuracy and authorized use of content and images.
Content Source Planner
| Source | Type | Frequency | Keep / change / remove |
|---|---|---|---|
You're done when: the planner has your first few sources listed.
Day 10: Connect the first sources
Today's outcome: one to three sources actually connected and producing content.
Why this matters: this is where the content engine actually starts running.
What to do: connect one to three supported sources and complete the setup or sync steps. Current supported source types are RSS, webpage, Meetup, and Eventbrite. Not every website is compatible.
- Source URL and type are correct.
- Imported items are relevant.
- Duplicate or low-quality items are flagged.
- Dates, links, images, and descriptions check out.
- Each source is kept, adjusted, or removed based on usefulness.
You're done when: your connected sources are producing content you'd actually publish.
Day 11: Define editorial standards
Today's outcome: a one-page standard you can hold any post to, including ones you didn't write yourself.
Why this matters: a simple standard keeps quality consistent even as more people touch the feed.
What to do: each post should be checked for a clear, specific title; an accurate description; correct date and time when relevant; correct location or online link; a useful category; a working call-to-action link; an appropriately licensed image; offer terms and expiration when relevant; clear sponsor or paid-placement identification when applicable; no invented details or unsupported claims; and fit with the feed promise. Add one rule: the feed owner is responsible for reviewing time-sensitive content and removing or correcting anything that's no longer useful.
You're done when: the checklist exists and you've run at least one post through it.
Day 12: Connect the AI assistant
Today's outcome: either the assistant is connected, or you've confirmed you're working manually for now.
Why this matters: this is the fastest way to turn raw source material into ready-to-review drafts.
What to do: MCP is the connection that lets a compatible AI assistant work with your Feedlnk account and prepare draft posts for you to review. Follow the current instructions for Claude, Codex, Cursor, or another compatible client. A few things worth knowing: the assistant can prepare drafts for review, it cannot publish independently through the current integration, connecting MCP alone does not schedule a recurring process, and you should never paste private credentials into an ordinary prompt or shared document.
- MCP connected.
- Working manually for now.
Day 13: Complete the AI Content Brief
Today's outcome: a reusable brief that keeps AI-prepared drafts accurate instead of generic.
Why this matters: a clear brief is what keeps AI-prepared drafts accurate instead of generic.
What to do: fill in the fields below, then use them to fill in this starter prompt:
Help me prepare draft posts for [FEED NAME]. Audience: [AUDIENCE]. Purpose: [FEED PROMISE]. Topics to include: [TOPICS]. Topics to exclude: [EXCLUSIONS]. Location or scope: [SCOPE]. Preferred sources: [SOURCES]. Freshness requirement: [DATE RANGE]. Categories: [CATEGORIES]. For every proposed post: use only details supported by the source, don't invent dates, prices, locations, offer terms, or links, flag anything missing or time-sensitive, write a clear title and useful description for this audience, suggest the right Feedlnk post type and category, and include the original source URL for review. Create drafts for my review, don't treat drafting as approval to publish.
AI Content Brief
| Field | Your answer |
|---|---|
| Feed name | |
| Target audience | |
| Feed promise | |
| Allowed topics | |
| Excluded topics | |
| Geographic scope | |
| Preferred sources | |
| Freshness requirement | |
| Categories | |
| Tone and description length | |
| Required facts | |
| Desired CTA behavior | |
| Rules for missing information | |
| Items needing special review |
You're done when: the brief is filled in and you've run it once.
Day 14: Build the starting collection
Today's outcome: a feed that's actually worth browsing, not just a handful of test posts.
Why this matters: a feed with three posts doesn't feel like a real destination yet.
What to do: create, import, or prepare enough posts that the feed is worth browsing. Fifteen to twenty-five is a reasonable starting range, not a strict requirement. A narrow, focused feed may need fewer. The real test: can a visitor browse and find more than one useful item?
- Current and timely content included.
- A few broadly useful items included.
- Every post has a clear action.
- More than one category represented.
- No expired or repetitive filler.
You're done when: you can honestly check every box above.
End of Phase 2 checkpoint
- Feed configured.
- Categories created.
- First sources evaluated.
- Editorial standards written.
- AI or manual creation process established.
- Starting collection reviewed.
- Every action link tested.
Prefer a printable, fillable copy? Download the Phase 2 PDF below Feedlnk_Phase2_Workbook.pdf (126 KB)