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

Add a documentation page describing the different parts of our stack #3201

Closed
AetherUnbound opened this issue Oct 16, 2023 · 5 comments · Fixed by #3786
Closed

Add a documentation page describing the different parts of our stack #3201

AetherUnbound opened this issue Oct 16, 2023 · 5 comments · Fixed by #3786
Assignees
Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: documentation Related to Sphinx documentation

Comments

@AetherUnbound
Copy link
Collaborator

Description

We have some information regarding the different aspects of our stack in the top level README.md: https://github.com/WordPress/openverse#openverse

It would be useful to have a documentation page on our docs site that goes further in-depth about the various pieces of our stack, with references to the related documentation and code for each entity (e.g. API, ingestion server, catalog, frontend).

@AetherUnbound AetherUnbound added 🌟 goal: addition Addition of new feature 📄 aspect: text Concerns the textual material in the repository 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: documentation Related to Sphinx documentation labels Oct 16, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Oct 16, 2023
@krysal krysal added good first issue New-contributor friendly help wanted Open to participation from the community labels Oct 18, 2023
@zealshah29
Copy link
Contributor

Hi, could you describe further in detail what exactly you want in the documentation?
Like suppose if one of the tech stack is django, so do we have to explain django tech stack in detail and provide link to it's documentation?

@AetherUnbound
Copy link
Collaborator Author

Hi @zealshah29! I think it would be ideal to have the following for each section of the stack listed in the link above:

  • Link to the folder for the service on GitHub
  • Link to the documentation for the service on docs.openverse.org
  • Primary language(s) for the project
  • List of all of the tools/technologies/frameworks the services uses
    • Links to each of the above's documentation would be ideal as well

For example for the API, we'd have (respectively):

Having a list like for each part of the stack would be excellent!

@zealshah29
Copy link
Contributor

Okay, got it! So shall I create a new page in the documentation folder? or shall I create a subfolder for the same within the documentation folder?

@AetherUnbound
Copy link
Collaborator Author

Good question! I think a new page in the documentation/general folder (maybe documentation/general/stack.md?) would be the best bet! Would you like me to assign this issue to you?

@zealshah29
Copy link
Contributor

Sounds great! Ya could you assign that to me? I would love to contribute.

@openverse-bot openverse-bot moved this from 📋 Backlog to 📅 To Do in Openverse Backlog Feb 6, 2024
@openverse-bot openverse-bot moved this from 📅 To Do to 🏗 In Progress in Openverse Backlog Feb 12, 2024
@openverse-bot openverse-bot moved this from 🏗 In Progress to ✅ Done in Openverse Backlog Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: documentation Related to Sphinx documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants