diff --git a/.idea/.gitignore b/.idea/.gitignore
deleted file mode 100644
index 13566b8..0000000
--- a/.idea/.gitignore
+++ /dev/null
@@ -1,8 +0,0 @@
-# Default ignored files
-/shelf/
-/workspace.xml
-# Editor-based HTTP Client requests
-/httpRequests/
-# Datasource local storage ignored files
-/dataSources/
-/dataSources.local.xml
diff --git a/.idea/inspectionProfiles/Project_Default.xml b/.idea/inspectionProfiles/Project_Default.xml
deleted file mode 100644
index 7c4836f..0000000
--- a/.idea/inspectionProfiles/Project_Default.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/.idea/jsLinters/eslint.xml b/.idea/jsLinters/eslint.xml
deleted file mode 100644
index 541945b..0000000
--- a/.idea/jsLinters/eslint.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
-
-
-
-
\ No newline at end of file
diff --git a/.idea/modules.xml b/.idea/modules.xml
deleted file mode 100644
index 90122d6..0000000
--- a/.idea/modules.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/.idea/shakhzod.me.iml b/.idea/shakhzod.me.iml
deleted file mode 100644
index 0c8867d..0000000
--- a/.idea/shakhzod.me.iml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/.idea/vcs.xml b/.idea/vcs.xml
deleted file mode 100644
index 35eb1dd..0000000
--- a/.idea/vcs.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
-
-
-
-
\ No newline at end of file
diff --git a/.vscode/settings.json b/.vscode/settings.json
new file mode 100644
index 0000000..e0f8b81
--- /dev/null
+++ b/.vscode/settings.json
@@ -0,0 +1,3 @@
+{
+ "editor.defaultFormatter": "dbaeumer.vscode-eslint"
+}
\ No newline at end of file
diff --git a/components/header.tsx b/components/header.tsx
new file mode 100644
index 0000000..ecb945d
--- /dev/null
+++ b/components/header.tsx
@@ -0,0 +1,17 @@
+import Image from 'next/image';
+import Link from 'next/link';
+
+export default function HeaderComponent() {
+ return (
+
+
+
+
+
+ );
+}
diff --git a/components/stream-schedule.tsx b/components/stream-schedule.tsx
new file mode 100644
index 0000000..64ec963
--- /dev/null
+++ b/components/stream-schedule.tsx
@@ -0,0 +1,11 @@
+import path from 'path';
+
+const rootDir = path.join(process.cwd(), 'content');
+
+// const raw = fs.readFileSync(rootDir + "stream-schedule.yaml")
+
+// console.log(raw)
+
+export default function StreamScheduleComponent() {
+ return
still doing...
;
+}
diff --git a/content/blog.mdx b/content/blog.mdx
deleted file mode 100644
index e006b13..0000000
--- a/content/blog.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: dev_b.log
----
-## this is my blog
\ No newline at end of file
diff --git a/content/gear.mdx b/content/gear.mdx
index 3477669..93762e9 100644
--- a/content/gear.mdx
+++ b/content/gear.mdx
@@ -6,10 +6,12 @@ i want to start by mentioning that windows os is only for gaming.
i can not work comfortably on it.
os:
-- linux, specifically manjaro distribution for the most time
+- linux, specifically nixos distribution for the most time (previously arch linux based manjaro)
- macos, because i have macbook air m1 and love it for its ui
- windows, only for gaming
+my nixos configs
+
hardware:
- macbook air m1 2020, 8gb ram, 256gb storage
- pc, i5-11600, gtx 1660 super, 16gb ram, 1tb + 500gb storage
@@ -18,8 +20,8 @@ i intentionally buy weaker hardware to use it in full potential
---
keyboards:
-- ergodox ez, black, blank keycaps, no rgb, cherry mx brown
-- hyperx alloy origins core tkl, rgb, cherry mx red
+- ergodox ez, black, blank keycaps, no rgb, gateron clear (previously cherry mx brown) switches
+- ~hyperx alloy origins core tkl, rgb, cherry mx red~
keyboard layout:
- programmer dvorak
diff --git a/content/index.mdx b/content/index.mdx
index cbad202..da23527 100644
--- a/content/index.mdx
+++ b/content/index.mdx
@@ -12,16 +12,17 @@ check out some sections out there:
- music i listen to
- gear i use
- projects i wrote (page is not ready yet)
-- me and kimmy writing tech related stuff
-- blog (coming soon)
+- shakhzod's lab on telegram
+- stream schedule last updated
ofc links too:
{/* TODO: Deal with links properly */}
+- youtube
- github
- linkedin
- spotify
- last.fm
- monkeytype
-btw, don't forget to by me a beer here.
+btw, don't forget to buy me a qibray or heineken.
diff --git a/content/stream-schedule.mdx b/content/stream-schedule.mdx
new file mode 100644
index 0000000..863f802
--- /dev/null
+++ b/content/stream-schedule.mdx
@@ -0,0 +1,7 @@
+---
+title: stream schedule | shakhzod's website
+---
+
+
+
+
\ No newline at end of file
diff --git a/content/stream-schedule.yaml b/content/stream-schedule.yaml
new file mode 100644
index 0000000..5733a21
--- /dev/null
+++ b/content/stream-schedule.yaml
@@ -0,0 +1,6 @@
+YAML:
+ - A human-readable data serialization language
+ - https://en.wikipedia.org/wiki/YAML
+yaml:
+ - A complete JavaScript implementation
+ - https://www.npmjs.com/package/yaml
\ No newline at end of file
diff --git a/package.json b/package.json
index 5d9a0e5..6906300 100644
--- a/package.json
+++ b/package.json
@@ -24,7 +24,8 @@
"react-dom": "18.2.0",
"rehype-attr": "^2.1.4",
"typescript": "4.9.5",
- "use-last-fm": "^0.6.1"
+ "use-last-fm": "^0.6.1",
+ "yaml": "^2.5.0"
},
"devDependencies": {
"@commitlint/cli": "^17.4.2",
diff --git a/pages/[[...page]].tsx b/pages/[[...page]].tsx
index cc2b874..6d7bccf 100644
--- a/pages/[[...page]].tsx
+++ b/pages/[[...page]].tsx
@@ -10,6 +10,15 @@ import Head from 'next/head';
import Link from 'next/link';
import CommentsComponent from '@/components/comments';
import CurrentlyListeningComponent from '@/components/currently-listening';
+import StreamScheduleComponent from '@/components/stream-schedule';
+import HeaderComponent from '@/components/header';
+
+const components = {
+ Link,
+ Comments: CommentsComponent,
+ CurrentlyListening: CurrentlyListeningComponent,
+ StreamSchedule: StreamScheduleComponent,
+};
const rootDir = path.join(process.cwd(), 'content');
const allPagesWithPath = async () =>
@@ -23,12 +32,6 @@ const allPagesWithPath = async () =>
});
});
-const components = {
- Link,
- Comments: CommentsComponent,
- CurrentlyListening: CurrentlyListeningComponent,
-};
-
export default function Page({
mdxSource,
}: {
@@ -48,6 +51,7 @@ export default function Page({
+
diff --git a/pages/typography.tsx b/pages/typography.tsx
deleted file mode 100644
index e5959ac..0000000
--- a/pages/typography.tsx
+++ /dev/null
@@ -1,441 +0,0 @@
-import React from 'react';
-import Head from 'next/head';
-
-export default function TypographyPage() {
- return (
- <>
-
- Tailwind Typography Test
-
-
-
-
- Until now, trying to style an article, document, or blog post with
- Tailwind has been a tedious task that required a keen eye for
- typography and a lot of complex custom CSS.
-
-
- By default, Tailwind removes all of the default browser styling from
- paragraphs, headings, lists and more. This ends up being really
- useful for building application UIs because you spend less time
- undoing user-agent styles, but when you really are just
- trying to style some content that came from a rich-text editor in a
- CMS or a markdown file, it can be surprising and unintuitive.
-
-
- We get lots of complaints about it actually, with people regularly
- asking us things like:
-
-
-
- Why is Tailwind removing the default styles on my h1{' '}
- elements? How do I disable this? What do you mean I lose all the
- other base styles too?
-
-
-
- We hear you, but we're not convinced that simply disabling our base
- styles is what you really want. You don't want to have to remove
- annoying margins every time you use a p element in a
- piece of your dashboard UI. And I doubt you really want your blog
- posts to use the user-agent styles either — you want them to look{' '}
- awesome, not awful.
-
-
- The @tailwindcss/typography plugin is our attempt to
- give you what you actually want, without any of the
- downsides of doing something stupid like disabling our base styles.
-
-
- It adds a new prose class that you can slap on any
- block of vanilla HTML content and turn it into a beautiful,
- well-formatted document:
-
-
-
- <article class="prose"> <h1>Garlic bread with cheese:
- What the science tells us</h1> <p> For years parents
- have espoused the health benefits of eating garlic bread with
- cheese to their children, with the food earning such an iconic
- status in our culture that kids will often dress up as warm,
- cheesy loaf for Halloween. </p> <p> But a recent study
- shows that the celebrated appetizer may be linked to a series of
- rabies cases springing up around the country. </p> <!--
- ... --> </article>
-
-
-
- For more information about how to use the plugin and the features it
- includes,{' '}
-
- read the documentation
-
- .
-
-
-
What to expect from here on out
-
- What follows from here is just a bunch of absolute nonsense I've
- written to dogfood the plugin itself. It includes every sensible
- typographic element I could think of, like{' '}
- bold text, unordered lists, ordered lists, code
- blocks, block quotes, and even italics.
-
-
- It's important to cover all of these use cases for a few reasons:
-
-
-
We want everything to look good out of the box.
-
- Really just the first reason, that's the whole point of the
- plugin.
-
-
- Here's a third pretend reason though a list with three items looks
- more realistic than a list with two items.
-
-
-
Now we're going to try out another header style.
-
Typography should be easy
-
- So that's a header for you — with any luck if we've done our job
- correctly that will look pretty reasonable.
-
-
Something a wise person once told me about typography is:
-
-
- Typography is pretty important if you don't want your stuff to
- look like trash. Make it good then it won't be bad.
-
-
-
- It's probably important that images look okay here by default as
- well:
-
-
-
-
- Contrary to popular belief, Lorem Ipsum is not simply random text.
- It has roots in a piece of classical Latin literature from 45 BC,
- making it over 2000 years old.
-
-
-
- Now I'm going to show you an example of an unordered list to make
- sure that looks good, too:
-
-
-
So here is the first item in this list.
-
In this example we're keeping the items short.
-
Later, we'll use longer, more complex list items.
-
-
And that's the end of this section.
-
What if we stack headings?
-
We should make sure that looks good, too.
-
- Sometimes you have headings directly underneath each other. In those
- cases you often have to undo the top margin on the second heading
- because it usually looks better for the headings to be closer
- together than a paragraph followed by a heading should be.
-
-
When a heading comes after a paragraph …
-
- When a heading comes after a paragraph, we need a bit more space,
- like I already mentioned above. Now let's see what a more complex
- list would look like.
-
-
-
-
-
- I often do this thing where list items have headings.
-
-
-
- For some reason I think this looks cool which is unfortunate
- because it's pretty annoying to get the styles right.
-
-
- I often have two or three paragraphs in these list items, too,
- so the hard part is getting the spacing between the paragraphs,
- list item heading, and separate list items to all make sense.
- Pretty tough honestly, you could make a strong argument that you
- just shouldn't write this way.
-
-
-
-
-
- Since this is a list, I need at least two items.
-
-
-
- I explained what I'm doing already in the previous list item,
- but a list wouldn't be a list if it only had one item, and we
- really want this to look realistic. That's why I've added this
- second list item so I actually have something to look at when
- writing the styles.
-
-
-
-
- It's not a bad idea to add a third item either.
-
-
- I think it probably would've been fine to just use two items but
- three is definitely not worse, and since I seem to be having no
- trouble making up arbitrary things to type, I might as well
- include it.
-
-
-
-
- After this sort of list I usually have a closing statement or
- paragraph, because it kinda looks weird jumping right to a heading.
-
-
Code should look okay by default.
-
- I think most people are going to use{' '}
- highlight.js or{' '}
- Prism or something if they want
- to style their code blocks but it wouldn't hurt to make them look{' '}
- okay out of the box, even with no syntax highlighting.
-
-
- Here's what a default tailwind.config.js file looks
- like at the time of writing:
-
- Nested lists basically always look bad which is why editors like
- Medium don't even let you do it, but I guess since some of you
- goofballs are going to do it we have to carry the burden of at least
- making it work.
-
-
-
- Nested lists are rarely a good idea.
-
-
- You might feel like you are being really "organized" or
- something but you are just creating a gross shape on the
- screen that is hard to read.
-
-
- Nested navigation in UIs is a bad idea too, keep things as
- flat as possible.
-
-
- Nesting tons of folders in your source code is also not
- helpful.
-
-
-
-
-
- Since we need to have more items, here's another one.
-
-
-
- I'm not sure if we'll bother styling more than two levels
- deep.
-
-
- Two is already too much, three is guaranteed to be a bad idea.
-
-
If you nest four levels deep you belong in prison.
-
-
-
-
- Two items isn't really a list, three is good though.
-
-
-
- Again please don't nest lists if you want people to actually
- read your content.
-
-
Nobody wants to look at this.
-
I'm upset that we even have to bother styling this.
-
-
-
-
- The most annoying thing about lists in Markdown is that{' '}
- <li> elements aren't given a child{' '}
- <p> tag unless there are multiple paragraphs in
- the list item. That means I have to worry about styling that
- annoying situation too.
-
-
-
-
- For example, here's another nested list.
-
-
But this time with a second paragraph.
-
-
- These list items won't have <p> tags
-
-
Because they are only one line each
-
-
-
-
-
- But in this second top-level list item, they will.
-
-
-
- This is especially annoying because of the spacing on this
- paragraph.
-
-
-
-
- As you can see here, because I've added a second line, this
- list item now has a <p> tag.
-
-
This is the second line I'm talking about by the way.
-
-
-
- Finally here's another list item so it's more like a list.
-
-
-
-
-
-
- A closing list item, but with no nested list, because why not?
-
-
-
-
And finally a sentence to close off this section.
-
There are other elements we need to style
-
- I almost forgot to mention links, like{' '}
-
- this link to the Tailwind CSS website
-
- . We almost made them blue but that's so yesterday, so we went with
- dark gray, feels edgier.
-
-
We even included table styles, check it out:
-
-
-
-
Wrestler
-
Origin
-
Finisher
-
-
-
-
-
Bret "The Hitman" Hart
-
Calgary, AB
-
Sharpshooter
-
-
-
Stone Cold Steve Austin
-
Austin, TX
-
Stone Cold Stunner
-
-
-
Randy Savage
-
Sarasota, FL
-
Elbow Drop
-
-
-
Vader
-
Boulder, CO
-
Vader Bomb
-
-
-
Razor Ramon
-
Chuluota, FL
-
Razor's Edge
-
-
-
-
- We also need to make sure inline code looks good, like if I wanted
- to talk about <span> elements or tell you the
- good news about @tailwindcss/typography.
-
-
- Sometimes I even use code in headings
-
-
- Even though it's probably a bad idea, and historically I've had a
- hard time making it look good. This{' '}
- "wrap the code blocks in backticks" trick works pretty well
- though really.
-
-
- Another thing I've done in the past is put a code tag
- inside of a link, like if I wanted to tell you about the{' '}
-
- tailwindcss/docs
- {' '}
- repository. I don't love that there is an underline below the
- backticks but it is absolutely not worth the madness it would
- require to avoid it.
-
-
- We haven't used an h4 yet
-
-
- But now we have. Please don't use h5 or h6{' '}
- in your content, Medium only supports two heading levels for a
- reason, you animals. I honestly considered using a{' '}
- before pseudo-element to scream at you if you use an{' '}
- h5 or h6.
-
-
- We don't style them at all out of the box because h4{' '}
- elements are already so small that they are the same size as the
- body copy. What are we supposed to do with an h5, make
- it smaller than the body copy? No thanks.
-
-
We still need to think about stacked headings though.
-
- Let's make sure we don't screw that up with h4{' '}
- elements, either.
-
-
- Phew, with any luck we have styled the headings above this text and
- they look pretty good.
-
-
- Let's add a closing paragraph here so things end with a decently
- sized block of text. I can't explain why I want things to end that
- way but I have to assume it's because I think things will look weird
- or unbalanced if there is a heading too close to the end of the
- document.
-
-
- What I've written here is probably long enough, but adding this
- final sentence can't hurt.
-
-