How to Submit a Pull Request to Add New Resources to design-resources-for-developers

Submitting a pull request to add new resources requires forking the repository, editing the README.md file to add a single resource to the appropriate markdown table, and opening a PR with a formatted title like [Resource Name] → [Section Name].

The bradtraversy/design-resources-for-developers repository maintains a curated list of design and UI resources for developers through community contributions. If you have discovered a useful tool that meets the free-resource criteria, submitting a pull request to add new resources follows a lightweight workflow defined in the project's CONTRIBUTING.md guidelines.

Step-by-Step Workflow for Submitting a Pull Request

Fork and Branch the Repository

Begin by forking the repository to your GitHub account. Clone your fork locally and create a descriptive branch name that indicates the resource you plan to add.

git clone https://github.com/<your-username>/design-resources-for-developers.git
cd design-resources-for-developers
git checkout -b add-tailwind-css

Edit the README.md File

Open README.md and locate the appropriate category section for your resource. Each category is organized as a markdown table with columns for the resource name, link, and description. Add a new row following the existing format.

| [Tailwind CSS](https://tailwindcss.com/) | Utility-first CSS framework with built-in dark mode |

Ensure you maintain the table structure with proper pipe (|) delimiters and consistent spacing to prevent rendering errors.

Commit and Push Your Changes

Stage your changes with a clear, descriptive commit message that identifies the resource and target section.

git add README.md
git commit -m "Add Tailwind CSS to CSS Frameworks"
git push origin add-tailwind-css

Contributing Guidelines and Requirements

The repository enforces specific quality controls defined in CONTRIBUTING.md to maintain consistency. Your pull request must satisfy the following requirements:

Requirement	Implementation Details
One resource per PR	Submit separate pull requests for each resource to simplify review and rollback processes. This rule is explicitly stated at line 3 of CONTRIBUTING.md.
Formatted PR title	Use the structure [Resource Name] → [Section Name] (e.g., [Tailwind CSS] → [CSS Frameworks]). This format appears at lines 5-7 of CONTRIBUTING.md.
Resource link in comment	Include a direct comment in the PR description with the format Link: https://example.com to provide reviewers immediate access (lines 8-10 of CONTRIBUTING.md).
Free usage verification	Confirm the resource is genuinely free without hidden fees, subscription traps, or restrictive licensing that would prevent developer use (line 11 of CONTRIBUTING.md).

Open the Pull Request

Navigate to the original bradtraversy/design-resources-for-developers repository and initiate a new pull request against the master branch. Populate the description field with the required link comment and any additional context about the resource's utility.

Example PR comment:

Link: https://tailwindcss.com/

Summary

Submitting a pull request to add new resources to the design-resources-for-developers repository requires adherence to a structured but lightweight workflow:

• Fork and branch the repository before making any edits.
• Modify README.md by adding a single resource to the appropriate markdown table.
• Follow the contributing guidelines strictly: one resource per PR, formatted titles, and verified free usage.
• Include the direct link in your PR description to expedite reviewer verification.

Once merged, your contribution becomes immediately visible in the curated list, helping thousands of developers discover quality design tools.

Frequently Asked Questions

Can I submit multiple resources in a single pull request?

No. The CONTRIBUTING.md guidelines explicitly require one resource per pull request to keep reviews atomic and manageable. Submitting multiple resources forces maintainers to reject the PR or request separation, delaying inclusion. Create separate branches and pull requests for each distinct resource.

What happens if I don't format the PR title correctly?

Pull requests with improperly formatted titles may be overlooked or rejected during triage. The required format [Resource Name] → [Section Name] allows maintainers to instantly categorize submissions without opening the full description. Always verify your title matches the pattern shown in lines 5-7 of CONTRIBUTING.md.

How do I verify that a resource qualifies as "free"?

According to line 11 of CONTRIBUTING.md, you must confirm the resource has no hidden fees, subscription traps, or restrictive licensing. Test the resource by attempting to access core features without payment, review the pricing page for "free tier" clarity, and check the license for commercial use restrictions. Resources requiring email-gated trials or credit cards for "free" access typically do not qualify.

Where should I place the resource in the README.md file?

Locate the appropriate category section that matches the resource's primary function (e.g., CSS Frameworks, Icons, Colors). Each section contains a markdown table; append your resource as a new row at the end of the relevant table. Do not create new sections without prior discussion, and maintain alphabetical order if the existing table uses it.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}