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

Make possible define more than one organization by coop #139

Open
4 tasks
vitormattos opened this issue May 4, 2023 · 0 comments
Open
4 tasks

Make possible define more than one organization by coop #139

vitormattos opened this issue May 4, 2023 · 0 comments

Comments

@vitormattos
Copy link
Contributor

vitormattos commented May 4, 2023

Today if we want to put more than an organization by coop the page render as multiple rows as a new coop, not as a coop with multiple organizations.

The suggestion is to be possible define one or more organizations by coop. Maybe we can change the Yaml structure from this:

key_org_name:
  source: github|gitlab|git.coop
  login: <USERNAME_IN_THE_SOURCE>
  name: <NAME_OF_THE_COOP>
  url: <URL_OF_THE_COOP>
  description: <DESCRIPTION>
  location: <LOCATION>

to this:

key_org_name:
  - source: github|gitlab|git.coop
    login: <USERNAME_IN_THE_SOURCE>
    name: <NAME_OF_THE_COOP>
    url: <URL_OF_THE_COOP>
    description: <DESCRIPTION>
    location: <LOCATION>
  - source: github|gitlab|git.coop
    login: <USERNAME_IN_THE_SOURCE>
    name: <NAME_OF_THE_COOP>
    url: <URL_OF_THE_COOP>
    description: <DESCRIPTION>
    location: <LOCATION>
  - source: github|gitlab|git.coop
    login: <USERNAME_IN_THE_SOURCE>
    name: <NAME_OF_THE_COOP>
    url: <URL_OF_THE_COOP>
    description: <DESCRIPTION>
    location: <LOCATION>

I suggest the follow to-do list:

  • Suggest a new layout to coop's page.
  • Document the new format at README.md
  • Refactor yaml file to new format
  • Apply the new layout of cooperatives page handling the new yaml file

Original discussion:

Yes, I know. Will be necessary refactor the place that render this page.

Maybe will be necessary to change the yaml structure to don't implement a workaround but to implement a good change.

But, I think that will be best to have this discussion in a issue, not at this PR.

And, about your request, what you want that me do?

Originally posted by @vitormattos in #138 (comment)

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

No branches or pull requests

1 participant