diff --git a/blog/public/blog-1.jpg b/blog/public/blog-1.jpg new file mode 100644 index 0000000..6ceceda Binary files /dev/null and b/blog/public/blog-1.jpg differ diff --git a/blog/public/blog-placeholder-1.jpg b/blog/public/blog-placeholder-1.jpg deleted file mode 100644 index 74d4009..0000000 Binary files a/blog/public/blog-placeholder-1.jpg and /dev/null differ diff --git a/blog/public/blog-placeholder-2.jpg b/blog/public/blog-placeholder-2.jpg deleted file mode 100644 index c4214b0..0000000 Binary files a/blog/public/blog-placeholder-2.jpg and /dev/null differ diff --git a/blog/public/blog-placeholder-3.jpg b/blog/public/blog-placeholder-3.jpg deleted file mode 100644 index fbe2ac0..0000000 Binary files a/blog/public/blog-placeholder-3.jpg and /dev/null differ diff --git a/blog/public/blog-placeholder-4.jpg b/blog/public/blog-placeholder-4.jpg deleted file mode 100644 index f4fc88e..0000000 Binary files a/blog/public/blog-placeholder-4.jpg and /dev/null differ diff --git a/blog/public/blog-placeholder-5.jpg b/blog/public/blog-placeholder-5.jpg deleted file mode 100644 index c564674..0000000 Binary files a/blog/public/blog-placeholder-5.jpg and /dev/null differ diff --git a/blog/public/blog-placeholder-about.jpg b/blog/public/blog-placeholder-about.jpg deleted file mode 100644 index cf5f685..0000000 Binary files a/blog/public/blog-placeholder-about.jpg and /dev/null differ diff --git a/blog/public/favicon.svg b/blog/public/favicon.svg deleted file mode 100644 index f157bd1..0000000 --- a/blog/public/favicon.svg +++ /dev/null @@ -1,9 +0,0 @@ - - - - diff --git a/blog/public/stars.ico b/blog/public/stars.ico new file mode 100644 index 0000000..4ec6450 Binary files /dev/null and b/blog/public/stars.ico differ diff --git a/blog/src/components/BaseHead.astro b/blog/src/components/BaseHead.astro index 3441240..aa9f9bf 100644 --- a/blog/src/components/BaseHead.astro +++ b/blog/src/components/BaseHead.astro @@ -1,28 +1,40 @@ --- // Import the global.css file here so that it is included on // all pages through the use of the component. -import '../styles/global.css'; +import "../styles/global.css"; interface Props { - title: string; - description: string; - image?: string; + title: string; + description: string; + image?: string; } const canonicalURL = new URL(Astro.url.pathname, Astro.site); -const { title, description, image = '/blog-placeholder-1.jpg' } = Astro.props; +const { title, description, image = "/blog-placeholder-1.jpg" } = Astro.props; --- - + - - + + diff --git a/blog/src/components/Footer.astro b/blog/src/components/Footer.astro index 96c2fce..5df2295 100644 --- a/blog/src/components/Footer.astro +++ b/blog/src/components/Footer.astro @@ -3,60 +3,70 @@ const today = new Date(); --- diff --git a/blog/src/components/Header.astro b/blog/src/components/Header.astro index c9ab99f..e1c1b96 100644 --- a/blog/src/components/Header.astro +++ b/blog/src/components/Header.astro @@ -1,85 +1,99 @@ --- -import HeaderLink from './HeaderLink.astro'; -import { SITE_TITLE } from '../consts'; +import HeaderLink from "./HeaderLink.astro"; +import { SITE_TITLE } from "../consts"; ---
- +
diff --git a/blog/src/consts.ts b/blog/src/consts.ts index 0df8a61..1a0e965 100644 --- a/blog/src/consts.ts +++ b/blog/src/consts.ts @@ -1,5 +1,5 @@ // Place any global data in this file. // You can import this data from anywhere in your site by using the `import` keyword. -export const SITE_TITLE = 'Astro Blog'; -export const SITE_DESCRIPTION = 'Welcome to my website!'; +export const SITE_TITLE = "maaz h."; +export const SITE_DESCRIPTION = "Welcome to my blog!"; diff --git a/blog/src/content/blog/first-blog.md b/blog/src/content/blog/first-blog.md new file mode 100644 index 0000000..b8e36bb --- /dev/null +++ b/blog/src/content/blog/first-blog.md @@ -0,0 +1,189 @@ +--- +title: 'Blogging? The Why and the How' +description: 'My first blog' +pubDate: 'Nov 17 2024' +heroImage: '/blog-1.jpg' +--- + +# Why? + +If I'm ever lying awake in bed at night or sitting idle on my couch on a Sunday morning, there’s usually a lot of interesting thoughts or ideas going around in my mind. It might be a personal dilemma, a world issue, a problem I’m envisioning but can’t seem to find a breakthrough for, my next big project idea, or something else entirely. + +There are times when I have found that sharing a thought with someone who might have an interest or an alternative perspective on it, helps spark an intellectual discussion. This often leads to better insights into the original thought, which I find beneficial. For this reason, I often refer back to recent ideas or thoughts when I’m conversing with a friend, family member, or a colleague. + +I was never particularly big on writing when I was in school—I used to despise those long creative writing assignments in English class. But as I’ve grown older, I’ve learned to appreciate the written form of communication. I’ve found that I can organize and convey my thoughts much more coherently when I write compared to when I speak. + +Getting ideas out of my head and into written words also helps clear my mental space and gives me a new perspective. For example, when tackling a complex problem, instead of overwhelming my brain with information, I’ve found it helpful to write out the context, sketch possible approaches, or explain the issue to someone else. This technique has often led to breakthroughs for me in the past. + +I have a wide range of interests and an endless curiosity to learn and educate myself about new things. I also find joy in sharing knowledge with others in areas where I might have some expertise. + +Combining these goals with the spare time I occasionally find on weekends, I decided to start this blog. I want to use this space to share interesting thoughts, opinions, ideas, solutions—whatever comes to mind. + +I don't want this blog to be confined to any single topic. It could be technical or non-technical. I might write about some random interests of mine like photography or basketball, share anecdotes from a movie I watched recently, or even explore the lyrics of a song I love. + +The possibilities are endless, but my primary aim is simple: +- To educate, inspire, or add value to even a single person’s life. +- To use this platform as a way to explore new topics and educate myself on things I wouldn’t normally dive into. + +

+ +# How? + +Now onto the more interesting bit. As this is my first blog post, I thought it would be fitting to start off by writing about an interesting technical problem I had to solve to get this blog up and running. + +As an aspiring web developer, I love some new technical challenges and keeping myself busy with fun projects and problems. + +### Context + +I developed and deployed a personal portfolio website a couple of months ago which lives on the domain https://maazh.tech. This website was a standard React app, but I had built a custom CI/CD pipeline to build and deploy the web app on a Google Cloud VM. I used GitHub Actions to automate the build and deploy process. + +Here's a general overview of the Github Workflow I used for the portfolio website: +- Log into Docker Hub +- Build Portfolio Docker image +- Push the Docker image to Docker Hub +- SSH into Google Cloud VM +- Pull the latest Docker image +- Take down the existing container +- Run the new container + +The run step was managed through a `docker-compose.yml` which used `nginx` as a reverse proxy to serve the React app and `nginx-acme` to handle SSL certificates. This is what the old `docker-compose.yml` looked like: + +```yaml +services: + nginx-proxy: + image: jwilder/nginx-proxy + container_name: nginx-proxy + ports: + - "80:80" + - "443:443" + volumes: + - /var/run/docker.sock:/tmp/docker.sock:ro + - ./certs:/etc/nginx/certs + - ./vhost:/etc/nginx/vhost.d + - ./html:/usr/share/nginx/html + nginx-proxy-acme: + image: nginxproxy/acme-companion + container_name: nginx-proxy-acme + volumes: + - /var/run/docker.sock:/var/run/docker.sock:ro + - ./certs:/etc/nginx/certs + - ./vhost:/etc/nginx/vhost.d + - ./html:/usr/share/nginx/html + - ./acme:/etc/acme.sh + environment: + - DEFAULT_EMAIL=MY_EMAIL + depends_on: + - nginx-proxy + volumes_from: + - nginx-proxy + app: + image: ghcr.io/GHCR_USERNAME/app:latest + container_name: app + restart: always + expose: + - 80 + environment: + - VIRTUAL_HOST=maazh.tech + - LETSENCRYPT_HOST=maazh.tech +``` + +Now as I started thinking about starting a blog, the obvious choice was to just add a route to my React app and start writing. But it didn't sit right in my head to use a bloated React app to serve a blog and write my posts in `JSX`. So I did some digging and looked for some web frameworks that used static site generation and markdown files for blog posts. I settled on a framework called AstroJS for my use case after playing around with a few others. + +### The Challenge +Since I had decided to use a completely separate framework for my blog, I still wanted this app to seamlessly integrate with my existing portfolio website i.e. I wanted to serve the blog on the same domain as my portfolio website, maybe under a `/blog` route link on the React app would take the user to the Astro app. This was mainly a devops heavy challenge and I started thinking about how I could achieve this. + +### Naive Approach +The most naive approach I thought of was to have these apps live completely separate from each other, i.e. separate git repos, separate CI/CD pipelines, separate deployments, etc. Next, I could use a subdomain routing like `blog.maazh.tech` to route to the Astro app. But both functionally and aesthetically, I wasn't a fan of this approach and it quite literally twice as expensive to maintain, since I would have to pay for two separate VMs, maintain multiples repos and pipelines, etc. Ideally, I wanted a solution where both apps would live under my old git repo, share the same CI/CD pipeline, and be deployed on the same VM. This sounded a lot more complex for obvious reasons, since the entire devops pipeline would have to be restructured, but the end result would be a lot cleaner and more importantly cheaper! + +### The Solution +So after some more thinking, research, talking to a friend, and bouncing back some ideas with ChatGPT, I discovered that this problem was easily solved using `nginx` reverse proxy by simply defining which container to route to based on the path. + +So to start off, I created a skeleton Astro app in my existing git repo under a directory called `blog` and moved all the contents of my old React app except the (`docker-compose.yml` and `README`) to a `portfolio` folder. I also setup a `Dockerfile` for the new Astro app. The new folder structure looked like this: + +``` +. +├── portfolio +│ ├── public +│ ├── src +│ ├── ... +│ ├── Dockerfile +│ ├── package.json +│ ├── ... +├── blog +│ ├── public +│ ├── src +│ ├── ... +│ ├── Dockerfile +│ ├── package.json +│ ├── ... +├── docker-compose.yml +├── README.md +``` + +Now, all I had to do was to update the `docker-compose.yml` adding a new service for the `blog` app and the key was to add a `VIRTUAL_PATH` environment variable under this service which would be used by `nginx` to route to the correct container based on the path. The updated `docker-compose.yml` looked like this: + +```yaml +services: + + nginx-proxy: + image: jwilder/nginx-proxy + container_name: nginx-proxy + ports: + - "80:80" + - "443:443" + volumes: + - /var/run/docker.sock:/tmp/docker.sock:ro + - ./certs:/etc/nginx/certs + - ./vhost:/etc/nginx/vhost.d + - ./html:/usr/share/nginx/html + nginx-proxy-acme: + image: nginxproxy/acme-companion + container_name: nginx-proxy-acme + volumes: + - /var/run/docker.sock:/var/run/docker.sock:ro + - ./certs:/etc/nginx/certs + - ./vhost:/etc/nginx/vhost.d + - ./html:/usr/share/nginx/html + - ./acme:/etc/acme.sh + environment: + - DEFAULT_EMAIL=MY_EMAIL + depends_on: + - nginx-proxy + volumes_from: + - nginx-proxy + + portfolio: + image: ghcr.io/GHCR_USERNAME/portfolio:latest + container_name: portfolio + restart: always + expose: + - 80 + environment: + - VIRTUAL_HOST=maazh.tech + - LETSENCRYPT_HOST=maazh.tech + + blog: + image: ghcr.io/GHCR_USERNAME/blog:latest + container_name: blog + restart: always + expose: + - 80 + environment: + - VIRTUAL_HOST=maazh.tech + - VIRTUAL_PATH=/blog +``` + +Finally, I just had to update the CI/CD pipeline to also build and push the `blog` image to Docker Hub. Thus the new workflow added 2 additional steps: +- Log into Docker Hub +- Build the Portfolio Docker image +- **Build the Blog Docker image** +- Push the Portfolio Docker image to Docker Hub +- **Push the Blog Docker image to Docker Hub** +- SSH into Google Cloud VM +- Pull the latest Docker image +- Take down the existing container +- Run the new container + +And that's it! I now have a fully functional blog that lives under the same domain as my portfolio website. If you head over to [maazh.tech](https://maazh.tech), you will land at the same old portfolio website I had but if you go to [maazh.tech/blog](https://maazh.tech/blog), you'll see the new blog built with AstroJS. + +This was already a super fun experience for me and I can't wait to start writing more posts and sharing my thoughts on here 😊 diff --git a/blog/src/content/blog/first-post.md b/blog/src/content/blog/first-post.md deleted file mode 100644 index 3066715..0000000 --- a/blog/src/content/blog/first-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'First post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 08 2022' -heroImage: '/blog-placeholder-3.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/blog/src/content/blog/markdown-style-guide.md b/blog/src/content/blog/markdown-style-guide.md deleted file mode 100644 index fd3de1e..0000000 --- a/blog/src/content/blog/markdown-style-guide.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -title: 'Markdown Style Guide' -description: 'Here is a sample of some basic Markdown syntax that can be used when writing Markdown content in Astro.' -pubDate: 'Jun 19 2024' -heroImage: '/blog-placeholder-1.jpg' ---- - -Here is a sample of some basic Markdown syntax that can be used when writing Markdown content in Astro. - -## Headings - -The following HTML `

`—`

` elements represent six levels of section headings. `

` is the highest section level while `

` is the lowest. - -# H1 - -## H2 - -### H3 - -#### H4 - -##### H5 - -###### H6 - -## Paragraph - -Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat. - -Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat. - -## Images - -### Syntax - -```markdown -![Alt text](./full/or/relative/path/of/image) -``` - -### Output - -![blog placeholder](/blog-placeholder-about.jpg) - -## Blockquotes - -The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a `footer` or `cite` element, and optionally with in-line changes such as annotations and abbreviations. - -### Blockquote without attribution - -#### Syntax - -```markdown -> Tiam, ad mint andaepu dandae nostion secatur sequo quae. -> **Note** that you can use _Markdown syntax_ within a blockquote. -``` - -#### Output - -> Tiam, ad mint andaepu dandae nostion secatur sequo quae. -> **Note** that you can use _Markdown syntax_ within a blockquote. - -### Blockquote with attribution - -#### Syntax - -```markdown -> Don't communicate by sharing memory, share memory by communicating.
-> — Rob Pike[^1] -``` - -#### Output - -> Don't communicate by sharing memory, share memory by communicating.
-> — Rob Pike[^1] - -[^1]: The above quote is excerpted from Rob Pike's [talk](https://www.youtube.com/watch?v=PAAkCSZUG1c) during Gopherfest, November 18, 2015. - -## Tables - -### Syntax - -```markdown -| Italics | Bold | Code | -| --------- | -------- | ------ | -| _italics_ | **bold** | `code` | -``` - -### Output - -| Italics | Bold | Code | -| --------- | -------- | ------ | -| _italics_ | **bold** | `code` | - -## Code Blocks - -### Syntax - -we can use 3 backticks ``` in new line and write snippet and close with 3 backticks on new line and to highlight language specific syntax, write one word of language name after first 3 backticks, for eg. html, javascript, css, markdown, typescript, txt, bash - -````markdown -```html - - - - - Example HTML5 Document - - -

Test

- - -``` -```` - -### Output - -```html - - - - - Example HTML5 Document - - -

Test

- - -``` - -## List Types - -### Ordered List - -#### Syntax - -```markdown -1. First item -2. Second item -3. Third item -``` - -#### Output - -1. First item -2. Second item -3. Third item - -### Unordered List - -#### Syntax - -```markdown -- List item -- Another item -- And another item -``` - -#### Output - -- List item -- Another item -- And another item - -### Nested list - -#### Syntax - -```markdown -- Fruit - - Apple - - Orange - - Banana -- Dairy - - Milk - - Cheese -``` - -#### Output - -- Fruit - - Apple - - Orange - - Banana -- Dairy - - Milk - - Cheese - -## Other Elements — abbr, sub, sup, kbd, mark - -### Syntax - -```markdown -GIF is a bitmap image format. - -H2O - -Xn + Yn = Zn - -Press CTRL + ALT + Delete to end the session. - -Most salamanders are nocturnal, and hunt for insects, worms, and other small creatures. -``` - -### Output - -GIF is a bitmap image format. - -H2O - -Xn + Yn = Zn - -Press CTRL + ALT + Delete to end the session. - -Most salamanders are nocturnal, and hunt for insects, worms, and other small creatures. diff --git a/blog/src/content/blog/second-post.md b/blog/src/content/blog/second-post.md deleted file mode 100644 index f47e093..0000000 --- a/blog/src/content/blog/second-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Second post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 15 2022' -heroImage: '/blog-placeholder-4.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/blog/src/content/blog/third-post.md b/blog/src/content/blog/third-post.md deleted file mode 100644 index af82f0e..0000000 --- a/blog/src/content/blog/third-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Third post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 22 2022' -heroImage: '/blog-placeholder-2.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/blog/src/content/blog/using-mdx.mdx b/blog/src/content/blog/using-mdx.mdx deleted file mode 100644 index 81603de..0000000 --- a/blog/src/content/blog/using-mdx.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: 'Using MDX' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jun 01 2024' -heroImage: '/blog-placeholder-5.jpg' ---- - -This theme comes with the [@astrojs/mdx](https://docs.astro.build/en/guides/integrations-guide/mdx/) integration installed and configured in your `astro.config.mjs` config file. If you prefer not to use MDX, you can disable support by removing the integration from your config file. - -## Why MDX? - -MDX is a special flavor of Markdown that supports embedded JavaScript & JSX syntax. This unlocks the ability to [mix JavaScript and UI Components into your Markdown content](https://docs.astro.build/en/guides/markdown-content/#mdx-features) for things like interactive charts or alerts. - -If you have existing content authored in MDX, this integration will hopefully make migrating to Astro a breeze. - -## Example - -Here is how you import and use a UI component inside of MDX. -When you open this page in the browser, you should see the clickable button below. - -import HeaderLink from '../../components/HeaderLink.astro'; - - - Embedded component in MDX - - -## More Links - -- [MDX Syntax Documentation](https://mdxjs.com/docs/what-is-mdx) -- [Astro Usage Documentation](https://docs.astro.build/en/guides/markdown-content/#markdown-and-mdx-pages) -- **Note:** [Client Directives](https://docs.astro.build/en/reference/directives-reference/#client-directives) are still required to create interactive components. Otherwise, all components in your MDX will render as static HTML (no JavaScript) by default. diff --git a/blog/src/pages/about.astro b/blog/src/pages/about.astro deleted file mode 100644 index c9d5b02..0000000 --- a/blog/src/pages/about.astro +++ /dev/null @@ -1,62 +0,0 @@ ---- -import Layout from '../layouts/BlogPost.astro'; ---- - - -

- Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut - labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo - viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam - adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus - et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus - vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque - sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. -

- -

- Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non - tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non - blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna - porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis - massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. - Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis - bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra - massa massa ultricies mi. -

- -

- Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl - suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet - nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae - turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem - dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat - semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus - vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum - facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam - vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla - urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. -

- -

- Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper - viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc - scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur - gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus - pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim - blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id - cursus metus aliquam eleifend mi. -

- -

- Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta - nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam - tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci - ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar - proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. -

- diff --git a/portfolio/src/components/Navbar/Navbar.jsx b/portfolio/src/components/Navbar/Navbar.jsx index 183799d..f535686 100644 --- a/portfolio/src/components/Navbar/Navbar.jsx +++ b/portfolio/src/components/Navbar/Navbar.jsx @@ -41,6 +41,9 @@ export const Navbar = () => {
  • Interests
    • +
  • + Blog +