You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting this issue to discuss ideally how to structure information and meta data about each package so it's easier to consume in "aggregators" (meta-website, notebooks project, etc.). Looping also @knaaptime as per call discussion.
From the notebooks project, elements that could immediately improve the appearance include:
Standard way of storing images present in the README which gets pulled at the introduction of each package notebooks.
Going forward, it might be worth thinking whether we want something different from the README to be the introduction. Maybe a short description of the pacakge, what it does and key links? This sounds like what the README should be, but maybe it's different in some contexts. Maybe something like a BLURB.md file which could also be pulled on the website?
Activity
darribas commentedon May 1, 2020
From the notebooks project, elements that could immediately improve the appearance include:
READMEwhich gets pulled at the introduction of each package notebooks.READMEto be the introduction. Maybe a short description of the pacakge, what it does and key links? This sounds like what theREADMEshould be, but maybe it's different in some contexts. Maybe something like aBLURB.mdfile which could also be pulled on the website?weikang9009 commentedon May 1, 2020
Sounds like a great idea.
We might also want to make sure we are using the same file format for README,
.mdor.rst.jGaboardi commentedon May 1, 2020
Linking the agenda notes where this was originally discussed.