Closed richelbilderbeek closed 1 week ago
This is still ongoing ...
Here are the notes:
Suggestion for overall rule 1
Most info on SiteVision
All HowTos on MkDocs, example:
YES: BC, RB, ML
No: PL
PL: I would prefer something like this, clearly defined what category of pages go where. But think many howtos about especially apply for project should be on SV.
What is the guiding premise:
Applying for an account:
Applying for NAISS projects:
Applying for a local project:
PUBA:
Hardware:
Instructions about (howto) Services offered through UIT (if a page is needed):
Suggestion for overall rule 2
Suggestion for other alternative rule(s)
Log in to each cluster, now at SiteVision And MkDocs
General description of hardware, now at SiteVision and MkDocs
Detailed Hardware (how to access), now at SiteVision and MkDocs
System usage, now a link from SiteVision to mkdocs
Applying for a projects and accounts, now SiteVision
Our Courses, Now SiteVision
Course registrations:
SiteVision additions:
SV calender/news (courses instance?)
Support on SiteVision (consists of links), now duplicated
Links back?
I will put this at CONTRIBUTING.md :-)
It has been put in CONTRIBUTING.md . Done!
What to put on SitevVision and what on GitHub?
This is a quote from Marcus Lundberg:
Or from Björn Claremar:
and
My suggestion rules would follow from these goals:
Then the rule would be:
Discussion cases would be: