Rick Cogley RickCogley

HTML Tags You Can Use on GitHub

Wherever HTML is rendered on GitHub (gists, README files in repos, comments on issues and pull requests, ...) you can use any of the HTML elements that GitHub Flavored Markdown (GFM) provides syntactic sugar for. You can either use the syntactic sugar that GFM (or other GitHub-supported markup language you're using) provides or, since Markdown can contain raw HTML, you can enter the HTML tags manually.

But GitHub also allows you to use a few HTML elements beyond what Markdown provides by entering the tags manually, and some of them are styled with CSS. Most raw HTML tags get stripped before rendering the HTML. Those tags that can be generated by GFM syntactic sugar, plus a few more, are whitelisted. These aren't documented anywhere that I can find. Here's what I've discovered so far:

`<details>` and `<summary>`

A `<detai

User Stories

Reading list

[Mark Shead: Creating Good User Stories][Mark Shead]
[GOV.UK Service manual: Writing user stories][GOV.UK]
[Mike Cohn's blog posts about user stories][Mike Cohn]
[Mike Cohn: User Stories Applied (book)][User Stories Applied]

Client side searching for Hugo.io with Fuse.js

WHY
Sample
Setup
Files

layouts/_default/index.json

Most Japanese websites use default font sets provided on Windows, Mac or Ubuntu. The latest ones are Meiryo, Hiragino Kaku Gothic Pro and Noto. For older versions such like Windows XP, it is good to add former default fonts MS Gothic(or MS Mincho)/Osaka. Older Linux versions may include Takao fonts.

Some old browsers could not understand those font names in English, some others do not recognize the names in Japanese, so it is safe to write both in Japanese and English.

Meiryo and Hiragino's order is, because Mac users may have Meiryo from MS-Office, and Hiragino is more familiar and matching well on Mac, better by starting Hiragino series.

So the current recommended practice is like this:

font-family: "ヒラギノ角ゴ Pro W3", "Hiragino Kaku Gothic Pro", Osaka, メイリオ, Meiryo, "ＭＳ Ｐゴシック", "MS PGothic", "ＭＳ ゴシック" , "MS Gothic", "Noto Sans CJK JP", TakaoPGothic, sans-serif;

layout

title

published

Install Clamav

Install clamav via homebrew

	<style>
	img {
	max-width: 100%;
	}
	</style>

	<h1>Creating a srcset loop based on Resources</h1>

	<!--
	NOTE: This requires Hugo 0.32

	{{ $image := .Params.image}}
	{{ $media := (.Site.GetPage "page" "media").Resources }}
	{{ $original := index ($media.Match (printf "%s" $image)) 0 }}
	{{ $width := $original.Width}}
	{{ $intWidth := int $width }}
	{{ $sizes := .Params.sizes}}
	{{ $options := .Params.options}}

	{{ if le (len $sizes) 1 }}
	{{ $oneSize := index $sizes 0}}

	#!/usr/bin/env bash

	# To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error
	# Make sure that the .gnupg directory and its contents is accessibile by your user.
	chown -R $(whoami) ~/.gnupg/

	# Also correct the permissions and access rights on the directory
	chmod 600 ~/.gnupg/*
	chmod 700 ~/.gnupg

	; Common buttons
	action.new = New
	action.view = View
	action.edit = Edit
	action.del = Del
	action.delete = Delete
	action.restore = Restore
	action.cancel = Cancel
	action.back = Back
	action.print = Print

	Thanks for stopping by.

	This code has been moved to https://github.com/kaushalmodi/hugo-debugprint as a Hugo theme component.