Skip to content

Commit 3f3dac6

Browse files
EdwardAngertEdwardAngert
EdwardAngert
authored and
EdwardAngert
committed
portfolio LinkCards
1 parent 6630d04 commit 3f3dac6

7 files changed

Lines changed: 28 additions & 47 deletions

File tree

‎src/content/docs/pi-hole/index.mdx‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,9 @@
22
slug: docs/pi-hole
33
title: "Install and Configure Pi-Hole With Unbound on a Local Omada Controller"
44
description: "Block Ads and Unwanted Content on Your Local Network With Pi-Hole."
5+
summary: "Comprehensive guide covering Pi-hole installation, configuration, and network-wide ad blocking. Created after repeatedly setting this up due to hardware issues and helping others with the process."
6+
icon: "laptop"
7+
category: "Personal Reference Documentation"
58
next:
69
link: /docs/pi-hole/install-configure/
710
label: Set Up Raspberry OS and Install Pi-Hole

‎src/content/docs/portfolio/coder-quickstart.mdx‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,9 @@
22
slug: portfolio/coder-quickstart
33
title: "Coder Quickstart Documentation"
44
description: "From-scratch quickstart guide for Coder's self-hosted cloud development environment"
5+
summary: "From-scratch quickstart guide for Coder's self-hosted cloud development environment. Tested across multiple platforms (MacBook, Raspberry Pi, Linode) to ensure universal compatibility and smooth onboarding experience."
6+
icon: "laptop"
7+
category: "Coder Technical Documentation"
58
---
69

710
One of the first projects I took on at Coder was to write a "Quickstart" doc.

‎src/content/docs/portfolio/contrib-pr.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22
slug: portfolio/contrib-pr
33
title: "Work on a Contributor's PR in the Docs Repository"
44
description: "Internal Confluence guide for technical writers working with external contributors"
5+
summary: "Created workflow documentation for technical writers collaborating with external contributors on GitHub PRs. Solved a recurring problem where writers needed to work on contributor branches but lacked clear steps."
6+
icon: "github"
7+
category: "Pantheon Internal Guide"
8+
pdfLink: "/pdfs/Edward-Angert-Pantheon-Confluence-work-on-a-contributor-PR-in-the-docs-repository.pdf"
59
---
610

711
"Work on a Contributor's PR in the Docs Repository" is a Confluence page I created to help resolve an issue Pantheon’s

‎src/content/docs/portfolio/gitlab-first-contribution.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22
slug: portfolio/gitlab-first-contribution
33
title: "GitLab: Make a GitLab contribution"
44
description: "Make documentation easier for first time contributors"
5+
summary: "Overhauled the 'Make a GitLab contribution' tutorial to reduce barriers for new contributors. Reorganized into sequential steps, added new contribution methods (Web IDE, Gitpod, GDK-in-a-box), and tested each path."
6+
icon: "gitlab"
7+
category: "GitLab Community Documentation"
8+
externalLink: "https://docs.gitlab.com/development/contributing/first_contribution/"
59
---
610

711
Contributor Success at GitLab found that first-time contributors had trouble with the long and intimidating process that

‎src/content/docs/portfolio/index.mdx‎

Lines changed: 6 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -4,57 +4,16 @@ title: "Work Samples"
44
description: "Documentation samples across different organizations and project types"
55
---
66

7-
import { Card, CardGrid } from '@astrojs/starlight/components';
7+
import { LinkCard, CardGrid } from '@astrojs/starlight/components';
88

99
<CardGrid>
10-
<Card title="Contributor PR Workflow" icon="github">
11-
**Pantheon Internal Guide**
10+
<LinkCard title="Coder Quickstart Documentation" href="/portfolio/coder-quickstart/" description="From-scratch quickstart guide for Coder's self-hosted cloud development environment. Tested across multiple platforms." />
1211

13-
Created workflow documentation for technical writers collaborating with external contributors on GitHub PRs. Solved a recurring problem where writers needed to work on contributor branches but lacked clear steps.
12+
<LinkCard title="Work on a Contributor's PR in the Docs Repository" href="/portfolio/contrib-pr/" description="Created workflow documentation for technical writers collaborating with external contributors on GitHub PRs." />
1413

15-
Approach: Documented the Git commands and GitHub workflow, then tested with team members to refine the process.
14+
<LinkCard title="GitLab: Make a GitLab contribution" href="/portfolio/gitlab-first-contribution/" description="Make documentation easier for first time contributors." />
1615

