daily Documentation

1. Project Overview & Quickstart (dailydotdev/daily) Copy Chapter

💜 About daily.dev Copy Chapter

[!IMPORTANT]
Star us to show your support and love for daily.dev ⭐️

daily.dev is a free, open source personalized news feed for developers, used by millions of developers worldwide. It aggregates articles, tutorials, release notes, and news from 2,000+ trusted sources across the web, and personalizes your feed based on the tags you follow (like #webdev, #ai, #devops) and what you read.

You can use daily.dev as a new tab browser extension for Chrome and Edge, as a web app, or with the daily.dev mobile apps for iOS and Android. Beyond the feed, daily.dev is a community: join Squads to share and discuss content with other developers, comment on posts, bookmark what you want to read later, and search across everything.

✨ What you get with daily.dev Copy Section

• 📰 Personalized feed: the best developer content from 2,000+ sources, tuned to your stack via tags and your reading activity
• 🧩 New tab extension: turn every new browser tab into your developer homepage (Chrome and Edge)
• 📱 Mobile apps: the same feed and community on iOS and Android
• 👥 Squads: developer communities for sharing and discussing content with your team or people who share your interests
• 💬 Discussions: comment on posts and learn from how other developers think
• 🔖 Bookmarks and reading list: save posts to read later, wherever you are
• 🔍 Search: find posts, tags, sources, and discussions across the entire network

📌 Get daily.dev Copy Chapter

daily.dev is available as a browser extension for Google Chrome and Microsoft Edge, as a web app, and as a mobile app for iOS and Android.

Get it now on:

📯 Philosophy Copy Chapter

We recognize that developers today have the greatest power as a professional group to drive change and affect the lives of billions. Many platforms provide developers with tools that serve their success or the goals of their workplace, but daily.dev is by design for developers themselves.

We, as developers, know how challenging it is to grow professionally with so much going on, and that's why we built daily.dev: to make it easy for us to navigate the abundant content out there and discover all the knowledge we need with zero effort.

You can use daily.dev to:

• 👨‍💻 Learn and stay up-to-date

• 🙌 Interact based on the latest trends in our ecosystem

• 🚀 Collaborate with other developers you know and appreciate

❓ FAQ Copy Chapter

Is daily.dev free?

Yes. The core daily.dev experience (the personalized feed, extension, mobile apps, Squads, bookmarks, and search) is free. There is an optional paid subscription, daily.dev Plus, that adds power features on top.

Is daily.dev open source?

Yes. daily.dev is open source under the AGPL-3.0 license. This repository is the central hub, and the frontend applications (extension and web app) live in dailydotdev/apps.

What are we doing to ensure daily.dev is safe?

The browser extension only replaces your new tab page. It never tracks your browsing on other websites, never reads or modifies content on other pages, never accesses your browsing history, and never injects scripts into any website. It requests only the permissions it needs, and because daily.dev is fully open source, you can verify all of this in the code yourself. Your data is never sold.

How does daily.dev make money?

daily.dev is an ad-supported business. The feed includes clearly marked native ads from developer-relevant brands, which is what keeps daily.dev free for the community. If you want to reach developers on daily.dev, see business.daily.dev.

Which platforms does daily.dev support?

Browser extension for Google Chrome and Microsoft Edge, a web app at daily.dev, and native mobile apps for iOS and Android.

How does the feed personalization work?

You pick the tags and sources you care about (for example #react, #kubernetes, #ai), and the feed learns from what you read, upvote, and bookmark. You stay in control: you can follow or block tags and sources at any time, and switch between personalized and popular feeds.

How is daily.dev different from dev.to or Hacker News?

They solve different problems. dev.to is a blogging community where most content is written on the platform itself. Hacker News is a single shared ranked list of tech and startup links, the same for everyone. daily.dev aggregates developer content from 2,000+ sources across the web and personalizes the feed to your stack, with communities (Squads) built around it. Many developers use daily.dev alongside these platforms.

How do I report a bug or request a feature?

Open a bug report or start a feature request discussion right here in this repository.

🌲 daily.dev projects Copy Chapter

daily.dev might look simple on the surface, but actually, it is powered by a complex and robust system of different applications. It contains several services, some are big, others are micro and easy to maintain. Below is the list of different projects that we maintain under daily.dev.

🙌 Community & Docs Copy Section

• daily - This is the repository you are currently at. It serves as a central place for all the projects. It contains documentation, community ideas, suggestions, and whatnot.

• docs - This is the repository for official product documentation of daily.dev.

• awesome-developer-essentials - A community-curated list of essential resources for developers, maintained by the daily.dev team.

🎨 Frontend Copy Section

• apps - Monorepo with all the frontend-related projects since daily.dev 3.0. This includes both the extension and the webapp.

🎈 Others Copy Section

• action-devcard - GitHub Actions for adding daily DevCard to GitHub profile. Read the guide to set it up.

🚀 Running daily.dev locally Copy Chapter

[!NOTE]
Currently, not all services are ready (or needed) for local environments, so Daily Redirector, Daily Monetization, and Authentication services are not available for you.

To spin up a local environment, you will need Docker. Do the steps below and you should be able to start trying to center a div:

• Fork the apps repo: https://github.com/dailydotdev/apps
• Pull it locally
• Run docker compose up
• Apply all migrations by running docker compose exec daily-api node ./node_modules/typeorm/cli.js migration:run -d src/data-source.js
• Once done, seed your local data by running docker compose exec daily-api node ./bin/import
• Then lastly, run npm run dev:oss
• The app should run at http://localhost:5002/

🙌 Want to contribute? Copy Chapter

We are open to all kinds of contributions. If you want to:

• 🤔 Suggest a feature

• 🐛 Report an issue

• 📖 Improve documentation

• 👨‍💻 Contribute to the code

You are more than welcome. Before contributing, kindly check our guidelines.

💬 What do you think of daily.dev? Copy Chapter

[](https://twitter.com/dailydotdev/)  Follow @dailydotdev to share your thoughts and stay up-to-date. 
[](https://www.producthunt.com/products/daily-dev)  Check out our Product Hunt page.
[](https://daily.dev)  Visit our home for a bunch of useful links.
[](https://chromewebstore.google.com/detail/dailydev-where-developers/jlmpjdjjbgclbocgajdjefcidcncaied)  See our Chrome Store page to grab the extension or share your feedback.
[](https://microsoftedge.microsoft.com/addons/detail/dailydev-the-homepage-/cbdhgldgiancdheindpekpcbkccpjaeb)  Check us out on Microsoft Edge Addons and let us know your thoughts.

📑 License Copy Chapter

Licensed under AGPL-3.0.

[

2. Official Technical Reference & Guides (dailydotdev/docs) Copy Chapter

File: README.md Copy Chapter

🎯 Overview Copy Chapter

This repository contains the comprehensive documentation for daily.dev, designed to help our community members get the most out of the platform. The documentation covers everything from getting started to advanced features and contribution guidelines.

✨ Key Features Copy Section

• Comprehensive Guides: Complete coverage of daily.dev features and functionality
• Algolia Search: Fast, integrated search across all documentation
• Dark/Light Mode: Theme toggle for comfortable reading
• Responsive Design: Optimized for all devices
• Edit Links: Direct GitHub integration for community contributions
• Fast Performance: Built with Docusaurus 3 for optimal speed

📊 Performance Metrics Copy Chapter

Our documentation site is optimized for speed and performance:

🚀 Quick Start Copy Chapter

Prerequisites Copy Section

• Node.js: v20.12 or higher
• npm: v7.0 or higher (or yarn/pnpm equivalent)

Development Setup Copy Section

# Clone the repository
git clone https://github.com/dailydotdev/docs.git
cd docs

# Use correct Node version (if using nvm)
nvm use

# Install dependencies
npm install

# Start development server
npm start

The site will be available at http://localhost:3000 with hot reload enabled.

🛠️ Developer Experience Copy Section

One-Click Setup:

VSCode Integration:

# Recommended extensions are auto-suggested
# Settings and tasks are pre-configured in .vscode/
code .

Development Tools:

• 🔥 Hot reload with instant feedback
• 🔍 Built-in link validation
• 📝 MDX syntax highlighting
• 🎨 Real-time preview
• 🧪 Integrated testing with Playwright

📋 Available Scripts Copy Chapter

🐳 Docker Development Copy Chapter

Using Docker Compose Copy Section

docker compose up --build

Using Pre-built Image Copy Section

docker run -p 3000:3000 francescoxx/dailydev-docs:0.19.0

Both methods serve the site on http://localhost:3000.

🧪 Testing & Quality Assurance Copy Chapter

Running Tests Copy Section

The project uses Playwright for end-to-end testing and additional quality assurance processes:

# Run Playwright tests
npm test

# Run tests in headed mode (with browser UI)
npm run test:headed

# Run tests with Playwright UI
npm run test:ui

# Build test (validates all content can be built)
npm run build

# Code linting and formatting
npm run lint
npm run format:check

Quality Checks Copy Section

• Content Validation: All markdown files are validated during build
• Link Validation: Internal links are checked during build process
• Performance Testing: Lighthouse CI can be run on built site
• Accessibility Testing: Built-in Docusaurus accessibility features
• SEO Validation: Meta tags and structured data are automatically generated

Continuous Integration Copy Section

The project uses GitHub Actions for:

• Build Verification: Ensures all changes build successfully
• Link Checking: Validates all documentation links
• Performance Monitoring: Lighthouse scores on pull requests
• Automated Deployment: Builds and deploys to production

Local Quality Checks Copy Section

# Check for broken links locally
npm run build && npm run serve
# Then manually test critical pages

# Validate markdown formatting
# Use your preferred markdown linter or IDE extensions

# Performance testing
# Use browser dev tools or Lighthouse extension

🏗️ Architecture Copy Chapter

This documentation site is built using modern web technologies:

• Docusaurus 3: Static site generator with React-based theming
• React 18: Component framework for interactive elements
• MDX: Markdown with JSX support for rich documentation
• Algolia Search: Fast, integrated search functionality

📁 Project Structure Copy Section

docs/
├── docs/                   # Documentation content (Markdown files)
├── src/
│   ├── components/        # React components
│   ├── pages/            # Custom pages
│   └── css/              # Global styles
├── static/               # Static assets (images, icons)
├── docusaurus.config.js  # Site configuration
└── sidebars.js          # Navigation structure

🤝 Contributing Copy Chapter

We welcome contributions from the community! Here's how you can help:

📝 Documentation Contributions Copy Section

1. Fork the repository
2. Create a new branch for your changes
3. Edit or add documentation in the docs/ directory
4. Test your changes locally with npm start
5. Submit a pull request with a clear description

🐛 Bug Reports & Feature Requests Copy Section

• Use GitHub Issues to report bugs or request features
• Provide detailed information and steps to reproduce
• Include screenshots when applicable

📋 Contribution Guidelines Copy Section

• Clear Documentation: Write clear, concise, and helpful content
• Consistent Style: Follow existing formatting and tone
• Test Changes: Ensure your changes work locally before submitting
• Descriptive PRs: Include meaningful commit messages and PR descriptions

🔍 Review Process Copy Section

Our review process ensures high-quality documentation:

1. Automated Checks: All PRs trigger automated builds and link validation
2. Content Review: Team members review for accuracy, clarity, and completeness
3. Technical Review: Changes are tested locally and validated against live site
4. Approval Requirements:
   • At least one team member approval required
   • All automated checks must pass
   • No merge conflicts or failing builds
5. Merge Timeline: Most PRs are reviewed within 48 hours during business days

Review Criteria:

• Content accuracy and helpfulness
• Consistent formatting and style
• Working links and references
• Mobile-friendly formatting
• SEO optimization (headings, meta descriptions)

🔧 Troubleshooting Copy Chapter

Common Issues Copy Section

Node version conflicts:

nvm use  # Use the version specified in .nvmrc
npm list  # Check installed packages

Port already in use:

npm start -- --port 3001  # Use a different port
lsof -ti:3000 | xargs kill -9  # Kill processes using port 3000

Build errors:

npm run clear  # Clear Docusaurus cache
npm install    # Reinstall dependencies
rm -rf node_modules package-lock.json && npm install  # Clean reinstall

Memory issues during build:

NODE_OPTIONS="--max-old-space-size=4096" npm run build  # Increase memory limit

Permission errors:

sudo chown -R $(whoami) ~/.npm  # Fix npm permissions
npm cache clean --force  # Clear npm cache

Algolia search not working:

# Check if ALGOLIA_APP_ID and ALGOLIA_API_KEY are set
npm run build  # Search only works in production build

Hot reload not working:

npm run clear  # Clear cache
npm start -- --no-minify  # Disable minification

Docker build failures:

docker system prune -a  # Clean Docker system
docker build --no-cache .  # Build without cache

Getting Help Copy Section

• Check existing Issues
• Visit daily.dev for general support
• Review Docusaurus troubleshooting for framework-specific issues

Thank you to our contributors! Copy Chapter

📄 License Copy Chapter

This project is licensed under the AGPL-3.0 License.

File: docs/customize-your-feed/density.md Copy Chapter

sidebar_position: 2 Copy Chapter

Density Settings

The density option enables you to set the density of content on the daily.dev feed. Choose from Eco, Roomy, and Cozy options to personalize your reading experience.

Eco Density Setting Copy Chapter

Set the density of your feed to Eco, as shown below:

Roomy Density Setting Copy Chapter

Set the density of your feed to Roomy, as shown below:

Cozy Density Setting Copy Chapter

Set the density of your feed to Cozy, as shown below:

File: docs/customize-your-feed/layout.md Copy Chapter

sidebar_position: 0 Copy Chapter

Layout Options

The layout option lets you select how posts are displayed on your daily.dev feed. Switch between Grid mode and List mode to suit your viewing preferences.

To switch between Grid and List mode, click on the customize option from the top-right profile menu, as shown below:

Grid Mode Copy Chapter

The Grid mode displays posts as cards arranged in a grid format, as seen in the image below:

In Grid mode, posts are positioned both vertically and horizontally, making it easy to scan and interact with the content. Grid mode adapts seamlessly to various viewports and orientations, providing consistency across different platforms and screen sizes.

List Mode Copy Chapter

In List mode, posts are stacked vertically in a list, as shown below:

List mode displays posts in a simple, stacked format, showing only source images without cover images. This option is ideal if you prefer a shorter feed with fewer visuals.

File: docs/customize-your-feed/preferences.md Copy Chapter

sidebar_position: 3 Copy Chapter

Preferences Settings

The preferences options allow you to fine-tune your daily.dev experience by toggling various features on or off. Currently, available options include:

• Show reading streaks
• Open links in a new tab
• Show custom shortcuts
• Show feed sorting menu
• Enable companion

Accessibility Copy Section

• Automatically dismiss notifications

Show Reading Streaks Copy Chapter

By default, daily.dev displays your reading streaks in the top right corner of your feed. If you’d prefer to hide your reading streaks, set the Show reading streaks toggle switch to off.

Open Links in a New Tab Copy Chapter

When you click a post link on your feed using the Read post button, daily.dev will open that post in a new tab by default. To have posts open in the current tab instead, set the Open links in new tab toggle switch to off.

Show Custom Shortcuts Copy Chapter

Enable this option to access custom shortcuts at the top center of your feed.

Show Feed Sorting Menu Copy Chapter

Turning this toggle switch on adds a dropdown menu to the My Feed and Popular Feed sections, enabling sorting by Date or by Recommended, as shown below:

Enable Companion Widget Copy Chapter

Switching this toggle to on activates the companion widget for daily.dev, while setting it to off deactivates the widget.

The companion widget enhances your experience by allowing you to bookmark, comment, and upvote directly on the original post. To activate this widget, click on the companion button in the top-right corner of the daily.dev menu bar, as seen below:

Then click on the Activate companion button in the description box:

You will then be asked to grant additional permissions to display the companion widget directly on the original post.

File: docs/customize-your-feed/theme.md Copy Chapter

sidebar_position: 1 Copy Chapter

Theme Options

The theme option allows you to change the look and feel of daily.dev by selecting from the available themes. Currently, you can choose from:

• Dark theme
• Light theme
• Auto theme

Dark Theme (Default) Copy Chapter

The Dark theme reduces eye strain and applies mostly dark surfaces across the UI, as shown below:

Dark theme balances light emissions with the minimal contrast required for readability. Additionally, the Dark theme can help conserve battery, extending device usage.

You can set the Dark theme for daily.dev as illustrated here:

Light Theme Copy Chapter

The Light theme uses a white or light background, offering a clean and professional appearance. This theme provides clear, readable content, allowing easy navigation and a smooth reading experience on daily.dev.

You can set the Light theme for daily.dev, as seen below:

Auto Theme Copy Chapter

The Auto theme option automatically adjusts the daily.dev theme to match your browser's theme setting, toggling between Light and Dark as per your browser configuration.

File: docs/for-content-creators/claiming-ownership-on-article.md Copy Chapter

sidebar_position: 3 Copy Chapter

Special Features for Content Creators on daily.dev

Who is This Guide For? Copy Chapter

Do you write blog posts for developers?

Have you seen your blog post picked up by the daily.dev feed?

Are you curious about how much traffic your post received through daily.dev?

If you answered yes to these questions, this guide is for you!

Introducing New Features for Content Creators Copy Chapter

This guide covers:

1. Why claim ownership of posts you've written
2. How to claim ownership of your posts
3. How to get your content featured on daily.dev

Why Claim Ownership of a Post You Wrote? Copy Chapter

Get Notified When Your Post is Listed on daily.dev Copy Section

Writing for an audience is all about engagement. Getting notified in real-time when your post is listed allows you to interact with readers and foster discussions about your content. This helps you increase readership and build stronger relationships with your audience.

Get an Exclusive Author Badge Copy Section

When you comment on a post you wrote, your exclusive author badge will appear next to your name—a small but impactful way to recognize your contribution.

See it in action:

Get an Analytics Report for Every Listed Post Copy Section

Curious about your blog post’s stats? Posts picked up by daily.dev come with a complete analytics report, typically provided within 24 hours.

Gain Reputation Points and Build Your Profile Copy Section

As mentioned in our previous announcements, here’s a quick reminder about What is reputation? How do I earn it?

We’ve redesigned the profile to feature a special section for your posts. For every upvote your post earns, you’ll receive a +1 reputation point, which helps build your reputation on daily.dev.

How to Claim Ownership of Posts You Write Copy Chapter

:::note
Note: We can only add posts that have been picked up by daily.dev. Not sure if your post appeared in our feed? Try searching its headline.
:::

1. Ensure your post’s HTML contains the twitter:creator meta tag within the <head> section, e.g., <meta name="twitter:creator" content="@username" /> where @username is your Twitter username.
2. Go to your profile on daily.dev.
3. Click Account details.
4. Add your Twitter handle.
5. Contact us or email [email protected].

How to Get Your Content Featured on daily.dev Copy Chapter

For a step-by-step guide, check out our how to get featured on daily.dev guide.

File: docs/for-content-creators/content-guidelines.md Copy Chapter

sidebar_position: 1 Copy Chapter

Content Guidelines for daily.dev

Introduction Copy Chapter

Welcome to our content guidelines! This document is your comprehensive guide to understanding the core principles and standards that shape content on our platform. Whether you’re a content creator, developer, or enthusiast, these guidelines reflect our commitment to quality, innovation, and ethics. To learn more about how to feature your content on daily.dev, see the guide on getting featured.

In this document, you’ll find detailed guidance on what content we look for, what we prioritize, and the conditions under which we might remove content. These guidelines provide a reference for anyone who creates or submits content to daily.dev and insight into our dedication to a respectful, diverse, and valuable community.

Take a moment, dive in, and let's build an inspiring space together!

:::tip
Aligning your content with our standards enhances our community’s quality and builds your reputation as a trusted source of knowledge. Non-compliance may lead to reduced reputation points. For more on reputation, see our reputation guide.
:::

What Content Are We Looking For? Copy Section

✅ Relevant, fresh, and up-to-date content for developers.

✅ Professional and well-produced textual or video content.

✅ Innovative, trending content that inspires developers.

✅ Content adhering to ethical publishing practices.

✅ Content from sources that publish regularly.

✅ Content from established sources with substantial published material.

✅ Clear distinction between sponsored and editorial content.

✅ Professional and constructive content

:::info
To maintain a balanced content inventory, we’re temporarily prioritizing niche sources. This helps us provide diverse and unique topics for our developer community. Mainstream content may be subject to more rigorous review to ensure a balanced mix.
:::

When Will We Reject, Ban, or Remove Content? Copy Section

❌ Content irrelevant to developers.

❌ Content used primarily for self-promotion.

❌ Non-English content.

❌ Content from inactive sources (three months or more without updates).

❌ Clickbait or misleading content that lacks substantial value.

❌ Content from sources without a publicly accessible RSS or Atom feed.

❌ Politically-oriented content.

❌ Content generated through programmatic SEO or methods that populate content automatically.

❌ AI-generated content, automated algorithms, or content with characteristics typical of AI-generated material.

❌ Content that is illegal, explicit, offensive, or incites discrimination or violence.

❌ Content violating privacy rights or using shortened or redirected URLs.

❌ Content unsuitable for daily.dev's business reputation.

❌ Content infringing third-party rights, including copyright, trademarks, or other IP rights.

✋ For personal or corporate blogs: Additional terms apply. See below for details.

Additional Guidelines for Corporate Blogs Copy Section

:::info
[Update January 2024] Corporate blogs are no longer eligible as sources on daily.dev. We encourage corporations to open a Squad on our platform instead. We will gradually migrate existing corporate blogs to Squads to adhere to these guidelines.

Learn more about why we're transitioning company sources to Squads.
:::

Additional Guidelines for Personal Blogs and Indie Content Creators Copy Section

:::info
[Update January 2024] Personal blogs are no longer eligible to be added as sources on daily.dev. Instead, personal bloggers and content creators are encouraged to create a Squad to share content with our community. We’ll transition existing personal blogs to Squads gradually.
:::

Update Regarding AI-Generated Content Copy Section

At daily.dev, we emphasize human insight, expertise, and lived experiences in content creation. We value the unique perspectives and nuanced understanding human authors bring, which strengthens the authenticity and quality of information on our platform. AI-generated content, while advancing in quality, doesn’t meet our standard for human insight, and we prioritize human-created content to maintain genuine engagement.

We appreciate your understanding and adherence to this policy.

Legal Information Copy Chapter

Please note that Daily Dev Ltd. does not claim ownership or copyright over any submitted content. Our team reviews all content for guideline compliance. If a claim arises (e.g., copyright infringement or guideline violation), we may remove the content and restrict future submissions from the offending user. Any community found in violation of these guidelines may be suspended or terminated. All platform interactions, including content publication, are governed by our Privacy Policy and Terms of Service. You can report content that may infringe on our policies at any time.

File: docs/for-content-creators/how-to-get-featured.md Copy Chapter

sidebar_position: 0 Copy Chapter

How to Get Featured on daily.dev

Overview Copy Chapter

We're thrilled you're interested in sharing your content on our platform. This guide explains the various ways to feature your content on daily.dev. Whether you're an individual developer, content creator, or representing a company, these pathways help you reach and engage with our diverse and vibrant developer community.

Methods to Feature Your Content on daily.dev Copy Chapter

There are three primary ways to have your content featured on daily.dev:

1. Start a Squad: A Squad is a group where you and other developers can come together around your content on daily.dev. Think of Squads as developer-specific online groups where you can publish content, share with the community, and build a following.
2. Suggest a Source: daily.dev collects posts from various unique sources across the web. All sources are added based on community requests, reflecting our community-driven approach.
3. Direct Posting: You can now contribute content directly by clicking "New Post" anywhere on daily.dev. This replaced the previous Community Picks system, making content contribution simpler and more direct.

Eligibility and Ideal Users for Each Method Copy Chapter

:::note
Remember, all featured content must adhere to our content guidelines regardless of the submission method.
:::

1. Starting a Squad Copy Section

Create a Squad on daily.dev to actively engage with the community by sharing your content. This feature is ideal for individual creators, professional bloggers, and companies aiming to grow their audience on daily.dev.

As a Squad leader, you’ll create a dedicated space for your content, interact with Squad members, and build a community around your shared interests or expertise. Whether you’re an individual blogger, a tech influencer, or a corporate entity, starting a Squad can significantly amplify your reach within the developer community.

→ Learn more about Starting a Squad

2. Suggesting a Source Copy Section

If you’re the owner of a prominent publication or a developer-focused blogging platform, you can submit your platform to be a content source on daily.dev. This method is designed for established tech and developer publications. By submitting your platform, the content you produce is automatically considered for featuring, increasing visibility. Please note, this method excludes corporate and personal blogs to maintain diversity and community focus.

→ Learn more about suggesting a source

3. Direct Posting Copy Section

Direct posting on daily.dev is open to all users, offering a simple way to share and promote content directly. Simply click "New Post" anywhere on the platform to contribute your content. This system replaced Community Picks in 2025, making content contribution more streamlined while giving contributors more credit and visibility. Your content is attributed directly to your profile, helping you build your following and reputation.

→ Learn more about the transition from Community Picks

Wrap Up Copy Chapter

Getting your content featured on daily.dev is a straightforward process. Each method - Starting a Squad, Submitting a Source, or Direct Posting - serves different goals and needs. Choose the method that aligns best with your content strategy and audience.

Adhering to our content guidelines is crucial to ensure a positive, constructive environment for all daily.dev members. By following these steps, you can effectively showcase your content and engage with a dynamic community of developers and tech enthusiasts.

File: docs/for-content-creators/suggest-new-source.md Copy Chapter

sidebar_position: 2 Copy Chapter

How to Suggest a New Source on daily.dev

Introduction Copy Chapter

We're delighted you’re interested in adding valuable content to daily.dev. Our platform continuously grows with community-recommended sources. If you’ve discovered a source that could benefit daily.dev, but it’s not currently listed, we invite you to suggest it.

:::caution
Please review our content guidelines before suggesting a new source. These guidelines are essential to our content review process, ensuring high-quality, relevant, and ethical content. Understanding and following these guidelines will improve the chances of your suggestion being accepted, helping us make daily.dev an exceptional resource.
:::

Prerequisites Copy Section

1. Familiarize yourself with our content guidelines.
2. Register on daily.dev.
3. Ensure your publication has a public RSS feed.
4. Confirm the source is a well-known publication or developer blogging platform.
5. Corporate and personal blogs are not eligible. Consider starting a Squad instead.

:::note
Some existing sources may not fully align with our updated criteria. We are gradually migrating relevant sources to Squads to ensure alignment with current standards.
:::

How to Submit Your Source Copy Section

1. Access your feed through the browser extension or the web app.
2. Sign up or log in.
3. Select Suggest new source from the top-right in the Sources section, as shown below:
4. Enter the URL of your publication's RSS feed (preferred) or homepage.
5. Click Check link.
6. Select the relevant RSS feed if multiple options appear.
7. Click Submit for review.

Review Process Copy Section

Our team manually reviews each submission to ensure compliance with our content guidelines. The review process may take up to 30 days.

You’ll receive email notifications:

1. Confirming your source request submission.
2. Informing you of your source’s approval or rejection.
3. If further information is needed, our team will contact you directly at [email protected].

FAQ Copy Chapter

What Happens After Approval? Copy Section

Once approved, new posts from your source will be automatically collected, analyzed, and potentially added to the feed. Note that historical content is not auto-populated from newly approved sources; only content published after approval will be considered. Please allow a few days for full synchronization.

Is Approval Permanent? Copy Section

We continuously monitor new sources to maintain content quality. Misuse of the platform may result in the disqualification of an approved source.

Can I Resubmit a Rejected Source? Copy Section

Yes, but only after making significant changes. For further assistance, contact [email protected].

How to Track the Review Process? Copy Section

Review status updates are communicated via email notifications. We appreciate your patience during this process.