Skip to content

Commit ba7dd66

Browse files
killshot13killshot13
committed
meta and content updates
1 parent 2271832 commit ba7dd66

9 files changed

+294
-29
lines changed

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ You can [create a site](https://app.stackbit.com/create?theme=https://github.com
4949

5050
1. Run the following command to assign this key to `STACKBIT_API_KEY` environment variable:
5151

52-
export STACKBIT_API_KEY={stackbit_api_key}
52+
export STACKBIT_API_KEY=""
5353

5454
1. Run the following command to fetch additional site contents from Stackbit if needed:
5555

‎site-metadata.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,5 @@
7979
}
8080
]
8181
},
82-
"title": "Michael Rehnert: Full-Stack Web Developer"
82+
"title": "Code. Develop. Engineer."
8383
}

‎src/data/data.json

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,17 @@
11
{
2-
"author": {
3-
"name": "Michael R.",
4-
"avatar": "https://res.cloudinary.com/practicaldev/image/fetch/s--mkPVL_Y4--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/497515/85abf111-5f97-462e-8e83-fe46b3be008b.jpeg"
5-
},
6-
"social": {
7-
"devto": { "username": "killshot13" },
8-
"twitter": { "username": "killsh0t13" },
9-
"github": { "username": "killshot13" },
10-
"linkedin": { "username": "Michael Rehnert"}
11-
}
12-
}
2+
"author": {
3+
"name": "Michael R.",
4+
"avatar": "https://res.cloudinary.com/practicaldev/image/fetch/s--mkPVL_Y4--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/497515/85abf111-5f97-462e-8e83-fe46b3be008b.jpeg"
5+
},
6+
"social": {
7+
"devto": {
8+
"username": "killshot13"
9+
},
10+
"twitter": {
11+
"username": "killsh0t13"
12+
},
13+
"github": {
14+
"username": "killshot13"
15+
}
16+
}
17+
}

‎src/pages/index.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Home
2+
title: M. Rehnert > Full-Stack Web Developer > Portfolio & Blog
33
hide_title: true
44
sections:
55
- section_id: hero
@@ -26,17 +26,17 @@ sections:
2626
url: blog/index.html
2727
style: button
2828
seo:
29-
title: M. Rehnert > Full-Stack Web Developer > Portfolio & Blog
30-
description: Articles, tutorials, and samples of open-source code for websites and software. Authored, designed, and published by Michael Rehnert.
29+
title: Code. Develop. Engineer.
30+
description: My Projects and Tutorials > A Curated Portfolio To Inspire and Educate > by Michael Rehnert | Full-Stack Web Developer | Author | Entepreneur
3131
extra:
3232
- name: "og:type"
3333
value: website
3434
keyName: property
3535
- name: "og:title"
36-
value: M. Rehnert > Full-Stack Web Developer > Portfolio & Blog
36+
value: Code. Develop. Enginner.
3737
keyName: property
3838
- name: "og:description"
39-
value: Articles, tutorials, and samples of open-source code for websites and software. Authored, designed, and published by Michael Rehnert.
39+
value: My Projects and Tutorials > A Curated Portfolio To Inspire and Educate > by Michael Rehnert | Full-Stack Web Developer
4040
keyName: property
4141
- name: "og:image"
4242
value: images/rehnert.co-OGimg.svg
@@ -46,9 +46,9 @@ seo:
4646
value: images/rehnert.co-twitter-card.png
4747
relativeUrl: true
4848
- name: "twitter:title"
49-
value: M. Rehnert | Web Developer | Portfolio & Blog
49+
value: Code. Develop. Enginner.
5050
- name: "twitter:description"
51-
value: Articles, tutorials, and samples of open-source code for websites and software by M. Rehnert.
51+
value: My Projects and Tutorials > A Curated Portfolio To Inspire and Educate > by Michael Rehnert | Full-Stack Web Developer | Author | Entepreneur
5252
- name: "twitter:image"
5353
value: images/rehnert.co-twitter-card.svg
5454
relativeUrl: true

