Skip to content

Commit 71e81ec

Browse files
jmooringbep
authored andcommittedNov 21, 2022
Remove asciicast from site
1 parent 1e56c65 commit 71e81ec

File tree

3 files changed

+0
-15
lines changed

3 files changed

+0
-15
lines changed
 

‎content/en/getting-started/quick-start.md

-10
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,6 @@ hugo version
4949

5050
It should state that it is `extended`. If it does not, uninstall it and try another installation method.
5151

52-
{{< asciicast ItACREbFgvJ0HjnSNeTknxWy9 >}}
53-
5452
## Step 2: Create a New Site
5553

5654
```bash
@@ -59,8 +57,6 @@ hugo new site quickstart
5957

6058
The above will create a new Hugo site in a folder named `quickstart`.
6159

62-
{{< asciicast 3mf1JGaN0AX0Z7j5kLGl3hSh8 >}}
63-
6460
## Step 3: Add a Theme
6561

6662
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:
7975
echo theme = \"ananke\" >> config.toml
8076
```
8177

82-
{{< asciicast 7naKerRYUGVPj8kiDmdh5k5h9 >}}
83-
8478
## Step 4: Add Some Content
8579

8680
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>
8983
hugo new posts/my-first-post.md
9084
```
9185

92-
{{< asciicast eUojYCfRTZvkEiqc52fUsJRBR >}}
93-
9486
Edit the newly created content file if you want, it will start with something like this:
9587

9688
```md
@@ -110,8 +102,6 @@ Drafts do not get deployed; once you finish a post, update the header of the pos
110102

111103
Now, start the Hugo server with [drafts](/getting-started/usage/#draft-future-and-expired-content) enabled:
112104

113-
{{< asciicast BvJBsF6egk9c163bMsObhuNXj >}}
114-
115105
```txt
116106
▶ hugo server -D
117107

‎content/en/news/0.28-relnotes/index.md

-3
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ images:
1212

1313
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:
1414

15-
{{< asciicast Lc5iwTVny2kuUC8lqvNnL6oDU >}}
16-
1715
See the [Updated Documentation](https://gohugo.io/content-management/syntax-highlighting/) for more information about how this works.
1816

1917
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:
6159
* 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)
6260
* 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)
6361
* 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)
64-

‎layouts/shortcodes/asciicast.html

-2
This file was deleted.

0 commit comments

Comments
 (0)
Please sign in to comment.