# πŸ«±πŸΌβ€πŸ«²πŸΌ Contributing to Scrollend Polyfill Thank you for considering a contribution to Scrollend Polyfill! Whether you're fixing bugs, suggesting improvements, writing docs, or sharing ideas – your input helps the project grow and evolve. --- ## πŸ’‘ Getting Started - Ensure your contribution aligns with the project's scope and goals. - If you're unsure, feel free to open an [`issue`](https://github.com/igorskyflyer/npm-scrollend-polyfill/issues) or discussion to explore the idea. - For substantial changes, it's best to open a draft pull request early for visibility and feedback. --- ## πŸ› Bugs & Features - **Bug Reports**: use the issue template and label `bug`. - **Feature Requests**: explain your use case clearly and tag with `feature`. - Check issues labeled `help wanted` or `good first issue` if you're looking for inspiration. --- ## πŸ”§ Making a Contribution 1. **Fork** the repository 2. **Clone** your fork and create a new branch `git checkout -b feature/amazing-idea` 3. **Make your changes** with clear commits 4. **Push** your branch and open a pull request Follow the PR template if one is provided, and keep your changes focused and well-described. --- ## πŸ“ Documentation & Content Contributions to documentation, examples, and config files are always appreciated: - keep the tone friendly and consistent, - use clean formatting and descriptive headings, - include helpful comments or instructions where needed. --- ## πŸ“¦ Code Style - follow the formatting and naming conventions already used in the project, - write clear, maintainable code with comments for non-obvious logic, - test your changes if applicable. --- ## πŸ’– Thank You! Your contribution helps maintain and improve Scrollend Polyfill β€” thank you for helping make it better! Check out [`SUPPORT.md`](https://github.com/igorskyflyer/npm-scrollend-polyfill/blob/main/SUPPORT.md) if you need help or want to sponsor its development.
Made with care, curiosity, and creativity.
Igor Dimitrijević (@igorskyflyer)