17-
[Internal Confluence Guide (PDF)](/pdfs/Edward-Angert-Pantheon-Confluence-work-on-a-contributor-PR-in-the-docs-repository.pdf)
18-
</Card>
19-
20-
<Card title="GitLab First Contribution" icon="gitlab">
21-
**GitLab Community Documentation**
22-
23-
Overhauled the "Make a GitLab contribution" tutorial to reduce barriers for new contributors. The original process was intimidating and scattered across multiple pages.
24-
25-
Approach: Reorganized into sequential steps, added new contribution methods (Web IDE, Gitpod, GDK-in-a-box), and tested each path.
26-
27-
[More info](/docs/gitlab-first-contribution/) | [GitLab Docs](https://docs.gitlab.com/development/contributing/first_contribution)
28-
</Card>
29-
30-
<Card title="WordPress Remote Database" icon="seti:db">
31-
**Linode Customer Documentation**
32-
33-
Developed comprehensive guide for configuring WordPress with remote databases. Started with a support engineer's outline, then researched, tested, and documented the complete process.
34-
35-
Approach: Built test environment, documented each step, gathered feedback from docs team, refined based on customer questions.
36-
37-
[Customer Guide (PDF)](/pdfs/Edward-Angert-Configure-WordPress-to-use-a-Remote-Database-Linode.pdf)
38-
</Card>
39-
40-
<Card title="Pi-Hole With Unbound on a Local Omada Controller" icon="laptop">
41-
**Personal Reference Documentation**
42-
43-
Comprehensive guide covering Pi-hole installation, configuration, and network-wide ad blocking. Created after repeatedly setting this up due to hardware issues and helping others with the process.
44-
45-
Approach: Documented each setup iteration, organized into logical sequence, included troubleshooting steps.
46-
47-
[Installation Guide](/docs/pi-hole/)
48-
</Card>
49-
50-
<Card title="Multizone Failover Diagram" icon="puzzle">
51-
**Pantheon Technical Documentation**
52-
53-
Collaborated with design team to create visual representation of complex multizone failover architecture. Needed to explain technical concept that was difficult to understand from text alone.
54-
55-
Approach: Created initial draft based on engineering feedback, worked with design team for final version, integrated into customer documentation.
56-
57-
[Documentation Project](/docs/site-mz-failover-diagram/) | [Live Pantheon Docs](https://docs.pantheon.io/multizone-failover)
58-
</Card>
16+
<LinkCard title="Configure WordPress to use a Remote Database" href="/portfolio/linode-wp-remote-db/" description="Step-by-step guide to configure WordPress with a remote database on Linode." />
5917

18+
<LinkCard title="Site Multizone Failover Diagram" href="/portfolio/site-mz-failover-diagram/" description="Technical diagram created for Pantheon's multizone failover documentation." />
6019
</CardGrid>

‎src/content/docs/portfolio/linode-wp-remote-db.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22
slug: portfolio/linode-wp-remote-db
33
title: "Configure WordPress to use a Remote Database"
44
description: "Step-by-step guide to configure WordPress with a remote database on Linode"
5+
summary: "Developed comprehensive guide for configuring WordPress with remote databases. Started with a support engineer's outline, then researched, tested, and documented the complete process including troubleshooting steps."
6+
icon: "seti:db"
7+
category: "Linode Customer Documentation"
8+
pdfLink: "/pdfs/Edward-Angert-Configure-WordPress-to-use-a-Remote-Database-Linode.pdf"
59
---
610

711
I wrote this based on a Linode support ticket in which the Linode Support engineer offered a broad outline of what the

‎src/content/docs/portfolio/site-mz-failover-diagram.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22
slug: portfolio/site-mz-failover-diagram
33
title: "Site Multizone Failover Diagram"
44
description: "Technical diagram created for Pantheon's multizone failover documentation"
5+
summary: "Collaborated with design team to create visual representation of complex multizone failover architecture. Needed to explain technical concept that was difficult to understand from text alone."
6+
icon: "puzzle"
7+
category: "Pantheon Technical Documentation"
8+
externalLink: "https://docs.pantheon.io/multizone-failover"
59
---
610

711
Based on feedback from Support and engineers, I created a draft of this diagram and then worked with Pantheon’s design

0 commit comments

Comments
 (0)