Skip to content

Latest commit

 

History

History
62 lines (43 loc) · 3.43 KB

workflow.md

File metadata and controls

62 lines (43 loc) · 3.43 KB

Tutorial authoring

tutorial naming

Each tutorial is in a directory, optimally with strings indicating:

  • topical area (e.g. surf)
  • body (e.g. mars)
  • experiment(s) (e.g. HRSC)

Available prefixes include:

examples tutorial names:

  • surf_mars_crism
  • magn_saturn_cassini
  • surf_moon_craters
  • atmo_titan_vims

Naming of tutorial directory

The directory name of each tutorial should be easy, self-explanatotory and without space, e.g. cassini-titan-flyby

Creation / migration of content

Please follow the template on template and use simple, meaningful image names without spaces in the filename.

A sample formatted tutorial based on the existing one on the VESPA wiki

Update of content

Once a tutorial exists, can be updated either directly (if added to the right team, please get in touch with @arosp. Or, you could fork the repository, make your changes and create a pull request. The procedure is described in several tutorials on the internet, e.g. GitHub's creating a pull request from a fork.

Embedding content

Images embedded in a tutorial should be in the [img][template/img] subdirectory of each tutorial.

Images

  • Images should be embedde with meaningful, short names and no spaces in the filename. Format preferably PNG or JPEG.
  • If too big (larger than ~400 px) please resize embedding the full path ("download", not url of location in repo), i.e.
<img src="https://raw.githubusercontent.com/epn-vespa/tutorials/master/template/img/1.png" width="400">
  • In any case, please keep image/screenshot file size reasonably small.

Videos

  • Videos can be linked from YouTube/Vimeo or similar video streaming, preferably with a placeholder screenshot, e.g. as described here.

GitHub & VESPA wiki