8 | Get started by editing
9 | src/app/page.js
10 |
56 | Find in-depth information about Next.js features and API. 57 |
58 | 59 | 60 | 66 |73 | Learn about Next.js in an interactive course with quizzes! 74 |
75 | 76 | 77 | 83 |90 | Explore the Next.js 13 playground. 91 |
92 | 93 | 94 | 100 |107 | Instantly deploy your Next.js site to a shareable URL with Vercel. 108 |
109 | 110 |32 | For years parents have espoused the health benefits of eating garlic bread 33 | with cheese to their children, with the food earning such an iconic status 34 | in our culture that kids will often dress up as warm, cheesy loaf for 35 | Halloween. 36 |
37 |38 | But a recent study shows that the celebrated appetizer may be linked to a 39 | series of rabies cases springing up around the country. 40 |
41 |` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too. 151 | 152 | - **For example, here's another nested list.** 153 | 154 | But this time with a second paragraph. 155 | 156 | - These list items won't have `
` tags 157 | - Because they are only one line each 158 | 159 | - **But in this second top-level list item, they will.** 160 | 161 | This is especially annoying because of the spacing on this paragraph. 162 | 163 | - As you can see here, because I've added a second line, this list item now has a `
` tag.
164 |
165 | This is the second line I'm talking about by the way.
166 |
167 | - Finally here's another list item so it's more like a list.
168 |
169 | - A closing list item, but with no nested list, because why not?
170 |
171 | And finally a sentence to close off this section.
172 |
173 | ## There are other elements we need to style
174 |
175 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
176 |
177 | We even included table styles, check it out:
178 |
179 | | Wrestler | Origin | Finisher |
180 | | ----------------------- | ------------ | ------------------ |
181 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
182 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
183 | | Randy Savage | Sarasota, FL | Elbow Drop |
184 | | Vader | Boulder, CO | Vader Bomb |
185 | | Razor Ramon | Chuluota, FL | Razor's Edge |
186 |
187 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
188 |
189 | ### Sometimes I even use `code` in headings
190 |
191 | 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.
192 |
193 | 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`](https://github.com/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.
194 |
195 | #### We haven't used an `h4` yet
196 |
197 | 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`.
198 |
199 | 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.
200 |
201 | ### We still need to think about stacked headings though.
202 |
203 | #### Let's make sure we don't screw that up with `h4` elements, either.
204 |
205 | Phew, with any luck we have styled the headings above this text and they look pretty good.
206 |
207 | 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.
208 |
209 | What I've written here is probably long enough, but adding this final sentence can't hurt.
210 |
211 | ## GitHub Flavored Markdown
212 |
213 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
214 |
215 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
216 |
217 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
218 |
219 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/automating-repetitive-tasks-productivity-hacks-for-developers/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Automating Repetitive Tasks: Productivity Hacks for Developers"
3 | description: How to deploy your Next.js apps on Vercel.
4 | image: "../../public/blogs/emile-perron-xrVDYZRGdw4-unsplash.jpg"
5 | publishedAt: "2023-01-01"
6 | updatedAt: "2023-01-01"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - productivity
11 | ---
12 |
13 | 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.
14 |
15 | 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.
16 |
17 | We get lots of complaints about it actually, with people regularly asking us things like:
18 |
19 | > 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?
20 | > 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.
21 |
22 | 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.
23 |
24 | 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:
25 |
26 | ```html
27 |
30 | For years parents have espoused the health benefits of eating garlic bread
31 | with cheese to their children, with the food earning such an iconic status
32 | in our culture that kids will often dress up as warm, cheesy loaf for
33 | Halloween.
34 |
36 | But a recent study shows that the celebrated appetizer may be linked to a
37 | series of rabies cases springing up around the country.
38 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
149 |
150 | - **For example, here's another nested list.**
151 |
152 | But this time with a second paragraph.
153 |
154 | - These list items won't have ` ` tags
155 | - Because they are only one line each
156 |
157 | - **But in this second top-level list item, they will.**
158 |
159 | This is especially annoying because of the spacing on this paragraph.
160 |
161 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
162 |
163 | This is the second line I'm talking about by the way.
164 |
165 | - Finally here's another list item so it's more like a list.
166 |
167 | - A closing list item, but with no nested list, because why not?
168 |
169 | And finally a sentence to close off this section.
170 |
171 | ## There are other elements we need to style
172 |
173 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
174 |
175 | We even included table styles, check it out:
176 |
177 | | Wrestler | Origin | Finisher |
178 | | ----------------------- | ------------ | ------------------ |
179 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
180 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
181 | | Randy Savage | Sarasota, FL | Elbow Drop |
182 | | Vader | Boulder, CO | Vader Bomb |
183 | | Razor Ramon | Chuluota, FL | Razor's Edge |
184 |
185 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
186 |
187 | ### Sometimes I even use `code` in headings
188 |
189 | 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.
190 |
191 | 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`](https://github.com/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.
192 |
193 | #### We haven't used an `h4` yet
194 |
195 | 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`.
196 |
197 | 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.
198 |
199 | ### We still need to think about stacked headings though.
200 |
201 | #### Let's make sure we don't screw that up with `h4` elements, either.
202 |
203 | Phew, with any luck we have styled the headings above this text and they look pretty good.
204 |
205 | 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.
206 |
207 | What I've written here is probably long enough, but adding this final sentence can't hurt.
208 |
209 | ## GitHub Flavored Markdown
210 |
211 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
212 |
213 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
214 |
215 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
216 |
217 | This works for email links too: contact@example.com.
218 |
--------------------------------------------------------------------------------
/project files/blogs/restful-apis-building-blocks/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "RESTful APIs: Building Blocks of Modern Web Applications"
3 | description: "Uncover the fundamental concepts of RESTful APIs and their crucial role in modern web application development."
4 | image: "../../public/blogs/luca-bravo-XJXWbfSo2f0-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - code quality
11 | - web development
12 | ---
13 |
14 |
15 |
16 | 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.
17 |
18 | 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.
19 |
20 | We get lots of complaints about it actually, with people regularly asking us things like:
21 |
22 | > 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?
23 | > 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.
24 |
25 | 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.
26 |
27 | 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:
28 |
29 | ```html
30 |
33 | For years parents have espoused the health benefits of eating garlic bread
34 | with cheese to their children, with the food earning such an iconic status
35 | in our culture that kids will often dress up as warm, cheesy loaf for
36 | Halloween.
37 |
39 | But a recent study shows that the celebrated appetizer may be linked to a
40 | series of rabies cases springing up around the country.
41 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
152 |
153 | - **For example, here's another nested list.**
154 |
155 | But this time with a second paragraph.
156 |
157 | - These list items won't have ` ` tags
158 | - Because they are only one line each
159 |
160 | - **But in this second top-level list item, they will.**
161 |
162 | This is especially annoying because of the spacing on this paragraph.
163 |
164 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
165 |
166 | This is the second line I'm talking about by the way.
167 |
168 | - Finally here's another list item so it's more like a list.
169 |
170 | - A closing list item, but with no nested list, because why not?
171 |
172 | And finally a sentence to close off this section.
173 |
174 | ## There are other elements we need to style
175 |
176 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
177 |
178 | We even included table styles, check it out:
179 |
180 | | Wrestler | Origin | Finisher |
181 | | ----------------------- | ------------ | ------------------ |
182 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
183 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
184 | | Randy Savage | Sarasota, FL | Elbow Drop |
185 | | Vader | Boulder, CO | Vader Bomb |
186 | | Razor Ramon | Chuluota, FL | Razor's Edge |
187 |
188 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
189 |
190 | ### Sometimes I even use `code` in headings
191 |
192 | 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.
193 |
194 | 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`](https://github.com/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.
195 |
196 | #### We haven't used an `h4` yet
197 |
198 | 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`.
199 |
200 | 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.
201 |
202 | ### We still need to think about stacked headings though.
203 |
204 | #### Let's make sure we don't screw that up with `h4` elements, either.
205 |
206 | Phew, with any luck we have styled the headings above this text and they look pretty good.
207 |
208 | 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.
209 |
210 | What I've written here is probably long enough, but adding this final sentence can't hurt.
211 |
212 | ## GitHub Flavored Markdown
213 |
214 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
215 |
216 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
217 |
218 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
219 |
220 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/web-accessibility-inclusive-design/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Web Accessibility: Inclusive Design for All Users"
3 | description: "Embrace the principles of web accessibility and ensure that your web applications reach all users, regardless of their abilities."
4 | image: "../../public/blogs/christina-wocintechchat-com-OtHEYbQXLFU-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - code quality
11 | - web development
12 | ---
13 |
14 |
15 |
16 | 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.
17 |
18 | 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.
19 |
20 | We get lots of complaints about it actually, with people regularly asking us things like:
21 |
22 | > 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?
23 | > 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.
24 |
25 | 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.
26 |
27 | 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:
28 |
29 | ```html
30 |
33 | For years parents have espoused the health benefits of eating garlic bread
34 | with cheese to their children, with the food earning such an iconic status
35 | in our culture that kids will often dress up as warm, cheesy loaf for
36 | Halloween.
37 |
39 | But a recent study shows that the celebrated appetizer may be linked to a
40 | series of rabies cases springing up around the country.
41 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
152 |
153 | - **For example, here's another nested list.**
154 |
155 | But this time with a second paragraph.
156 |
157 | - These list items won't have ` ` tags
158 | - Because they are only one line each
159 |
160 | - **But in this second top-level list item, they will.**
161 |
162 | This is especially annoying because of the spacing on this paragraph.
163 |
164 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
165 |
166 | This is the second line I'm talking about by the way.
167 |
168 | - Finally here's another list item so it's more like a list.
169 |
170 | - A closing list item, but with no nested list, because why not?
171 |
172 | And finally a sentence to close off this section.
173 |
174 | ## There are other elements we need to style
175 |
176 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
177 |
178 | We even included table styles, check it out:
179 |
180 | | Wrestler | Origin | Finisher |
181 | | ----------------------- | ------------ | ------------------ |
182 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
183 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
184 | | Randy Savage | Sarasota, FL | Elbow Drop |
185 | | Vader | Boulder, CO | Vader Bomb |
186 | | Razor Ramon | Chuluota, FL | Razor's Edge |
187 |
188 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
189 |
190 | ### Sometimes I even use `code` in headings
191 |
192 | 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.
193 |
194 | 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`](https://github.com/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.
195 |
196 | #### We haven't used an `h4` yet
197 |
198 | 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`.
199 |
200 | 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.
201 |
202 | ### We still need to think about stacked headings though.
203 |
204 | #### Let's make sure we don't screw that up with `h4` elements, either.
205 |
206 | Phew, with any luck we have styled the headings above this text and they look pretty good.
207 |
208 | 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.
209 |
210 | What I've written here is probably long enough, but adding this final sentence can't hurt.
211 |
212 | ## GitHub Flavored Markdown
213 |
214 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
215 |
216 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
217 |
218 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
219 |
220 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/web-development-tools-productivity/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "10 Essential Web Development Tools for Productivity"
3 | description: "Discover 10 must-have web development tools that can significantly boost your productivity, streamline your workflow, and enhance code quality."
4 | image: "../../public/blogs/lauren-mancke-aOC7TSLb1o8-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - productivity
11 | - web development
12 | ---
13 |
14 |
15 |
16 | 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.
17 |
18 | 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.
19 |
20 | We get lots of complaints about it actually, with people regularly asking us things like:
21 |
22 | > 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?
23 | > 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.
24 |
25 | 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.
26 |
27 | 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:
28 |
29 | ```html
30 |
33 | For years parents have espoused the health benefits of eating garlic bread
34 | with cheese to their children, with the food earning such an iconic status
35 | in our culture that kids will often dress up as warm, cheesy loaf for
36 | Halloween.
37 |
39 | But a recent study shows that the celebrated appetizer may be linked to a
40 | series of rabies cases springing up around the country.
41 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
152 |
153 | - **For example, here's another nested list.**
154 |
155 | But this time with a second paragraph.
156 |
157 | - These list items won't have ` ` tags
158 | - Because they are only one line each
159 |
160 | - **But in this second top-level list item, they will.**
161 |
162 | This is especially annoying because of the spacing on this paragraph.
163 |
164 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
165 |
166 | This is the second line I'm talking about by the way.
167 |
168 | - Finally here's another list item so it's more like a list.
169 |
170 | - A closing list item, but with no nested list, because why not?
171 |
172 | And finally a sentence to close off this section.
173 |
174 | ## There are other elements we need to style
175 |
176 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
177 |
178 | We even included table styles, check it out:
179 |
180 | | Wrestler | Origin | Finisher |
181 | | ----------------------- | ------------ | ------------------ |
182 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
183 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
184 | | Randy Savage | Sarasota, FL | Elbow Drop |
185 | | Vader | Boulder, CO | Vader Bomb |
186 | | Razor Ramon | Chuluota, FL | Razor's Edge |
187 |
188 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
189 |
190 | ### Sometimes I even use `code` in headings
191 |
192 | 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.
193 |
194 | 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`](https://github.com/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.
195 |
196 | #### We haven't used an `h4` yet
197 |
198 | 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`.
199 |
200 | 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.
201 |
202 | ### We still need to think about stacked headings though.
203 |
204 | #### Let's make sure we don't screw that up with `h4` elements, either.
205 |
206 | Phew, with any luck we have styled the headings above this text and they look pretty good.
207 |
208 | 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.
209 |
210 | What I've written here is probably long enough, but adding this final sentence can't hurt.
211 |
212 | ## GitHub Flavored Markdown
213 |
214 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
215 |
216 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
217 |
218 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
219 |
220 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/building-progressive-web-apps-bridging-the-gap-between-web-and-mobile/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Building Progressive Web Apps: Bridging the Gap Between Web and Mobile"
3 | description: "Integrating mindfulness practices helps developers cultivate present-moment awareness, fostering focus, problem-solving, and work-life balance."
4 | image: "../../public/blogs/charlesdeluvio-cZr2sgaxy3Q-unsplash.jpg"
5 | publishedAt: "2023-01-04"
6 | updatedAt: "2023-01-04"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - web development
11 | ---
12 |
13 |
14 |
15 | 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.
16 |
17 | 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.
18 |
19 | We get lots of complaints about it actually, with people regularly asking us things like:
20 |
21 | > 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?
22 | > 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.
23 |
24 | 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.
25 |
26 | 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:
27 |
28 | ```html
29 |
32 | For years parents have espoused the health benefits of eating garlic bread
33 | with cheese to their children, with the food earning such an iconic status
34 | in our culture that kids will often dress up as warm, cheesy loaf for
35 | Halloween.
36 |
38 | But a recent study shows that the celebrated appetizer may be linked to a
39 | series of rabies cases springing up around the country.
40 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
151 |
152 | - **For example, here's another nested list.**
153 |
154 | But this time with a second paragraph.
155 |
156 | - These list items won't have ` ` tags
157 | - Because they are only one line each
158 |
159 | - **But in this second top-level list item, they will.**
160 |
161 | This is especially annoying because of the spacing on this paragraph.
162 |
163 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
164 |
165 | This is the second line I'm talking about by the way.
166 |
167 | - Finally here's another list item so it's more like a list.
168 |
169 | - A closing list item, but with no nested list, because why not?
170 |
171 | And finally a sentence to close off this section.
172 |
173 | ## There are other elements we need to style
174 |
175 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
176 |
177 | We even included table styles, check it out:
178 |
179 | | Wrestler | Origin | Finisher |
180 | | ----------------------- | ------------ | ------------------ |
181 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
182 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
183 | | Randy Savage | Sarasota, FL | Elbow Drop |
184 | | Vader | Boulder, CO | Vader Bomb |
185 | | Razor Ramon | Chuluota, FL | Razor's Edge |
186 |
187 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
188 |
189 | ### Sometimes I even use `code` in headings
190 |
191 | 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.
192 |
193 | 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`](https://github.com/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.
194 |
195 | #### We haven't used an `h4` yet
196 |
197 | 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`.
198 |
199 | 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.
200 |
201 | ### We still need to think about stacked headings though.
202 |
203 | #### Let's make sure we don't screw that up with `h4` elements, either.
204 |
205 | Phew, with any luck we have styled the headings above this text and they look pretty good.
206 |
207 | 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.
208 |
209 | What I've written here is probably long enough, but adding this final sentence can't hurt.
210 |
211 | ## GitHub Flavored Markdown
212 |
213 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
214 |
215 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
216 |
217 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
218 |
219 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/mastering-css-grid-layout/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Mastering CSS Grid Layout: A Comprehensive Guide"
3 | description: "Dive into the world of CSS Grid Layout with this comprehensive guide. Learn how to create responsive and dynamic layouts using CSS Grid, and explore various examples and best practices for building modern web interfaces."
4 | image: "../../public/blogs/kelly-sikkema--1_RZL8BGBM-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - css
11 | - web development
12 | ---
13 |
14 |
15 |
16 | 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.
17 |
18 | 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.
19 |
20 | We get lots of complaints about it actually, with people regularly asking us things like:
21 |
22 | > 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?
23 | > 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.
24 |
25 | 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.
26 |
27 | 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:
28 |
29 | ```html
30 |
33 | For years parents have espoused the health benefits of eating garlic bread
34 | with cheese to their children, with the food earning such an iconic status
35 | in our culture that kids will often dress up as warm, cheesy loaf for
36 | Halloween.
37 |
39 | But a recent study shows that the celebrated appetizer may be linked to a
40 | series of rabies cases springing up around the country.
41 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
152 |
153 | - **For example, here's another nested list.**
154 |
155 | But this time with a second paragraph.
156 |
157 | - These list items won't have ` ` tags
158 | - Because they are only one line each
159 |
160 | - **But in this second top-level list item, they will.**
161 |
162 | This is especially annoying because of the spacing on this paragraph.
163 |
164 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
165 |
166 | This is the second line I'm talking about by the way.
167 |
168 | - Finally here's another list item so it's more like a list.
169 |
170 | - A closing list item, but with no nested list, because why not?
171 |
172 | And finally a sentence to close off this section.
173 |
174 | ## There are other elements we need to style
175 |
176 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
177 |
178 | We even included table styles, check it out:
179 |
180 | | Wrestler | Origin | Finisher |
181 | | ----------------------- | ------------ | ------------------ |
182 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
183 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
184 | | Randy Savage | Sarasota, FL | Elbow Drop |
185 | | Vader | Boulder, CO | Vader Bomb |
186 | | Razor Ramon | Chuluota, FL | Razor's Edge |
187 |
188 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
189 |
190 | ### Sometimes I even use `code` in headings
191 |
192 | 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.
193 |
194 | 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`](https://github.com/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.
195 |
196 | #### We haven't used an `h4` yet
197 |
198 | 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`.
199 |
200 | 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.
201 |
202 | ### We still need to think about stacked headings though.
203 |
204 | #### Let's make sure we don't screw that up with `h4` elements, either.
205 |
206 | Phew, with any luck we have styled the headings above this text and they look pretty good.
207 |
208 | 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.
209 |
210 | What I've written here is probably long enough, but adding this final sentence can't hurt.
211 |
212 | ## GitHub Flavored Markdown
213 |
214 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
215 |
216 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
217 |
218 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
219 |
220 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/progressive-web-apps-pwa/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "The Rise of Progressive Web Apps (PWAs): A Game Changer in Web Development"
3 | description: "Progressive Web Apps (PWAs) have transformed how users interact with web applications. Learn about the benefits of PWAs, their architecture, and how to build highly performant, offline-capable web apps using modern web technologies."
4 | image: "../../public/blogs/carlos-muza-hpjSkU2UYSU-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - PWA
11 | ---
12 |
13 |
14 |
15 | 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.
16 |
17 | 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.
18 |
19 | We get lots of complaints about it actually, with people regularly asking us things like:
20 |
21 | > 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?
22 | > 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.
23 |
24 | 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.
25 |
26 | 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:
27 |
28 | ```html
29 |
32 | For years parents have espoused the health benefits of eating garlic bread
33 | with cheese to their children, with the food earning such an iconic status
34 | in our culture that kids will often dress up as warm, cheesy loaf for
35 | Halloween.
36 |
38 | But a recent study shows that the celebrated appetizer may be linked to a
39 | series of rabies cases springing up around the country.
40 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
151 |
152 | - **For example, here's another nested list.**
153 |
154 | But this time with a second paragraph.
155 |
156 | - These list items won't have ` ` tags
157 | - Because they are only one line each
158 |
159 | - **But in this second top-level list item, they will.**
160 |
161 | This is especially annoying because of the spacing on this paragraph.
162 |
163 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
164 |
165 | This is the second line I'm talking about by the way.
166 |
167 | - Finally here's another list item so it's more like a list.
168 |
169 | - A closing list item, but with no nested list, because why not?
170 |
171 | And finally a sentence to close off this section.
172 |
173 | ## There are other elements we need to style
174 |
175 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
176 |
177 | We even included table styles, check it out:
178 |
179 | | Wrestler | Origin | Finisher |
180 | | ----------------------- | ------------ | ------------------ |
181 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
182 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
183 | | Randy Savage | Sarasota, FL | Elbow Drop |
184 | | Vader | Boulder, CO | Vader Bomb |
185 | | Razor Ramon | Chuluota, FL | Razor's Edge |
186 |
187 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
188 |
189 | ### Sometimes I even use `code` in headings
190 |
191 | 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.
192 |
193 | 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`](https://github.com/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.
194 |
195 | #### We haven't used an `h4` yet
196 |
197 | 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`.
198 |
199 | 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.
200 |
201 | ### We still need to think about stacked headings though.
202 |
203 | #### Let's make sure we don't screw that up with `h4` elements, either.
204 |
205 | Phew, with any luck we have styled the headings above this text and they look pretty good.
206 |
207 | 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.
208 |
209 | What I've written here is probably long enough, but adding this final sentence can't hurt.
210 |
211 | ## GitHub Flavored Markdown
212 |
213 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
214 |
215 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
216 |
217 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
218 |
219 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/web-accessibility-best-practices/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Best Practices for Web Accessibility: Building Inclusive Websites"
3 | description: "Ensuring web accessibility is vital for reaching a broader audience and creating inclusive digital experiences. This blog highlights essential web accessibility best practices, guidelines, and tools to make your websites accessible to everyone."
4 | image: "../../public/blogs/marvin-meyer-SYTO3xs06fU-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - code quality
11 | ---
12 |
13 |
14 |
15 | 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.
16 |
17 | 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.
18 |
19 | We get lots of complaints about it actually, with people regularly asking us things like:
20 |
21 | > 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?
22 | > 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.
23 |
24 | 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.
25 |
26 | 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:
27 |
28 | ```html
29 |
32 | For years parents have espoused the health benefits of eating garlic bread
33 | with cheese to their children, with the food earning such an iconic status
34 | in our culture that kids will often dress up as warm, cheesy loaf for
35 | Halloween.
36 |
38 | But a recent study shows that the celebrated appetizer may be linked to a
39 | series of rabies cases springing up around the country.
40 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
151 |
152 | - **For example, here's another nested list.**
153 |
154 | But this time with a second paragraph.
155 |
156 | - These list items won't have ` ` tags
157 | - Because they are only one line each
158 |
159 | - **But in this second top-level list item, they will.**
160 |
161 | This is especially annoying because of the spacing on this paragraph.
162 |
163 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
164 |
165 | This is the second line I'm talking about by the way.
166 |
167 | - Finally here's another list item so it's more like a list.
168 |
169 | - A closing list item, but with no nested list, because why not?
170 |
171 | And finally a sentence to close off this section.
172 |
173 | ## There are other elements we need to style
174 |
175 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
176 |
177 | We even included table styles, check it out:
178 |
179 | | Wrestler | Origin | Finisher |
180 | | ----------------------- | ------------ | ------------------ |
181 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
182 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
183 | | Randy Savage | Sarasota, FL | Elbow Drop |
184 | | Vader | Boulder, CO | Vader Bomb |
185 | | Razor Ramon | Chuluota, FL | Razor's Edge |
186 |
187 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
188 |
189 | ### Sometimes I even use `code` in headings
190 |
191 | 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.
192 |
193 | 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`](https://github.com/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.
194 |
195 | #### We haven't used an `h4` yet
196 |
197 | 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`.
198 |
199 | 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.
200 |
201 | ### We still need to think about stacked headings though.
202 |
203 | #### Let's make sure we don't screw that up with `h4` elements, either.
204 |
205 | Phew, with any luck we have styled the headings above this text and they look pretty good.
206 |
207 | 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.
208 |
209 | What I've written here is probably long enough, but adding this final sentence can't hurt.
210 |
211 | ## GitHub Flavored Markdown
212 |
213 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
214 |
215 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
216 |
217 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
218 |
219 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/js-frameworks-comparison/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "The Power of JavaScript Frameworks: Angular vs. React vs. Vue.js"
3 | description: "Get a detailed comparison of three popular JavaScript frameworks - Angular, React, and Vue.js. Understand the strengths, weaknesses, and use cases for each framework to make an informed decision for your next web development project."
4 | image: "../../public/blogs/paul-esch-laurent-oZMUrWFHOB4-unsplash.jpg"
5 | publishedAt: "2022-11-12"
6 | updatedAt: "2022-11-12"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - javascript
11 | - web development
12 | ---
13 |
14 |
15 |
16 | 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.
17 |
18 | 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.
19 |
20 | We get lots of complaints about it actually, with people regularly asking us things like:
21 |
22 | > 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?
23 | > 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.
24 |
25 | 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.
26 |
27 | 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:
28 |
29 | ```html
30 |
33 | For years parents have espoused the health benefits of eating garlic bread
34 | with cheese to their children, with the food earning such an iconic status
35 | in our culture that kids will often dress up as warm, cheesy loaf for
36 | Halloween.
37 |
39 | But a recent study shows that the celebrated appetizer may be linked to a
40 | series of rabies cases springing up around the country.
41 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
152 |
153 | - **For example, here's another nested list.**
154 |
155 | But this time with a second paragraph.
156 |
157 | - These list items won't have ` ` tags
158 | - Because they are only one line each
159 |
160 | - **But in this second top-level list item, they will.**
161 |
162 | This is especially annoying because of the spacing on this paragraph.
163 |
164 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
165 |
166 | This is the second line I'm talking about by the way.
167 |
168 | - Finally here's another list item so it's more like a list.
169 |
170 | - A closing list item, but with no nested list, because why not?
171 |
172 | And finally a sentence to close off this section.
173 |
174 | ## There are other elements we need to style
175 |
176 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
177 |
178 | We even included table styles, check it out:
179 |
180 | | Wrestler | Origin | Finisher |
181 | | ----------------------- | ------------ | ------------------ |
182 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
183 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
184 | | Randy Savage | Sarasota, FL | Elbow Drop |
185 | | Vader | Boulder, CO | Vader Bomb |
186 | | Razor Ramon | Chuluota, FL | Razor's Edge |
187 |
188 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
189 |
190 | ### Sometimes I even use `code` in headings
191 |
192 | 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.
193 |
194 | 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`](https://github.com/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.
195 |
196 | #### We haven't used an `h4` yet
197 |
198 | 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`.
199 |
200 | 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.
201 |
202 | ### We still need to think about stacked headings though.
203 |
204 | #### Let's make sure we don't screw that up with `h4` elements, either.
205 |
206 | Phew, with any luck we have styled the headings above this text and they look pretty good.
207 |
208 | 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.
209 |
210 | What I've written here is probably long enough, but adding this final sentence can't hurt.
211 |
212 | ## GitHub Flavored Markdown
213 |
214 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
215 |
216 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
217 |
218 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
219 |
220 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/blogs/mindfulness-and-meditation-techniques-for-developers-improving-focus-and-clarity/index.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Mindfulness and Meditation Techniques for Developers: Improving Focus and Clarity"
3 | description: "Integrating mindfulness practices helps developers cultivate present-moment awareness, fostering focus, problem-solving, and work-life balance."
4 | image: "../../public/blogs/c-d-x-PDX_a_82obo-unsplash.jpg"
5 | publishedAt: "2023-01-03"
6 | updatedAt: "2023-01-03"
7 | author: "codebucks"
8 | isPublished: true
9 | tags:
10 | - productivity
11 | ---
12 |
13 | 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.
14 |
15 | 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.
16 |
17 | We get lots of complaints about it actually, with people regularly asking us things like:
18 |
19 | > 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?
20 | > 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.
21 |
22 | 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.
23 |
24 | 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:
25 |
26 | ```html {1-3,4} title="index.html" caption="This is index.html file" showLineNumbers /will/
27 |
30 | For years parents have espoused the health benefits of eating garlic bread
31 | with cheese to their children, with the food earning such an iconic status
32 | in our culture that kids will often dress up as warm, cheesy loaf for
33 | Halloween.
34 |
36 | But a recent study shows that the celebrated appetizer may be linked to a
37 | series of rabies cases springing up around the country.
38 | ` tag unless there are multiple paragraphs in the list item. That means I have to worry about styling that annoying situation too.
149 |
150 | - **For example, here's another nested list.**
151 |
152 | But this time with a second paragraph.
153 |
154 | - These list items won't have ` ` tags
155 | - Because they are only one line each
156 |
157 | - **But in this second top-level list item, they will.**
158 |
159 | This is especially annoying because of the spacing on this paragraph.
160 |
161 | - As you can see here, because I've added a second line, this list item now has a ` ` tag.
162 |
163 | This is the second line I'm talking about by the way.
164 |
165 | - Finally here's another list item so it's more like a list.
166 |
167 | - A closing list item, but with no nested list, because why not?
168 |
169 | And finally a sentence to close off this section.
170 |
171 | ## There are other elements we need to style
172 |
173 | I almost forgot to mention links, like [this link to the Tailwind CSS website](https://tailwindcss.com). We almost made them blue but that's so yesterday, so we went with dark gray, feels edgier.
174 |
175 | We even included table styles, check it out:
176 |
177 | | Wrestler | Origin | Finisher |
178 | | ----------------------- | ------------ | ------------------ |
179 | | Bret "The Hitman" Hart | Calgary, AB | Sharpshooter |
180 | | Stone Cold Steve Austin | Austin, TX | Stone Cold Stunner |
181 | | Randy Savage | Sarasota, FL | Elbow Drop |
182 | | Vader | Boulder, CO | Vader Bomb |
183 | | Razor Ramon | Chuluota, FL | Razor's Edge |
184 |
185 | We also need to make sure inline code looks good, like if I wanted to talk about `` elements or tell you the good news about `@tailwindcss/typography`.
186 |
187 | ### Sometimes I even use `code` in headings
188 |
189 | 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.
190 |
191 | 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`](https://github.com/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.
192 |
193 | #### We haven't used an `h4` yet
194 |
195 | 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`.
196 |
197 | 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.
198 |
199 | ### We still need to think about stacked headings though.
200 |
201 | #### Let's make sure we don't screw that up with `h4` elements, either.
202 |
203 | Phew, with any luck we have styled the headings above this text and they look pretty good.
204 |
205 | 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.
206 |
207 | What I've written here is probably long enough, but adding this final sentence can't hurt.
208 |
209 | ## GitHub Flavored Markdown
210 |
211 | I've also added support for GitHub Flavored Mardown using `remark-gfm`.
212 |
213 | With `remark-gfm`, we get a few extra features in our markdown. Example: autolink literals.
214 |
215 | A link like www.example.com or https://example.com would automatically be converted into an `a` tag.
216 |
217 | This works for email links too: contact@example.com.
--------------------------------------------------------------------------------
/project files/Icons.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import { cx } from "../utils";
3 |
4 | export const SunIcon = ({ className, ...rest }) => (
5 |
158 | );
159 |
160 | export const MoonIcon = ({ className, ...rest }) => (
161 |
336 | );
337 |
338 | export const LinkedinIcon = ({ className, ...rest }) => {
339 | return (
340 |
364 | );
365 | };
366 |
367 | export const TwitterIcon = ({ className, ...rest }) => {
368 | return (
369 |
389 | );
390 | };
391 |
392 | export const GithubIcon = ({ className, ...rest }) => {
393 | return (
394 |
409 | );
410 | };
411 |
412 | export const DribbbleIcon = ({ className, ...rest }) => {
413 | return (
414 |
438 | );
439 | };
440 |
--------------------------------------------------------------------------------
Garlic bread with cheese: What the science tells us
29 | Garlic bread with cheese: What the science tells us
32 | Garlic bread with cheese: What the science tells us
32 | Garlic bread with cheese: What the science tells us
32 | Garlic bread with cheese: What the science tells us
31 | Garlic bread with cheese: What the science tells us
32 | Garlic bread with cheese: What the science tells us
31 | Garlic bread with cheese: What the science tells us
31 | Garlic bread with cheese: What the science tells us
32 | Garlic bread with cheese: What the science tells us
29 | This is inline code
{:html}`
49 |
50 | It's important to cover all of these use cases for a few reasons:
51 |
52 | 1. We want everything to look good out of the box.
53 | 2. Really just the first reason, that's the whole point of the plugin.
54 | 3. Here's a third pretend reason though a list with three items looks more realistic than a list with two items.
55 |
56 | Now we're going to try out another header style.
57 |
58 | ### Typography should be easy
59 |
60 | So that's a header for you — with any luck if we've done our job correctly that will look pretty reasonable.
61 |
62 | Something a wise person once told me about typography is:
63 |
64 | > Typography is pretty important if you don't want your stuff to look like trash. Make it good then it won't be bad.
65 |
66 | It's probably important that images look okay here by default as well:
67 |
68 |