docs: reduce feed directory repetition

Author: gildesmarais

src/content/docs/common-use-cases.mdx

@@ -1,51 +1,47 @@
 ---
 title: "Common Use Cases"
-description: "See how people use html2rss to stay updated with their favorite websites. Real examples for personal and business use cases."
+description: "Use html2rss for common tracking and monitoring workflows."
 ---
 
-Discover how people are using html2rss to take control of their web content consumption. These real-world examples show the power and flexibility of creating custom RSS feeds.
-
----
+Use html2rss when you want updates in a reader instead of checking websites by hand.
 
 ## Personal Use Cases
 
 ### Following Your Favorite Bloggers
 
-Many bloggers don't offer RSS feeds, but you can create them with html2rss. Follow writers you love without relying on social media algorithms.
+Many blogs and creator sites do not publish feeds.
 
-**Example:** Create a feed for a personal blog that only posts to social media.
+**Example:** Follow a newsroom, company blog, or publication section from your own `html2rss-web` deployment.
 
 ### Job Hunting
 
 Track job postings from multiple company websites in one place. Never miss an opportunity again.
 
-**Example:** Follow job boards, company career pages, and industry-specific job sites.
+**Example:** Track a company careers page or a narrower role-specific listing.
 
 ### Local News
 
 Follow your local newspaper or community website to stay informed about your neighborhood.
 
-**Example:** Create feeds for local news sites, community forums, and city government updates.
+**Example:** Subscribe to local news sites, community forums, and city government updates from one reader.
 
 ### Academic Research
 
 Follow new papers and research in your field from multiple sources.
 
-**Example:** Track arXiv submissions, journal publications, and conference proceedings.
+**Example:** Track publication pages, research blogs, and conference updates.
 
 ### Product Updates
 
 Get notified when software you use releases updates, new features, or security patches.
 
-**Example:** Follow product blogs, changelog pages, and release notes.
+**Example:** Track release notes, changelog pages, and product blogs.
 
 ### Hobby Communities
 
 Follow forums, communities, and websites related to your hobbies and interests.
 
-**Example:** Track gaming forums, photography communities, or cooking blogs.
-
----
+**Example:** Track gaming forums, photography communities, or cooking blogs without manually checking each site.
 
 ## Business Use Cases
 
@@ -59,21 +55,19 @@ Track what your competitors are posting about - new products, features, or annou
 
 Follow multiple industry publications in one feed to stay ahead of trends.
 
-**Example:** Aggregate news from industry blogs, trade publications, and thought leaders.
+**Example:** Aggregate trade publications, company blogs, and research updates in one reader.
 
 ### Customer Support
 
 Monitor customer feedback and support requests across different platforms.
 
-**Example:** Track support forums, review sites, and social media mentions.
+**Example:** Track support forums, review sites, and product-update pages that affect your users.
 
 ### Content Marketing
 
 Follow industry influencers and competitors for content inspiration.
 
-**Example:** Track competitor blogs, industry newsletters, and thought leadership content.
-
----
+**Example:** Track competitor blogs, industry newsletters, and thought leadership content in one place.
 
 ## Technical Use Cases
 
@@ -95,20 +89,8 @@ Follow multiple open source projects and their updates.
 
 **Example:** Track project blogs, release notes, and community discussions.
 
----
-
-## Getting Started with Your Use Case
-
-1. **Identify the websites** you want to follow
-2. **Check our [Feed Directory](/feed-directory/)** to see if feeds already exist
-3. **Try the [Web App](/web-application/getting-started)** to create feeds easily
-4. **Learn advanced techniques** with our [Config Guide](/creating-custom-feeds/)
-
----
-
-## Need Help?
+## Next Steps
 
