01 / CASE STUDYCI Fundamentals
Short lessons, real pipelines, and hands-on labs. A technical curriculum rebuilt from the ground up.
29% → 68% completion
Kim Hokanson
Portfolio
I bring together technical writing, content strategy, and learning design to help people understand complex products and put them to work. My work spans customer onboarding, developer education, and hands-on learning, with a focus on clear guidance and practical outcomes. This portfolio features selected case studies and work samples that show how I turn technical workflows into approachable content.
Strategy & results
01 / CASE STUDY
02 / CASE STUDYGitLab Duo
Practical AI training for troubleshooting pipelines, understanding code, and fixing vulnerabilities.
Modular courses + prebuilt labs
03 / CASE STUDYGitLab University
A central home for technical learning, from the information architecture to the launch catalog.
80K+ users · 180+ countries
04 / CASE STUDYCloud-migration onboarding
Two role-based learning paths that helped a customer team prepare for its move to the cloud.
6 weeks · 100% customer CSAT
Selected writing samples
A shared Style Guide and a hands-on lab: two examples of how I structure and write technical content.
Content standards & governance
Style Guide
A shared reference for content structure, taxonomy, accessibility, and the authoring workflow—from planning through review and publishing.
Explore the Style GuideScenario-based technical writing
Hands-on lab
A connected set of hands-on GitLab Duo exercises, with environment setup, task instructions, troubleshooting, and expected results.
Read the lab instructionsExperience
I connect content strategy, technical writing, and learning design with cross-functional program delivery.
Education
Ed.S., Educational Psychology
B.S., Human Development
OpenAI
— Present
Learning Experience & Curriculum Lead
Defining a shared learning taxonomy and prototyping role-based learning journeys with Codex.
GitLab
—
Senior Education Architect
Co-led GitLab University and built courses, labs, and videos on AI, CI/CD, and DevOps. Content reached 1.7M+ views with 93–96% CSAT.
PLEXSYS Interface Products
—
Technical Instructional Designer → Supervisor
Authored technical onboarding in MadCap Flare using shared content and Git-based workflows, turning 1,000+ pages of documentation into role-based learning.
Higher education
—
Instructional Designer · UWS & SLCC
Designed accessible digital courses, faculty training, and a university-wide course evaluation process.
Content structure, accessibility, authoring, and review standards. Open the Style Guide in a new tab
Written sample from the original GitLab training. Running the exercises requires the original provisioned environment and invitation code.
Hands-on lab · Full instructions
The scenario
You've been tasked with creating a simple website for the fictional store, DevOps Swag Shop, to showcase their collection of merch. As a new developer on the team, you need to quickly get up to speed with the project and become familiar with the work that's already been completed and what still needs to be updated to make the site ready for launch. To help you with rapid iterations, you'll use GitLab Duo as you oversee the process end-to-end, including quickly summarizing long discussion threads, committing code changes, managing broken CI/CD pipelines, and addressing security vulnerabilities.
Set up the lab environment
You'll complete all work on the DevOps Swag Store in the GitLab training environment. Follow the steps below to provision your access.
Note: in order to access to the lab environment, you must have a GitLab.com user account. These accounts are free and you can sign up for an account on GitLab.com.
- Make sure that you have logged into your GitLab.com account first.
- Navigate to gitlabdemo.com/login
- When prompted for an invitation code, enter the following: [invitation code supplied for the original training session]
- Select Provision Training Environment.
- When prompted for your GitLab.com username, enter your username without the @ symbol.
- To find your username, select your profile picture from the main GitLab navigation bar. Your username will be underneath your name.
- Select Provision Training Environment (again). Take note of your GitLab demo lab credentials and when they expire. We also recommend bookmarking your test group URL for safe keeping.
- Select My Group to be directly navigated to your test group.
Under your list of projects, you should see a project called DevOps Swag Store.
DevOps Swag Store background
It's time to get started on your work with the DevOps Swag Store, but first you need to know what you're working on. Prior to being added to the GitLab project, you were assigned an issue outlining some of the history behind the store. In addition to the issue description, there's a scrolling list of comments made from different team members. Using GitLab Duo, read the AI-generated summary below to bring you up to speed:
Update Product Descriptions
All of the products in the catalog currently have very brief, 1-2 sentence descriptions. We should update each product to have a more detailed description that includes:
- Specific features of the product
- Dimensions/sizing information
- Materials used
- Any other relevant details
This will allow customers to make more informed decisions when purchasing products.
Create an issue
From the issue summary, you learned that you'll be picking up with the action item to update the catalog product descriptions. In this exercise, you'll create a new issue in your project to start tracking your work.
- Navigate to the DevOps Swag Store project in the lab environment.
- From the lefthand menu, select Issues.
- Select the New issue button.
- In the Title textbox, add a name for your issue.
- In the Description textbox, select the Switch to plain text editing button.
- From the text editor, select the GitLab Duo (a Tanuki icon) button.
- Select Generate issue description.
- In the textbox that appears, write a short summary of the task you'll be working on - updating catalog product descriptions.
- Select Submit.
- Review the AI-generated summary and make changes as needed.
- Assign the issue to yourself and leave all other fields as their defaults.
- Select Create issue.
Investigate the failed pipeline
You may have noticed as you were working on the DevOps Swag Store merge request that the pipeline failed. Using what you know now about Root Cause Analysis, in this lab we'll use GitLab Duo to fix our broken pipeline.
- From the lefthand menu, select Build, then Pipelines.
- Select the most recent pipeline to open the pipeline graph.
- Select the failed test_job.
- Select the Troubleshoot button to open GitLab Duo Chat and automatically apply the /troubleshoot slash command.
- Review the AI-generated explanation of the failure and the example fix.
Fix the pipeline configuration
While the output from GitLab Duo will vary, it should explain the cause of the failure is the exit 1 command in our .gitlab-ci.yml file. In this case, we've intentionally added this code to create a job that always fails. Let's apply the fix to make the job succeed.
- Return to the root of the project and select the .gitlab-ci.yml file.
- From the Edit dropdown, select Edit in pipeline editor.
- In test_job, remove the line - exit 1 and replace it with - echo "Job completed successfully".
- Write any commit message and select Commit changes.
Wait for the pipeline to run and verify that the job now succeeds.
Now that we have a successful pipeline and we've finished all the changes to our merge request, go ahead and merge the changes! Then, view your newly deployed page to see your updated product descriptions. Nice work!
Remediate the vulnerability
Let's check in on our DevOps Swag Store project to see if there are any identified security vulnerabilities and use GitLab Duo to propose any needed fixes.
- From the lefthand menu, expand the Secure section.
- Select Vulnerability report. You should see one high severity vulnerability identified by the SAST scanner.
- Select the Explain or Resolve with AI button, then Explain with AI.
- Review explanation, exploitation example, and proposed fix.
- Return to the vulnerability overview and select Explain or Resolve with AI.
- Select Resolve with AI.
- Review the newly generated merge request, including the suggested changes.