Thanks, Chris! This is great feedback, so thank you so much for sharing!!
Is it ever a "problem" that the content is "owned" by the original user? Would changing the owner itself be helpful or problematic? The only caveat about changing the owner is that you would have to be sure that the service account is still a "collaborator" or future deployments would fail.
A few options in the short term:
More customized content view
Are you familiar with the "Description" field and the "Expanded" view of content? You can add an arbitrary text description to content and then change the server view to "Expanded," which will show users this text description. You could, for instance, set some conventional behavior inside your organization that specifies, for instance, descriptions of the format:
Description: My fun project
Again, this is only arbitrary text and would give users the information without any Connect UI affordances.
To explore this more, click the button in the top right corner of the content list.
You can set this to be the default view on the server by setting the following in the RStudio Connect configuration file.
NOTE: You may need to update for this. I forget when this option became available. Also, you do have to upload the images yourself.
DefaultContentListView = expanded
Are you currently using programmatic deployment with a custom webhook or CI pipeline? I'm curious if you have any feedback to share around how that process went, what pain points you experienced, or how Connect might be able to simplify that workflow.
One feature that landed recently (in the 1.7.6 release) is Git-backed deployment. The blog post linked below discusses in more detail, but basically this could allow a "service-account approach" and being the owner too
Basically, a user clicks on the "New Content" button shown in my screen shot above, selects a git repository, branch, and sub-directory, and then Connect will "watch" that branch / sub-directory and pull / deploy updates as necessary. Essentially, this is a "pull-based" CI that makes the user who originally created the "watcher" the owner of the content. I'm curious to hear your thoughts about this and how it relates to your current workflow!
EDIT: If you find these features useful and were unaware, I definitely recommend subscribing to our blog at https://blog.rstudio.com so you can stay up-to-date on the latest releases and features that we are adding
We also just made some changes to the
blastula package (which should simplify email generation) and added
pins as a new content type: