Data sanitation

[leapalazzolo]

Is your feature request related to a problem? Please describe. not really but it's an improvement

Describe the solution you'd like We need to ensure that all the information displayed on the website is precise and accurate.

• We need to create a table to maintain the projects (repos) and interests (here may be a good idea https://github.com/orgs/kudos-ink/projects)
• We should get all the main repositories from polkadot-ecosystem (dapps, docs, parachains, etc)
  • https://careers.substrate.io/companies
  • https://polkadot.network/ecosystem/dapps
• We may need to update the list of repositories in the cloud functions that maintains our notion's database
• We need to check that all the languages in the filter have at least one issue
• We need to check that the repository information saved in notion has the correct languages
• Once we have all the repositories,
  • We need to redefine the "mapping" of interests
• We need to define the order of the filters' values

[leapalazzolo]

Update:

Workflow

TODO

1. Create new repo as a source of truth with a json file

• initial load by us (based on keywords)
• external people can contribute and add projects there

2. Define JSON structure:

• Interests: manual selection. Maintained by us

[{ "value", "label", "emoji" }]

• Project: name, emoji, repository, interests

  "name": "Singular 2.0", "url": "https://singular.app/", "icon": "https://raw.githubusercontent.com/novasamatech/nova-utils/master/icons/dapps/color/Singular_2.0.svg", "categories": [ "nft" ] https://github.com/kudos-ink/repository-classification/blob/main/dapps_output.json

Structure

projects.json

[ { "name": Kudos Portal "emoji": octupus "repository_url": https://github.com/kudos-ink/portal (take project, icon from here) "interests": [dapp, front-end, ...] } ]

3.

• dapps from dapps portal (Polkadot)
• substrate project from substrate jobs portal
• reuse projects from Notion
• manual list (docs)

4. project.json in the root the rest of the files -> delete or hide

5. readme with explanation

6. issue template with interests selection like this https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

7. workflow that gets project, icon, etc

8. add in Notion https://polkadot-open-issues.notion.site/polkadot-open-issues/4b173a8695924fdb900fb57095b83b32?v=10b33b50bad14ae382b4537383cdef2c

9. OPTIONAL: Add interests table in Notion and automate portal using it

[leapalazzolo]

Next steps:

• use the production db in the CI :heavy_check_mark:
• add new projects :heavy_check_mark:
• check again filters
• automate repositories subscription :heavy_check_mark:
• remove duplicated issues