Commit Graph

54 Commits

Author SHA1 Message Date
Alexandros
5d9d7786a2 Update HugoBasicExample Content (#45)
Closes #7 , closes #9 

The existing outdated Hugo documentation in this repo will be replaced with the following more-or-less *evergreen* content:

- **Markdown & HTML Syntax Guide** shows whether a theme has decorated basic HTML elements with CSS. Note that I have not included the Markdown syntax for aligning table columns due to: https://github.com/russross/blackfriday/issues/506

- **Rich Content** features a brief showcase of Hugo’s Privacy config and related Simple shortcodes. Note that I have chosen to embed content that showcases typography by several designers in various media including a 360° interactive YouTube video (for inspiration). Also these embeds should be covered under [Fair Use](https://fairuse.stanford.edu/overview/fair-use/what-is-fair-use/) since these are meant for teaching users how these Hugo shortcodes work.

- **Placeholder Content** includes dummy copy along with a diagram and a link with info about the *Van de Graaf Canon* for constructing layouts (that can also be applied to websites). Note: the diagram is Open Source and taken from https://en.wikipedia.org/wiki/Canons_of_page_construction#Van_de_Graaf_canon (there is a link to this page in the caption).

- **Math Typesetting** a brief tutorial about enabling KaTeX in Hugo (the Hugo Docs mention MathJax which is slower)

- **Emoji Support** brief tutorial about Hugo’s built-in Unicode emoji support (as mentioned in the Hugo Docs) but also this includes an original technique for enabling non Unicode emoji in Hugo by using Static Image Replacement with the `replaceRE` function. Note: custom icons are from the Open Source [Mutant Standard](https://mutant.tech) emoji set.

Also note that the **About** Page has been expanded and updated to reflect Hugo’s current features.

---

**NOTES**

Besides quoting from the Hugo Docs (when needed), these content files contain original content written and curated by me and whatever sources I used were modified  to such an extent that there is no need for footnotes.

The author credit for the new content is Hugo Authors since this is meant for the Hugo community -of which I am a current member- furthermore the content also may be modified by someone else in the future, so this credit seems more appropriate than one with my name.

P.S. @digitalcraftsman I have not included a guide about Modular Typography as this would have been quite involved and I am running out of time.

P.S.2 This PR also fixes the path of the `menu.main` `/about/` item see: #41 by @guylyons
2019-03-11 17:58:40 +01:00
Alexandros
24a0baeb7f Fixes (#43)
This PR fixes the issues that have arisen with #42 and it needs to be merged before https://github.com/gohugoio/hugoThemes/pull/600
2019-03-09 11:28:06 +01:00
Alexandros
5cf42a224f Remove SymLink Add Aliases (#26)
This PR reverts commit 6ad74b6 and instead adds the following under `content/post/_index.md`:
```
aliases = ["posts","articles"]
```

Basically the symlink from #24 duplicated all posts in theme demos, so it needs to be removed.

Aliases on the other hand thanks to the Netlify Redirect Output Format defined in the gohugoio theme over [here](4320e757c9/config.toml (L21-L31)) and [here](https://github.com/gohugoio/gohugoioTheme/blob/master/layouts/index.redir) become 301 redirects, so they hopefully offer a solution to the issue of the various themes using different sections in their demos that I described in https://github.com/gohugoio/hugoBasicExample/pull/24
2019-02-21 00:53:36 +01:00
Alexandros
6ad74b6295 Add posts symlink (#24)
Some themes like for example [Hyde Hyde](https://github.com/htr3n/hyde-hyde/tree/master/exampleSite/content) have their content files under a section called `posts` 

Currently the index page of these theme demos renders empty because there is no `posts` section in the HugoBasicExample.

So to fix this I have added a symlink called `posts` that points to the content files located under the `post` of the HugoBasicExample repo.

In theory this workaround can be used for other sections as well like e.g. `articles` etc (as long as it doesn't break anything).
2019-02-20 19:21:10 +01:00