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:
Until applying on SiteVision (proj application on MkDocs) - All instructions:
[VOTED] BC, DI, ML, RB
Until using (including applying) on SiteVision:
?PL
Applying for an account:
On SiteVision: ?PL
On MkDocs: BC, DI, ML, RB
Applying for NAISS projects:
On SiteVision: ?PL
On MkDocs: BC, DI, ML, RB
Applying for a local project:
On SiteVision: ?PL
On MkDocs: BC, DI, ML, RB
PUBA:
On SiteVision:
On MkDocs: BC, DI, ML, RB, ?PL
Hardware:
On SiteVision:
On MkDocs:
Instructions about (howto) Services offered through UIT (if a page is needed):
On SiteVision:
On MkDocs: RB, DI, ML
Suggestion for overall rule 2
[VOTED]: try hard for minimal duplication
Minimize double info
[VOTED] Yes: BC, RB, PL
No
2b: absolutely no double (no pragmatism)
Yes: PL
No: BC, RB, PL
PL: I vote for both… "no pragmatism" sounds a bit harsh, but we should really minimize hard. The end user experience gets confusing when info are in two places - "am I reading in the correct place?" One page would be best. If we need two pages it is good if they are clearly defined to cover different parts, this will also minimize the times you have to jump between the two pages.
Suggestion for other alternative rule(s)
Extreme MkDocs:
everything except links to mkdocs on SiteVision
no subpages
Almost Extreme MkDocs:
keep subpages but only put links here
Like today
on cluster on MkDocs
Project management on SiteVision
More SiteVision: PL
Some MkDocs content –> SiteVision
As much as possible on SiteVision
Only use mkdocs when we can motivate it
dynamic pages (sw list)
frequently updates pages - easier on mkdocs(?)
lots of code - easier with markdown
Specific topics
Log in to each cluster, now at SiteVision And MkDocs
SiteVision only:
Cons/pros??
MkDocs only: BC, RB, PL (if other howtos/userguides are on mkdocs)
Both
General description of hardware, now at SiteVision and MkDocs
[VOTED] SiteVision only: DI, ML, BC
MkDocs only: RB
Both:
Detailed Hardware (how to access), now at SiteVision and MkDocs
System usage, now a link from SiteVision to mkdocs
Link from SiteVision
Link from MkDocs (move):
[VOTED] Link from Both: RB, BC, ML, DI
PL: this might become problematic on SV in the future if we want to add more, and more dynamic content. job dashbords and such. But we can move to mkdocs later if necessary.
Applying for a projects and accounts, now SiteVision
Problem today: can be much more pedagocigal in MkDocs
PL: "can be much more pedagogical" - how?
SiteVision (keep): PL
MkDocs (move): RB
Both: BC
Example:
Info about projects in SiteVision
How to: in MkDocs, of course with links from SiteVision
allinea ddt F+WebTree, - Installing and development/debuggers debuggers and profile gdb F+WT- RB, put under misc - Installing and development/debuggers gaussian - PM
Björn: cluster environments in quickstart containig modules and Slurm
There are different ideas what makes a pretty schematical picture. In an earlier meeting, the idea was that Jonas would decide upon a color scheme. Richel now thinks that that is overkill and he suggest the rule 'If you don't like the look of a schemetical picture, just edit it'. People agreed that we should use a more lightweight approach and we discussed in which way to do so:
Freely edit
Notify the original author after an edit
Ask the original author for ideas what to change
This differed between team members:
Pavlin and Richel are in the 'freely edit' camp; hence you can freely modify their pictures
mermaid colors: we discussed a procedure to allow us to all agree, instead of discussing every little hue every time. Jonas seemed most eager to make these color decisions and Richel and Pavlin will accept his decisions. Jdddng thongas will join the UPPMAX meeting on Tuesday ?10 January and talk with Elisabeth. Note that Diana also was working on a color scheme suggestion. Jonas will contact Diana and discuss
Pages done or worked on (as seen under Support on old web)
Getting started
Slurm Diana
First log-in to UPPMAX Björn
rackham
snowy
bianca
Disk storage guide Marcus (move to Clusters)
Apply for a project Marcus
Cluster user guide HPC
compiling source code Björn
MPI and OpenMP user guide Björn
workshops and courses
workshops and courses Diana
outside the UU structure:
Software page Matias, Jonas – the link out will not work in firefox because of security interactions with linking embeded pages. – add {:target="_blank"} to the links that link out. To fix the embeded link security issue with frames.
Setup Mkdocs insiders Matias
Update theme Matias
Meeting Fri 29 sep at 13:30
Status?
Björn started to play with new pages in Site-vision
Matias made a lighter style look red–>grey
software table!
Meeting Fri 22 Sep at 13:30
To discuss?
insiders 5$/month
ledningsgrupp next Tuesday
On GH
new menu
some present pages coupled
created files to be filled with content
mv hardware to site vision
Pages done or worked on (as seen under Support on old web)
Getting started
Slurm Diana
First log-in to UPPMAX Björn
Disk storage guide Marcus (move to Clusters)
Apply for a project Marcus
Cluster user guide HPC
compiling source code Björn
MPI and OpenMP user guide Björn
workshops and courses
workshops and courses Diana
outside the UU structure:
Software page Matias, Jonas – the link out will not work in firefox because of security interactions with linking embeded pages. – add {:target="_blank"} to the links that link out. To fix the embeded link security issue with frames.
Setup Mkdocs insiders Matias
Update theme Matias
Meeting 8 Sep
To discuss
who takes what?
see list above
where to prioritize?
see list above
Tree
Getting Started:
Applying for a Project: getting_started/project_apply.md
Logging into Rackham: getting_started/login_rackham.md
Logging into Snowy: getting_started/login_snowy.md
Logging into Bianca: getting_started/login_bianca.md
Running your first job: getting_started/first_job.md