#Hello there This is a sample “Bonus” page: a way to post videos, images, data, code, links, or any other information which you can’t fit into your presentation, poster, or paper1, but still wish to make available to the public. The name is a (bad) joke alluding to the Bonus Content found on DVDs or digital movie/TV purchases.
##Making a page Bonus pages can be edited and put up in the same way
as most other pages on our public website. The Markdown files are hosted
on ye
ole group fileshare in the directory
/Public/Group website
. The one for this page is named
2018-09-16-Sample-bonus-features.markdown
, so you can see
what gets rendered into what. Markdown is a markup language which is
pretty easy to use; here’s
a Markdown cheatsheet. Once you’ve written up your project’s
.markdown
file, upload it to
/Public/Group website/_posts/bonus/
.
The important bit for bonus feature pages is the permalink; this is usually important for every page on this site, but we assume that people will arrive at Bonus pages directly by URL instead of browsing through the home page. The permalink will also determine the locations of any supporting files. Merlin’s decreed convention is that Bonus permalinks should follow the format of a BibTex citation key: first author’s last name, underscore, the first three unique-ish words (no articles) from the title, underscore, year. Aping the BibTeX citation keys just makes sense: they’re controlled by and known to the author long before a DOI, they’re designed to be specific and unique enough for our uses, and readers–and you!–have a fighting chance of remembering them or guessing them later on.
###Where the File Things Are If you want to host and offer files for
viewing or download that are specific to a bonus feature, you should
make a sub-directory of /assets/img/bonus
with the same
name as the Bonus page’s permalink. For example, since this page’s
permalink is Mah_SampleBonusFeatures_2018, make a folder in
/assets/img/bonus/Mah_SampleBonusFeatures_2018
.
###Images, videos, etc.
.m4v
only) without invocation difference. Only
the file name needs to be specified: the
/assets/img/bonus/(page permalink name)
bit is
automatically prepended.
###Galleries Got a crapload of images that might not need involved textual descriptions? You can stick them in a gallery.
We can do pictures side-by-side, a little awkwardly, by shoving them into a table:
![]() |
![]() |
---|---|
Caption 1. | Caption 2. |
Things should auto-scale to fit if you cross your fingers. Make sure there are at least two blank lines after the table. Also, the number of dashes in that line between the images and the captions (the one that contains only pipes, colons, and dashes) DOES matter–too few, and your images will be tiny and scrunched to the left!
###Code A block quote follows this Italic line.
10 START
20 HCF
30 GOTO 10
And a code block follows this bold-text line. (You
can do inline code
as well.)
= ['awesome', 'barely a language', 'hard']
adjectives for index, language in enumerate(['Python', 'MATLAB', 'C']):
print("{} is {}".format(language, adjectivers(index))
For more involved code, you probably want to link to the source files, or out to GitHub etc.
##Getting people to this page If your chosen permalink is
Your_PermalinkGoesHere_YEAR
, the URL for your Bonus page
will be
http://omems.umn.edu/bonus/Your_PermalinkGoesHere_YEAR
.
(If we’re using https, it will redirect automatically.) To make things
easy, we recommend putting a QR code in your poster, presentation,
abstract, or other easily accessible place; most smartphones can scan QR
codes–iOS doesn’t even require an app–and follow them directly to the
site, or a simple photo can record it for later use.
##Any questions? Feel free to ask Merlin.
You don’t have to read this part unless you’d like to test out all the page decorations yourself. If you have no interest in these, someone will eventually get around to them or walk you through it.
Now that the wimps have left: you’ll notice that the top of each
Markdown file has some lines following the form
field: fieldvalue
. These tell Jekyll which template or
style should be used for the page, how to file it, and so forth. Most of
these are pretty self-explanatory (and if not, should probably be left
alone), but a few could be of particular interest:
layout:
specifies the template which will be applied to
this page. For Bonus pages this is bonus
. #TODO bold Don’t
change this.img:
is the standard picture used to represent this
Bonus page around the site, if we ever get around to adding an index of
them. Specify a big and pretty image, and upload it to
/Public/Group website/assets/img/bonus/
. #TODO when I do
the index page, does it work if the images are in the /posts
subdirectory instead?covershot:
produces a big pretty image behind the
project name in white text at the top of the page. Deleting this line
entirely will produce a simple dark grey background behind the title.
The image or video file named here should be placed in
/Public/Group website/assets/img/project/
.####Footnotes! Here are some footnotes! Handy for references, as well
as fine print disclaimers you don’t want people to read get
distracted by.