Splitting the "Add Resources" button functionality to each respective page.
Data Page will have "Create Dataset" and "Upload Dataset" button
Maps Page will have "Create Map" button
GeoStories Page will have "Create GeoStory" button
Dashboards Page will have "Create Dashboard" button
Resources Page will have "Upload Resource" button
Acceptance criteria
Introduce the concept of "catalog pages", which are distinct catalog views per resource type (Datasets, Maps, etc.)
The catalog config will be extended to support distinct configs per page:
distinct filters
distinct action buttons (dropdown) configurations
The current section will be highlighted by a border rendered below the specific button (see mockup from the client)
The specific configurations for each section should be implemented smartly and efficiently. Instead of repeating the full configuration in each section (as we're doing now in many other parts of the config), only the overrides / diffs should be configured.
We must define how the menu buttons will be mapped to sections. They're provided by the Django template, so it could be provided by the template itself, updating the URL, after the hash (#), which will be intercepted by the catalog app.
For clarity, it will still use the current single-page app (catalog), contrary to the hypothesis we were doing yesterday of implementing new views on the backend.
Description
Splitting the "Add Resources" button functionality to each respective page.
Acceptance criteria
The specific configurations for each section should be implemented smartly and efficiently. Instead of repeating the full configuration in each section (as we're doing now in many other parts of the config), only the overrides / diffs should be configured.
We must define how the menu buttons will be mapped to sections. They're provided by the Django template, so it could be provided by the template itself, updating the URL, after the hash (
#), which will be intercepted by the catalog app.For clarity, it will still use the current single-page app (catalog), contrary to the hypothesis we were doing yesterday of implementing new views on the backend.