Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
357 lines (237 loc) · 9.17 KB

CONTRIBUTING.md

File metadata and controls

357 lines (237 loc) · 9.17 KB

🤝 Contributing to Awesome Low-Code/No-Code Platforms

Thank you for your interest in contributing to this repository! This project thrives on community contributions and we welcome everyone who wants to help make this the most comprehensive resource for low-code/no-code platforms.

🌟 Ways to Contribute

🎯 Quick Contributions

  • ⭐ Star this repository to show support
  • 🐛 Report broken links or outdated information
  • 💡 Suggest improvements via issues
  • 🔄 Share on social media to help others discover

📝 Content Contributions

  • ➕ Add new platforms we might have missed
  • 📊 Update platform information (pricing, features, etc.)
  • 🔗 Add useful resources (tutorials, guides, tools)
  • 🌐 Translate content to other languages
  • 📈 Add use cases and success stories

📋 Submission Guidelines

✅ What Makes a Good Addition

For Platforms:

  • Must be actively maintained (updated within last 12 months)
  • Has clear documentation and getting started guide
  • Serves a specific low-code/no-code use case
  • Has a reasonable user base or community
  • Offers something unique or valuable

For Resources:

  • High-quality, informative content
  • Relevant to low-code/no-code development
  • Accessible and well-written
  • Not overly promotional

❌ What We Don't Accept

  • Abandoned or inactive projects
  • Purely promotional content
  • Duplicate platforms already listed
  • Platforms requiring extensive traditional coding
  • Spam or low-quality submissions

📝 How to Add a New Platform

1. Check for Duplicates

Before adding a platform, please:

  • Search the README for existing entries
  • Check open pull requests for pending additions
  • Look through closed PRs for previously rejected submissions

2. Choose the Right Category

Open Source Categories:

  • 🎨 Visual Development: Drag-and-drop app builders
  • 🔄 Workflow Automation: Process and task automation
  • 🗄️ Database & Backend: API builders, headless CMS
  • 🖼️ Frontend Builders: Website and UI builders
  • 📱 Mobile Development: Mobile app builders
  • 🤖 AI/ML Platforms: AI-powered development tools

Commercial Categories:

  • 🏢 Enterprise Solutions: Large-scale business platforms
  • 🚀 Rapid Development: Quick prototyping tools
  • 🔗 Integration Platforms: Automation and connectivity
  • 📊 Data & Analytics: BI and data visualization

3. Use the Correct Format

For Open Source Platforms:

#### [Platform Name](GitHub/Website URL) ⭐ Stars

> Brief, compelling description (max 100 characters)

**Key Features:**

- Feature 1 (be specific and concise)
- Feature 2 (focus on unique capabilities)
- Feature 3 (mention integration options)
- Feature 4 (highlight deployment options)
- Feature 5 (note any special features)

**Best For:** Target use cases and audience

For Commercial Platforms:

#### Platform Name

> Brief, compelling description

**Key Features:**

- Feature 1
- Feature 2
- Feature 3
- Feature 4
- Feature 5

**Pricing:** Starting price or pricing model
**Best For:** Target use cases and audience

4. Required Information

For All Platforms:

  • Accurate and current description
  • Up-to-date feature list
  • Correct categorization
  • Working links

For Open Source Platforms:

  • GitHub star count (if available)
  • License type
  • Self-hosting capability
  • Cloud option availability

For Commercial Platforms:

  • Pricing information (even if "Contact sales")
  • Target user base
  • Deployment options

🔄 How to Submit Changes

Via GitHub Web Interface (Beginner-Friendly)

  1. Fork the Repository

    • Click the "Fork" button at the top of this page
    • This creates your own copy of the repository

  2. Edit the File

    • Navigate to the file you want to edit (usually README.md)
    • Click the pencil icon (Edit this file)
    • Make your changes following the guidelines above

  3. Commit Your Changes

    • Scroll down to "Commit changes"
    • Write a clear commit message (e.g., "Add Appsmith to Visual Development section")
    • Select "Create a new branch" and name it descriptively
    • Click "Propose changes"

  4. Create Pull Request

    • Click "Create pull request"
    • Fill in the pull request template
    • Submit for review

Via Command Line (Advanced)

# 1. Fork the repository (via GitHub web interface)

# 2. Clone your fork
git clone https://github.com/YOUR-USERNAME/Low-Code-No-Code-Platforms.git
cd Low-Code-No-Code-Platforms

# 3. Create a feature branch
git checkout -b add-platform-name

# 4. Make your changes
# Edit README.md or other files

# 5. Commit your changes
git add .
git commit -m "Add [Platform Name] to [Category] section"

# 6. Push to your fork
git push origin add-platform-name

# 7. Create a pull request via GitHub web interface

📋 Pull Request Checklist

Before submitting your pull request, please ensure:

Content Quality

  • Information is accurate and up-to-date
  • Description is clear and concise
  • Features listed are current and relevant
  • Pricing information is accurate (for commercial platforms)
  • Links are working and lead to correct destinations

Formatting

  • Follows the established format exactly
  • Proper markdown formatting is used
  • Alphabetical ordering is maintained within sections
  • Consistent emoji usage
  • No typos or grammatical errors

Technical Requirements

  • Added to the correct category
  • Table of contents updated (if adding new sections)
  • No duplicate entries
  • GitHub star count is accurate (for open source)
  • Links use HTTPS where available

🎨 Style Guidelines

Writing Style

  • Concise but Informative: Get to the point quickly
  • Neutral Tone: Avoid overly promotional language
  • Professional: Use proper grammar and spelling
  • Consistent: Follow the existing style and format

Descriptions

  • Brief: 1-2 sentences maximum
  • Specific: Mention what makes it unique
  • Actionable: Help users understand what they can build

Features

  • Prioritize: List most important features first
  • Specific: Avoid vague terms like "powerful" or "advanced"
  • Quantifiable: Include numbers when relevant (e.g., "100+ integrations")

🔍 Review Process

What Happens After Submission

  1. Automated Checks: Links and formatting are validated
  2. Community Review: Other contributors may provide feedback
  3. Maintainer Review: Final review for quality and accuracy
  4. Merge or Request Changes: Decision communicated via PR comments

Review Timeline

  • Simple additions: 2-5 days
  • Major changes: 5-10 days
  • Complex submissions: 1-2 weeks

Review Criteria

  • Accuracy: Information must be correct and current
  • Relevance: Must fit the repository's scope
  • Quality: High standard for descriptions and formatting
  • Community Value: Must benefit the community

🏷️ Issue Labels

When creating issues or PRs, consider using these labels:

  • new-platform - Adding a new platform
  • update-info - Updating existing platform information
  • broken-link - Reporting broken links
  • enhancement - Suggesting improvements
  • question - Asking for clarification
  • good-first-issue - Good for newcomers
  • help-wanted - Community assistance needed

🤔 Questions?

Before Asking

  • Check if your question is answered in this guide
  • Search existing issues for similar questions
  • Review closed PRs for context

How to Ask

  • Create an Issue: For general questions or discussions
  • Comment on PR: For specific submission questions
  • Discussion Tab: For broader community discussions

Getting Help

  • Community Support: Other contributors often help newcomers
  • Documentation: Most questions are covered in this guide
  • Examples: Look at recent merged PRs for examples

🏆 Recognition

Contributor Benefits

  • Recognition: Your contributions are appreciated and acknowledged
  • Learning: Discover new platforms and technologies
  • Network: Connect with other developers and creators
  • Impact: Help thousands of developers choose the right tools

Hall of Fame

Outstanding contributors may be featured in the repository with special recognition.

📜 Code of Conduct

Our Standards

  • Respectful: Treat all contributors with respect
  • Constructive: Provide helpful, actionable feedback
  • Inclusive: Welcome contributors of all backgrounds and skill levels
  • Professional: Maintain a professional tone in all interactions

Unacceptable Behavior

  • Harassment or discrimination
  • Spam or promotional content
  • Destructive criticism without suggestions
  • Off-topic or disruptive discussions

🙏 Thank You!

Every contribution, no matter how small, helps make this repository better for everyone. Whether you're fixing a typo, adding a new platform, or helping with reviews, your efforts are valued and appreciated.

Happy contributing! 🚀

Questions? Problems? Ideas?
Open an Issue • Start a Discussion • View Contributors