-- **Can't find what you're looking for?** [Browse our Feed Directory](/feed-directory/)
-- **Want to create custom feeds?** [Try the Web App](/web-application/getting-started)
-- **Need advanced features?** [Check our Ruby Gem docs](/ruby-gem/)
-- **Have questions?** [Join our community discussions](https://github.com/orgs/html2rss/discussions)
+- **[Run html2rss-web with Docker](/web-application/getting-started)** to verify your own instance.
+- **[Use automatic feed generation](/web-application/how-to/use-automatic-feed-generation/)** when you want direct page-URL conversion.
+- **[Create custom feeds](/creating-custom-feeds/)** when you need stable, reviewable extraction rules.

src/content/docs/creating-custom-feeds.mdx

@@ -7,14 +7,13 @@ sidebar:
 
 import { Aside, Code } from "@astrojs/starlight/components";
 
-When auto-sourcing isn't enough, you can write your own configuration files to create custom RSS feeds for any website. This guide shows you how to take full control with YAML configs.
+When existing feeds or auto-sourcing are not enough, write a YAML config for the site you want to follow.
 
 **Prerequisites:** You should be familiar with the [Getting Started](/getting-started) guide before diving into custom configurations.
 
 <Aside type="tip" title="Use this guide when you need more control">
-  Start with included feeds first. If your site is not covered, try [automatic feed
-  generation](/web-application/how-to/use-automatic-feed-generation/) next. Reach for a custom config when you
-  need a stable, reviewable setup or the generated feed misses important content.
+  Reach for a custom config when you need stable, reviewable extraction rules or generated output misses
+  important content.
 </Aside>
 
 ---
@@ -29,10 +28,6 @@ When auto-sourcing isn't enough, you can write your own configuration files to c
 - **The website has complex structure** that requires custom selectors
 - **You want to combine data** from multiple sources
 
-**Don't need custom configs?** Check the [Feed Directory](/feed-directory/) first - there might already be a working feed for your website.
-
----
-
 ## Recommended Workflow
 
 1. **Inspect the live page** in your browser developer tools
@@ -217,7 +212,6 @@ there.
 
 **For Beginners:**
 
-- **[Browse the Feed Directory](/feed-directory/)** - See real-world examples
 - **[Run html2rss-web with Docker](/web-application/getting-started)** - Use the newest integrated behavior
 - **[Learn more about selectors](/ruby-gem/reference/selectors/)** - Master CSS selectors
 - **[Submit your config via GitHub Web](https://github.com/html2rss/html2rss-configs)** - No Git knowledge required!

src/content/docs/getting-started.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Getting Started"
-description: "Start html2rss-web locally, verify a working included feed from your self-hosted instance, and decide when to enable automatic generation or move to custom configs."
+description: "Start html2rss-web locally, verify one feed, and decide when to enable automatic generation or move to custom configs."
 sidebar:
   order: 1
 ---
@@ -17,13 +17,12 @@ That guide is the canonical setup flow for:
 
 - running `html2rss-web` locally
 - confirming the interface is working
-- opening a first included feed URL
+- opening a known feed URL
 - deciding when to use automatic generation or custom configs
 
 ## Quick Shortcuts
 
 - **[Run html2rss-web with Docker](/web-application/getting-started)**: recommended first step
-- **[Browse working feed examples](/feed-directory/)**: see what successful outputs look like
 - **[Use automatic feed generation](/web-application/how-to/use-automatic-feed-generation/)**: enable direct feed creation from a page URL when you want that workflow
 - **[Create Custom Feeds](/creating-custom-feeds)**: write configs when you need more control
 - **[Troubleshooting Guide](/troubleshooting/troubleshooting)**: fix startup or extraction problems

src/content/docs/index.mdx

@@ -1,9 +1,9 @@
 ---
 title: "Turn Any Website Into an RSS Feed"
-description: "Run html2rss-web with Docker, verify a working included feed from your self-hosted instance, then consciously enable automatic generation or move to custom configs when you need more control."
+description: "Run html2rss-web with Docker, verify one feed, then enable automatic generation or move to custom configs when you need more control."
 ---
 
-Run `html2rss-web` with Docker, verify a working included feed from your self-hosted instance, and only then decide whether to enable automatic generation or move to custom configs.
+Run `html2rss-web` with Docker, verify one feed from your own instance, then decide whether you need automatic generation or custom configs.
 
 ## Start Here
 
@@ -13,14 +13,8 @@ That guide is the canonical onboarding flow for:
 
 - starting a local instance
 - verifying the web interface
-- opening a first included feed URL
-- deciding when to consciously enable automatic generation or move to custom configs
-
-## How It Works
-
-1. **Run your own local instance** with Docker
-2. **Open a built-in feed URL** from your own instance
-3. **Copy the feed URL into your reader**
+- opening a known feed URL
+- choosing the next path
 
 ## What is html2rss?
 
@@ -36,8 +30,7 @@ Most people should start with the web application:
 ### I want a working instance first
 
 1. **[Run html2rss-web with Docker](/web-application/getting-started)**: recommended starting path
-2. **[Use the included configs](/web-application/how-to/use-included-configs/)**: use real embedded feeds from your own instance
-3. **[Browse working feed examples](/feed-directory/)**: see what working outputs look like
+2. **[Use the included configs](/web-application/how-to/use-included-configs/)**: optional guide for the embedded feed set
 
 ### I need more control
 
@@ -62,7 +55,7 @@ Most people should start with the web application:
 ## Practical Notes
 
 - Start with Docker, not a public instance.
-- Use an included feed to verify the deployment first.
+- Verify the deployment with one known feed first.
 - Enable automatic generation only when you want the direct page-URL workflow and are ready to allow it on your self-hosted instance.
 - Move to custom configs when you need a stable, reviewable setup.
 

src/content/docs/web-application/getting-started.mdx

@@ -10,7 +10,7 @@ import { Code } from "@astrojs/starlight/components";
 import AutoGenerationOptional from "../../../components/docs/AutoGenerationOptional.astro";
 import MinimalDockerCompose from "../../../components/docs/MinimalDockerCompose.astro";
 
-Run `html2rss-web` locally with Docker, open the web interface, and verify that your instance can serve a working included feed before you enable direct feed generation.
+Run `html2rss-web` locally with Docker and verify one included feed before enabling direct feed generation.
 
 ## What You Will Have When This Works
 
@@ -23,7 +23,7 @@ After this guide, you should have:
 
 ## Installation Guide
 
-This guide walks you through a local Docker setup that gives you the most reliable starting point.
+This guide uses a local Docker Compose stack.
 
 ### What You'll Need
 
@@ -50,7 +50,7 @@ Create a file called `docker-compose.yml` in that folder and start with the mini
 
 <MinimalDockerCompose />
 
-This minimal stack intentionally proves the included-feed path first. Add automatic updates, reverse proxying, or your own config file only after this first run works.
+Add automatic updates, reverse proxying, or your own config file after this first run works.
 
 ### Step 3: Start html2rss-web
 
@@ -73,28 +73,16 @@ Then run:
 
 ## First Success Check
 
-At this point, `html2rss-web` should be running.
-
 1. Open `http://localhost:4000`
 2. Confirm the web interface loads
 3. Open one of the included feed URLs from your own instance:
    - `http://localhost:4000/microsoft.com/azure-products.rss`
    - `http://localhost:4000/phys.org/weekly.rss`
    - `http://localhost:4000/softwareleadweekly.com/issues.rss`
 4. Confirm the feed opens
-5. Copy that feed URL into your reader
-
-If that works, the deployment, included-config path, and reader subscription path are working together.
-
-## What To Do First
-
-Start with an included config from your own instance:
-
-1. open a known included feed URL
-2. copy that feed URL into your reader
-3. confirm your reader can subscribe successfully
+5. Copy that feed URL into your reader if you want to keep it
 
-That proves the lowest-friction path before you invest in automatic generation or custom configs.
+If that works, the local app and included-feed path are ready.
 
 ## What Changes If You Enable Feed Generation
 

src/content/docs/web-application/index.mdx

@@ -1,20 +1,19 @@
 ---
 title: "Web Application"
-description: "html2rss-web is the self-hosted web interface and feed server for running included feeds first, then enabling direct generation only when needed."
+description: "html2rss-web is the self-hosted web interface and feed server for included feeds, direct generation, and custom configs."
 sidebar:
   label: "Overview"
   order: 1
 ---
 
-`html2rss-web` is the recommended way to get started. Run it locally with Docker, verify a working included feed from your own instance, and only then decide whether you need token-gated direct generation or custom configs.
+`html2rss-web` is the recommended way to get started. Run it locally with Docker, verify one feed from your own instance, then decide whether you need token-gated direct generation or custom configs.
 
 ## Get Started
 
 Start with **[Getting Started](/web-application/getting-started)** to:
 
 - run your own local instance
 - verify the web interface
-- open a first included feed URL
 - choose the right next step for your site
 
 ## What The Web App Gives You
@@ -31,10 +30,9 @@ The scraping and feed-building engine is provided by the Ruby gem [`html2rss`](h
 ## Recommended Flow
 
 1. **[Getting Started](/web-application/getting-started)**: run the app locally
-2. **[Use the included configs](/web-application/how-to/use-included-configs/)**: start with embedded feed paths from your own instance
-3. **[Browse working feed examples](/feed-directory/)**: compare against existing outputs
-4. **[Use automatic feed generation](/web-application/how-to/use-automatic-feed-generation/)**: enable direct page-URL conversion when you want that workflow
-5. **[Create Custom Feeds](/creating-custom-feeds)**: build a stable custom setup when needed
+2. **[Use the included configs](/web-application/how-to/use-included-configs/)**: use the embedded feed set when it covers your site
+3. **[Use automatic feed generation](/web-application/how-to/use-automatic-feed-generation/)**: enable direct page-URL conversion when you want that workflow
+4. **[Create Custom Feeds](/creating-custom-feeds)**: build a stable custom setup when needed
 
 ## For Integrations