New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Landing pages by project / tag #77
Comments
To do for all project landing pages(these are each pretty substantial, should have their own issue?)
To do by Project:nonparametric-bayes
phylogenetics
warning-signals
decision-theory / optimal controlmultiple-uncertainty, pdg-control, and nonparametric-bayes are all related; but should they be separate projects? In some way everything is clearly related. Not sure where to make this division... multiple-uncertaintypdg-controlpopulationdynamicsopen-scienceAnother project whose landing page will need to differ from the standard research project structure.
ropensciNeed to figure out how to structure this. What elements should this include?
|
Put the publications and notebook entries on top, and the commits and issues below. I think you want to provide a gateway to the more accessible stuff first. The screen breaks before the bottom row of the grid so that stuff isn't apparent at first. Actually, I might make a column of highlighted notebook entries that point to some of your more interesting recent analysis (featured: TRUE, or tag: featured in the post YAML, maybe?). That's the kind of thing that will probably require some manual creation. (from @noamross) |
Landing pages essentially accomplished. Outstanding items remaining are either ongoing (updating manual content, largely relatively static), or ambitious ideas belonging to another issue, such as automated inclusion of publications and slides, and the addition of RDFa to collaborators, funding, and other outputs. So closing issue. |
Each major project should have it's own landing page:
Associate/Link these landing pages from their tags on the tag page?
The text was updated successfully, but these errors were encountered: