mirror of
https://github.com/KazooTTT/kazoottt-blog.git
synced 2025-06-23 18:51:31 +08:00
feat : remove md files
This commit is contained in:
KazooTTT
Binary file not shown.
|
Before Width: | Height: | Size: 591 KiB |
@ -1,11 +0,0 @@
|
|||||||
---
|
|
||||||
title: "Example Cover Image"
|
|
||||||
description: "This post is an example of how to add a cover/hero image"
|
|
||||||
publishDate: "04 July 2023"
|
|
||||||
updatedDate: "14 August 2023"
|
|
||||||
coverImage:
|
|
||||||
src: "./cover.png"
|
|
||||||
alt: "Astro build wallpaper"
|
|
||||||
tags: ["test", "image"]
|
|
||||||
category: c1
|
|
||||||
---
|
|
||||||
@ -1,10 +0,0 @@
|
|||||||
---
|
|
||||||
title: "A working draft title"
|
|
||||||
description: "This post is for testing the draft post functionality"
|
|
||||||
publishDate: "10 Sept 2023"
|
|
||||||
tags: ["test"]
|
|
||||||
draft: true
|
|
||||||
category: c2
|
|
||||||
---
|
|
||||||
|
|
||||||
If this is working correctly, this post should only be accessible in a dev environment, as well as any tags that are unique to this post.
|
|
||||||
@ -1,9 +0,0 @@
|
|||||||
---
|
|
||||||
title: "Lorem ipsum dolor sit, amet consectetur adipisicing elit. Id"
|
|
||||||
description: "This post is purely for testing if the css is correct for the title on the page"
|
|
||||||
publishDate: "01 Feb 2023"
|
|
||||||
tags: ["test"]
|
|
||||||
category: c3
|
|
||||||
---
|
|
||||||
|
|
||||||
## Testing the title tag
|
|
||||||
@ -1,161 +0,0 @@
|
|||||||
---
|
|
||||||
title: "A post of Markdown elements"
|
|
||||||
description: "This post is for testing and listing a number of different markdown elements"
|
|
||||||
publishDate: "22 Feb 2023"
|
|
||||||
updatedDate: 22 Jan 2024
|
|
||||||
tags: ["test", "markdown"]
|
|
||||||
---
|
|
||||||
|
|
||||||
## This is a H2 Heading
|
|
||||||
|
|
||||||
### This is a H3 Heading
|
|
||||||
|
|
||||||
#### This is a H4 Heading
|
|
||||||
|
|
||||||
##### This is a H5 Heading
|
|
||||||
|
|
||||||
###### This is a H6 Heading
|
|
||||||
|
|
||||||
## Horizontal Rules
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Emphasis
|
|
||||||
|
|
||||||
**This is bold text**
|
|
||||||
|
|
||||||
_This is italic text_
|
|
||||||
|
|
||||||
~~Strikethrough~~
|
|
||||||
|
|
||||||
## Quotes
|
|
||||||
|
|
||||||
"Double quotes" and 'single quotes'
|
|
||||||
|
|
||||||
## Blockquotes
|
|
||||||
|
|
||||||
> Blockquotes can also be nested...
|
|
||||||
>
|
|
||||||
> > ...by using additional greater-than signs right next to each other...
|
|
||||||
|
|
||||||
## References
|
|
||||||
|
|
||||||
An example containing a clickable reference[^1] with a link to the source.
|
|
||||||
|
|
||||||
Second example containing a reference[^2] with a link to the source.
|
|
||||||
|
|
||||||
[^1]: Reference first footnote with a return to content link.
|
|
||||||
[^2]: Second reference with a link.
|
|
||||||
|
|
||||||
If you check out this example in `src/content/post/markdown-elements/index.md`, you'll notice that the references and the heading "Footnotes" are added to the bottom of the page via the [remark-rehype](https://github.com/remarkjs/remark-rehype#options) plugin.
|
|
||||||
|
|
||||||
## Lists
|
|
||||||
|
|
||||||
Unordered
|
|
||||||
|
|
||||||
- Create a list by starting a line with `+`, `-`, or `*`
|
|
||||||
- Sub-lists are made by indenting 2 spaces:
|
|
||||||
- Marker character change forces new list start:
|
|
||||||
- Ac tristique libero volutpat at
|
|
||||||
- Facilisis in pretium nisl aliquet
|
|
||||||
- Nulla volutpat aliquam velit
|
|
||||||
- Very easy!
|
|
||||||
|
|
||||||
Ordered
|
|
||||||
|
|
||||||
1. Lorem ipsum dolor sit amet
|
|
||||||
2. Consectetur adipiscing elit
|
|
||||||
3. Integer molestie lorem at massa
|
|
||||||
|
|
||||||
4. You can use sequential numbers...
|
|
||||||
5. ...or keep all the numbers as `1.`
|
|
||||||
|
|
||||||
Start numbering with offset:
|
|
||||||
|
|
||||||
57. foo
|
|
||||||
1. bar
|
|
||||||
|
|
||||||
## Code
|
|
||||||
|
|
||||||
Inline `code`
|
|
||||||
|
|
||||||
Indented code
|
|
||||||
|
|
||||||
// Some comments
|
|
||||||
line 1 of code
|
|
||||||
line 2 of code
|
|
||||||
line 3 of code
|
|
||||||
|
|
||||||
Block code "fences"
|
|
||||||
|
|
||||||
```
|
|
||||||
Sample text here...
|
|
||||||
```
|
|
||||||
|
|
||||||
Syntax highlighting
|
|
||||||
|
|
||||||
```js
|
|
||||||
var foo = function (bar) {
|
|
||||||
return bar++;
|
|
||||||
};
|
|
||||||
|
|
||||||
console.log(foo(5));
|
|
||||||
```
|
|
||||||
|
|
||||||
### Expressive code examples
|
|
||||||
|
|
||||||
Adding a title
|
|
||||||
|
|
||||||
```js title="file.js"
|
|
||||||
console.log("Title example");
|
|
||||||
```
|
|
||||||
|
|
||||||
A bash terminal
|
|
||||||
|
|
||||||
```bash
|
|
||||||
echo "A base terminal example"
|
|
||||||
```
|
|
||||||
|
|
||||||
Highlighting code lines
|
|
||||||
|
|
||||||
```js title="line-markers.js" del={2} ins={3-4} {6}
|
|
||||||
function demo() {
|
|
||||||
console.log("this line is marked as deleted");
|
|
||||||
// This line and the next one are marked as inserted
|
|
||||||
console.log("this is the second inserted line");
|
|
||||||
|
|
||||||
return "this line uses the neutral default marker type";
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
[Expressive Code](https://expressive-code.com/) can do a ton more than shown here, and includes a lot of [customisation](https://expressive-code.com/reference/configuration/).
|
|
||||||
|
|
||||||
## Tables
|
|
||||||
|
|
||||||
| Option | Description |
|
|
||||||
| ------ | ------------------------------------------------------------------------- |
|
|
||||||
| data | path to data files to supply the data that will be passed into templates. |
|
|
||||||
| engine | engine to be used for processing templates. Handlebars is the default. |
|
|
||||||
| ext | extension to be used for dest files. |
|
|
||||||
|
|
||||||
Right aligned columns
|
|
||||||
|
|
||||||
| Option | Description |
|
|
||||||
| -----: | ------------------------------------------------------------------------: |
|
|
||||||
| data | path to data files to supply the data that will be passed into templates. |
|
|
||||||
| engine | engine to be used for processing templates. Handlebars is the default. |
|
|
||||||
| ext | extension to be used for dest files. |
|
|
||||||
|
|
||||||
## Images
|
|
||||||
|
|
||||||
Image in the same folder: `src/content/post/markdown-elements/logo.png`
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Links
|
|
||||||
|
|
||||||
[Content from markdown-it](https://markdown-it.github.io/)
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 4.2 KiB |
@ -1,6 +0,0 @@
|
|||||||
---
|
|
||||||
title: "This post doesn't have any content"
|
|
||||||
description: "This post is purely for testing the table of content, which should not be rendered"
|
|
||||||
publishDate: "22 Feb 2023"
|
|
||||||
tags: ["test", "toc"]
|
|
||||||
---
|
|
||||||
@ -1,22 +0,0 @@
|
|||||||
---
|
|
||||||
title: "Example OG Social Image"
|
|
||||||
publishDate: "27 January 2023"
|
|
||||||
description: "An example post for Astro Cactus, detailing how to add a custom social image card in the frontmatter"
|
|
||||||
tags: ["example", "blog", "image"]
|
|
||||||
ogImage: "/social-card.png"
|
|
||||||
---
|
|
||||||
|
|
||||||
## Adding your own social image to a post
|
|
||||||
|
|
||||||
This post is an example of how to add a custom [open graph](https://ogp.me/) social image, also known as an OG image, to a blog post.
|
|
||||||
By adding the optional ogImage property to the frontmatter of a post, you opt out of [satori](https://github.com/vercel/satori) automatically generating an image for this page.
|
|
||||||
|
|
||||||
If you open this markdown file `src/content/post/social-image.md` you'll see the ogImage property set to an image which lives in the public folder[^1].
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
ogImage: "/social-card.png"
|
|
||||||
```
|
|
||||||
|
|
||||||
You can view the one set for this template page [here](https://astro-cactus.chriswilliams.dev/social-card.png).
|
|
||||||
|
|
||||||
[^1]: The image itself can be located anywhere you like.
|
|
||||||
@ -1,12 +0,0 @@
|
|||||||
---
|
|
||||||
title: "Unique tags validation"
|
|
||||||
publishDate: "30 January 2023"
|
|
||||||
description: "This post is used for validating if duplicate tags are removed, regardless of the string case"
|
|
||||||
tags: ["blog", "blog", "Blog", "test", "bloG", "Test", "BLOG"]
|
|
||||||
---
|
|
||||||
|
|
||||||
## This post is to test zod transform
|
|
||||||
|
|
||||||
If you open the file `src/content/post/unique-tags.md`, the tags array has a number of duplicate blog strings of various cases.
|
|
||||||
|
|
||||||
These are removed as part of the removeDupsAndLowercase function found in `src/content/config.ts`.
|
|
||||||
Reference in New Issue
Block a user