mirror of
https://github.com/gohugoio/hugo.git
synced 2026-08-24 15:28:54 +00:00
Remove asciicast from site
This commit is contained in:
committed by
Bjørn Erik Pedersen
parent
1e56c653ff
commit
71e81ec5f6
@@ -49,8 +49,6 @@ hugo version
|
||||
|
||||
It should state that it is `extended`. If it does not, uninstall it and try another installation method.
|
||||
|
||||
{{< asciicast ItACREbFgvJ0HjnSNeTknxWy9 >}}
|
||||
|
||||
## Step 2: Create a New Site
|
||||
|
||||
```bash
|
||||
@@ -59,8 +57,6 @@ hugo new site quickstart
|
||||
|
||||
The above will create a new Hugo site in a folder named `quickstart`.
|
||||
|
||||
{{< asciicast 3mf1JGaN0AX0Z7j5kLGl3hSh8 >}}
|
||||
|
||||
## Step 3: Add a Theme
|
||||
|
||||
See [themes.gohugo.io](https://themes.gohugo.io/) for a list of themes to consider. This quickstart uses the beautiful [Ananke theme](https://themes.gohugo.io/gohugo-theme-ananke/).
|
||||
@@ -79,8 +75,6 @@ Then, add the theme to the site configuration:
|
||||
echo theme = \"ananke\" >> config.toml
|
||||
```
|
||||
|
||||
{{< asciicast 7naKerRYUGVPj8kiDmdh5k5h9 >}}
|
||||
|
||||
## Step 4: Add Some Content
|
||||
|
||||
You can manually create content files (for example as `content/<CATEGORY>/<FILE>.<FORMAT>`) and provide metadata in them, however you can use the `new` command to do a few things for you (like add title and date):
|
||||
@@ -89,8 +83,6 @@ You can manually create content files (for example as `content/<CATEGORY>/<FILE>
|
||||
hugo new posts/my-first-post.md
|
||||
```
|
||||
|
||||
{{< asciicast eUojYCfRTZvkEiqc52fUsJRBR >}}
|
||||
|
||||
Edit the newly created content file if you want, it will start with something like this:
|
||||
|
||||
```md
|
||||
@@ -110,8 +102,6 @@ Drafts do not get deployed; once you finish a post, update the header of the pos
|
||||
|
||||
Now, start the Hugo server with [drafts](/getting-started/usage/#draft-future-and-expired-content) enabled:
|
||||
|
||||
{{< asciicast BvJBsF6egk9c163bMsObhuNXj >}}
|
||||
|
||||
```txt
|
||||
▶ hugo server -D
|
||||
|
||||
|
||||
@@ -12,8 +12,6 @@ images:
|
||||
|
||||
Hugo has been caching the highlighter output to disk, so for repeated builds it has been fine, but this little snippet, showing a build of the [gohugo.io](https://gohugo.io/) site without cache and with both Pygments and Chroma, should illustrate the improvement:
|
||||
|
||||
{{< asciicast Lc5iwTVny2kuUC8lqvNnL6oDU >}}
|
||||
|
||||
See the [Updated Documentation](https://gohugo.io/content-management/syntax-highlighting/) for more information about how this works.
|
||||
|
||||
Worth mentioning is also the `liveReloadPort` flag on `hugo server`, which makes it possible to do "live reloads" behind a HTTPS proxy, which makes for very cool remote customer demos.
|
||||
@@ -61,4 +59,3 @@ Hugo now has:
|
||||
* Add `liveReloadPort` flag to server [b1804776](https://github.com/gohugoio/hugo/commit/b180477631555824a06293053e2b6e63c5f07361) [@bep](https://github.com/bep) [#3882](https://github.com/gohugoio/hugo/issues/3882)
|
||||
* Add `noHTTPCache` flag to hugo server (default on) [0b34af21](https://github.com/gohugoio/hugo/commit/0b34af216154367af7f53ce93d44e6b3d58c3f34) [@bep](https://github.com/bep) [#3897](https://github.com/gohugoio/hugo/issues/3897)
|
||||
* Make `noHTTPCache` default on [80c7ea60](https://github.com/gohugoio/hugo/commit/80c7ea60a0e0f488563a6b7311f3d4c23457aac7) [@bep](https://github.com/bep) [#3897](https://github.com/gohugoio/hugo/issues/3897)
|
||||
|
||||
|
||||
@@ -1,2 +0,0 @@
|
||||
{{ $id := .Get 0 }}
|
||||
<script type="text/javascript" src="https://asciinema.org/a/{{ $id }}.js" id="asciicast-{{ $id }}" data-rows="10" async></script>
|
||||
Reference in New Issue
Block a user