posit-dev / posit-dev/connect-extensions
Publisher Command Center: Display more information about content
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 10
- Forks
- 8
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 1
Description
From feedback from from @kmasiello
tell me the versions of PQR that it uses. tell me the vanity URL. tell me the number of hits in the last X days. Running processes isn't interesting to me as a publisher. tell me if it is git backed and the status of the last git check. tell me who has access, who my collaborators are. tell me the last content visit.
Possible additional data to display. We should prioritize among these.
- Display vanity URL
- Display git-backed content info
- Display last content visit
- Display runtime versions in use
- Display usage metrics
My initial thought reading this is, "These are mostly visible on the Dashboard, and we don't want to fully re-implement that." But, if the purpose of Gallery content is to give an idea of the world of possibilities, there is probably a subset of this which is easier to add than others.
May want to convert some of these to sub-issues, e.g. git-backed content.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing the Publisher Command Center and the referenced Dashboard, then use the checklist to determine which information is in scope. Done should be an agreed priority and implementation plan for the selected display items.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, r
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100