# Contributing to Awesome Free Developer Resources

Thank you for helping make this directory more useful, accurate, and accessible for developers!

We welcome new resources, corrections, updated descriptions, and reports of broken or outdated links.

## Before you contribute

1. Read the [README](README.md) and search for the resource to avoid duplicates.
2. Check existing issues and pull requests to see whether the change has already been proposed.
3. Prefer official product homepages, official documentation, or original project repositories over tracking links, URL shorteners, and third-party mirrors.
4. Confirm that the resource is relevant to developers and offers genuine free or open-source access.

## Adding a resource

1. Choose the most relevant existing category in `README.md`. Suggest a new category only when the resource does not fit an existing one.
2. Use the official resource name and link directly to its official website or documentation.
3. Write a concise, neutral, one-sentence description of what it does.
4. Clearly identify its access model when relevant: **open source**, **free**, **free tier**, or **paid features**.
5. Verify that the URL works and that the description and free-access claim are accurate.
6. Add your entry using the table format used in the relevant README section.

### Resource table format

```markdown
| Resource                                                                                    | Description                                                                                                                                             |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Awesome Free Developer Resources](https://github.com/Sujon-Ahmed/free-developer-resources) | A curated directory of developer tools, APIs, design assets, frameworks, hosting options, and learning materials; includes free and freemium resources. |
```

The example above demonstrates formatting; please replace it with the **new resource you are contributing**. If the target README section uses a different structure, follow that section's existing style rather than introducing an inconsistent table.

## Submitting a pull request

1. Fork the repository and create a branch for your change.
2. Edit `README.md` (or the relevant repository file), keeping the existing layout and ordering consistent.
3. Review your changes for duplicate entries, spelling, working links, and accurate descriptions.
4. Commit your changes with a clear message, such as `docs: add free API testing resource`.
5. Open a pull request and briefly describe what you added, changed, or removed, and why.

For larger reorganizations or new categories, consider opening an issue first to discuss the proposed structure.

## Editorial guidelines

- Include only lawful, generally useful, developer-relevant resources.
- Distinguish access models accurately:
  - **Open source:** The source code is available under an open-source license; check the license for terms.
  - **Free:** Core use is available without payment (subject to any stated limits).
  - **Free tier:** A usable no-cost plan exists but may have usage, feature, or account limits.
  - **Paid features:** Some features or higher limits require payment.
- Do not describe a time-limited trial as a permanent free tier.
- Avoid duplicate entries, exaggerated claims, promotional language, referral links, and affiliate links.
- Use official product names and clear, respectful English.
- Do not add pirated software, unauthorized downloads, or links that facilitate illegal activity.
- Respect copyright, licenses, and trademarks. A free download does not necessarily permit commercial reuse.
- If a service shuts down, changes its URL, or removes its free offering, update the entry or propose its removal.
- Do not include personal access tokens, credentials, private account information, or other secrets in contributions.

## Fixing existing entries

Corrections are welcome, including:

- Replacing outdated links with official working URLs.
- Updating descriptions, free-tier limitations, or licensing information.
- Correcting spelling and formatting.
- Moving a resource to a more appropriate category.
- Removing resources that are unavailable, misleading, or no longer qualify.

Please keep unrelated changes out of the same pull request where practical.

## Reporting broken links or outdated resources

Open a [GitHub issue](https://github.com/Sujon-Ahmed/free-developer-resources/issues) and include:

- **Resource name** and **current URL**.
- **Problem:** broken link, redirect, discontinued service, changed pricing/free tier, or inaccurate description.
- **Replacement official URL**, if you have one.
- Any brief supporting context that helps maintainers verify the report.

You can also submit a pull request with a verified fix.

## Code of conduct

Be constructive and respectful in issues, pull requests, and reviews. Discuss the resource or proposed change rather than the contributor. Maintainers may decline contributions that do not meet these guidelines.

Thank you for contributing!
