Liz Marlowe

Technical Writing Portfolio

Clear, user-focused documentation that simplifies complexity and accelerates adoption.

I’m Liz Marlowe, a Senior Technical Writer with 20+ years of experience creating clear, task-focused documentation that empowers users and accelerates product adoption. I specialize in simplifying complex technology and delivering structured, actionable content that improves usability and enhances the user experience. This portfolio highlights best practices—logical organization, clarity, and real-world context. It includes a docs‑as‑code project suite (Docusaurus, Jekyll, MkDocs, Hugo) that demonstrates my hands‑on experience with modern documentation pipelines. It also includes recent contributions to open‑source projects, where I strengthen conceptual documentation and end‑user workflows.

📚 Writing Samples 🧩 Docs‑as‑Code Projects 🌱 Open Source Contributions

📖 Writing Samples

Explore a curated list of writing samples grouped by content type—user guides, API documentation, knowledge base articles, and technical reference guides.

Note: To respect confidentiality from prior roles, all samples are based on open‑source, commercial, or fictional products.

📚 User Guides

Docmost User Guide
Comprehensive guide for end users that describes a collaborative wiki platform—task‑based instructions with intuitive navigation.
Taiga User Guide
Agile project management tool guide for project leads—emphasizing usability, workflows, and clear outcomes.

🔗 API Guides

OpenWeatherMap API Guide
RESTful API documentation for developers—conceptual overview, authentication, rate limits, tutorials, and curated endpoint references.
Spotify API Guide
Developer documentation integrating music metadata, playback control, and user data through OAuth—authentication flows, pagination, errors, and practical use cases.

🛠️ How To Article

Create a relationship table in MadCap Flare
Step‑by‑step how-to article with annotated screenshots and best practices.

📖 Technical Reference Guides

Optiflow‑CloudSync CRM Integration Guide
Integration guide for technical users that describes a system integration, including data flows and a customer onboarding workflow.
AuroraOps Platform 5.2.0 Release Notes
Release Notes document that summarizes new features, resolved and known issues, and hotfixes, an actionable communication deliverable for diverse audiences.

🧩 Docs‑as‑Code Projects

Hands‑on documentation sites built with static site generators (SSGs). Each project demonstrates real docs‑as‑code workflows using Markdown and Git/GitHub.

Docusaurus — View site • IA & theming; versioning‑ready
Jekyll — View site • Layout & theme customization
MkDocs — View site • Material theme & search
Hugo (WIP) — View site • Shortcodes & fast builds

🌱 Open Source Contributions

I actively contribute to open‑source projects by improving documentation structure, clarity, and usability. My work focuses on strengthening conceptual understanding, tightening information architecture, and ensuring docs are actionable for end users and developers.

Docmost — Conceptual Documentation Additions — Added two new conceptual topics to improve user understanding of Docmost’s core information architecture:
- A concept page explaining workspaces, spaces, and pages, supported by a visual diagram.
- An example topic showing how an organization might structure content using these concepts.
These additions help new users form clear mental models and better navigate the platform.
PR (Pending Review):
Taiga — Complete End‑User Guide Creation — Authored a brand‑new user guide to fill a significant gap in Taiga’s documentation. While the developer docs are comprehensive (installation, backup & restore, webhooks/APIs), there was no end‑user guide. The new guide includes:
- An introduction to Taiga’s purpose, UI, and core concepts
- A full end‑to‑end Scrum workflow overview
- Backlog management tasks: Creating epics, user stories, and tasks
- Sprint planning: Creating sprints and assigning user stories
- Sprint execution: Tracking progress, updating work, and completing user stories
PR (Pending Review):

Why I Contribute to Open Source

Open‑source projects let me collaborate with diverse teams, improve documentation where it’s needed most, and support tools that serve real users. I’m especially drawn to projects with strong developer docs but missing end‑user guidance—opportunities to add clarity, structure, and onboarding paths that help communities thrive.

🛠 Skills & Tools

Tools: MadCap Flare, GitHub Desktop, Git/GitHub, M365 Copilot, Swagger/OpenAPI, Jira, Confluence, Snagit, MadCap Capture, Adobe CC, Camtasia, Audacity, Zeplin, Figma, Pendo
Languages: Markdown, HTML, XML
Specialties: SaaS documentation, API guides, user guides, configuration guides, integration guides, release notes, UI/UX writing

🗂 Planning & Process

I approach every project with a repeatable framework that emphasizes clarity, consistency, and measurable outcomes:

Content Strategy: Define audience, goals, success criteria, and scope before writing.
Information Architecture: Organize by content type (task, concept, reference) to support a structured, topic‑based/DITA‑informed approach.
Tools & Quality: Use templates, editing checklists, and version control to ensure consistency and maintainability.

✅ About This Portfolio

Format: Markdown for portability and native GitHub rendering
Tools Used: GitHub Wiki, Markdown, Snagit, MadCap Capture, Visio, Microsoft PowerPoint
Focus Areas: User guides, API guides, knowledge base content, technical reference guides

📬 Contact

LinkedIn Email