Details
-
Suggestion
-
Resolution: Unresolved
Description
I'm liking the new team/project functionality, with one glaring exception: if one gets a link, or finds one's way, to a project (e.g., this) one sees an almost-naked list of repositories. That's all a project landing page currently is: a repository list! (Am I missing something?) This is much less information-rich than a repo landing page. So I'd like to enquire about, and advocate for, something to serve a project in the same way that the current overview/README content on a landing page serves a repo. Some options that come to mind, in order (roughly) of increasing preference by me:
- most minimally: display the project description on the project landing page. It might still be editable only via the project>Settings.
- "rich-up" the project description (in addition to showing it on the project landing page). E.g., allow composing/editing it with the same sort of Markdown support as you use for these Issues.
- an all-the-way project README, supporting the same range of markup as a repo README. (Definitely reST Might be difficult, depending on how you've implemented projects.
- a project-designatable "master repo." I suspect this is a strategy OP have adopted, and I certainly have, esp "back in the day" before Bitbucket got Projects: one had a single master repo which pointed to and explained the others. (I'm currently extending this to a Project by having the Project>Settings>Description point to the landing page for my old master repo ... but until project descriptions are better surfaced, that's kinda pointless.) The ease-of-implementation (for youse guys) advantage I can see (ICBW) for this option is that you could just
- leverage (unchanged) the existing UI to set a repo's landing page (in its Settings).
- add UI to allow the user to designate a master repo (e.g., in the Project>Settings).
- surface the content from the master repo's landing-page on the project's landing page. Perhaps without Edit decorations--user could still be required to do that via the master repo's landing page.
- make the project repo list a separate page accessible from the project landing page (as, e.g., Source, Issues, etc are for a repo's landing page).
Apologies if this is a FAQ, but I saw no good match when searching Bitbucket issues, support, or documentation (or when I did a more general websearch).
Attachments
Issue Links
- mentioned in
-
Page Loading...