Squidex
  • Welcome to Squidex
  • Getting Started
    • Squidex Cloud
    • Installation Instructions
      • Platforms
        • Install on Kubernetes
        • Install on AWS (Deprecated)
        • Install on AWS EC2 using Docker
        • Install on Azure
        • Install on Azure using ARM
        • Install on Google Cloud Platform (GCP)
        • Install on Docker
        • Install on Heroku
        • Install on IIS
        • Install on Render
        • Install on Vultr
      • Configuration
        • Deploying the Image Resizer Service
      • Troubleshooting and Support
        • Diagnose Runtime Issues
        • Restoring Deleted Apps
      • Install Identity (Deprecated)
      • External Identity Providers
        • Azure AD (OAuth) with Squidex
    • Contributing and Developing
      • Building
      • Developing
      • Extensions
        • Custom Rule Action
      • Contributing
      • Architecture
      • Translating
      • Squidex Docs Program
    • Roadmap
    • Quick Start Guides
      • Vue.js Blog with Squidex
      • React.js Blog with Squidex
      • Angular Blog with Squidex
  • Documentation
    • Introduction and Use Case
    • Concepts
      • Apps
      • Teams
      • Schemas
        • Field Rules
      • Content
        • Scheduled Publishing
      • Assets
        • Querying Assets
      • Localization
      • Migrations
      • Roles & Permissions
      • Rules
        • Publish an Event to Azure Queues using Rules
        • Populate Elasticsearch Index
      • Backups
      • Subscriptions
        • App Subscriptions v/s Team Subscriptions
      • Notifications
      • Dashboard
      • Workflows
    • Software Development Kits
      • TypeScript
      • .NET
        • Version v14 (and Earlier)
        • Version v15 (and Later)
      • PHP
      • Java
    • Developer Guides
      • API
        • Authentication
        • Postman
        • Queries
        • Assets
      • Automation Tools (CLI)
      • Scripting
        • Scripting Helper Methods
      • Embed Content
      • Custom Workflows
      • Custom Editors
      • Custom Sidebars
      • Preview Content
      • Rule Formatting
        • Simple
        • Script
        • Liquid
      • Tutorials
        • Building a Blog with Squidex and Next.js
  • Next
    • Squidex 3.0: API Compatibility
Powered by GitBook
On this page
  • Community
  • Ways to Contribute
  • Reporting Issues
  • User feedback
  • Writing Samples

Was this helpful?

  1. Getting Started
  2. Contributing and Developing

Contributing

Welcome to the Community! If Wou Want to Contribute to Squidex to Build the Most Awesome, Headless CMS, You're in the Right Place!

PreviousCustom Rule ActionNextArchitecture

Last updated 2 years ago

Was this helpful?

Community

The support forum is the primary communication forum for the Squidex community. It's a great place to start, whether you have a question, you're a new contributor, a new user, or anything else. Make sure that you read the posting templates carefully before posting. The Squidex community is also governed by a .

Ways to Contribute

To create a code or documentation contribution, here's a small sample of the type of work that needs doing:

  • Bug squashing and feature development on our .NET Core backend, or Angular framework.

  • .

  • Improving our .

  • and manually testing pull requests.

Non-code Contributions: Some of the most valuable ways to contribute don’t require touching the source code at all. Here are a few of them below:

  • Reporting issues, including both feature requests and bug reports.

  • Giving feedback if you're evaluating or using Squidex.

  • Star us on GitHub, upvote us on product comparison sites, or write for .

Reporting Issues

If you find an easily reproducible bug and/or are experienced in reporting bugs, feel free to just open an issue in our support forum. We've decided to collect all issues in one single place, therefore the issues in Github are now closed.

Reporting Security Issues. Please do not report security issues publicly.

User feedback

Nearly every feature we develop starts with a user request. If you are part of a group that is either using or considering using Squidex, we would love to hear about your experience with the product. If you’re not sure what to write, here are some questions we’re always very curious to know the answer to:

  • Evaluation: What is the process by which your organization chose or will choose a group chat product?

  • Pros and Cons: What are the pros and cons of Squidex for your organization, and the pros and cons of other products you are evaluating?

  • Features: What are the features that are most important for your organization? In the best case scenario, what would your chat solution do for you?

  • Onboarding: If you remember it, what was your impression during your first few minutes of using Squidex? What did you notice about it and how did you feel? Was there anything that stood out to you as confusing, or broken, or great?

  • Organization: What does your organization do? How big is your organization? Can you provide a link to your organization’s website?

  • Cloud or Self-hosted: What do your prefer, the Cloud or an on-premise solution? Can we convince you to move to the Cloud?

Writing Samples

Our main programming language is C# and Typescript. However, Squidex speaks HTTP that can be used with any programming language. We cannot cover all programming languages that are out there in the wild! If you have developed a sample or extension, please share it with us. We would like to make it available for other users as well.

You can email issues to . We create a CVE for every security issue.

code of conduct
Writing an integration
documentation
Reviewing code
Squidex Blog
hello@squidex.io