Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provider Custom Content #294

Closed
thanasis457 opened this issue Sep 23, 2024 · 0 comments · Fixed by #306
Closed

Provider Custom Content #294

thanasis457 opened this issue Sep 23, 2024 · 0 comments · Fixed by #306
Assignees

Comments

@thanasis457
Copy link
Contributor

thanasis457 commented Sep 23, 2024

Description

Currently, the registering page for a new provider has the following sections:
Screenshot 2024-09-23 at 16 02 44

We want to add a new section named "Content". This will be a section where the Provider can add custom content like charts, galleries of photos, calendars, etc.

It should look something like this:
Screenshot 2024-09-23 at 16 07 17
("Information" should actually be "Content". Look at Figma for more details)

The "Content" section has sub-sections of each own. The user can add as many sub-sections as needed. Each subsection is essentially a collapsible component on a provider's page. Within each sub-section (eg. sub-section "Demo" from the screenshot above) can have many components but they will all be part of the same collapsible component.

Your task is to add the new "Content" section, make the sub-sections UI and necessary backend changes to support this, and make everything look and function like in the Figma.
For the backend, make the necessary changes so that this new information (section names, and orders, components etc) are stored along with the rest of the information for a provider.

When pushing the information for a provider to Firestore the you should include a new field names "Content" with the following schema:

{
    "Content": {
        "sections": [
            {
                "name": "Section 1",
                "components": [ /* Empty array which will later contain component descriptions */]
            },
            {
                "name": "Section 2",
                "components": []
            }
        ]
    }
}

You should not focus on what the content inside sections should be. These are components for later sprint. Ie. The things in the red box will be made later:
Screenshot 2024-09-23 at 16 13 05
Do create some sample empty collapsible components but do not populate them with anything pie charts or text boxes like in the example.

The Figma has some inconsistencies so feel free to slack me (@thanasis457) if anything does not make sense.

@thanasis457 thanasis457 linked a pull request Oct 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants