diff --git a/README.md b/README.md
index 46a3d59..d6caa6a 100644
--- a/README.md
+++ b/README.md
@@ -1,187 +1,5 @@
-# AstroPaper π
+# Ignacio PS
-
-[](https://www.figma.com/community/file/1356898632249991861)
-
-
-[](https://conventionalcommits.org)
-[](http://commitizen.github.io/cz-cli/)
+This repo contains the source files for my projects website [ignaciops.dev](https://ignaciops.dev).
-AstroPaper is a minimal, responsive, accessible and SEO-friendly Astro blog theme. This theme is designed and crafted based on [my personal blog](https://satnaing.dev/blog).
-
-This theme follows best practices and provides accessibility out of the box. Light and dark mode are supported by default. Moreover, additional color schemes can also be configured.
-
-This theme is self-documented \_ which means articles/posts in this theme can also be considered as documentations. Read [the blog posts](https://astro-paper.pages.dev/posts/) or check [the README Documentation Section](#-documentation) for more info.
-
-## π₯ Features
-
-- [x] type-safe markdown
-- [x] super fast performance
-- [x] accessible (Keyboard/VoiceOver)
-- [x] responsive (mobile ~ desktops)
-- [x] SEO-friendly
-- [x] light & dark mode
-- [x] fuzzy search
-- [x] draft posts & pagination
-- [x] sitemap & rss feed
-- [x] followed best practices
-- [x] highly customizable
-- [x] dynamic OG image generation for blog posts [#15](https://github.com/satnaing/astro-paper/pull/15) ([Blog Post](https://astro-paper.pages.dev/posts/dynamic-og-image-generation-in-astropaper-blog-posts/))
-
-_Note: I've tested screen-reader accessibility of AstroPaper using **VoiceOver** on Mac and **TalkBack** on Android. I couldn't test all other screen-readers out there. However, accessibility enhancements in AstroPaper should be working fine on others as well._
-
-## β Lighthouse Score
-
-
-
- {/* Other Codes */}
-
-// Other Codes
-```
-
-## Conclusion
-
-By following the provided steps and tweaks, you can now incorporate this useful feature into your content. I hope this post helps you adding `readingTime` in your blog. AstroPaper might include reading time by default in future releases. π€·π»ββοΈ
-
-Kyay Zuu for Reading ππ»
diff --git a/src/content/blog/how-to-add-latex-equations-in-blog-posts.md b/src/content/blog/how-to-add-latex-equations-in-blog-posts.md
deleted file mode 100644
index fc68850..0000000
--- a/src/content/blog/how-to-add-latex-equations-in-blog-posts.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-author: Alberto Perdomo
-pubDatetime: 2024-09-08T20:58:52.737Z
-title: Adding LaTeX Equations in AstroPaper blog posts
-featured: false
-tags:
- - rendering
- - docs
-description: How to use LaTeX equations in your Markdown files for AstroPaper.
----
-
-This document demonstrates how to use LaTeX equations in your Markdown files for AstroPaper. LaTeX is a powerful typesetting system often used for mathematical and scientific documents.
-
-## Table of contents
-
-## Instructions
-
-In this section, you will find instructions on how to add support for LaTeX in your Markdown files for AstroPaper.
-
-1. Install the necessary remark and rehype plugins by running `npm install rehype-katex remark-math katex`.
-
-2. Update the Astro configuration (`astro.config.ts`) to use the these plugins:
-
-```ts
-// other imports
-import remarkMath from "remark-math";
-import rehypeKatex from "rehype-katex";
-
-export default defineConfig({
- // other configs
- markdown: {
- remarkPlugins: [
- remarkMath,
- remarkToc,
- [
- remarkCollapse,
- {
- test: "Table of contents",
- },
- ],
- ],
- rehypePlugins: [rehypeKatex],
- // other markdown configs
- },
- // other configs
-});
-```
-
-3. Import KaTeX CSS in the main layout file `src/layouts/Layout.astro`
-
-```astro
----
-import { LOCALE, SITE } from "@config";
-
-// astro code
----
-
-
-
-
-
-
-
-
-
-```
-
-And _voilΓ _, this setup allows you to write LaTeX equations in your Markdown files, which will be rendered properly when the site is built. Once you do it, the rest of the document will appear rendered correctly.
-
-## Inline Equations
-
-Inline equations are written between single dollar signs `$...$`. Here are some examples:
-
-1. The famous mass-energy equivalence formula: `$E = mc^2$`
-2. The quadratic formula: `$x = \frac{-b \pm \sqrt{b^2 - 4ac}}{2a}$`
-3. Euler's identity: `$e^{i\pi} + 1 = 0$`
-
-## Block Equations
-
-For more complex equations or when you want the equation to be displayed on its own line, use double dollar signs `$$...$$`:
-
-The Gaussian integral:
-
-```bash
-$$ \int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi} $$
-```
-
-The definition of the Riemann zeta function:
-
-```bash
-$$ \zeta(s) = \sum_{n=1}^{\infty} \frac{1}{n^s} $$
-```
-
-Maxwell's equations in differential form:
-
-```bash
-$$
-\begin{aligned}
-\nabla \cdot \mathbf{E} &= \frac{\rho}{\varepsilon_0} \\
-\nabla \cdot \mathbf{B} &= 0 \\
-\nabla \times \mathbf{E} &= -\frac{\partial \mathbf{B}}{\partial t} \\
-\nabla \times \mathbf{B} &= \mu_0\left(\mathbf{J} + \varepsilon_0 \frac{\partial \mathbf{E}}{\partial t}\right)
-\end{aligned}
-$$
-```
-
-## Using Mathematical Symbols
-
-LaTeX provides a wide range of mathematical symbols:
-
-- Greek letters: `$\alpha$`, `$\beta$`, `$\gamma$`, `$\delta$`, `$\epsilon$`, `$\pi$`
-- Operators: `$\sum$`, `$\prod$`, `$\int$`, `$\partial$`, `$\nabla$`
-- Relations: `$\leq$`, `$\geq$`, `$\approx$`, `$\sim$`, `$\propto$`
-- Logical symbols: `$\forall$`, `$\exists$`, `$\neg$`, `$\wedge$`, `$\vee$`
diff --git a/src/content/blog/how-to-configure-astropaper-theme.md b/src/content/blog/how-to-configure-astropaper-theme.md
deleted file mode 100644
index 95ea128..0000000
--- a/src/content/blog/how-to-configure-astropaper-theme.md
+++ /dev/null
@@ -1,161 +0,0 @@
----
-author: Sat Naing
-pubDatetime: 2022-09-23T04:58:53Z
-modDatetime: 2024-01-15T13:05:56.066Z
-title: How to configure AstroPaper theme
-slug: how-to-configure-astropaper-theme
-featured: true
-draft: false
-tags:
- - configuration
- - docs
-description: How you can make AstroPaper theme absolutely yours.
----
-
-AstroPaper is a highly customizable Astro blog theme. With AstroPaper, you can customize everything according to your personal taste. This article will explain how you can make some customizations easily in the config file.
-
-## Table of contents
-
-## Configuring SITE
-
-The important configurations lies in `src/config.ts` file. Within that file, you'll see the `SITE` object where you can specify your website's main configurations.
-
-During development, it's okay to leave `SITE.website` empty. But in production mode, you should specify your deployed url in `SITE.website` option since this will be used for canonical URL, social card URL etc.. which are important for SEO.
-
-```js
-// file: src/config.ts
-export const SITE = {
- website: "https://astro-paper.pages.dev/",
- author: "Sat Naing",
- desc: "A minimal, responsive and SEO-friendly Astro blog theme.",
- title: "AstroPaper",
- ogImage: "astropaper-og.jpg",
- lightAndDarkMode: true,
- postPerPage: 3,
- scheduledPostMargin: 15 * 60 * 1000, // 15 minutes
-};
-```
-
-Here are SITE configuration options
-
-| Options | Description |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `website` | Your deployed website url |
-| `author` | Your name |
-| `desc` | Your site description. Useful for SEO and social media sharing. |
-| `title` | Your site name |
-| `ogImage` | Your default OG image for the site. Useful for social media sharing. OG images can be an external image url or they can be placed under `/public` directory. |
-| `lightAndDarkMode` | Enable or disable `light & dark mode` for the website. If disabled, primary color scheme will be used. This option is enabled by default. |
-| `postPerIndex` | The number of posts to be displayed at the home page under `Recent` section. |
-| `postPerPage` | You can specify how many posts will be displayed in each posts page. (eg: if you set SITE.postPerPage to 3, each page will only show 3 posts per page) |
-| `scheduledPostMargin` | In Production mode, posts with a future `pubDatetime` will not be visible. However, if a post's `pubDatetime` is within the next 15 minutes, it will be visible. You can set `scheduledPostMargin` if you don't like the default 15 minutes margin. |
-
-## Configuring locale
-
-You can configure the default locale used for the build (e.g., date format in the post page), and for the rendering in browsers (e.g., date format in the search page)
-
-```js
-// file: src/config.ts
-export const LOCALE = {
- lang: "en", // html lang code. Set this empty and default will be "en"
- langTag: ["en-EN"], // BCP 47 Language Tags. Set this empty [] to use the environment default
-} as const;
-```
-
-`LOCALE.lang` will be used as HTML ISO Language code in ``. If you don't specify this, default fallback will be set to `en`.
-`LOCALE.langTag` is used as [datetime locale](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleDateString#locales). For this, you can specify an array of locales for fallback languages. Leave `LOCALE.langTag` empty `[]` to use the environment default at _build-_ and _run-time_.
-
-## Configuring logo or title
-
-You can specify site's title or logo image in `src/config.ts` file.
-
-
-
-```js
-// file: src/config.ts
-export const LOGO_IMAGE = {
- enable: false,
- svg: true,
- width: 216,
- height: 46,
-};
-```
-
-If you specify `LOGO_IMAGE.enable` => `false`, AstroPaper will automatically convert `SITE.title` to the main site text logo.
-
-If you specify `LOGO_IMAGE.enable` => `true`, AstroPaper will use the logo image as the site's main logo.
-
-You have to specify `logo.png` or `logo.svg` under `/public/assets` directory. Currently, only svg and png image file formats are supported. (**_Important!_** _logo name has to be logo.png or logo.svg)_
-
-If your logo image is png file format, you have to set `LOGO_IMAGE.svg` => `false`.
-
-It is recommended that you specify width and height of your logo image. You can do that by setting `LOGO_IMAGE.width` _and_ `LOGO_IMAGE.height`
-
-## Configuring social links
-
-You can configure your own social links along with its icons.
-
-
-
-Currently 20 social icons are supported. (Github, LinkedIn, Facebook etc.)
-
-You can specify and enable certain social links in hero section and footer. To do this, go to `/src/config.ts` and then you'll find `SOCIALS` array of object.
-
-```js
-// file: src/config.ts
-export const SOCIALS: SocialObjects = [
- {
- name: "Github",
- href: "https://github.com/satnaing/astro-paper",
- linkTitle: ` ${SITE.title} on Github`,
- active: true,
- },
- {
- name: "Facebook",
- href: "https://github.com/satnaing/astro-paper",
- linkTitle: `${SITE.title} on Facebook`,
- active: true,
- },
- {
- name: "Instagram",
- href: "https://github.com/satnaing/astro-paper",
- linkTitle: `${SITE.title} on Instagram`,
- active: true,
- },
- ...
-]
-```
-
-You have to set specific social link to `active: true` in order to appear your social links in hero and footer section. Then, you also have to specify your social link in `href` property.
-
-For instance, if I want to make my Github appear, I'll make it like this.
-
-```js
-export const SOCIALS: SocialObjects = [
- {
- name: "Github",
- href: "https://github.com/satnaing", // update account link
- linkTitle: `${SITE.title} on Github`, // this text will appear on hover and VoiceOver
- active: true, // makre sure to set active to true
- }
- ...
-]
-```
-
-Another thing to note is that you can specify the `linkTitle` in the object. This text will display when hovering on the social icon link. Besides, this will improve accessibility and SEO. AstroPaper provides default link title values; but you can replace them with your own texts.
-
-For example,
-
-```js
-linkTitle: `${SITE.title} on Twitter`,
-```
-
-to
-
-```js
-linkTitle: `Follow ${SITE.title} on Twitter`;
-```
-
-## Conclusion
-
-This is the brief specification of how you can customize this theme. You can customize more if you know some coding. For customizing styles, please read [this article](https://astro-paper.pages.dev/posts/customizing-astropaper-theme-color-schemes/). Thanks for reading.βπ»
diff --git a/src/content/blog/how-to-connect-astro-paper-blog-with-forestry-cms.md b/src/content/blog/how-to-connect-astro-paper-blog-with-forestry-cms.md
deleted file mode 100644
index e205c91..0000000
--- a/src/content/blog/how-to-connect-astro-paper-blog-with-forestry-cms.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: How to connect AstroPaper blog with Forestry CMS
-author: Sat Naing
-pubDatetime: 2022-09-21T05:17:19Z
-slug: how-to-connect-astro-paper-blog-with-forestry-cms
-featured: false
-draft: false
-tags:
- - docs
- - forestry-cms
- - astro-paper
-ogImage: https://res.cloudinary.com/noezectz/v1663745737/astro-paper/astropaper-x-forestry-og_kqfwp0.png
-description:
- Step by step process of connecting Astro-Paper blog theme with Forestry
- Headless CMS.
----
-
-> Important!!! Forestry is going to be discontinued on April 22nd, 2023. You can [read their announcement](https://forestry.io/blog/forestry.io-end-of-life/) for more info.
-
-In this article, I will explain step by step process of connecting AstroPaper theme with the Forestry headless CMS. So, let's get started π
-
-## Table of contents
-
-## What is Forestry?
-
-[Forestry](https://forestry.io/ "Forestry Website") is a git-based headless CMS and we can manage our markdown contents easily by using that. Although it is not an open-sourced CMS, it has a good free plan by which we can import up to 3 sites (3 repositories). In this article, I'll demonstrate how we can use Forestry as git-based CMS of our AstroPaper blog theme.
-
-## Login / Register an account at Forestry.io
-
-First of all, you have to create an account at [Forestry website](https://app.forestry.io/login "Forestry Login Page"). I usually sign up with my Github account.
-
-
-
-## Import AstroPaper site (repository)
-
-This part is importing the repository to Forestry and a little bit of set up process.
-
-### Add Site
-
-After logging in/signing up an account, import your AstroPaper site by clicking "Add Site" button.
-
-
-
-### Select SSG
-
-In this case, just choose "Others"
-
-
-
-### Select Git Provider
-
-My git provider is Github and I assume yours is the same. So, choose "Github".
-
-
-
-After this, the process of importing site (repo) is done.
-
-## Set up Sidebar
-
-The next phase after importing site is setting up sidebar menu. You can add many sidebar menu as you want. However, I'll only add one sidebar menu in this case.
-
-Navigate to "Finish setup process" > "Set up sidebar" and click "Configure sitebar"
-
-
-
-Then, click "Add Section" button.
-
-
-
-After that, choose DIRECTORY for the Section Type.
-
-
-
-Then, configure the directory section. You can follow along with my setup.
-
-
-
-After this step, you should see a sidebar menu "Blog Posts" and some blog posts.
-
-## Set up Media Import
-
-In Forestry CMS, you can set up different options for media (aka assets) such as Cloudinary, git commit media etc. I usually store my assets in [Cloudinary](https://cloudinary.com/). To set up media import, go to Settings > Media. Then select your image storage provider. (I chose Cloudinary).
-
-
-
-You can see details of Forestry Cloudinary setup at [Forestry documentation](https://forestry.io/docs/media/cloudinary/).
-
-## Set up Front matter template
-
-After setting everything up, you can set up front matter template for your future blog post. To set up front matter template, navigate to "Front matter" menu on the sidebar.
-
-Then, click "Add Template" button at the top right corner.
-
-
-
-Select new template based on existing document.
-
-
-
-Then, add template name and choose one of my document page as template.
-
-As the final setup, make some adjustment in the front matter field settings.
-
-
-
-Here are some adjustments you have to make.
-
-**_title_**
-
-- Validation => REQUIRED => true
-
-**_author_**
-
-- Default => your name
-
-**_datetime_**
-
-- Default => USE "NOW" AS DEFAULT
-
-**_description_**
-
-- Validation => REQUIRED => true
-
-## Conclusion
-
-You can now post your articles and write whatever you want.
diff --git a/src/content/blog/how-to-integrate-giscus-comments.md b/src/content/blog/how-to-integrate-giscus-comments.md
deleted file mode 100644
index a27496f..0000000
--- a/src/content/blog/how-to-integrate-giscus-comments.md
+++ /dev/null
@@ -1,202 +0,0 @@
----
-author: FjellOverflow
-pubDatetime: 2024-07-25T11:11:53Z
-title: How to integrate Giscus comments into AstroPaper
-slug: how-to-integrate-giscus-comments
-featured: true
-draft: false
-tags:
- - astro
- - blog
- - docs
-description: Comment function on a static blog hosted on GitHub Pages with Giscus.
----
-
-Hosting a thin static blog on a platform like [GitHub Pages](https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site) has numerous advantages, but also takes away some interactivity. Fortunately, [Giscus](https://giscus.app/) exists and offers a way to embed user comments on static sites.
-
-## Table of contents
-
-## How _Giscus_ works
-
-[Giscus uses the GitHub API](https://github.com/giscus/giscus?tab=readme-ov-file#how-it-works) to read and store comments made by _GitHub_ users in the `Discussions` associated with a repository.
-
-Embed the _Giscus_ client-side script bundle on your site, configure it with the correct repository URL, and users can view and write comments (when logged into _GitHub_).
-
-The approach is serverless, as the comments are stored on _GitHub_ and dynamically loaded from there on client side, hence perfect for a static blog, like _AstroPaper_.
-
-## Setting up _Giscus_
-
-_Giscus_ can be set up easily on [giscus.app](https://giscus.app/), but I will outline the process shortly still.
-
-### Prequisites
-
-Prequisites to get _Giscus_ working are
-
-- the repository is [public](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility#making-a-repository-public)
-- the [Giscus app](https://github.com/apps/giscus) is installed
-- the [Discussions](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository) feature is turned on for your repository
-
-If any of these conditions cannot be fulfilled for any reason, unfortunately, _Giscus_ cannot be integrated.
-
-### Configuring _Giscus_
-
-Next, configuring _Giscus_ is necessary. In most cases, the preselected defaults are suitable, and you should only modify them if you have a specific reason and know what you are doing. Don't worry too much about making the wrong choices; you can always adjust the configuration later on.
-
-However you need to
-
-- select the right language for the UI
-- specify the _GitHub_ repository you want to connect, typically the repository containing your statically hosted _AstroPaper_ blog on _GitHub Pages_
-- create and set an `Announcement` type discussion on _GitHub_ if you want to ensure nobody can create random comments directly on _GitHub_
-- define the color scheme
-
-After configuring the settings, _Giscus_ provides you with a generated `
-```
-
-Simply add that to the source code of the site. Most likely, if you're using _AstroPaper_ and want to enable comments on posts, navigate to `src/layouts/PostDetails.astro` and paste it into the desired location where you want the comments to appear, perhaps underneath the `Share this post on:` buttons.
-
-```diff
-
-
-
-+
-
-
-
-```
-
-> Technically, you can store images inside any directory under `src`. In here, `src/assets` is just a recommendation.
-
-### Inside `public` directory
-
-You can store images inside the `public` directory. Keep in mind that images stored in the `public` directory remain untouched by Astro, meaning they will be unoptimized and you need to handle image optimization by yourself.
-
-For these images, you should use an absolute path; and these images can be displayed using [markdown annotation](https://www.markdownguide.org/basic-syntax/#images-1) or [HTML img tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img).
-
-Example: Assume `example.jpg` is located at `/public/assets/images/example.jpg`.
-
-```md
-
-
-
-
-
-```
-
-## Bonus
-
-### Image compression
-
-When you put images in the blog post (especially for images under `public` directory), it is recommended that the image is compressed. This will affect the overall performance of the website.
-
-My recommendation for image compression sites.
-
-- [TinyPng](https://tinypng.com/)
-- [TinyJPG](https://tinyjpg.com/)
-
-### OG Image
-
-The default OG image will be placed if a post does not specify the OG image. Though not required, OG image related to the post should be specify in the frontmatter. The recommended size for OG image is **_1200 X 640_** px.
-
-> Since AstroPaper v1.4.0, OG images will be generated automatically if not specified. Check out [the announcement](https://astro-paper.pages.dev/posts/dynamic-og-image-generation-in-astropaper-blog-posts/).
diff --git a/src/content/blog/astro-paper-2.md b/src/content/blog/astro-paper-2.md
deleted file mode 100644
index 092606b..0000000
--- a/src/content/blog/astro-paper-2.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-author: Sat Naing
-pubDatetime: 2023-01-30T15:57:52.737Z
-title: AstroPaper 2.0
-slug: astro-paper-2
-featured: false
-ogImage: https://user-images.githubusercontent.com/53733092/215771435-25408246-2309-4f8b-a781-1f3d93bdf0ec.png
-tags:
- - release
-description: AstroPaper with the enhancements of Astro v2. Type-safe markdown contents, bug fixes and better dev experience etc.
----
-
-Astro 2.0 has been released with some cool features, breaking changes, DX improvements, better error overlay and so on. AstroPaper takes advantage of those cool features, especially Content Collections API.
-
-
-
-
-
-## Table of contents
-
-## Features & Changes
-
-### Type-safe Frontmatters and Redefined Blog Schema
-
-Frontmatter of AstroPaper 2.0 markdown contents are now type-safe thanks to Astroβs Content Collections. Blog schema is defined inside the `src/content/_schemas.ts` file.
-
-### New Home for Blog contents
-
-All the blog posts were moved from `src/contents` to `src/content/blog` directory.
-
-### New Fetch API
-
-Contents are now fetched with `getCollection` function. No relative path to the content needs to be specified anymore.
-
-```ts
-// old content fetching method
-- const postImportResult = import.meta.glob