Skip to content

Commit de0f289

Browse files
TheColetrainTheColetrain
committed
used ChatGPT to revise formatting
1 parent 54b8708 commit de0f289

File tree

1 file changed

+34
-33
lines changed

1 file changed

+34
-33
lines changed

‎_posts/2025-03-14-Jecyll The Static Site Generator.md‎

Lines changed: 34 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,39 +1,42 @@
11
---
22
title: "Jekyll"
3-
Date: 2025-3-14 10:03:00 CST
3+
date: 2025-03-14 10:03:00 CST
44
layout: post
5-
Categories: [web, resume]
6-
Tags: [jekyll,chirpy,static site generator] # Tag names should always be lowercase
5+
categories: [web, resume]
6+
tags: [jekyll, chirpy, static site generator] # Tag names should always be lowercase
77
permalink: /jekyll/
88
pin: true
99

1010
---
1111

1212

13-
# THE JEKYLL PROJECT
13+
# The Jekyll Project
1414

15-
I wanted to make a website with my resume and to highlight some fun projects I have done. TechnoTim is one of my favorite YouTubers and he has a great Discord. So naturally, I wanted to do what he does.
15+
I wanted to create a website to showcase my resume and highlight some fun projects I've worked on. Techno Tim is one of my favorite YouTubers and tech enthusiasts, and he runs an awesome Discord. Naturally, I decided to follow his approach.
1616

17-
I would advise to follow his guide and his notes, but then I will try and add some more notes, if you get stuck.
17+
I recommend following his guide and notes; I'll add extra tips if you get stuck.
1818

1919

2020
<iframe width="560" height="315" src="https://www.youtube.com/embed/F8iOU1ci19Q?si=QMUPZVlZZ_0uDWLG" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
2121

2222

23-
Here are his notes [Meet Jekyll - The Static Site Generator](https://technotim.live/posts/jekyll-docs-site/)
23+
Here are his notes: [Meet Jekyll - The Static Site Generator](https://technotim.live/posts/jekyll-docs-site/)
2424

25-
Here are Jekyll Install notes [Jekyll - Installation](https://jekyllrb.com/docs/installation/)
25+
Here are Jekyll installation notes: [Jekyll - Installation](https://jekyllrb.com/docs/installation/)
2626

27-
Here are Chirpy Notes [Chirpy - Getting Started](https://chirpy.cotes.page/posts/getting-started/)
27+
Here are Chirpy Notes: [Chirpy - Getting Started](https://chirpy.cotes.page/posts/getting-started/)
2828

2929

30-
- <h1>1 </h1> The First issue I had, and once you know, then you know, was to get the local site up. I was running it on a VM on Proxmox. I tried using the VM IP + Port *192.168.10.55:4000* and I tried localhost:4000, but what would have made my life easy was just doing **`http://127.0.0.1:4000`**
31-
32-
- <h1>2 </h1> How I actually got it to work in the first place is with VS Code. - Half way down the page in blue.
33-
>If you are using Dev Containers, you must run that command in the VS Code Terminal.`<
34-
[Chirpy Getting started](https://chirpy.cotes.page/posts/getting-started/)
35-
36-
- <h1> 3 </h1> Also, you could add this to the top of your `_config.yml` And This is my favorite, now that I know.
30+
## 1. The first issue I encountered was getting the local site running. I was using a VM on Proxmox and tried accessing it:
31+
- Via the VM IP + Port (e.g. `192.168.10.55:4000`) *did not work*
32+
- `localhost:4000` *did not work*
33+
- In the short term, **`http://127.0.0.1:4000`** worked. (But I did not think to try it for some time. I mistakingly thought localhost and 127.0.0.1 were the same, andthey are not. Seems easy now, but it took me a while before i realized. :confounded: )
34+
35+
## 2. I got it working using VS Code.
36+
**If you are using Dev Containers, run the command in the VS Code Terminal.**
37+
[Chirpy Getting Started](https://chirpy.cotes.page/posts/getting-started/)
38+
(Look for the command highlighted in blue further down the page.)
39+
## 3. Additionally, add the following to the top of your `_config.yml` (My favorite solution!):
3740
```yml
3841
# Server settings
3942
host: 192.168.1.55
@@ -42,36 +45,34 @@ Here are Chirpy Notes [Chirpy - Getting Started](https://chirpy.cotes.page/post
4245
4346
## Here is a quote for you.
4447
45-
"Once you know what you are doing, it is really easy. When you do NOT know what you are doing, it is really hard."
46-
<br>
47-
<br>
48+
"Once you know what you are doing, it is really easy. When you do NOT know what you are doing, it is really hard." :laughing:
4849
4950
50-
Site Structure <br>
51-
=======================
52-
<br> Once you get it up and running, I guess all these Tech guys just know things intuitively. But I dod not. I did not know what the header meant, what all the codes were.
51+
# Site Structure
52+
Once you get it up and running, I guess all these Tech guys just know things intuitively. But I did not. I did not know what the header meant, what all the codes were.
5353
54-
***`_site` Directory***: This is the output directory where Jekyll generates the static site. You **do not** put your new files here directly. Instead, Jekyll automatically builds your site into the `_site` folder when you run `jekyll build`. It contains the final, generated HTML files, along with any other assets that Jekyll processes.
54+
**`_site` Directory**: This is the output directory where Jekyll generates the static site. **Do not** place new files here directly; instead, Jekyll builds your site into the `_site` folder.Producing the final HTML files and assets.
5555

56-
***`_tabs` Directory***: This is used for Jekyll's "Tabs" plugin that Chirpy uses. The `_tabs` directory typically contains markdown files or other content that is used to populate or generate content dynamically on your site (for example, tabs for navigating content). If you make a new file under `_tabs' Your are making a new page on the website. The headers of those pages have numbers, if you want to change the order.
56+
**`_tabs` Directory**: This is used for Jekyll's "Tabs" plugin that Chirpy uses. The `_tabs` directory typically contains markdown files or other content that is used to populate or generate content dynamically on your site (for example, tabs for navigating content). If you make a new file under `_tabs' Your are making a new page on the website. The headers of those pages have numbers, if you want to change the order.
5757

58-
***For a new post***: Put the markdown file under `_posts/` with the correct filename format (`YEAR-MONTH-DAY-title.md`). And it will "shoot over" to the `_site/posts` folder.
58+
**For a new post**: Put the markdown file under `_posts/` with the correct filename format (`YEAR-MONTH-DAY-title.md`). It will then be generated into the `_site/posts` folder.
5959

6060
> ### To summarize:
6161
>
62-
> - You ***don’t*** manually put new files in `_site`.
63-
> - New content like posts goes in `_posts`.
62+
> - **Do Not** manually put new files in `_site`.
63+
> - Place new posts in `_posts` With the date in the file name, properly formatted.
6464
> - Static files or content like tabs might go in `_tabs`
6565

6666

67-
=========================================
67+
---
68+
---
6869

6970
## PUSH TO GITHUB
70-
`git status` Should show nothing at first<br>
71-
`git add .` dont forget the period <br>
72-
`git status` will show green now. <br>
73-
`git commit -m "updated main" ` you can change the coment <br>
74-
`git push` <br>
71+
- `git status` Should show nothing at first, but could show pending changes.
72+
- `git add .` (Don't forget the period)
73+
- `git status` will show green now.
74+
- `git commit -m "updated main" ` (Change the comment to what is appropriate.)
75+
- `git push`
7576

7677

7778

0 commit comments

Comments
 (0)