The image processing examples are rendered within containers with a
'nested-img' parent CSS class, which by default makes images responsive
by resizing them to the size of their containers.
That doesn't work well for the examples as the small images end up
stretched.
Since there can be other images in the same 'nested-img' context, we
keep that class in the parent and set the example images width to auto,
such that they will render with their actual size.
On small screens, larger images will still be sized down via the
max-width property.
Fixes#812
When running hugo new site sitename it does not create the assets or config directories by default.
I updated the layout example to remove the directories and include config.toml and made a note in the assets and config directory sections to highlight they are not created by default.
The development server isn't really that important for quick start.
Yes it is useful but makes things complex.
The most important part is really static site generation, and it is actually hard to find how to do it in your tutorials!
Same for `hugo new`. It is automagic, and anti-thesis of things being simple. This is why I added section to make it less magic, and simply allow content to be done manually.
Note that I changed the reading time example for pluralization from ‘One minute read’ to ‘One minute _to_ read’ because, in common US usage at least, this might properly be punctuated as ‘One-minute read’, and longer would be handled like ‘12-minute read’ (not ‘12 minutes read’), so it actually wouldn’t make a good example for demonstraing single and plural forms. By adding ‘to’, though, the example aligns with common US usage while also serving as an example of single and plural forms.
Closes#694
* Correct typo "RFC339" to "RFC1123Z"
Per discussion in PR #887, I added a link to the Go time package documentation that lists constants that can serve as further examples.
Hugo `0.55.0` introduced some new interface types for `Page` etc.
This worked great in general, but there were cases where this would fail in `where` and `sort`.
One such example would be sorting by `MenuItem.Page.Date` where `Page` on `MenuItem` was a small subset of the bigger `page.Page` interface.
This commit fixes that by unwrapping such interface values.
Fixes#5989
Sadly, goorgeous has not been updated in over a year and still has a lot of
open issues (e.g. no support for nested lists).
go-org fixes most of those issues and supports a larger subset of Org mode
syntax.
Hugo requires some front matter values to be arrays (e.g. for taxonomies).
Org mode front matter syntax (`#+KEY: VALUE`) does however not support anything
but string values normally - which is why goorgeous hardcoded the values for
the keys tags, categories & aliases to be parsed as string arrays. This causes
problems with custom taxonomies.
A simple thing we can do instead is make keywords ending in '[]' be parsed as
string arrays.
Sadly, goorgeous has not been updated in over a year and still has a lot of
open issues (e.g. no support for nested lists).
go-org fixes most of those issues and supports a larger subset of Org mode
syntax.
