feat: Demo updates

I guess it's ready to be shown to Masto folks!
This commit is contained in:
daudix-UFO
2023-09-02 06:30:33 +03:00
parent c5f0d0280c
commit 86193ce7e5
6 changed files with 118 additions and 20 deletions

View File

@ -3,6 +3,7 @@ layout: post
title: "The Quill of Duck"
tags: Demo Test
toc: true
disclaimer: "See [demo](../demo) for showcase of all Duckquill possibilities, this page is a demo of a post with title, publication date, tags, disclaimer, table of contents and comments."
comments:
id:
---
@ -11,7 +12,19 @@ comments:
## The what?
This is a Duckquill post example, this post has nothing but a bunch of text and random formattings, acting like a demo.
This is a Duckquill post example, this post has nothing but a bunch of text and random formatting, acting like a demo.
## Some info for ya
Since you are here, lemme tell ya some nice tricks about creating posts
First, the naming. The URLs are very picky about them, so you shouldn't use spaces in them, and preferebly any other "special" character, if you managed to have a lot of posts with ugly names, you can use `rename.sh <DIR>` to fix the mess quickly, it works for any files really, useful for renaming assets.
The first thing in the name of post should be publicaion date, it should be in ISO 8601 format. On \*nix you can use `date -I` to quickly get one.
Now to the front matter, front matter in Jekyll is the weird thing at the top of Markdown file, that has 3 dashes at start and end. It includes needed info about your post so Jekyll can cook it properly. The important ones are `layout` that tells if the page are plain one or post, `title` with... well you get it, `tags` and `toc` that if exists or set to `true` will make Jekyll generate table of contents at top of the post.
Now to the _Stanley!_
## The Stanley!
@ -21,6 +34,8 @@ _Stanley_ worked for a company in a big building where he was Employee `#427`.
![The Office](../assets/posts/2023-08-31/The_Office.webp){:.full.media.hover}
<figcaption>The Office where Stanley works, it has yellow floor and beige walls</figcaption>
Employee `#427`'s job was simple: he sat at his desk in Room `427` and he pushed buttons on a keyboard.
Orders came to him through a monitor on his desk telling him what buttons to push, how long to push them, and in what order.