Base skeleton for the new Gobierto Dashboards module #3028
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Entry in application.yml - Entries in routes.rb - New module
- Controllers with empty actions - Empty views - Empty JS and SCSS files - Eppty locale files
- Controllers with empty actions - Empty views - Empty locale files
ferblape
approved these changes
May 6, 2020
|
@entantoencuanto I'm going to merge this PR of the new module because there are going to be more branches based on this. |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2995
✌️ What does this PR do?
It adds a new (for now, empty) module called Gobierto Dashboards that can be enabled through the admin panel.
🔍 How should this be manually tested?
As an admin, you should be able to enable/disable the new module in staging from the Customize Site (for instance, in the madrid site: https://madrid.gobify.net/admin/sites/2/edit). Once enabled there shouldn't be any changes in the main navigation section of the site, but these urls should be now accessible:
If disabled, those urls should not be accessible.
For now, the content of each of those pages is a single string with its name.
👀 Screenshots
Before this PR
After this PR
.env.example?config/application.yml?config/secrets.yml?(Changes in these files might need to update the role in Ansible)
📖 Does this PR require updating the documentation?