Page groups

[gadenbuie]

Currently we have

• Blog
• Projects
• Publications

but discussion on Slack indicates we may want to rethink how we divide content.

Impacts #3.

[tgerke]

I might suggest swapping Publications with Releases where we could then put the items which are currently in the Projects page. Projects could then be named something like Research initiatives to outline key applied areas we're working in.

[gadenbuie]

Similar to the conversation in #7, I'm a fan of having big if slightly ambiguous top-level buckets and then imposing structure within those groups via metadata like categories, tags, etc.

From a blogdown/hugo perspective, it's good to keep in mind that the groups serve to setup templates so sub-pages all have the same look/structure in the presentation of the information. From a user's perspective, it's good to keep in mind the commonly used headings and that often it's a high-level first decision about where to find what they're looking for.

Folding in @tgerke's suggestion, what about having Software instead of Releases and Research or Projects instead of Research Initiatives?

• Blogs
  • Any unstructured post, tutorial, note, announcement
• Projects (or Research)
  • Creates an umbrella page for a research initiative or project. Can link out to other blog posts, external pages, etc.
• Software
  • Creates an umbrella page for software packages or releases so that we can share gerkelab.com/software/shinydag instead of the github link.
• Publications
  • Any "produced" research artifacts, in particular things that are published or were delivered outside of our webpage. So talks and posters etc that wouldn't have an external link can be included here too.

[tgerke]

Looks great to me (and selecting Projects over Research perhaps makes sense for that group). Re: publications, these could be folded into Projects or Software as appropriate, and this would follow with the bigger top-level bucket philosophy. I imagine it will be relatively rare that we have publications that are totally ancillary to any one of the Projects or Software releases.

[gadenbuie]

Structurally, it'll be easier to have them as a separate bucket and then link between them. For example, http://www.gerkelab.com/publication/epitad/ demos a "Project Page" button that links to http://www.gerkelab.com/project/epitad/.

Future epiTAD pubs can use that mechanism to link back to the project. And on the flip side, we can use tags to add automatically generated link sections in the project page to fold in any pubs or software releases related to a project.

Hugo works really well when the page templates are defined by the directory structure. Nesting publication pages under /software/epitad/publication/... is possible but a bit more complicated.

[tgerke]

That all makes good sense. My only concern is that the Publications page may be very slow to develop because of extreme lags in the peer review process, and as a result may not give visitors a representative/timely snapshot of our work as a team. For example, I have a decent number of publications that are the result of me collaborating with other teams, but not necessarily a result of Gerke Lab stuff.

[gadenbuie]

I see. Do you feel that we shouldn't include those collaborations in this page? What if we used metadata to separate core Gerke Lab from collaborations and add a filtered view (core|collabs|all)?

[tgerke]

I think the metadata idea could work; I simply want to make sure people like you and @jhcreed are highlighted most prominently on this site, as you're the real stars!