‎src/pages/posts/discussions-1n5b.md

Lines changed: 169 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,169 @@
1+
---
2+
stackbit_url_path: posts/discussions-1n5b
3+
title: '"Discussions"'
4+
date: '2021-03-17T20:17:34.665Z'
5+
excerpt: >-
6+
A THOROUGH REVIEW OF GITHUB'S LATEST BRAINCHILD Overview After
7+
nearly a year...
8+
thumb_img_path: >-
9+
https://res.cloudinary.com/practicaldev/image/fetch/s--mS00IFfr--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/73suok4xhx023jic9t21.jpg
10+
comments_count: 2
11+
positive_reactions_count: 5
12+
tags:
13+
- github
14+
- news
15+
- productivity
16+
canonical_url: 'https://sth13.medium.com/discussions-d216ce8bba6e'
17+
template: post
18+
---
19+
#### **A THOROUGH REVIEW OF GITHUB'S LATEST BRAINCHILD**
20+
21+
---
22+
23+
## Overview
24+
25+
After nearly a year of private beta testing, GitHub confirmed last month in a blog post that its new [Discussions](https://docs.github.com/en/discussions) feature is now available as a public beta.
26+
27+
First revealed during the live stream of GitHub's [Satellite Virtual 2020](https://githubsatellite.com/), this latest addition to the GitHub platform seeks to provide a way for software communities to collaborate outside the codebase.
28+
29+
---
30+
31+
![View of a "GitHub Discussion"](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3oud35r5wy6wjbrwoe7v.jpeg)
32+
<iframe class="liquidTag" src="https://dev.to/embed/details?args=" style="border: 0; width: 100%;"></iframe>
33+
View of a "GitHub Discussion"
34+
<iframe class="liquidTag" src="https://dev.to/embed/enddetails?args=" style="border: 0; width: 100%;"></iframe>
35+
36+
37+
---
38+
39+
In theory, the new feature will improve collective participation for open-source projects while smoothing communication lines between project managers, developers, beta testers, and end-users.
40+
41+
> _"Discussions is a collaborative communication forum for the community around an open-source project."_ — [GitHub Docs](https://docs.github.com/en/discussions)
42+
43+
Some prominent repositories, such as [Node.js](https://github.com/nodejs/node/discussions), [Laravel](https://github.com/laravel/framework/discussions), [Next.js](https://github.com/vercel/next.js/discussions), and [Prisma](https://github.com/prisma/prisma/discussions), participated in the first round of beta testing and have already successfully integrated Discussions. Based on current trends, **it appears that Discussions is poised to reshape the existing structure of most GitHub repositories**.
44+
45+
---
46+
47+
[![A view of "Discussions" from the Next.js repository](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/p57qxyax6vzculdnu5th.jpeg)](https://github.com/vercel/next.js/discussions)
48+
<iframe class="liquidTag" src="https://dev.to/embed/details?args=" style="border: 0; width: 100%;"></iframe>
49+
[View of a "GitHub Discussion"](https://github.com/vercel/next.js/discussions)
50+
<iframe class="liquidTag" src="https://dev.to/embed/enddetails?args=" style="border: 0; width: 100%;"></iframe>
51+
52+
53+
---
54+
55+
## Features
56+
57+
By default, **four categories** are created to help Discussions stay organized.
58+
59+
> 1. 💬 General
60+
> 2. 💡 Idea
61+
> 3. 🙏 Q&A
62+
> 4. 🙌 Show and tell
63+
64+
Aside from these templated options, repository owners can author unlimited custom threads. **Users are encouraged to mark quality answers as helpful**, similar to the familiar layout of Stack Overflow.
65+
66+
Discussions also attempts to establish content moderation by **allowing top contributors to achieve higher privileges**. This option should help relieve some stress for the developer(s), who would otherwise be forced to keep a constant eye on the conversations.
67+
68+
---
69+
70+
71+
<iframe class="liquidTag" src="https://dev.to/embed/youtube?args=DbTWBP3_RbM" style="border: 0; width: 100%;"></iframe>
72+
73+
<iframe class="liquidTag" src="https://dev.to/embed/details?args=" style="border: 0; width: 100%;"></iframe>
74+
Video provided courtesy of [Github](https://www.youtube.com/channel/UC7c3Kb6jYCRj4JO) and [Michelle Mannering](https://www.mishmanners.com/).
75+
<iframe class="liquidTag" src="https://dev.to/embed/enddetails?args=" style="border: 0; width: 100%;"></iframe>
76+
77+
78+
---
79+
80+
## Configuration
81+
82+
Anyone can configure Discussions quite easily; it took me about **5–10 minutes per repository** on average.
83+
84+
The layout is almost identical to GitHub issues, allowing for creating any number of topics linked to a single repository, each with a unique title and URL. While this is conducive in most scenarios, the setup could intimidate some developers who maintain an extensive library of source code.
85+
86+
Fortunately, **most of the configuration is already provided by a boilerplate template**. I found the default options to be well-balanced, sparing precious design time while still allowing customization.
87+
88+
---
89+
[![Getting Started with Discussions](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/iayo2uvy9x6l4top9lp4.jpeg)](https://docs.github.com/en/discussions/quickstart)
90+
<iframe class="liquidTag" src="https://dev.to/embed/details?args=" style="border: 0; width: 100%;"></iframe>
91+
[Getting Started with Discussions](https://docs.github.com/en/discussions/quickstart)
92+
<iframe class="liquidTag" src="https://dev.to/embed/enddetails?args=" style="border: 0; width: 100%;"></iframe>
93+
94+
95+
---
96+
97+
As shown above, the option to enable Discussions is now available for every repository. To access, open the settings tab and scroll to the bottom of the features section.
98+
99+
You are now presented with a template containing several options to personalize if you so desire. Styling with Markdown is supported, so once you are satisfied, preview and publish just like a
100+
`README`
101+
.
102+
103+
A new menu tab should appear in the navbar of the repository. Here, members of the software community who utilize your code can now gather to converse and collaborate.
104+
105+
---
106+
107+
## Outlook
108+
109+
Some developers contend that Discussions shares too much similarity with existing features to be worth the hassle. Others fear that management will pile more expectations onto an already overwhelming workload.
110+
111+
As it stands, Discussions admittedly leaves room for improvement and likely will not be suitable for every situation. That being said, the latest metrics released by GitHub in a new report are nothing short of impressive.*
112+
113+
Since January 2020 —
114+
115+
> * **3000 discussions** have been created.
116+
> * **50% of active Discussions users** contributed or pushed code.
117+
> * **34% more pull requests** were merged.
118+
> * **18% less time** was required to accomplish a merge.
119+
120+
All figures were derived from beta testing conducted after the addition of Discussions to the Next.js repository, which produced a marked overall improvement in **user participation and developer productivity**.
121+
122+
*If you wish to read the entire report, visit [octoverse.github.com](octoverse.github.com), where you can also download a PDF copy for later reference.
123+
124+
---
125+
126+
![Customization options for pinned Discussions](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fo3ashle60qa848i1gi4.jpeg)
127+
<iframe class="liquidTag" src="https://dev.to/embed/details?args=" style="border: 0; width: 100%;"></iframe>
128+
Customization options for pinned Discussions
129+
<iframe class="liquidTag" src="https://dev.to/embed/enddetails?args=" style="border: 0; width: 100%;"></iframe>
130+
131+
132+
---
133+
134+
## Conclusion
135+
136+
Every developer knows that data from a test environment cannot be used conclusively to predict future performance.
137+
138+
However, if the benchmarks established last year hold steady, we can safely assume that Discussions' popularity and usage will continue to increase across GitHub. So here is my personal opinion on the matter.
139+
140+
**Provided as users, we treat Discussions like a tool and not a social media platform; and as project managers, we gradually and tactfully integrate the feature; I believe many benefits can be realized.**
141+
142+
I would love to hear perspectives from all of you, so please leave your thoughts in the comments.
143+
144+
Don't forget to 💖 this article and leave a 💭. If you're feeling extra generous, please click my name below to 🎆subscribe🎇!
145+
146+
-- killshot13
147+
148+
---
149+
150+
151+
<iframe class="liquidTag" src="https://dev.to/embed/user?args=killshot13" style="border: 0; width: 100%;"></iframe>
152+
153+
154+
---
155+
156+
*[This post is also available on DEV.](https://dev.to/killshot13/discussions-1n5b)*
157+
158+
159+
<script>
160+
const parent = document.getElementsByTagName('head')[0];
161+
const script = document.createElement('script');
162+
script.type = 'text/javascript';
163+
script.src = 'https://cdnjs.cloudflare.com/ajax/libs/iframe-resizer/4.1.1/iframeResizer.min.js';
164+
script.charset = 'utf-8';
165+
script.onload = function() {
166+
window.iFrameResize({}, '.liquidTag');
167+
};
168+
parent.appendChild(script);
169+
</script>

‎src/pages/posts/how-to-build-an-smtp-mail-server-with-express-node-and-gmail-aof.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ excerpt: >-
88
thumb_img_path: >-
99
https://res.cloudinary.com/practicaldev/image/fetch/s--U2LLP4Iw--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/de3p75v2w0yfb2sxcgpy.jpg
1010
comments_count: 5
11-
positive_reactions_count: 225
11+
positive_reactions_count: 226
1212
tags:
1313
- tutorial
1414
- node
@@ -401,7 +401,7 @@ We’ve successfully created an SMTP Email Server using Express and Node. We als
401401

402402
Feel free to clone the source code and explore your own methods of implementation. I hope you have found this tutorial useful, and thank you for taking the time to follow along!
403403

404-
Please don't forget to 💖 this article and leave a 💭. If you're feeling extra generous, click my name below so I get that 🎆subscribe🎇 notification!
404+
Don't forget to 💖 this article and leave a 💭. If you're feeling extra generous, please click my name below to 🎆subscribe🎇!
405405

406406
-- killshot13
407407

@@ -413,9 +413,6 @@ Please don't forget to 💖 this article and leave a 💭. If you're feeling ext
413413

414414
---
415415

416-
> _This article was originally published and featured on the
417-
> [daily.dev blog](https://daily.dev). Here is [the canonical link](https://daily.dev/blog/how-to-build-an-smtp-mail-server-with-express-node-and-gmail) to the original._
418-
419416

420417

421418

‎src/pages/posts/new-wordpress-admin-color-palette-1001.md

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
stackbit_url_path: posts/new-wordpress-admin-color-palette-1001
3+
title: New WordPress Admin Color Palette
4+
date: '2021-03-18T12:42:56.127Z'
5+
excerpt: >-
6+
WOW! So pretty... Let me just say I am loving this brand-new color palette
7+
repository for...
8+
thumb_img_path: >-
9+
https://res.cloudinary.com/practicaldev/image/fetch/s--DRSma37v--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/y56ze6gdam4dnsn0tvl7.jpg
10+
comments_count: 0
11+
positive_reactions_count: 3
12+
tags:
13+
- codepen
14+
- ux
15+
- wordpress
16+
canonical_url: 'https://dev.to/killshot13/new-wordpress-admin-color-palette-1001'
17+
template: post
18+
---
19+
#### **WOW!**
20+
21+
So pretty...
22+
23+
Let me just say I am loving this brand-new color palette repository for WordPress! (core, .org, and related projects)
24+
25+
Oh, and if you're a WP plugin developer, listen up because this applies to you too. And you'll also want to grab [this handy PostCSS tool](https://gist.github.com/ryelle/ce466fe20e9c8165d8cafe9597b84316) to automate your CSS changes courtesy of [@ryelle](https://profiles.wordpress.org/ryelle/)! 😁😎
26+
27+
In his February post, [Standardization of WP-Admin colors in WordPress 5.7](https://make.wordpress.org/core/2021/02/23/standardization-of-wp-admin-colors-in-wordpress-5-7/), WP Core dev [Jb Audras](https://profiles.wordpress.org/audrasjb/) offered the following in-depth summary, and I quote:
28+
29+
---
30+
31+
> "This is the first part of a larger project in cleaning up WordPress admin CSS. In WordPress 5.7, all colors used in the CSS are collapsed to one of 12 blues, greens, reds, and yellows, 13 grays, pure black, and pure white.
32+
>
33+
> This new streamlined color palette collapses all the colors that used to be in the WordPress source code down to seven core colors and a range of 56 shades that meet the WCAG 2.0 AA recommended contrast ratio against white or black.
34+
>
35+
> The colors are perceptually uniform from light to dark in each range, which means they start at white and get darker by the same amount with each step. Half the range has a 4.5 or higher contrast ratio against black, and the other half maintains the same contrast against white.
36+
>
37+
> Standardizing on this set of colors will help contributors make consistent, accessible design decisions. Themes and Plugin developers are encouraged to use this new color palette for better consistency between their products and WordPress Core.
38+
>
39+
> **Plugin authors that use the existing CSS Core classes should be all set up with the new color palette, as every Core class was updated accordingly."**
40+
41+
---
42+
43+
Need/want more details? Check out the official [Design Handbook](https://make.wordpress.org/design/handbook/foundations/colors) or the CodePen palette shown below.
44+
45+
---
46+
47+
48+
<iframe class="liquidTag" src="https://dev.to/embed/codepen?args=https%3A%2F%2Fcodepen.io%2Fryelle%2Fpen%2FWNGVEjw" style="border: 0; width: 100%;"></iframe>
49+
50+
51+
---
52+
53+
_Now for a quick recruitment pitch_ 😅
54+
55+
Did you know that anyone is welcome to come and help shape future upgrades and improvements to WordPress? True open-source to the core, there are no prerequisites to joining the WordPress community.
56+
57+
It's also an excellent opportunity for those of us starting out as developers and designers to join a thriving open-source community and gain some valuable experience.
58+
59+
Interested? Consider contributing just 5% of your overall development time/effort by joining us in the [Five for the Future](https://wordpress.org/five-for-the-future/) initiative!
60+
61+
You will have the opportunity to help develop the subsequent versions of WordPress in countless ways, from casually providing feedback to working directly with the elite WP Core team.
62+
63+
---
64+
65+
Don't forget to 💖 this article and leave a 💭. If you're feeling extra generous, please click my name below to 🎆subscribe🎇!
66+
67+
-- killshot13
68+
69+
---
70+
71+
72+
<iframe class="liquidTag" src="https://dev.to/embed/user?args=killshot13" style="border: 0; width: 100%;"></iframe>
73+
74+
75+
---
76+
77+
78+
*[This post is also available on DEV.](https://dev.to/killshot13/new-wordpress-admin-color-palette-1001)*
79+
80+
81+
<script>
82+
const parent = document.getElementsByTagName('head')[0];
83+
const script = document.createElement('script');
84+
script.type = 'text/javascript';
85+
script.src = 'https://cdnjs.cloudflare.com/ajax/libs/iframe-resizer/4.1.1/iframeResizer.min.js';
86+
script.charset = 'utf-8';
87+
script.onload = function() {
88+
window.iFrameResize({}, '.liquidTag');
89+
};
90+
parent.appendChild(script);
91+
</script>

0 commit comments

Comments
 (0)