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

docs: How to configure the project_url table #293

Open
1 task
fyliu opened this issue Jun 3, 2024 · 2 comments
Open
1 task

docs: How to configure the project_url table #293

fyliu opened this issue Jun 3, 2024 · 2 comments
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it p-feature: projects project and projects p-feature: Stakeholder documentation documentation for Users of People Depot ready for prioritization role: technical writing s: PD team stakeholder: People Depot Team size: 0.5pt Can be done in 3 hours or less

Comments

@fyliu
Copy link
Member

fyliu commented Jun 3, 2024

Overview

We need some documentation to explain how project_url works in relation to project. This is especially true of the external_id field, which is not obvious that it's an id provided by an external service such as github.

Action Items

  • create documentation

Resources/Instructions

@fyliu fyliu added size: 0.5pt Can be done in 3 hours or less p-feature: projects project and projects s: PD team stakeholder: People Depot Team role: technical writing Feature: docs: User Guide labels Jun 3, 2024
@fyliu fyliu added this to the v0.01 - initial setup milestone Jun 3, 2024
@fyliu fyliu changed the title [docs] Document how to configure the project_url table [docs] How to configure the project_url table Jun 3, 2024
@fyliu fyliu changed the title [docs] How to configure the project_url table docs: How to configure the project_url table Jun 10, 2024
@fyliu fyliu added p-feature: Stakeholder documentation documentation for Users of People Depot and removed Feature: docs: User Guide labels Jun 10, 2024
@ExperimentsInHonesty
Copy link
Member

@fyliu

  • Q1: Where do you want this information to go once we write a draft?
  • Q2: Who is the audience for this documentation
  • Q3: When will this information be accessed?

@fyliu
Copy link
Member Author

fyliu commented Jun 25, 2024

@ExperimentsInHonesty
This corresponds to a high level explanation for an end user setting up projects for an organization.
But this is really at the API level so that a frontend client app developer will know how to integrate it into the app and how to guide the end user.

  • Q1: Where do you want this information to go once we write a draft?
  • An explanation page for the project "module" (maybe a file called docs/topics/project.md, where docs/topics/ contains all the high-level explanatory pages)
  • Q2: Who is the audience for this documentation
  • frontend client developers
  • should the stakeholder labels be s:VRMS also?
  • Q3: When will this information be accessed?
  • during development of the corresponding frontend feature
  • or when potential consumer of the API is evaluating our system

@fyliu fyliu added ready for product complexity: small All steps are laid out in detail so that someone new to the project can work on it and removed ready for dev lead complexity: missing labels Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it p-feature: projects project and projects p-feature: Stakeholder documentation documentation for Users of People Depot ready for prioritization role: technical writing s: PD team stakeholder: People Depot Team size: 0.5pt Can be done in 3 hours or less
Projects
Status: 🆕New Issue Review
Development

No branches or pull requests

2 participants