Documentation Feedback Guidelines
    • Dark
      Light
    • PDF

    Documentation Feedback Guidelines

    • Dark
      Light
    • PDF

    Article summary

    Rocket.Chat values the accuracy and relevance of its documentation to ensure users and developers can effectively utilize the platform. Maintaining top-notch documentation is a collaborative effort involving the readers, users, and the documentation team. As a result, we welcome your feedback to help us improve.

    Here’s how you can leave feedback on the Rocket.Chat documentation:

    1. Feedback prompt: At the end of each document, there is a prompt asking if the document was helpful, with options for "Yes" or "No."

    2. Positive feedback: If you select "Yes," you will be prompted to leave a comment. We urge you to provide your email address so our team can contact you for further clarification if needed and to keep you informed about the status of your feedback.

    3. Constructive criticism: If you select "No," you will see prepared options from which you can choose. If these options don’t fully capture your feedback, you can leave a comment and provide an optional email address to be notified of any updates.

    When you submit the feedback, the documentation team will be notified and make adjustments as needed.

    Your email address is secure with us. It will only be used to notify you about the changes you requested and will not be shared or used for any other purposes without your explicit approval.

    Feedback template

    Follow the guide below to submit your feedback.

    1. What is the current behavior?

      Please provide detailed steps for reproducing the current behavior.

    2. What is the expected behavior?

    3. New documentation request.

      Please provide any relevant information, including links to hosted images or videos, explaining how we can best use your feedback.

    Keeping Rocket.Chat documentation up-to-date is a shared responsibility between our documentation team and readers. By following these guidelines, you can effectively communicate feedback and help ensure our documentation remains reliable so that you can make the best use of all Rocket.Chat has to offer.

    Our goal is to maintain clarity and accuracy in our documentation, making Rocket.Chat easy to use, and your feedback plays a vital role in achieving this.


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    ESC

    Eddy AI, facilitating knowledge discovery through conversational intelligence
https://developer.rocket.chat/docs/documentation-contribution-guidelines
developer.rocket.chat
CC-MAIN-2024-30
64414
application/http; msgtype=response
sha1:7DBMVBVOKLWMPFJITP36X3RURIL3LNOC
<urn:uuid:ac789e69-08b9-45f8-91b5-b983cd87625e>
2024-07-18T23:45:12Z
104.18.21.218
text/html
sha1:4ULXSYRBN2ELFZUN2YX6PXLVUFGDTEF7
<urn:uuid:c532c69b-2132-4e24-92e0-7e9c6c0b6eb1>
https://developer.rocket.chat/docs/documentation-contribution-guidelines
response
<urn:uuid:94b2c8e5-2eaf-4de5-9064-bfb0983e3f4b>
isPartOf: CC-MAIN-2024-30
publisher: Common Crawl
description: Wide crawl of the web for July 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-168
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/