richardrodgers
commented
9 years ago I think the intent is that there be a 'project site' (which the visualization app now links out to) - which may (or may not) contain some or all of that sort of information. I'm not sure it makes sense to put all that in the portfolio visualization data model itself. There are actually 2 links: the 'project' url and a repository url. For demo purposes alone I used the Github repo as the project url also, but for more real-world large projects, the project url would be a wiki or even dedicated web site with out-links,etc
would this view be embedded in another web page or is it a standalone?
as a use case, our portfolio site would have other docs available ( in a LibGuide or other site) such as: -explanation of project sizing measurements -explanation of roles of participants (like what we expect a Biz Owner to do) -request/intake form for other project support -display of requested projects that are already in queue or in idea stage that we know are happening -links to project sites beyond the Git site such as Basecamp, wikis, project briefs etc. Githubs for each project sometimes may not always link to actual scope