When contributing to the Feature Requests and Improvements category, it's important to focus on making posts that are actionable and conducive to the development of the Cuemby Cloud Platform. To maintain the quality and relevance of discussions, please avoid the following in your posts:

• Subjective or open-ended posts: Avoid posts that do not prompt a specific action or improvement, such as “What’s your favorite feature?” Such inquiries do not generate actionable feature requests or improvements.

Rhetorical or hypothetical questions: Refrain from posting questions where the answer is already implied or where you are exploring hypothetical scenarios without practical relevance, such as “What if we had unlimited resources?”

Posts that do not seek to solve a specific problem:  Ensure your post is aimed at addressing a real issue or need within the platform, rather than sharing general curiosities or opinions, like “I’m curious if others think we should change this.”

Rants or non-constructive criticism: Posts should not serve as a venting mechanism. For example, avoid statements like “This feature is poorly designed, don’t you agree?” Instead, offer constructive feedback and specific suggestions for improvement.

• Posts that duplicate existing discussions: Before making a post, check if there is already an active discussion about the same feature or improvement. This helps prevent fragmentation of ideas and keeps the conversation focused.

Additionally, please ensure your posts adhere to the following guidelines to foster productive and respectful discussions:

• Keep responses on-topic:  Responses should directly address the original post. Do not shift the discussion to unrelated topics or expand it beyond the scope of the initial request.
• Avoid commenting within answers: If you need to respond to another user’s post, use the comment feature rather than posting an answer. This keeps the thread organized and focused.
• Provide complete answers: While linking to external resources for further reading is helpful, ensure that your answer stands on its own with a clear and complete explanation. Links should support your contribution, not substitute it.

By adhering to these guidelines, you will help ensure that the Feature Requests and Improvements category remains a productive space for fostering innovation and practical enhancements to the Cuemby Cloud Platform.

Answers should not add or expand questions. Instead, either edit the question or add a comment.

Answers should not comment other answers. Instead add a comment on the other answers.

Answers shouldn't just point to other questions. Instead add a comment indicating "Possible duplicate of...". However, it's fine to include links to other questions or answers providing relevant additional information.

Answers shouldn't just provide a link a solution. Instead provide the solution description text in your answer, even if it's just a copy/paste. Links are welcome, but should be complementary to answer, referring sources or additional reading.

Answers should not start debates This community Q&A is not a discussion group. Please avoid holding debates in your answers as they tend to dilute the essence of questions and answers. For brief discussions please use commenting facility.

When a question or answer is upvoted, the user who posted them will gain some points, which are called "karma points". These points serve as a rough measure of the community trust to him/her. Various moderation tasks are gradually assigned to the users based on those points.

For example, if you ask an interesting question or give a helpful answer, your input will be upvoted. On the other hand if the answer is misleading - it will be downvoted. Each vote in favor will generate 10 points, each vote against will subtract 2 points. There is a limit of 200 points that can be accumulated for a question or answer per day. The table given at the end explains reputation point requirements for each type of moderation task.