add author images and links

Author: wagslane

CONTRIBUTING.md

@@ -12,34 +12,34 @@ Editing is really easy - just open a pull request that modifies the articles mar
 
 By writing and publishing your ideas publicly, you can:
 
-* Impress future employers
-* Help you solidify what you've recently learned
-* Help others find answers that took you a long time to research
-* Gain traffic and domain authority for your own blogs and projects
-* Get helpful feedback on your writing skills from our editorial team
+- Impress future employers
+- Help you solidify what you've recently learned
+- Help others find answers that took you a long time to research
+- Gain traffic and domain authority for your own blogs and projects
+- Get helpful feedback on your writing skills from our editorial team
 
 ### Style guide and quality standards
 
-We are *very* picky about the quality of articles we publish. Don't be discouraged if your submissions get rejected! Feel free to publish the rejected work on your own blog, and come back and submit to Boot.dev again with new content in the future. Here are some guidelines that will help you as you craft stories for us to accept:
-
-* The article *must* be related to programming, ideally back-end development.
-* No "blog-a-day" or "stream of consciousness" posts.
-* Cite **all** sources.
-* Bring data as needed.
-* Bring quotes as needed.
-* Bring original data visualizations as needed.
-* Write at least 500 words, preferably 1000+.
-* Avoid clickbait titles.
-* Do not hot-link images, add images to the `static/img/{size}` directory.
-* Use a descriptive, evergreen URL path (filename) for your post.
-* Use a grammar plugin like Grammarly to avoid typos.
-* Structure text with bullet points, lists, etc. Avoid walls of paragraph text.
-* Use code blocks. We support syntax highlighting for popular programming languages.
-* Nest your headings properly. For example, you shouldn't have an `h3` within an `h1`.
-* You may include *tasteful* links back to your own site and projects. It is perfectly fine to have a one-sentence call-to-action for your product at the end of your story.
-* No affiliate links.
-* The Boot.dev version of your article *must* be the canonical version. If you're unsure what this means, do not cross post your content on other sites. You're only allowed to cross post to other sites if you set the canonical URL on those sites to point back to the Boot.dev post.
-* Proof read your article, then proof read it again.
+We are _very_ picky about the quality of articles we publish. Don't be discouraged if your submissions get rejected! Feel free to publish the rejected work on your own blog, and come back and submit to Boot.dev again with new content in the future. Here are some guidelines that will help you as you craft stories for us to accept:
+
+- The article _must_ be related to programming, ideally back-end development.
+- No "blog-a-day" or "stream of consciousness" posts.
+- Cite **all** sources.
+- Bring data as needed.
+- Bring quotes as needed.
+- Bring original data visualizations as needed.
+- Write at least 500 words, preferably 1000+.
+- Avoid clickbait titles.
+- Do not hot-link images, add images to the `static/img/{size}` directory.
+- Use a descriptive, evergreen URL path (filename) for your post.
+- Use a grammar plugin like Grammarly to avoid typos.
+- Structure text with bullet points, lists, etc. Avoid walls of paragraph text.
+- Use code blocks. We support syntax highlighting for popular programming languages.
+- Nest your headings properly. For example, you shouldn't have an `h3` within an `h1`.
+- You may include _tasteful_ links back to your own site and projects. It is perfectly fine to have a one-sentence call-to-action for your product at the end of your story.
+- No affiliate links.
+- The Boot.dev version of your article _must_ be the canonical version. If you're unsure what this means, do not cross post your content on other sites. You're only allowed to cross post to other sites if you set the canonical URL on those sites to point back to the Boot.dev post.
+- Proof read your article, then proof read it again.
 
 ### How to submit
 
