diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..d8f52df
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1 @@
+*.mdx linguist-vendored
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
index 16d54bb..7b9c288 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,24 +1,13 @@
-# build output
dist/
-# generated types
.astro/
-
-# dependencies
node_modules/
-
-# logs
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
-
-
-# environment variables
.env
.env.production
-
-# macOS-specific files
.DS_Store
-
-# jetbrains setting folder
.idea/
+teaser.pptx
+~$teaser.pptx
\ No newline at end of file
diff --git a/.prettierrc b/.prettierrc
deleted file mode 100644
index e1265f8..0000000
--- a/.prettierrc
+++ /dev/null
@@ -1,9 +0,0 @@
-{
- "useTabs": false,
- "printWidth": 800,
- "tabWidth": 2,
- "singleQuote": true,
- "trailingComma": "all",
- "semi": false,
- "plugins": ["prettier-plugin-astro"]
-}
\ No newline at end of file
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
deleted file mode 100644
index 56f043d..0000000
--- a/.vscode/extensions.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "recommendations": ["astro-build.astro-vscode", "unifiedjs.vscode-mdx"],
- "unwantedRecommendations": []
-}
diff --git a/.vscode/launch.json b/.vscode/launch.json
deleted file mode 100644
index d642209..0000000
--- a/.vscode/launch.json
+++ /dev/null
@@ -1,11 +0,0 @@
-{
- "version": "0.2.0",
- "configurations": [
- {
- "command": "./node_modules/.bin/astro dev",
- "name": "Development server",
- "request": "launch",
- "type": "node-terminal"
- }
- ]
-}
diff --git a/.vscode/settings.json b/.vscode/settings.json
deleted file mode 100644
index c9be8be..0000000
--- a/.vscode/settings.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- "css.customData": [".vscode/tailwind.json"],
- "editor.tabSize": 2,
- "editor.insertSpaces": true,
- "editor.detectIndentation": false,
- "prettier.documentSelectors": ["**/*.astro"],
- "[astro]": {
- "editor.defaultFormatter": "esbenp.prettier-vscode"
- }
-}
\ No newline at end of file
diff --git a/.vscode/tailwind.json b/.vscode/tailwind.json
deleted file mode 100644
index 9ccc998..0000000
--- a/.vscode/tailwind.json
+++ /dev/null
@@ -1,55 +0,0 @@
-{
- "version": 1.1,
- "atDirectives": [
- {
- "name": "@tailwind",
- "description": "Use the `@tailwind` directive to insert Tailwind's `base`, `components`, `utilities` and `screens` styles into your CSS.",
- "references": [
- {
- "name": "Tailwind Documentation",
- "url": "https://tailwindcss.com/docs/functions-and-directives#tailwind"
- }
- ]
- },
- {
- "name": "@apply",
- "description": "Use the `@apply` directive to inline any existing utility classes into your own custom CSS. This is useful when you find a common utility pattern in your HTML that you’d like to extract to a new component.",
- "references": [
- {
- "name": "Tailwind Documentation",
- "url": "https://tailwindcss.com/docs/functions-and-directives#apply"
- }
- ]
- },
- {
- "name": "@responsive",
- "description": "You can generate responsive variants of your own classes by wrapping their definitions in the `@responsive` directive:\n```css\n@responsive {\n .alert {\n background-color: #E53E3E;\n }\n}\n```\n",
- "references": [
- {
- "name": "Tailwind Documentation",
- "url": "https://tailwindcss.com/docs/functions-and-directives#responsive"
- }
- ]
- },
- {
- "name": "@screen",
- "description": "The `@screen` directive allows you to create media queries that reference your breakpoints by **name** instead of duplicating their values in your own CSS:\n```css\n@screen sm {\n /* ... */\n}\n```\n…gets transformed into this:\n```css\n@media (min-width: 640px) {\n /* ... */\n}\n```\n",
- "references": [
- {
- "name": "Tailwind Documentation",
- "url": "https://tailwindcss.com/docs/functions-and-directives#screen"
- }
- ]
- },
- {
- "name": "@variants",
- "description": "Generate `hover`, `focus`, `active` and other **variants** of your own utilities by wrapping their definitions in the `@variants` directive:\n```css\n@variants hover, focus {\n .btn-brand {\n background-color: #3182CE;\n }\n}\n```\n",
- "references": [
- {
- "name": "Tailwind Documentation",
- "url": "https://tailwindcss.com/docs/functions-and-directives#variants"
- }
- ]
- }
- ]
- }
\ No newline at end of file
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..f643981
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Trevor Lee
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
index 758716e..7b779b7 100644
--- a/README.md
+++ b/README.md
@@ -1,68 +1,286 @@
-# Astro Starter Kit: Blog
+
-```sh
-npm create astro@latest -- --template blog
+
+ )
+}
+
+function PaginationItem({ ...props }: React.ComponentProps<'li'>) {
+ return
+}
+
+type PaginationLinkProps = {
+ isActive?: boolean
+ isDisabled?: boolean
+} & Pick, 'size'> &
+ React.ComponentProps<'a'>
+
+function PaginationLink({
+ className,
+ isActive,
+ isDisabled,
+ size = 'icon',
+ ...props
+}: PaginationLinkProps) {
+ return (
+
+ )
+}
+
+function PaginationPrevious({
+ className,
+ isDisabled,
+ ...props
+}: React.ComponentProps) {
+ return (
+
+
+ Previous
+
+ )
+}
+
+function PaginationNext({
+ className,
+ isDisabled,
+ ...props
+}: React.ComponentProps) {
+ return (
+
+ Next
+
+
+ )
+}
+
+function PaginationEllipsis({
+ className,
+ ...props
+}: React.ComponentProps<'span'>) {
+ return (
+
+
+ More pages
+
+ )
+}
+
+const PaginationComponent: React.FC = ({
+ currentPage,
+ totalPages,
+ baseUrl,
+}) => {
+ const pages = Array.from({ length: totalPages }, (_, i) => i + 1)
+
+ const getPageUrl = (page: number) => {
+ if (page === 1) return baseUrl
+ return `${baseUrl}${page}`
+ }
+
+ return (
+
+
+
+ 1 ? getPageUrl(currentPage - 1) : undefined}
+ isDisabled={currentPage === 1}
+ />
+
+
+ {pages.map((page) => (
+
+
+ {page}
+
+
+ ))}
+
+ {totalPages > 5 && (
+
+
+
+ )}
+
+
+
+
+
+
+ )
+}
+
+interface PaginationProps {
+ currentPage: number
+ totalPages: number
+ baseUrl: string
+}
+
+export default PaginationComponent
+
+export {
+ Pagination,
+ PaginationContent,
+ PaginationLink,
+ PaginationItem,
+ PaginationPrevious,
+ PaginationNext,
+ PaginationEllipsis,
+}
diff --git a/src/components/ui/scroll-area.tsx b/src/components/ui/scroll-area.tsx
new file mode 100644
index 0000000..9e28547
--- /dev/null
+++ b/src/components/ui/scroll-area.tsx
@@ -0,0 +1,56 @@
+import * as React from 'react'
+import { ScrollArea as ScrollAreaPrimitive } from 'radix-ui'
+
+import { cn } from '@/lib/utils'
+
+function ScrollArea({
+ className,
+ children,
+ ...props
+}: React.ComponentProps) {
+ return (
+
+
+ {children}
+
+
+
+
+ )
+}
+
+function ScrollBar({
+ className,
+ orientation = 'vertical',
+ ...props
+}: React.ComponentProps) {
+ return (
+
+
+
+ )
+}
+
+export { ScrollArea, ScrollBar }
diff --git a/src/components/ui/separator.tsx b/src/components/ui/separator.tsx
new file mode 100644
index 0000000..8624369
--- /dev/null
+++ b/src/components/ui/separator.tsx
@@ -0,0 +1,26 @@
+import * as React from 'react'
+import { Separator as SeparatorPrimitive } from 'radix-ui'
+
+import { cn } from '@/lib/utils'
+
+function Separator({
+ className,
+ orientation = 'horizontal',
+ decorative = true,
+ ...props
+}: React.ComponentProps) {
+ return (
+
+ )
+}
+
+export { Separator }
diff --git a/src/consts.ts b/src/consts.ts
index 4470a79..ee6e96d 100644
--- a/src/consts.ts
+++ b/src/consts.ts
@@ -1,5 +1,55 @@
-// Place any global data in this file.
-// You can import this data from anywhere in your site by using the `import` keyword.
+import type { IconMap, SocialLink, Site } from '@/types'
-export const SITE_TITLE = 'Sr Izan\'s website';
-export const SITE_DESCRIPTION = 'Welcome to my website!';
+export const SITE: Site = {
+ title: 'astro-erudite',
+ description:
+ 'astro-erudite is a opinionated, unstyled blogging template—built with Astro, Tailwind, and shadcn/ui.',
+ href: 'https://astro-erudite.vercel.app',
+ author: 'jktrn',
+ locale: 'en-US',
+ featuredPostCount: 2,
+ postsPerPage: 3,
+}
+
+export const NAV_LINKS: SocialLink[] = [
+ {
+ href: '/blog',
+ label: 'blog',
+ },
+ {
+ href: '/authors',
+ label: 'authors',
+ },
+ {
+ href: '/about',
+ label: 'about',
+ },
+]
+
+export const SOCIAL_LINKS: SocialLink[] = [
+ {
+ href: 'https://github.com/jktrn',
+ label: 'GitHub',
+ },
+ {
+ href: 'https://twitter.com/enscry',
+ label: 'Twitter',
+ },
+ {
+ href: 'mailto:jason@enscribe.dev',
+ label: 'Email',
+ },
+ {
+ href: '/rss.xml',
+ label: 'RSS',
+ },
+]
+
+export const ICON_MAP: IconMap = {
+ Website: 'lucide:globe',
+ GitHub: 'lucide:github',
+ LinkedIn: 'lucide:linkedin',
+ Twitter: 'lucide:twitter',
+ Email: 'lucide:mail',
+ RSS: 'lucide:rss',
+}
diff --git a/src/content.config.ts b/src/content.config.ts
new file mode 100644
index 0000000..09c56ff
--- /dev/null
+++ b/src/content.config.ts
@@ -0,0 +1,48 @@
+import { glob } from 'astro/loaders'
+import { defineCollection, z } from 'astro:content'
+
+const blog = defineCollection({
+ loader: glob({ pattern: '**/*.{md,mdx}', base: './src/content/blog' }),
+ schema: ({ image }) =>
+ z.object({
+ title: z.string(),
+ description: z.string(),
+ date: z.coerce.date(),
+ image: image().optional(),
+ tags: z.array(z.string()).optional(),
+ authors: z.array(z.string()).optional(),
+ draft: z.boolean().optional(),
+ }),
+})
+
+const authors = defineCollection({
+ loader: glob({ pattern: '**/*.{md,mdx}', base: './src/content/authors' }),
+ schema: z.object({
+ name: z.string(),
+ pronouns: z.string().optional(),
+ avatar: z.string().url().or(z.string().startsWith('/')),
+ bio: z.string().optional(),
+ mail: z.string().email().optional(),
+ website: z.string().url().optional(),
+ twitter: z.string().url().optional(),
+ github: z.string().url().optional(),
+ linkedin: z.string().url().optional(),
+ discord: z.string().url().optional(),
+ }),
+})
+
+const projects = defineCollection({
+ loader: glob({ pattern: '**/*.{md,mdx}', base: './src/content/projects' }),
+ schema: ({ image }) =>
+ z.object({
+ name: z.string(),
+ description: z.string(),
+ tags: z.array(z.string()),
+ image: image(),
+ link: z.string().url(),
+ startDate: z.coerce.date().optional(),
+ endDate: z.coerce.date().optional(),
+ }),
+})
+
+export const collections = { blog, authors, projects }
diff --git a/src/content/authors/enscribe.md b/src/content/authors/enscribe.md
new file mode 100644
index 0000000..57cac26
--- /dev/null
+++ b/src/content/authors/enscribe.md
@@ -0,0 +1,10 @@
+---
+name: 'enscribe'
+pronouns: 'he/him'
+avatar: 'https://gravatar.com/avatar/9bfdc4ec972793cf05cb91efce5f4aaaec2a0da1bf4ec34dad0913f1d845faf6.webp?size=256'
+bio: 'd(-_-)b'
+website: 'https://enscribe.dev'
+twitter: 'https://twitter.com/enscry'
+github: 'https://github.com/jktrn'
+mail: 'jason@enscribe.dev'
+---
diff --git a/src/content/blog/2023-post/banner.png b/src/content/blog/2023-post/banner.png
new file mode 100644
index 0000000..a642338
Binary files /dev/null and b/src/content/blog/2023-post/banner.png differ
diff --git a/src/content/blog/2023-post/index.mdx b/src/content/blog/2023-post/index.mdx
new file mode 100644
index 0000000..d805c02
--- /dev/null
+++ b/src/content/blog/2023-post/index.mdx
@@ -0,0 +1,10 @@
+---
+title: '2023 Post'
+description: 'This is a dummy post written in the year 2023.'
+date: 2023-06-01
+tags: ['v1.0.0']
+image: './banner.png'
+authors: ['enscribe']
+---
+
+This is a dummy post written in the year 2023.
diff --git a/src/content/blog/2024-post/banner.png b/src/content/blog/2024-post/banner.png
new file mode 100644
index 0000000..a642338
Binary files /dev/null and b/src/content/blog/2024-post/banner.png differ
diff --git a/src/content/blog/2024-post/index.mdx b/src/content/blog/2024-post/index.mdx
new file mode 100644
index 0000000..dda8300
--- /dev/null
+++ b/src/content/blog/2024-post/index.mdx
@@ -0,0 +1,154 @@
+---
+title: '2024 Post'
+description: 'This is a dummy post written in the year 2024 (with multiple authors).'
+date: 2024-06-01
+tags: ['v1.0.0']
+image: './banner.png'
+authors: ['enscribe', 'jktrn']
+---
+
+This is a dummy post written in the year 2024! Here is a long blog post with heavily nested headers, which can be used to test the table of contents:
+
+## Test 2
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+##### Test 5
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+##### Test 5
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+##### Test 5
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+##### Test 5
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+###### Test 6
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+#### Test 4
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+##### Test 5
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
+
+### Test 3
+
+Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
diff --git a/src/content/blog/callouts-component/banner.png b/src/content/blog/callouts-component/banner.png
new file mode 100644
index 0000000..2ba53be
Binary files /dev/null and b/src/content/blog/callouts-component/banner.png differ
diff --git a/src/content/blog/callouts-component/index.mdx b/src/content/blog/callouts-component/index.mdx
new file mode 100644
index 0000000..3d0bc25
--- /dev/null
+++ b/src/content/blog/callouts-component/index.mdx
@@ -0,0 +1,442 @@
+---
+title: 'v1.5.0: “A Callout Component for Nerds”'
+description: 'A quick update introduces our first content-based component: the callout!'
+date: 2025-04-24
+tags: ['v1.5.0']
+image: './banner.png'
+authors: ['enscribe']
+---
+
+import Callout from '@/components/Callout.astro'
+import { Icon } from 'astro-icon/components'
+
+## Our (hesitantly) first content-based component
+
+This new version of astro-erudite, v1.5.0, introduces our first content-based component: the callout! I was a bit hesitant about adding this component because, frankly, the entire philosophy behind this project was to be as minimalistic as possible—I wanted to simply provide boilerplate to remove the "busy work" factor that often takes away from the writing process.
+
+However, just based on some blog posts I've seen that use this template, I felt like there would be a universal desire just to have this component around in the case where it'd be needed. The primary inspiration came when user [@rezaarezvan](https://github.com/rezaarezvan) sent in a PR to add their site, [rezaarezvan.com](https://rezaarezvan.com), to the examples section in the README. They had years upon years of accumulated notes and resources on their site, most of which were in the form of LaTeX-style academic content that requires "blocks" for things like definitions, theorems, and proofs. I sent in an encouraging reply to the PR and then started building the component:
+
+> [[@jktrn]](https://github.com/jktrn/astro-erudite/pull/29#issuecomment-2814894034) your blog posts are literally insane btw @rezaarezvan how have you written multiple textbooks worth of educational resources???
+>
+> i think i might add latex-style theorem/lemma/corollary/def/proof/eg/ex/remark blocks to astro-erudite so i can accommodate for these academia-style blogs, like e.g. for exercises it'd just be a component with an expandable section to hide the answer
+
+### How does it work?
+
+I've added a simple `Callout.astro` to `src/components` that now comes shipped with the template. It's a very easy-to-read component that has an insanely long configuration scheme for all of the different types of callouts that I've added. Fundamentally, it follows the same paradigm as [shadcn/ui](https://ui.shadcn.com) which uses [class-variance-authority](https://cva.style/docs) to create different "variants" on top of a base styling scheme:
+
+```astro title="src/components/Callout.astro" collapse={12-126} {8-10,131}
+---
+import { cn } from '@/lib/utils'
+import { Icon } from 'astro-icon/components'
+import { cva, type VariantProps } from 'class-variance-authority'
+
+const calloutConfig = {
+ note: {
+ style: 'border-blue-500 dark:bg-blue-950/5',
+ textColor: 'text-blue-700 dark:text-blue-300',
+ icon: 'lucide:info',
+ },
+ tip: {
+ style: 'border-green-500 dark:bg-green-950/5',
+ textColor: 'text-green-700 dark:text-green-300',
+ icon: 'lucide:lightbulb',
+ },
+ warning: {
+ style: 'border-amber-500 dark:bg-amber-950/5',
+ textColor: 'text-amber-700 dark:text-amber-300',
+ icon: 'lucide:alert-triangle',
+ },
+ danger: {
+ style: 'border-red-500 dark:bg-red-950/5',
+ textColor: 'text-red-700 dark:text-red-300',
+ icon: 'lucide:shield-alert',
+ },
+ important: {
+ style: 'border-purple-500 dark:bg-purple-950/5',
+ textColor: 'text-purple-700 dark:text-purple-300',
+ icon: 'lucide:message-square-warning',
+ },
+ definition: {
+ style: 'border-purple-500 dark:bg-purple-950/5',
+ textColor: 'text-purple-700 dark:text-purple-300',
+ icon: 'lucide:book-open',
+ },
+ theorem: {
+ style: 'border-teal-500 dark:bg-teal-950/5',
+ textColor: 'text-teal-700 dark:text-teal-300',
+ icon: 'lucide:check-circle',
+ },
+ lemma: {
+ style: 'border-sky-400 dark:bg-sky-950/5',
+ textColor: 'text-sky-700 dark:text-sky-300',
+ icon: 'lucide:puzzle',
+ },
+ proof: {
+ style: 'border-gray-500 dark:bg-gray-950/5',
+ textColor: 'text-gray-700 dark:text-gray-300',
+ icon: 'lucide:check-square',
+ },
+ corollary: {
+ style: 'border-cyan-500 dark:bg-cyan-950/5',
+ textColor: 'text-cyan-700 dark:text-cyan-300',
+ icon: 'lucide:git-branch',
+ },
+ proposition: {
+ style: 'border-slate-500 dark:bg-slate-950/5',
+ textColor: 'text-slate-700 dark:text-slate-300',
+ icon: 'lucide:file-text',
+ },
+ axiom: {
+ style: 'border-violet-600 dark:bg-violet-950/5',
+ textColor: 'text-violet-700 dark:text-violet-300',
+ icon: 'lucide:anchor',
+ },
+ conjecture: {
+ style: 'border-pink-500 dark:bg-pink-950/5',
+ textColor: 'text-pink-700 dark:text-pink-300',
+ icon: 'lucide:help-circle',
+ },
+ notation: {
+ style: 'border-slate-400 dark:bg-slate-950/5',
+ textColor: 'text-slate-700 dark:text-slate-300',
+ icon: 'lucide:pen-tool',
+ },
+ remark: {
+ style: 'border-gray-400 dark:bg-gray-950/5',
+ textColor: 'text-gray-700 dark:text-gray-300',
+ icon: 'lucide:message-circle',
+ },
+ intuition: {
+ style: 'border-yellow-500 dark:bg-yellow-950/5',
+ textColor: 'text-yellow-700 dark:text-yellow-300',
+ icon: 'lucide:lightbulb',
+ },
+ recall: {
+ style: 'border-blue-300 dark:bg-blue-950/5',
+ textColor: 'text-blue-600 dark:text-blue-300',
+ icon: 'lucide:rotate-ccw',
+ },
+ explanation: {
+ style: 'border-lime-500 dark:bg-lime-950/5',
+ textColor: 'text-lime-700 dark:text-lime-300',
+ icon: 'lucide:help-circle',
+ },
+ example: {
+ style: 'border-emerald-500 dark:bg-emerald-950/5',
+ textColor: 'text-emerald-700 dark:text-emerald-300',
+ icon: 'lucide:code',
+ },
+ exercise: {
+ style: 'border-indigo-500 dark:bg-indigo-950/5',
+ textColor: 'text-indigo-700 dark:text-indigo-300',
+ icon: 'lucide:dumbbell',
+ },
+ problem: {
+ style: 'border-orange-600 dark:bg-orange-950/5',
+ textColor: 'text-orange-700 dark:text-orange-300',
+ icon: 'lucide:alert-circle',
+ },
+ answer: {
+ style: 'border-teal-500 dark:bg-teal-950/5',
+ textColor: 'text-teal-700 dark:text-teal-300',
+ icon: 'lucide:check',
+ },
+ solution: {
+ style: 'border-emerald-600 dark:bg-emerald-950/5',
+ textColor: 'text-emerald-700 dark:text-emerald-300',
+ icon: 'lucide:check-circle-2',
+ },
+ summary: {
+ style: 'border-sky-500 dark:bg-sky-950/5',
+ textColor: 'text-sky-700 dark:text-sky-300',
+ icon: 'lucide:list',
+ },
+} as const
+
+const capitalize = (str: string) => str.charAt(0).toUpperCase() + str.slice(1)
+
+const calloutVariants = cva('relative px-4 py-3 my-6 border-l-4 text-sm', {
+ variants: {
+ variant: Object.fromEntries(
+ Object.entries(calloutConfig).map(([key, config]) => [key, config.style]),
+ ),
+ },
+ defaultVariants: {
+ variant: 'note',
+ },
+})
+```
+
+As such, if you feel like there's any variant that you're missing, it's insanely trivial to add it yourself. It's less trivial, however, to figure out what colors to use since I've essentially taken up every good Tailwind color for these!
+
+### How do I use these?
+
+Within any `src/content/blog/**/*.mdx` file, you can now use the `Callout` component by importing it like so underneath your frontmatter:
+
+```mdx title="src/content/blog/callouts-component/index.mdx" add={10}
+---
+title: 'v1.5.0: “A Callout Component for Nerds”'
+description: 'A quick update introduces our first content-based component: the callout!'
+date: 2025-04-24
+tags: ['v1.5.0']
+image: './1200x630.png'
+authors: ['enscribe']
+---
+
+import Callout from '@/components/Callout.astro'
+```
+
+Then, you can use the component like so. This is just an example but you should actually read the text since it's relevant to the article:
+
+````mdx showLineNumbers=false collapse={3-11}
+
+ I know that Github typically uses the following syntax for "alerts" (which is what they call these callouts, you can see their documentation [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts)):
+ ```md showLineNumbers=false
+ > [!NOTE]
+ > Useful information that users should know, even when skimming content.
+ ```
+ The above syntax is supposed to render like this:
+
+ Useful information that users should know, even when skimming content.
+
+ I believe they do this so they can keep you within the Markdown-like syntax system. However, since this is MDX, I thought we'd be better off just using the component paradigm since it's a bit impractical to make a rehype plugin that can parse this form of syntax (also, solutions for this already exist, such as [lin-stephanie/rehype-callouts](https://github.com/lin-stephanie/rehype-callouts)). Additionally, I find it a pain to work with the `>{:md}` (the `
{:html}` indicators for Markdown) syntax, as it makes it difficult to nest things such as code blocks within them in pure Markdown. We'll use components for now!
+
+````
+
+
+ I know that Github typically uses the following syntax for "alerts" (which is what they call these callouts, you can see their documentation [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts)):
+ ```md showLineNumbers=false
+ > [!NOTE]
+ > Useful information that users should know, even when skimming content.
+ ```
+ The above syntax is supposed to render like this:
+
+ Useful information that users should know, even when skimming content.
+
+ I believe they do this so they can keep you within the Markdown-like syntax system. However, since this is MDX, I thought we'd be better off just using the component paradigm since it's a bit impractical to make a rehype plugin that can parse this form of syntax (also, solutions for this already exist, such as [lin-stephanie/rehype-callouts](https://github.com/lin-stephanie/rehype-callouts)). Additionally, I find it a pain to work with the `>{:md}` (the `
{:html}` indicators for Markdown) syntax, as it makes it difficult to nest things such as code blocks within them in pure Markdown. We'll use components for now!
+
+
+Callout only supports three props:
+
+| Prop | Description | Default |
+| ---- | ----------- | ------- |
+| `title` | The title of the callout | `undefined{:js}` |
+| `variant` | The variant of the callout | `"note"{:js}` |
+| `defaultOpen` | Whether the callout `{:html}` box is open by default | `true{:js}` |
+
+I've added an insane amount of variants to this component for potentially any use case you could think of. For the more general ones, you can use the following:
+
+
+| Variant | Usage |
+| ------- | ----- |
+| Note | For general information or comments that don't fit other categories |
+| Tip | For helpful advice or shortcuts related to the topic at hand |
+| Warning | For potential pitfalls or common misconceptions |
+| Danger | For things that could potentially be destructive or harmful |
+| Important | For things that are important to the reader's understanding |
+
+
+For the potentially more academic/mathy folk, you can use the following. I've created specific variants that are tailor-made to be used alongside and/or nested into each other:
+
+
+| Variant | Usage |
+| ------- | ----- |
+| Definition | For defining terms or concepts |
+| Theorem | For important mathematical or logical statements that have been proven |
+| Lemma | For helper theorems used in proving larger results |
+| Proof | For logical arguments that establish the truth of a theorem or lemma |
+| Corollary | For results that follow directly from theorems |
+| Proposition | For important statements that are less significant than theorems |
+| Axiom | For fundamental assumptions that are accepted without proof |
+| Conjecture | For unproven statements believed to be true |
+| Notation | For explaining mathematical notation |
+| Remark | For additional comments or (potentially out-of-scope) observations |
+| Intuition | For explaining the intuitive reasoning behind concepts |
+| Recall | For reminding readers of previously covered material |
+| Explanation | For providing deeper insights or clarifying complex topics |
+| Example | For illustrating concepts with concrete examples or analogies |
+| Exercise | For practice problems or take-home challenges for the reader |
+| Problem | For presenting problems to be solved thoroughly |
+| Answer | For providing simple, short answers to exercises or problems |
+| Solution | For detailed solutions to exercises or problems |
+| Summary | For summarizing key points or concepts |
+
+
+## Generic callouts
+
+These are what the generic callouts look like (of course, all the text is made up):
+
+
+ This tutorial assumes you're familiar with React hooks and the component lifecycle. If you need a refresher, check out the [official React documentation](https://reactjs.org/docs/hooks-intro.html) before proceeding.
+
+
+
+ You can quickly format your code by pressing Ctrl + Alt + F (Windows/Linux) or Cmd + Option + F (Mac).
+
+ Additional shortcuts include:
+
+ | Action | Windows/Linux | Mac |
+ | ------ | ------------- | --- |
+ | Search | Ctrl + F | Cmd + F |
+ | Replace | Ctrl + H | Cmd + H |
+ | Save all | Ctrl + Alt + S | Cmd + Option + S |
+
+
+
+ This API is **not supported** in Internet Explorer and has limited support in older browsers. Make sure to include appropriate polyfills.
+
+ ```js title="polyfill.js"
+ if (!Object.fromEntries) {
+ Object.fromEntries = function(entries) {
+ const obj = {};
+ for (const [key, value] of entries) {
+ obj[key] = value;
+ }
+ return obj;
+ };
+ }
+ ```
+
+ See the [Browser Compatibility Table](#) for detailed information.
+
+
+
+ Running this command will **permanently delete** all files in your current directory. Make sure to back up important data before proceeding.
+
+ ```bash title="danger.sh"
+ # This will delete everything in the current directory
+ rm -rf ./*
+ # Safer alternative with confirmation
+ rm -ri ./*
+ ```
+
+ This operation cannot be undone and recovery tools may not be able to restore your data.
+
+
+
+ Version 2.0 introduces significant API changes. You'll need to update your existing code to use the new parameter structure.
+
+ 1. The `configure(){:js}` method now returns a Promise
+ 2. Authentication requires an API key object instead of a string
+ 3. Event handlers use a new callback pattern
+
+ A migration example looks like the following:
+ ```diff lang="js"
+ - app.configure("api-key-string");
+ + await app.configure({ key: "api-key-string", version: "2.0" });
+
+ - app.on('event', callback);
+ + app.on('event', { handler: callback, options: { once: true } });
+ ```
+
+
+## Mathematical callouts
+
+Like I mentioned before, some of these variants are meant to be nested within each other. Take, for example, the following:
+
+
+ A function $f: X \rightarrow Y$ between topological spaces is continuous if for every open set $V \subseteq Y$, the preimage $f^{-1}(V) \subseteq X$ is open in $X$.
+
+
+ For metric spaces, continuity can be characterized by: $\forall \varepsilon > 0, \exists \delta > 0$ such that $d_X(x,y) < \delta \implies d_Y(f(x),f(y)) < \varepsilon$. This captures the intuition that points close to each other in $X$ map to points close to each other in $Y$.
+
+
+
+
+ Let $X_1, X_2, \ldots$ be a sequence of independent and identically distributed random variables with expected value $\mathbb{E}[X_i] = \mu < \infty$. Then for any $\varepsilon > 0$:
+ $$
+ \lim_{n \to \infty} P\left(\left|\frac{1}{n}\sum_{i=1}^{n}X_i - \mu\right| > \varepsilon\right) = 0
+ $$
+
+
+ We'll prove this using Chebyshev's inequality. Let $S_n = \sum_{i=1}^{n}X_i$ and $\sigma^2 = \text{Var}(X_i)$. By Chebyshev's inequality:
+ $$
+ P\left(\left|\frac{S_n}{n} - \mu\right| \geq \varepsilon\right) \leq \frac{\text{Var}(S_n/n)}{\varepsilon^2}
+ $$
+
+ Since the variables are independent, we have:
+ $$
+ \text{Var}(S_n/n) = \frac{\text{Var}(S_n)}{n^2} = \frac{n\sigma^2}{n^2} = \frac{\sigma^2}{n}
+ $$
+
+ Substituting this into our inequality:
+ $$
+ P\left(\left|\frac{S_n}{n} - \mu\right| \geq \varepsilon\right) \leq \frac{\sigma^2}{n\varepsilon^2}
+ $$
+
+ As $n \to \infty$, the right side approaches 0, which proves the theorem.
+
+
+
+
+ Let $(f_n)$ be a sequence of non-negative measurable functions such that $f_n(x) \leq f_{n+1}(x)$ for all $n \in \mathbb{N}$ and almost all $x$. Define $f(x) = \lim_{n \to \infty} f_n(x)$. Then:
+ $$
+ \lim_{n \to \infty} \int f_n \, d\mu = \int f \, d\mu
+ $$
+
+
+ Let $g_n = f_n \cdot \chi_E$ where $E = \{x : f(x) < \infty\}$. By Fatou's lemma:
+ $$
+ \int f \, d\mu = \int \lim_{n \to \infty} g_n \, d\mu \leq \liminf_{n \to \infty} \int g_n \, d\mu = \liminf_{n \to \infty} \int f_n \, d\mu
+ $$
+
+ For the reverse inequality, note that $f_n \leq f$ for all $n$, so $\int f_n \, d\mu \leq \int f \, d\mu$. Taking the limit:
+ $$
+ \limsup_{n \to \infty} \int f_n \, d\mu \leq \int f \, d\mu
+ $$
+
+ Combining these inequalities:
+ $$
+ \int f \, d\mu \leq \liminf_{n \to \infty} \int f_n \, d\mu \leq \limsup_{n \to \infty} \int f_n \, d\mu \leq \int f \, d\mu
+ $$
+
+ Therefore, $\lim_{n \to \infty} \int f_n \, d\mu = \int f \, d\mu$.
+
+
+
+I'll add this little subgenre of variant called "example-based" callouts that have more generally a question-answer format. For the "exercise-answer" pairing, the difference is that I'd recommend you default the answer to a closed state to hide the answer from any peeping readers until they've actually done the work themselves. Typically, the difference between an "Answer" and a "Solution" is that the answer basically just gives you the final answer, while the solution will show you the steps it takes to get to the answer:
+
+
+ Calculate the derivative of $f(x) = x^3 \sin(x)$ using the product rule.
+
+
+ $$
+ \frac{d}{dx}[x^3 \sin(x)] = 3x^2 \sin(x) + x^3 \cos(x)
+ $$
+
+
+
+
+ Prove that if a sequence $(a_n)$ converges to $L$, then the sequence of arithmetic means $(\frac{a_1 + a_2 + \ldots + a_n}{n})$ also converges to $L$.
+
+
+ Let $\varepsilon > 0$ be given. Since $(a_n)$ converges to $L$, there exists $N \in \mathbb{N}$ such that $|a_n - L| < \frac{\varepsilon}{2}$ for all $n \geq N$. Let $S_n = \frac{a_1 + a_2 + \ldots + a_n}{n}$ be the sequence of arithmetic means.
+
+ We can split $S_n$ as follows:
+ $$
+ S_n = \frac{a_1 + a_2 + \ldots + a_N + a_{N+1} + \ldots + a_n}{n}
+ $$
+
+ For $n > N$, we have:
+ $$
+ \begin{align*}
+ |S_n - L| &= \left|\frac{a_1 + a_2 + \ldots + a_n}{n} - L\right| \\
+ &= \left|\frac{a_1 + a_2 + \ldots + a_n - nL}{n}\right| \\
+ &= \left|\frac{(a_1 - L) + (a_2 - L) + \ldots + (a_n - L)}{n}\right| \\
+ &\leq \frac{|a_1 - L| + |a_2 - L| + \ldots + |a_N - L| + |a_{N+1} - L| + \ldots + |a_n - L|}{n}
+ \end{align*}
+ $$
+
+ Let $M = \max\{|a_1 - L|, |a_2 - L|, \ldots, |a_N - L|\}$. Then:
+ $$
+ |S_n - L| \leq \frac{NM + (n-N)\frac{\varepsilon}{2}}{n} = \frac{NM}{n} + \frac{n-N}{n} \cdot \frac{\varepsilon}{2}
+ $$
+
+ As $n \to \infty$, $\frac{NM}{n} \to 0$ and $\frac{n-N}{n} \to 1$. So for sufficiently large $n$, we have:
+ $$
+ |S_n - L| < \varepsilon
+ $$
+
+ Therefore, the sequence of arithmetic means converges to $L$.
+
+
diff --git a/src/content/blog/mobile-nav-and-subposts/assets/new-toc-closed.png b/src/content/blog/mobile-nav-and-subposts/assets/new-toc-closed.png
new file mode 100644
index 0000000..374f0e5
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/assets/new-toc-closed.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/assets/new-toc-open.png b/src/content/blog/mobile-nav-and-subposts/assets/new-toc-open.png
new file mode 100644
index 0000000..9d1d211
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/assets/new-toc-open.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/assets/old-toc.png b/src/content/blog/mobile-nav-and-subposts/assets/old-toc.png
new file mode 100644
index 0000000..dc30598
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/assets/old-toc.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/assets/subpost-navigation.png b/src/content/blog/mobile-nav-and-subposts/assets/subpost-navigation.png
new file mode 100644
index 0000000..5442426
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/assets/subpost-navigation.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/assets/subposts-listing.png b/src/content/blog/mobile-nav-and-subposts/assets/subposts-listing.png
new file mode 100644
index 0000000..60646b2
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/assets/subposts-listing.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/banner.png b/src/content/blog/mobile-nav-and-subposts/banner.png
new file mode 100644
index 0000000..e343baa
Binary files /dev/null and b/src/content/blog/mobile-nav-and-subposts/banner.png differ
diff --git a/src/content/blog/mobile-nav-and-subposts/index.mdx b/src/content/blog/mobile-nav-and-subposts/index.mdx
new file mode 100644
index 0000000..dd1a599
--- /dev/null
+++ b/src/content/blog/mobile-nav-and-subposts/index.mdx
@@ -0,0 +1,82 @@
+---
+title: 'v1.6.0: "Mobile Navigation & Subposts"'
+description: 'This new version introduces improved mobile navigation (via sticky table of contents) and the concept of "subposts."'
+date: 2025-05-21
+tags: ['v1.6.0']
+image: './banner.png'
+authors: ['enscribe']
+---
+
+## Two major improvements to the reading experience
+
+astro-erudite's v1.6.0 brings about two significant enhancements that I've been wanting to implement for quite some time! The first addresses a longstanding mobile UX issue, while the second introduces a content organization paradigm that I find interesting.
+
+### Mobile navigation
+
+The original table of contents implementation was frankly inadequate for mobile users. While desktop users enjoyed a beautiful sticky sidebar with scroll-aware highlighting, mobile users were stuck with a basic collapsible `{:html}` element that provided no indication of reading progress or current location within the post:
+
+
+
+
+
+The new mobile navigation system introduces a sticky header that sits just below the main site navigation, featuring a circular progress indicator and dynamic section display. As you scroll through a post, the progress circle fills to show how far you've read, while the text updates to reflect which section you're currently viewing. Tapping on this header expands a comprehensive table of contents that mirrors the desktop experience but in a mobile-friendly format:
+
+
+
+This gives users the same level of navigation control as if they were on desktop, in a very intuitive and mobile-friendly format.
+
+### Subposts for hierarchical content organization
+
+The second major feature is something I'm calling "subposts," a way to organize related content in a parent-child hierarchy within your blog. This concept came from when I was writing [this](https://enscribe.dev/blog/japan-retrospective) travel blog post on my personal site, where I essentially wanted a "subpost" for each day of the trip since it was way too long to fit into a single post.
+
+Instead of creating separate blog posts in a "series" (and thus clogging up your blog post listings with a bunch of smaller, tangentially-related posts), you can now automatically establish a parent-child relationship between posts by creating a folder for your main topic with an `index.mdx` file as your parent post, then adding additional `.mdx` files in the same folder as subposts. For example, this very post demonstrates the feature by containing two subposts that explore the technical implementation details of each feature. On desktop, we display a `{:tsx}` component on the right-hand side of the page that shows a list of all the subposts alongside the parent post:
+
+
+
+The file structure is intuitive: create a folder for your main topic with an `index.mdx` file as your parent post, then add additional `.mdx` files in the same folder as subposts. Astro's file-based routing handles the URL structure automatically, creating paths like `/blog/subposts` for the parent post and `/blog/subposts/mobile-navigation` and `/blog/subposts/subposts` for the subposts.
+
+#### Enhanced navigation patterns
+
+Of course, we need to adjust our `{:tsx}` component to support this new feature. Now, whenever we're reading a subpost, we now have the option to traverse between subposts or even upwards to the parent post:
+
+
+
+This is contextually aware, meaning that if you're reading a parent post (or a post with no children), then this component will only show adjacent parent-level posts.
+
+#### Hint: this is great for technical content
+
+The subposts feature particularly shines for technical content which is meant to educate. In a similar manner to a tutorial or a textbook, we can now fragment our content into more digestible and informative subposts which are easily traversable between each other and from the parent post, and the reader is now free to jump around to whichever subpost they're interested in.
+
+This post itself serves as an example, since you're currently reading the parent post (which I've called the "Index" post in the `{:tsx}` component) and the subposts are the two posts that I've written about the technical implementation details of each feature.
+
+What's great about the way I engineered subposts is that it's fully backwards-compatible with blog posts written before this, so there's no need to define extra frontmatter metadata or manually establish the parent-child relationships between posts. It serves lovely on the DX side as well!
+
+## Go ahead and read the subposts
+
+On desktop, the `{:tsx}` sticks to the right column on your screen, and you can click on any of the subposts to read them. On mobile, it will turn into a `{:tsx}` component that will appear underneath the sticky header, above the sticky table of contents we just added.
\ No newline at end of file
diff --git a/src/content/blog/mobile-nav-and-subposts/mobile-navigation.mdx b/src/content/blog/mobile-nav-and-subposts/mobile-navigation.mdx
new file mode 100644
index 0000000..ee8a989
--- /dev/null
+++ b/src/content/blog/mobile-nav-and-subposts/mobile-navigation.mdx
@@ -0,0 +1,151 @@
+---
+title: 'Implementing sticky mobile navigation'
+description: 'Technical deep-dive into the sticky mobile table of contents with progress tracking and smart section highlighting'
+date: 2025-05-21
+tags: ['v1.6.0']
+authors: ['enscribe']
+---
+
+import Callout from '@/components/Callout.astro'
+
+The original mobile table of contents was a simple collapsible element that lived within the post content. This created several usability issues:
+1. Users had no sense of how much content remained other than implying it based on the length of the browser scrollbar
+2. Once you scrolled past the TOC, you lose the ability to quickly navigate to other sections of the post without scrolling back up to the inline TOC
+3. Mobile users should have the exact same experience as desktop users in terms of navigation, and as of now the desktop experience was better (due to the sticky aside TOC)
+
+## Building the sticky header system
+
+Design-wise, the component is relatively simple, since it only includes a chevron to indicate expansion state, a circular progress indicator that fills as you scroll, and a dynamic text showing the current section (or a combination of sections, if multiple are visible at the same time).
+
+### Live scroll highlighting sucks
+
+One of the more interesting problems I encountered was how to handle the highlighting of sections as you scroll. Of course, this applies to both mobile and desktop versions, but in this update I changed the implementation of both.
+
+A naive implementation of live scroll highlighting would simply use an `IntersectionObserver(){:js}` to watch for headers entering and exiting the viewport. The issue with this is that it doesn't highlight anything if headers are no longer visible in your viewport, regardless of whether you're in a section that "belongs" to a heading.
+
+
+ Say that we have a post with the following structure:
+
+ ```markdown
+ ## Part 1
+ [500 lines of content]
+
+ ## Part 2
+ [500 lines of content]
+ ```
+
+ If you were to scroll way past the first heading and was deep into the first section underneath it, the naive implementation would not highlight the first heading because it's no longer in your viewport. This is unintuitive and a poor user experience. In a perfect world, if we were to view 250 lines of Part 1 and 250 lines of Part 2, then we would see both headings highlighted in the TOC and not need to make a decision about which heading to highlight.
+
+
+I used to rely on [jakelow/remark-sectionize](https://github.com/jake-low/remark-sectionize), a [remarkjs/remark](https://github.com/remarkjs/remark) plugin that retroactively generates `{:html}` tags based on the headers in the generated HTML. This would have done the following conversion:
+
+
+
+
+```markdown
+# Forest elephants
+
+## Introduction
+
+In this section, we discuss the lesser known forest elephants.
+
+## Habitat
+
+Forest elephants do not live in trees but among them.
+```
+
+
+
+
+```html
+
+
Forest elephants
+
+
Introduction
+
In this section, we discuss the lesser known forest elephants.
+
+
+
Habitat
+
Forest elephants do not live in trees but among them.
+
+
+```
+
+
+
+
+However, this approach had pretty complicated issues involving section nesting and the fact that we didn't have any control over its output other than by patching it. So, I decided to opt for a home-grown solution.
+
+### The concept of "jurisdictions"
+
+The naming is interesting but I felt like it was the most intuitive to me. Basically, I created a system that assigns each heading a "territory" that extends from its position to the start of the next heading (or the end of the document):
+
+```javascript title="src/components/TOCHeader.astro" startLineNumber={123}
+function buildHeadingJurisdictions() {
+ headingElements = Array.from(
+ document.querySelectorAll('.prose h2, .prose h3, .prose h4, .prose h5, .prose h6')
+ )
+
+ jurisdictions = headingElements.map((heading, index) => {
+ const nextHeading = headingElements[index + 1]
+ return {
+ id: heading.id,
+ start: heading.offsetTop,
+ end: nextHeading ? nextHeading.offsetTop : document.body.scrollHeight
+ }
+ })
+}
+```
+
+1. First, we collect all heading elements (`
{:html}` through `
{:html}`) from the document's prose content area using `.querySelectorAll(){:js}`.
+2. For each heading, we create a jurisdiction object that contains the heading's `id`, the vertical position where this section begins (the heading's `offsetTop` value, which we name `start`), and the vertical position where this section ends (the `offsetTop` of the next heading or the bottom of the document if it's the last heading, which we name `end`).
+
+This creates a map of "territories" that each heading controls. This is crucial for accurately tracking which jurisdictions are currently visible as the user scrolls, even when the actual heading element itself is no longer in view.
+
+### The decision to show all visible sections
+
+One of the more interesting decisions I made was to display all sections as comma-separated within the mobile TOC's unexpanded state. This manifests as follows:
+
+
+ Recall the previous example's scenario:
+ ```markdown
+ ## Part 1
+ [500 lines of content]
+
+ ## Part 2
+ [500 lines of content]
+ ```
+ If we saw 250 lines of Part 1 and 250 lines of Part 2, then the text snippet in the mobile TOC would read "Part 1, Part 2".
+
+
+The temptation is to implement a "smart" selection algorithm, perhaps showing the section with the most visible content, or the one closest to the viewport center, or to show the "deepest," most specifically nested section. However, this creates numerous edge cases:
+
+1. If you click to navigate to a short final section, it might never become the "primary" section because there isn't enough content below it to scroll it to the top of the viewport.
+
+2. As you scroll between sections, a "smart" selector might switch which section it considers primary at seemingly arbitrary points, creating a jarring experience.
+
+3. When your viewport shows roughly equal amounts of two sections, any selection algorithm becomes essentially arbitrary.
+
+By showing all visible sections, we give users complete awareness of their position in the document, eliminate the edge cases mentioned above, and create predictable behavior.
+
+## Progress indicator implementation
+
+The circular progress indicator provides immediate visual feedback about reading progress without requiring any interaction:
+
+```javascript title="src/components/TOCHeader.astro" startLineNumber={216}
+ function updateProgressCircle() {
+ if (!progressCircleElement) return
+ const scrollableDistance =
+ document.documentElement.scrollHeight - window.innerHeight
+ const scrollProgress =
+ scrollableDistance > 0
+ ? Math.min(Math.max(window.scrollY / scrollableDistance, 0), 1)
+ : 0
+ progressCircleElement.style.strokeDashoffset = (
+ PROGRESS_CIRCLE_CIRCUMFERENCE *
+ (1 - scrollProgress)
+ ).toString()
+ }
+```
+
+The progress is calculated as a ratio of current scroll position to total scrollable distance, then applied as a stroke-dashoffset to create the filling effect.
\ No newline at end of file
diff --git a/src/content/blog/mobile-nav-and-subposts/subposts.mdx b/src/content/blog/mobile-nav-and-subposts/subposts.mdx
new file mode 100644
index 0000000..05adc64
--- /dev/null
+++ b/src/content/blog/mobile-nav-and-subposts/subposts.mdx
@@ -0,0 +1,160 @@
+---
+title: 'Implementing file-based subpost routing'
+description: 'How file-based hierarchical content organization works under the hood'
+date: 2025-05-21
+tags: ['v1.6.0']
+authors: ['enscribe']
+---
+
+import Callout from '@/components/Callout.astro'
+
+The subposts feature leverages Astro's file-based routing to automatically detect parent-child relationships without any configuration. The entire implementation hinges on a simple observation: if a post ID contains a forward slash, it's a subpost.
+
+```typescript title="src/lib/data-utils.ts" startLineNumber={161}
+export function isSubpost(postId: string): boolean {
+ return postId.includes('/')
+}
+
+export function getParentId(subpostId: string): string {
+ return subpostId.split('/')[0]
+}
+```
+
+This is a pretty elegant solution which requires no frontmatter configuration, no manual relationship mapping, and zero migration effort for existing posts.
+
+## Navigation complexity
+
+One of the more intricate parts of this update was rethinking navigation. The original `getAdjacentPosts(){:ts}` function assumed simple previous/next relationships. With subposts, we now have three distinct navigation contexts:
+
+
+ Consider this structure:
+ ```
+ blog/
+ getting-started.mdx
+ react-tutorial/
+ index.mdx
+ components.mdx
+ state.mdx
+ advanced-patterns.mdx
+ ```
+
+ Navigation depends on context:
+ - From `getting-started.mdx`: next goes to `react-tutorial/index.mdx`
+ - From `react-tutorial/components.mdx`: next goes to `state.mdx`, previous to `index.mdx`
+ - From `react-tutorial/state.mdx`: previous goes to `components.mdx`, parent goes to `index.mdx`
+
+
+Here's how we handle this complexity:
+
+```typescript title="src/lib/data-utils.ts" startLineNumber={40}
+export async function getAdjacentPosts(currentId: string): Promise<{
+ newer: CollectionEntry<'blog'> | null
+ older: CollectionEntry<'blog'> | null
+ parent: CollectionEntry<'blog'> | null
+}> {
+ const allPosts = await getAllPosts()
+
+ if (isSubpost(currentId)) {
+ const parentId = getParentId(currentId)
+ const parent = allPosts.find((post) => post.id === parentId) || null
+
+ // Get all sibling subposts
+ const posts = await getCollection('blog')
+ const subposts = posts
+ .filter(
+ (post) =>
+ isSubpost(post.id) &&
+ getParentId(post.id) === parentId &&
+ !post.data.draft
+ )
+ .sort((a, b) => a.data.date.valueOf() - b.data.date.valueOf())
+
+ const currentIndex = subposts.findIndex((post) => post.id === currentId)
+
+ return {
+ newer: currentIndex < subposts.length - 1
+ ? subposts[currentIndex + 1]
+ : null,
+ older: currentIndex > 0
+ ? subposts[currentIndex - 1]
+ : null,
+ parent,
+ }
+ }
+
+ // For parent posts, only navigate among other parent-level posts
+ const parentPosts = allPosts.filter((post) => !isSubpost(post.id))
+ const currentIndex = parentPosts.findIndex((post) => post.id === currentId)
+
+ return {
+ newer: currentIndex > 0 ? parentPosts[currentIndex - 1] : null,
+ older: currentIndex < parentPosts.length - 1
+ ? parentPosts[currentIndex + 1]
+ : null,
+ parent: null,
+ }
+}
+```
+
+As a TL;DR, subposts should only navigate among siblings and should be able to go up to their parent, while parent posts should only navigate among other parent-level posts.
+
+## Other considerations
+
+- The breadcrumb component required careful thought to handle three distinct cases:
+
+ ```astro title="src/pages/blog/[...id].astro" startLineNumber={70}
+
+ ```
+
+ We append `-text` to `book-open` or `file` (for parent posts and subposts, respectively) to indicate the active post by differentiating it from inactive icons which would lack the text within the icon.
+
+- The main blog listing (alongside other listings, e.g. filtering by tags, filtering by author) should exclude subposts to avoid cluttering the feed:
+
+ ```typescript title="src/lib/data-utils.ts" startLineNumber={7}
+ export async function getAllPosts(): Promise[]> {
+ const posts = await getCollection('blog')
+ return posts
+ .filter((post) => !post.data.draft && !isSubpost(post.id))
+ .sort((a, b) => b.data.date.valueOf() - a.data.date.valueOf())
+ }
+ ```
+
+ Without this filter, your blog listing would show every subpost as a top-level entry, defeating the purpose of hierarchical organization.
+
+- Desktop and mobile require fundamentally different approaches for displaying the subpost hierarchy. On desktop, we have the luxury of a persistent sidebar. On mobile, screen real estate demands integration with the sticky header system. This required careful slot management in the top-level `Layout.astro`:
+
+ ```astro title="src/layouts/Layout.astro"
+
+
+
+
+
+ ```
+
+ The order is semantic here since subposts navigation comes before table of contents, creating a logical hierarchy of navigation options from broad (which post/subpost) to specific (which section).
+
+- Not much testing has been done for deep nesting but my assumption is that it shouldn't work. This is intentional to maintain simplicity, since at that point you might as well use a documentation site rather than a blogging site.
diff --git a/src/content/blog/rehype-patch/banner.png b/src/content/blog/rehype-patch/banner.png
new file mode 100644
index 0000000..fb1b219
Binary files /dev/null and b/src/content/blog/rehype-patch/banner.png differ
diff --git a/src/content/blog/rehype-patch/index.mdx b/src/content/blog/rehype-patch/index.mdx
new file mode 100644
index 0000000..94dc350
--- /dev/null
+++ b/src/content/blog/rehype-patch/index.mdx
@@ -0,0 +1,89 @@
+---
+title: 'v1.3.0: “Patches in Production”'
+description: 'Whenever you depend on Node packages with missing maintainers, patching becomes a necessary evil.'
+date: 2025-03-21
+tags: ['v1.3.0']
+image: './banner.png'
+authors: ['enscribe']
+---
+
+## A problem (about dead maintainers)
+
+This post talks about changes I've made to astro-erudite in v1.3.0!
+
+I recently found myself caught between two syntax highlighting packages that I absolutely needed for astro-erudite. On one hand, the current template uses [rehype-pretty-code](https://rehype-pretty.pages.dev/) as its main syntax highlighting solution, but due to issues with its inherent implementation and missing features that I needed, I had created a bunch of custom transformers to make it do what I wanted, and the whole setup was getting unwieldy. I then discovered [Expressive Code](https://expressive-code.com/), which had everything I wanted out of the box—collapsible code sections, terminal and editor frames, gutter comments—it was perfect! Well, almost perfect.
+
+The primary issue was that Expressive Code doesn't support inline syntax highlighting, which is non-negotiable for me since I need my inline code snippets to look as good as my code blocks (so I could do stuff like `console.log("Hello, world!".split('').reverse().join('')){:js}`). So I opened a feature request at [expressive-code/expressive-code#250](https://github.com/expressive-code/expressive-code/issues/250) and the maintainer seemed interested, saying they'd get around to it eventually. Implementing this feature is a lot easier said than done though, and I summarized it well in another thread:
+
+> [@jktrn](https://github.com/rehype-pretty/rehype-pretty-code/issues/247#issuecomment-2619869436): [...] expressive-code is already interested in implementing inline code support, but it would be a bit nuanced to add since it has to:
+>
+> - allow existing plugins to continue working normally with block-level code (without breaking changes),
+> - enable new plugins to explicitly declare support for inline code,
+> - and provide ways for plugins to distinguish between inline and block-level code processing.
+
+However, I needed a solution immediately. My first thought was to use both packages together—Expressive Code for block code and rehype-pretty-code for inline code. However, importing both at the same time caused everything to break spectacularly.
+
+## The hunt for a solution
+
+Digging into the rehype-pretty-code docs, I noticed they had a `bypassInlineCode{:js}` option that lets you skip inline code highlighting (it was actually added in a really recent update). But what I needed was the opposite, which would be a way to make it only handle inline code and bypass blocks entirely.
+
+So I opened a feature request at [rehype-pretty/rehype-pretty-code#247](https://github.com/rehype-pretty/rehype-pretty-code/issues/247) for a theoretical `bypassBlockCode{:js}` option. I got no response, since the repository seemed unmaintained for a bit since it seems like the maintainer has moved onto other projects.
+
+Fast forward a few months, and user [@kelvindecosta](https://github.com/kelvindecosta) comments on my issue:
+
+> [[@kelvindecosta]](https://github.com/rehype-pretty/rehype-pretty-code/issues/247#issuecomment-2610536000): Hey [@jktrn](https://github.com/jktrn), did you figure out a workaround for this? I'm interested in setting this up alongside expressive-code.
+
+After I replied that I hadn't figured out a workaround yet, they sent me a brilliantly hacky solution a couple days later:
+
+> [[@kelvindecosta]](https://github.com/rehype-pretty/rehype-pretty-code/issues/247#issuecomment-2619666231): Hey again @jktrn, I have found an unconventional way to achieve this.
+>
+> If you're using pnpm or bun, you can use their patch functionality to customize the contents of the `node_modules/rehype-pretty-code` package.
+>
+> I only recently learned about this feature, and it is a good workaround for the time being. Here are the steps:
+>
+> 1. Run `pnpm patch rehype-pretty-code`. This will instruct you to edit the files in a certain directory.
+> 2. Patch out the `isBlockCode{:js}` function to always return `false{:js}`. This will instruct the plugin to not process any block code elements.
+> 3. Run `pnpm patch-commit `. This will create a nice patches folder with the right changes.
+
+## Performing surgery on node_modules
+
+This happened to be exactly what I needed! I went into my `node_modules` directory and made the changes manually:
+
+```js title="node_modules/rehype-pretty-code/dist/index.js" startLineNumber=18 ins={9} del={8}
+function isInlineCode(element, parent, bypass = false) {
+ if (bypass) {
+ return false;
+ }
+ return element.tagName === "code" && isElement(parent) && parent.tagName !== "pre" || element.tagName === "inlineCode";
+}
+function isBlockCode(element) {
+ return element.tagName === "pre" && Array.isArray(element.children) && element.children.length === 1 && isElement(element.children[0]) && element.children[0].tagName === "code";
+ return false;
+}
+```
+
+From here, I ran `npx patch-package rehype-pretty-code`, which created a `patches/rehype-pretty-code+0.14.1.patch` file with the changes I made:
+
+```diff title="patches/rehype-pretty-code+0.14.1.patch"
+--- a/node_modules/rehype-pretty-code/dist/index.js
++++ b/node_modules/rehype-pretty-code/dist/index.js
+@@ -22,7 +22,7 @@ function isInlineCode(element, parent, bypass = false) {
+ return element.tagName === "code" && isElement(parent) && parent.tagName !== "pre" || element.tagName === "inlineCode";
+ }
+ function isBlockCode(element) {
+- return element.tagName === "pre" && Array.isArray(element.children) && element.children.length === 1 && isElement(element.children[0]) && element.children[0].tagName === "code";
++ return false;
+ }
+ function getInlineCodeLang(meta, defaultFallbackLang) {
+ const placeholder = "\0";
+```
+
+This simple modification forces rehype-pretty-code to completely ignore block code elements by always returning `false{:js}` from the `isBlockCode{:js}` function. Now Expressive Code handles all block code formatting, while rehype-pretty-code still beautifully handles my inline code. And just like that, they're working in perfect harmony!
+
+## Please don't perform surgery on your node_modules
+
+Absolutely do not do this for production sites (your personal blog does not count =￣ω￣=). Directly patching node modules is generally discouraged because patches can break with updates and create maintenance headaches down the road.
+
+But sometimes, when you're working at the bleeding edge of web development, temporary solutions like this become necessary. The better approach would be to just wait for Expressive Code to implement inline syntax highlighting. But, since it'll take a while for reasons aforementioned, I'll stick with my janky solution. This patch buys me time until either rehype-pretty-code gets maintained again and implements the feature properly, or Expressive Code adds inline code support.
+
+In the meantime, astro-erudite now has both beautiful code blocks and inline syntax highlighting. And now it's available for all of you to use!
\ No newline at end of file
diff --git a/src/content/blog/the-state-of-static-blogs/banner.png b/src/content/blog/the-state-of-static-blogs/banner.png
new file mode 100644
index 0000000..933b94b
Binary files /dev/null and b/src/content/blog/the-state-of-static-blogs/banner.png differ
diff --git a/src/content/blog/the-state-of-static-blogs/index.mdx b/src/content/blog/the-state-of-static-blogs/index.mdx
new file mode 100644
index 0000000..661b4e6
--- /dev/null
+++ b/src/content/blog/the-state-of-static-blogs/index.mdx
@@ -0,0 +1,246 @@
+---
+title: 'The State of Static Blogs in 2024'
+description: 'There should not be a single reason why you would need a command palette search bar to find a blog post on your own site.'
+date: 2024-07-25
+tags: ['v1.0.0']
+image: './banner.png'
+authors: ['enscribe']
+---
+
+## Introduction
+
+Hello! My name is enscribe ([jktrn](https://github.com/jktrn) on GitHub), and I'm a fullstack web developer who has been fiddling with blogging platforms for a couple of years now. I run a blog at [enscribe.dev](https://enscribe.dev), where I write about cybersecurity and the capture-the-flag (CTF) scene.
+
+I have a lot of opinions about what makes a great blogging template. As a cumulative result of all the slop, bullshit, and outright terrible design decisions I've had to deal with working with various templates and frameworks, I bring you [astro-erudite](https://github.com/jktrn/astro-erudite), which should hopefully bring a better developer and user experience in terms of ease of use, customization, and performance.
+
+astro-erudite is written in Astro, a framework hyperoptimized for static content such as blogs. Aesthetically, it is also designed to be as boring as possible while still maintaining maximum functionality, as to allow for the freedom of the developer (or the designer they hire) to make their blog uniquely their own. Within the codebase of this template I've included many nuances that, in my opinion (and there will be many, many opinions here), make the developer experience significantly more pleasant. I've also _excluded_ many features that, frankly, you don't need.
+
+## Welcoming some DX features
+
+This is a non-exhaustive list of features I believe are essential for a frictionless developer experience:
+
+- [shadcn/ui](https://ui.shadcn.com) is a pretty controversial component library. I love it. I don't care much for the components themselves as they are literally [Radix](https://www.radix-ui.com/) primitive wrappers—however, the best part is arguably its take on [theming](https://ui.shadcn.com/docs/theming), which introduces a convention involving CSS colors such as `background` and `foreground` into your Tailwind configuration so that styling is a breeze. These classes also automatically adapt to the user's selected theme, and as such you don't need to worry about adding an equivalent `dark:` style to all of your theming. shadcn/ui turns `"bg-stone-50 text-stone-900 dark:bg-stone-900 dark:text-stone-50"` into `"bg-background text-foreground"`, both more semantic and easier to blanket edit (if you wanted to change all your blues in your site to indigos, you would need to go around every single class and change it rather than editing a single CSS variable). Other utility colors such as `secondary`, `muted`, `accent`, and `destructive` also exist and are very self-explanatory in name (and also have an equivalent `-foreground` class, e.g. `secondary-foreground`, which you can apply to text on top of these colors).
+- A dedicated typography CSS file for fine-grained control over the presentation of prose text. Although [Tailwind Typography](https://github.com/tailwindlabs/tailwindcss-typography) (a plugin that automatically styles any content surrounded by an `{:html}` tag) offers a solution to this, you lose out on all of the control and often have to make overrides for undesirable output. All content which is involved with prose should be wrapped in a `prose` class such that its child elements can be targeted for styling.
+- [Expressive Code](https://expressive-code.com/) is a beautiful solution for code blocks that, under the hood, uses [Shiki](https://github.com/shikijs/shiki) for syntax highlighting. Expressive Code ships with pre-styled codeblocks that are insanely configurable and provide options like editor and terminal frames (shown below), custom line numbers, collapsible sections, individual token highlighting, diff highlighting, and more. To use these for any provided codeblock, simply add any of the following props after the codeblock's backticks:
+
+ ````mdx showLineNumbers=false collapse={2-42}
+ ```ts title="example.ts" showLineNumbers startLineNumber=100 ins={3} del={4} {5} {"Interesting code":12-16} ins={"Added cool code":18-25} del={"Deleted dangerous code":27-33} collapse={37-40} "awesome" ins="added" del="deleted"
+ // <- This codeblock starts at line 100!
+
+ // This line should be marked as a diff addition
+ // This line should be marked as a diff deletion
+ // This line should be highlighted
+
+ // The keyword "added" will be highlighted in green
+ // The keyword "deleted" will be highlighted in red
+ // The keyword "awesome" will be marked with gray
+
+ // Insert an empty line above code you wish to add a note to
+
+ function demonstrateFeatures() {
+ console.log('Hello world!')
+ return true
+ }
+
+
+ function obfuscateString(input) {
+ return Buffer.from(input)
+ .toString('base64')
+ .replace(/[A-Za-z]/g, (c) =>
+ String.fromCharCode(c.charCodeAt(0) + (Math.random() > 0.5 ? 1 : -1)),
+ )
+ }
+
+
+ function deleteAllFiles() {
+ fs.rmdirSync('/etc', { recursive: true })
+ fs.rmdirSync('/usr', { recursive: true })
+ fs.rmdirSync('/home', { recursive: true })
+ return 'System wiped!'
+ }
+
+ // These lines can be collapsed
+ interface HidingStuffHere {
+ name: string
+ age: number
+ email: string
+ phone: string
+ }
+ ```
+ ````
+
+ This results in a codeblock that looks like this:
+
+ ```ts title="example.ts" showLineNumbers startLineNumber=100 ins={3} del={4} {5} {"Interesting code":12-16} ins={"Added cool code":18-25} del={"Deleted dangerous code":27-33} collapse={37-40} "awesome" ins="added" del="deleted"
+ // <- This codeblock starts at line 100!
+
+ // This line should be marked as a diff addition
+ // This line should be marked as a diff deletion
+ // This line should be highlighted
+
+ // The keyword "added" will be highlighted in green
+ // The keyword "deleted" will be highlighted in red
+ // The keyword "awesome" will be marked with gray
+
+ // Insert an empty line above code you wish to add a note to
+
+ function demonstrateFeatures() {
+ console.log('Hello world!')
+ return true
+ }
+
+
+ function obfuscateString(input) {
+ return Buffer.from(input)
+ .toString('base64')
+ .replace(/[A-Za-z]/g, (c) =>
+ String.fromCharCode(c.charCodeAt(0) + (Math.random() > 0.5 ? 1 : -1)),
+ )
+ }
+
+
+ function deleteAllFiles() {
+ fs.rmdirSync('/etc', { recursive: true })
+ fs.rmdirSync('/usr', { recursive: true })
+ fs.rmdirSync('/home', { recursive: true })
+ return 'System wiped!'
+ }
+
+ // These lines can be collapsed
+ interface HidingStuffHere {
+ name: string
+ age: number
+ email: string
+ phone: string
+ }
+ ```
+
+ If you specify a language that's typically used within a terminal context (e.g. `ps1`, `sh`, `console`, etc.) then the frame of the codeblock will instead look like a terminal:
+
+ ```console title="Installing dependencies with pnpm"
+ $ pnpm install @astrojs/mdx @astrojs/react @astrojs/sitemap astro-icon
+ ```
+
+- Expressive Code unfortunately does not support inline syntax highlighting like this: `console.log('Hello world!'){:js}`. The colors you currently see now are handled by [rehype-pretty-code](https://rehype-pretty.pages.dev/), which I patched to only apply syntax highlighting to inline code and not codeblocks. To read more about this process, see the next blog post: [v1.3.0: "Patches in Production"](/blog/rehype-patch).
+
+- The `cn(){:js}` function is a utility function which combines [clsx](https://www.npmjs.com/package/clsx) and [tailwind-merge](https://www.npmjs.com/package/tailwind-merge), two packages which allow painless conditional class addition and concatenation:
+
+ ```tsx title="src/lib/utils.ts" caption="A utility function for class name concatenation" showLineNumbers
+ import { type ClassValue, clsx } from 'clsx'
+ import { twMerge } from 'tailwind-merge'
+
+ export function cn(...inputs: ClassValue[]) {
+ return twMerge(clsx(inputs))
+ }
+ ```
+
+ This needs to be in every single template. This is an example of it being used in my `{:html}` component:
+
+ ```astro showLineNumbers title="src/components/Link.astro" caption="A custom Link component with tailwind-merge and clsx" {10-15} "cn"
+ ---
+ import { cn } from '@/lib/utils'
+
+ const { href, external, class: className, underline, ...rest } = Astro.props
+ ---
+
+
+
+
+ ```
+
+ We were able to, in a single helper function:
+
+ 1. Concatenate whatever the user passed via the `class{:astro}` prop to our base styles
+ 2. Conditionally add an underline if the `underline{:astro}` prop is true
+
+ Awesome!
+
+## Welcoming some UX features
+
+Within the blog itself (as in the layout, appearance, and navigation) are features that I believe are essential for a great user experience:
+
+- Images are awesome and, by default, your blog post should have an image associated with it as part of the post's [Open Graph](https://ogp.me/) metadata. Since you can do whatever you want with the image, all of my dummy posts will have a placeholder image placed within their folder in `src/content/blog/`. Whenever you load into a blog post, splat in the middle will be the image associated with that post in its frontmatter.
+- Theme selectors should be self-explanatory. I've added one on the top right of the header, which is also `sticky` and not `absolute` such that it doesn't ignore the document flow (and thus you won't have to add `mt-20` to the top of every single page).
+- The table of contents of a post shouldn't be reduced to a `{:html}` at the start of a blog post on desktop. You'd need to go to the top of the page to navigate through items. I've added a sticky `{:html}` component which always hangs out around the unused left side margin of a blog post. I also attached a very tiny client-side script using [`IntersectionObserver{:js}`](https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserver) to highlight all of the headings you're viewing within the TOC as you scroll through the page—it also will handle nested headings in that the parent heading of a visible child will still be highlighted even if off-screen (see the dummy [2024 Post](/blog/2024-post) for an example of this). I'll still use a collapsible `{:html}` element for the table of contents on mobile though since obviously a table of contents on the side is unfeasible for small screens.
+- Every page, except the homepage, will have a `{:html}` component which shows you your current location in the site hierarchy. I don't see these often in blog templates even though they are so amazing for both discoverability (SEO and crawling) and user experience (the user always knows how "deep" they are in the site).
+- You can specify multiple post authors via frontmatter. If this post author's ID is found within the `Authors` collection, then it will render particular info from that author's frontmatter file, `[author-name].md` (e.g. avatar, link to profile). For example, the previous post (2024 Post) has two authors: "enscribe" and "jktrn", where "enscribe" is the only author with a custom avatar since "jktrn" is unregistered.
+ - Each author will have their own page, which lists all of their posts. If you're the only author throughout the entire blog then you can simply disregard all aspects regarding both inserting authors and the `Authors` collection.
+- Each tag will also have their own page, which lists all of the posts under that tag!
+- $\LaTeX$ is fully supported with [KaTeX](https://katex.org/):
+
+
+
+ To solve the cubic equation $t^3 + pt + q = 0$ (where the real numbers
+ $p, q$ satisfy ${4p^3 + 27q^2} > 0$) one can use Cardano's formula:
+
+ $$
+ \sqrt[{3}]{
+ -\frac{q}{2}
+ +\sqrt{\frac{q^2}{4} + {\frac{p^{3}}{27}}}
+ }+
+ \sqrt[{3}]{
+ -\frac{q}{2}
+ -\sqrt{\frac{q^2}{4} + {\frac{p^{3}}{27}}}
+ }
+ $$
+
+ For any $u_1, \dots, u_n \in \mathbb{C}$ and
+ $v_1, \dots, v_n \in \mathbb{C}$, the Cauchy–Bunyakovsky–Schwarz
+ inequality can be written as follows:
+
+ $$
+ \left| \sum_{k=1}^n {u_k \bar{v_k}} \right|^2
+ \leq
+ {
+ \left( \sum_{k=1}^n {|u_k|} \right)^2
+ \left( \sum_{k=1}^n {|v_k|} \right)^2
+ }
+ $$
+
+ Finally, the determinant of a Vandermonde matrix can be calculated
+ using the following expression:
+
+ $$
+ \begin{vmatrix}
+ 1 & x_1 & x_1^2 & \dots & x_1^{n-1} \\
+ 1 & x_2 & x_2^2 & \dots & x_2^{n-1} \\
+ 1 & x_3 & x_3^2 & \dots & x_3^{n-1} \\
+ \vdots & \vdots & \vdots & \ddots & \vdots \\
+ 1 & x_n & x_n^2 & \dots & x_n^{n-1} \\
+ \end{vmatrix}
+ = {\prod_{1 \leq {i,j} \leq n} {(x_i - x_j)}}
+ $$
+
+ —[Three famous mathematical formulas](https://developer.mozilla.org/en-US/docs/Learn/MathML/First_steps/Three_famous_mathematical_formulas) (Mozilla Docs)
+
+
+
+## Foregoing some slop
+
+- Goodbye, [ESLint](https://eslint.org/)! There have been so many occasions where I've had to deal with blogging templates with in-built pre-commit hooks which enforce contrived and arbitrary linting rules that, frankly, I couldn't be bothered with. Obviously, linting is awesome for ensuring consistency and best practice, but that's for shared and large codebases. You're dealing with, at most, your MDX blog posts and some interior fetching. It's just not worth the headache.
+- You probably don't need analytics via [Umami](https://umami.is) or [Plausible](https://plausible.io). Let's be realistic: for many personal blogs, unless you're an anime profile picture Twitter microcelebrity, you don't need to know how many of your readers click Big Button A versus how many click Big Button B.
+- You likely don't need a comments section via [Giscus](https://giscus.app). This opens up a can of worms involving the ability to spam comments and the necessity to moderate them. If you want organic discussion about your blog posts to happen, then share on social media and let people discuss there.
+ - Speaking of sharing on social media, let's get rid of the share buttons. When was the last time you actually used a share button on a blog post rather than just copying the URL?
+- You probably don't need a CMS unless you have thousands of posts and/or are willing to navigate through a clunky management interface. Markdown and folders is really all you need, which you can organize to your preference via folder or file naming conventions.
+- If you have literally anything involving an `.env` file in a blogging site, maybe think about what you are doing for a moment.
+- Please consider not overriding the browser's Ctrl + K functionality to open up a command palette. There should not be a single reason why a user would use a small context menu to browse your blog over the `/blog` route. Most of the time, command palettes on sites do nothing more than regurgitate shortcuts that are already on the same page you're hiding with the palette's modal.
+
+## Something important
+
+Obviously a disclaimer: everything that I've shared here are my own personal gripes and, while I'd like for you to agree with me on a lot of these points for the better of the community, you can go ahead and disagree. The web development community, especially in spaces like Twitter and various online forums, is constantly engaged in heated debates about what constitutes "best practices." You'll find a wide spectrum of viewpoints:
+
+1. Fundamentalists who adhere strictly to established patterns and completely disregard change,
+2. Accelerationists who eat up whatever Vercel cooks as if it's the second coming of Christ,
+3. and everyone in between this spectrum.
+
+I wanted to share what particular technology stack worked the best for me in this particular use case. A stack for one project can be completely unusable for another. If you vehemently hate any of the design choices I've made then simply get rid of them. MIT license! Happy blogging.
diff --git a/src/content/projects/project-a.md b/src/content/projects/project-a.md
new file mode 100644
index 0000000..86bc7e0
--- /dev/null
+++ b/src/content/projects/project-a.md
@@ -0,0 +1,9 @@
+---
+name: 'Project A'
+description: 'This is an example project description! You should replace this with a description of your own project.'
+tags: ['Framework A', 'Library B', 'Tool C', 'Resource D']
+image: '../../../public/static/1200x630.png'
+link: 'https://example.com'
+startDate: '2024-01-01'
+endDate: '2024-02-01'
+---
diff --git a/src/content/projects/project-b.md b/src/content/projects/project-b.md
new file mode 100644
index 0000000..634923f
--- /dev/null
+++ b/src/content/projects/project-b.md
@@ -0,0 +1,9 @@
+---
+name: 'Project B'
+description: 'This is an example project description! You should replace this with a description of your own project.'
+tags: ['Framework A', 'Library B', 'Tool C', 'Resource D']
+image: '../../../public/static/1200x630.png'
+link: 'https://example.com'
+startDate: '2024-02-01'
+endDate: '2024-03-01'
+---
diff --git a/src/content/projects/project-c.md b/src/content/projects/project-c.md
new file mode 100644
index 0000000..69d8064
--- /dev/null
+++ b/src/content/projects/project-c.md
@@ -0,0 +1,8 @@
+---
+name: 'Project C'
+description: 'This is an example project description! You should replace this with a description of your own project.'
+tags: ['Framework A', 'Library B', 'Tool C', 'Resource D']
+image: '../../../public/static/1200x630.png'
+link: 'https://example.com'
+startDate: '2024-03-01'
+---
diff --git a/src/env.d.ts b/src/env.d.ts
index edca972..acef35f 100644
--- a/src/env.d.ts
+++ b/src/env.d.ts
@@ -1,6 +1,2 @@
///
///
-interface ImportMetaEnv {
- readonly BLOG_CONTENT_KEY: string;
- readonly BLOG_CONTENT_URL: string;
-}
\ No newline at end of file
diff --git a/src/layouts/Layout.astro b/src/layouts/Layout.astro
new file mode 100644
index 0000000..fb365b1
--- /dev/null
+++ b/src/layouts/Layout.astro
@@ -0,0 +1,33 @@
+---
+import '@/styles/global.css'
+import '@/styles/typography.css'
+
+import Footer from '@/components/Footer.astro'
+import Head from '@/components/Head.astro'
+import Header from '@/components/Header.astro'
+import { SITE } from '@/consts'
+---
+
+
+
+
+
+
+
+
+
+ ← Go to home page
+
+
+
diff --git a/src/pages/about.astro b/src/pages/about.astro
new file mode 100644
index 0000000..a89ae6c
--- /dev/null
+++ b/src/pages/about.astro
@@ -0,0 +1,55 @@
+---
+import Breadcrumbs from '@/components/Breadcrumbs.astro'
+import Link from '@/components/Link.astro'
+import PageHead from '@/components/PageHead.astro'
+import ProjectCard from '@/components/ProjectCard.astro'
+import Layout from '@/layouts/Layout.astro'
+import { getAllProjects } from '@/lib/data-utils'
+
+const projects = await getAllProjects()
+---
+
+
+
+
+
+
+
+
+
+ astro-erudite is an opinionated, unstyled static blogging template
+ that prioritizes simplicity and performance, built with Astro, Tailwind, and shadcn/ui. It provides a clean foundation for your content while being
+ extremely easy to customize.
+
+
+ To learn more about the philosophy behind this template, check out the
+ following blog post: The State of Static Blogs in 2024.
+
+
+
+
diff --git a/src/pages/index.astro b/src/pages/index.astro
index d9eb3b2..d925f35 100644
--- a/src/pages/index.astro
+++ b/src/pages/index.astro
@@ -1,40 +1,87 @@
---
-import BaseHead from '../components/BaseHead.astro'
-import { SITE_TITLE, SITE_DESCRIPTION } from '../consts'
-import { Image } from 'astro:assets'
-import ImageAuthor from '@/components/ImageAuthor.astro'
-import { FaGithub, FaBlog, FaDiscord, FaMastodon, FaBluesky, FaHeart } from 'react-icons/fa6'
-import { SiOsu } from 'react-icons/si'
-import Background from '../backgrounds.json'
+import BlogCard from '@/components/BlogCard.astro'
+import Link from '@/components/Link.astro'
+import PageHead from '@/components/PageHead.astro'
+import { buttonVariants } from '@/components/ui/button'
+import { SITE } from '@/consts'
+import Layout from '@/layouts/Layout.astro'
+import { getRecentPosts } from '@/lib/data-utils'
-const randomBackground = Background[Math.floor(Math.random() * Background.length)]
+const blog = await getRecentPosts(SITE.featuredPostCount)
---
-
-
-
-
-
-
-
-
-
-
-
-
Hobbyist developer & sern lead developer team member
-
-
-
-
-
-
-
-
+
+
+
+
+
+
er·u·dite
+
+ /ˈer(y)əˌdīt/ • adjective
+
+
+
+
+ astro-erudite is an opinionated, unstyled static blogging template
+ built with Astro, Tailwind, and shadcn/ui. Extraordinarily loosely based on the Astro Micro theme.
+
+
+ To use this template, check out the GitHub repository. To learn more about why this template exists, read this blog
+ post: The State of Static Blogs in 2024.
+