Technical Documentation
Return to Main Documentation
ENGLISH - version 2.3
ENGLISH - version 2.3
  • Introduction
  • Getting started
    • Create your fork
    • Configure your fork
    • Keep your fork updated
    • Communication
  • Installation
    • Local installation
      • Prerequisites
      • Ubuntu Linux
      • Debian Linux
      • macOS
      • Windows
      • Vagrant
      • Docker
    • Production and staging servers
      • Installer
      • Create a deploy user
      • Generating SSH Key
      • Manual installation (not recommended)
      • Digital Ocean
      • Heroku
      • Mail server configuration
    • Basic configuration
    • User documentation and guides
  • Customization
    • Introduction
    • Translations and texts
    • Images
    • Styles with CSS
    • JavaScript
    • Models
    • Controllers
    • Views and HTML
    • Components
    • Other Ruby classes (GraphQL, lib, mailers, builders)
    • Gems
    • Application configuration
    • Routes
    • Tests
  • Technical Features
    • OAuth
    • GraphQL
    • Debates and proposals recommendations
    • Configure Census Connection
    • Local Census
    • Multitenancy
    • User content translations
  • Open Source project
    • Code of conduct
    • Contributing
    • Coding conventions
    • Open source forks and modifications
    • License
Powered by GitBook
On this page
  1. Getting started

Communication

PreviousKeep your fork updatedNextInstallation

Last updated 2 months ago

The preferred way to report any missing piece of information is .

Before doing it, please take some time to check the and make sure what you are about to report isn't already reported by another person. In case someone else reported the same problem before or a similar one, and you have more details about it, you can write a comment in the issue page. A little more help can make a huge difference!

In order to write a new issue, take into account these few tips to make it easy to read and comprehend:

  • Try to use a descriptive and to-the-point title.

  • It's a good idea to include some sections -in case they're needed- such as: steps to reproduce the bug, expected behaviour/response, actual response or screenshots.

  • Also it could be helpful to provide your operating system, browser version and installed plugins.

On the other hand, if you need a space for more informal and open interaction, we have the section. It's similar to a discussion forum within the project, where you can ask questions, make suggestions, share ideas, and have conversations that don't necessarily fit into an issue or pull request.

opening an issue in the project's Github repo
existing issues
Discussions