@@ -54,8 +54,8 @@ We use [Hugo](https://gohugo.io/) as our static site generator. All articles are
 
 To contribute an article, all you need to do is:
 
-* Add your Markdown file
-* Add any images that will be used within your article (we'll handle to cover image)
+- Add your Markdown file
+- Add any images that will be used within your article (we'll handle to cover image)
 
 ### Add your Markdown file
 
@@ -67,21 +67,12 @@ Be sure to add `draft: true` to the frontmatter. This will prevent your article
 
 ### Adding images
 
-Do *not* worry about a cover image - we will add one for you.
+Do _not_ worry about a cover image - we will add one for you.
 
 All images go in the `static/img/{size}` directory, where `size` is the width. Use `webp` images, and make sure they're properly sized. You can use our [image resizer script](https://github.com/bootdotdev/blog#resize-images) if you're comfortable using [yarn](https://yarnpkg.com/).
 
 Link to the image using a relative link. The root is the `img` directory, e.g. `![alt text here](/img/800/my-image.webp)`.
 
-### Whitelisting your domain
-
-If you want to get some sweet SEO juice flowing back to your own site, awesome! Simply add your domain to the `dofollows` array in your post's frontmatter! e.g.
-
-```
-dofollows:
-  - "https://mydomain.com"
-```
-
 ### Wait for approval
 
 We'll usually get back to you quickly, certainly within a few days. We may leave comments on your pull request and ask for changes. If the article is "too far off" in terms of quality, we'll simply give you a rejection message and close the pull request. If that happens, feel free to publish your work elsewhere, and come back to us with different content in the future.
@@ -92,4 +83,4 @@ Once approved, we'll merge your pull request! As soon as it's merged, our CI/CD
 
 ## License
 
-Boot.dev retains the rights to all content submitted to and published via this public repository. You *may not* host this site elsewhere. That said, you may ask us to remove an article you have previously authored for us and we will do so as quickly as we reasonably can. If you do ask us to remove content, you likely will be unable to contribute again in the future, we don't want to be dealing with take-downs and dead URLs often.
+Boot.dev retains the rights to all content submitted to and published via this public repository. You _may not_ host this site elsewhere. That said, you may ask us to remove an article you have previously authored for us and we will do so as quickly as we reasonably can. If you do ask us to remove content, you likely will be unable to contribute again in the future, we don't want to be dealing with take-downs and dead URLs often.

assets/css/styles.css

@@ -218,7 +218,7 @@ main table thead th {
 
 main th,
 td {
-  padding: .5em;
+  padding: 0.5em;
 }
 
 main thead,

assets/css/tail-out.css

@@ -772,6 +772,11 @@ video {
   margin-bottom: 1rem;
 }
 
+.my-2 {
+  margin-top: 0.5rem;
+  margin-bottom: 0.5rem;
+}
+
 .mx-auto {
   margin-left: auto;
   margin-right: auto;
@@ -857,6 +862,10 @@ video {
   height: 24rem;
 }
 
+.h-12 {
+  height: 3rem;
+}
+
 .h-6 {
   height: 1.5rem;
 }
@@ -873,10 +882,6 @@ video {
   height: 100%;
 }
 
-.h-12 {
-  height: 3rem;
-}
-
 .min-h-screen {
   min-height: 100vh;
 }
@@ -885,6 +890,10 @@ video {
   width: 100%;
 }
 
+.w-12 {
+  width: 3rem;
+}
+
 .w-6 {
   width: 1.5rem;
 }
@@ -969,6 +978,12 @@ video {
   gap: 0.5rem;
 }
 
+.space-x-4 > :not([hidden]) ~ :not([hidden]) {
+  --tw-space-x-reverse: 0;
+  margin-right: calc(1rem * var(--tw-space-x-reverse));
+  margin-left: calc(1rem * calc(1 - var(--tw-space-x-reverse)));
+}
+
 .space-y-1 > :not([hidden]) ~ :not([hidden]) {
   --tw-space-y-reverse: 0;
   margin-top: calc(0.25rem * calc(1 - var(--tw-space-y-reverse)));
@@ -987,6 +1002,10 @@ video {
   border-radius: 0.25rem;
 }
 
+.rounded-full {
+  border-radius: 9999px;
+}
+
 .rounded-md {
   border-radius: 0.375rem;
 }
@@ -1008,6 +1027,11 @@ video {
   border-color: hsl(234 3% 39% / var(--tw-border-opacity));
 }
 
+.border-gray-500 {
+  --tw-border-opacity: 1;
+  border-color: hsl(235 1% 50% / var(--tw-border-opacity));
+}
+
 .border-gray-700 {
   --tw-border-opacity: 1;
   border-color: hsl(235 5% 24% / var(--tw-border-opacity));
@@ -1059,6 +1083,10 @@ video {
   padding: 0px;
 }
 
+.p-3 {
+  padding: 0.75rem;
+}
+
 .p-2 {
   padding: 0.5rem;
 }
@@ -1152,6 +1180,11 @@ video {
   color: hsl(235 3% 62% / var(--tw-text-opacity));
 }
 
+.text-gray-100 {
+  --tw-text-opacity: 1;
+  color: hsl(235 9% 94% / var(--tw-text-opacity));
+}
+
 .text-gray-300 {
   --tw-text-opacity: 1;
   color: hsl(235 5% 76% / var(--tw-text-opacity));
@@ -1272,6 +1305,11 @@ video {
   border-color: rgb(239 187 3 / var(--tw-border-opacity));
 }
 
+.hover\:border-gray-300:hover {
+  --tw-border-opacity: 1;
+  border-color: hsl(235 5% 76% / var(--tw-border-opacity));
+}
+
 .hover\:bg-blue-550:hover {
   --tw-bg-opacity: 1;
   background-color: hsl(235 87% 61% / var(--tw-bg-opacity));

config.toml

@@ -8,9 +8,6 @@ enableRobotsTXT = true
 summaryLength = 15
 pluralizelisttitles = false
 
-[Author]
-name = "Lane Wagner"
-
 [sitemap]
 changefreq = 'weekly'
 filename = 'sitemap.xml'
@@ -23,27 +20,11 @@ post = "/:section/:slug/"
 categories = "/:slug/"
 
 [params]
+author = "lane"
 description = "You don't need a CS degree to get hired, but you do need computer science skills. Prepare to land an entry-level role in tech by building real coding projects."
 footer = "© [Boot.dev](https://www.boot.dev) {Year}"
 logo = "/favicons/favicon-32x32.png"
 googleTagManager = "GTM-PT7FHFB"
-dofollows = [
-  "https://boot.dev",
-  "https://www.boot.dev",
-  "https://blog.boot.dev",
-  "https://www.boot.dev",
-  "https://wagslane.dev",
-  "https://scrimba.com",
-  "https://prepcards.dev",
-  "https://www.stratascratch.com",
-  "https://www.youtube.com",
-  "https://youtube.com",
-  "https://podcasts.apple.com",
-  "https://backendbanter.fm",
-  "https://www.backendbanter.fm",
-  "https://www.golanginterview.dev",
-  "https://golanginterview.dev",
-]
 
 [markup]
 [markup.tableOfContents]

content/about.md

@@ -1,6 +1,6 @@
 ---
 title: "About Boot.dev"
-author: Lane Wagner
+author: lane
 date: "2020-02-06"
 images:
   - /img/800/bootdev-explorer.png.webp

content/affiliate-terms.md

@@ -1,6 +1,6 @@
 ---
 title: "Affiliate Program Terms of Service"
-author: Lane Wagner
+author: lane
 date: "2020-02-06"
 ---
 

content/backend/backend-as-a-service.md

@@ -1,8 +1,8 @@
 ---
 title: "What is Backend-as-a-Service?"
-author: Natalie Schooner
+author: natalie
 date: "2022-12-05"
-categories: 
+categories:
   - "backend"
 images:
   - /img/800/backend-as-a-service-scifi.png.webp
@@ -20,16 +20,16 @@ Most BaaS products on the market include services like cloud storage, database m
 
 There are numerous BaaS providers, each with a different pricing plan and a slightly different offering of the services they include with each tier or product. HiTechNector compiled a comprehensive [list of BaaS providers](https://www.hitechnectar.com/blogs/top-14-backend-as-a-service-providers/), including:
 
-* 8 Base
-* Apache Usergrid
-* AWS Amplify
-* Back4App
-* Backendless
-* Built.io backend
-* Couchbase
-* Windows Azure Mobile Services
-* Firebase
-* Supabase
+- 8 Base
+- Apache Usergrid
+- AWS Amplify
+- Back4App
+- Backendless
+- Built.io backend
+- Couchbase
+- Windows Azure Mobile Services
+- Firebase
+- Supabase
 
 Firebase is probably the best-known option of these, focusing on BaaS for mobile and web apps. Other options have specialized services, like built.io backend which offers social media integration.