I create documentation that solves real problems.

Context: Backstage is an open-source developer portal used by platform engineering teams. Despite good official documentation, teams were struggling with understanding core concepts and implementation.

My contribution:

• Created a comprehensive guide grounded in a real-world scenario using a fictional company (Koslog)
• Authored step-by-step tutorials covering core features from initial setup through TechDocs integration
• Built and published a working demo repository that teams could use as a reference
• Identified and fixed an undocumented authentication error by contributing directly to the official Backstage documentation via PR
• Proposed and implemented clearer language in the official docs to help new users understand GitHub authentication flows

Impact: The guide and demo project now serve as a reference for platform engineering teams implementing Backstage. Several teams have used my template as a starting point for their own deployments, and my contributions to the official docs have helped prevent common setup errors.

Context: Ory is an open-source identity management product trusted by companies like OpenAI. The documentation was comprehensive but needed reorganization to better support new adopters dealing with complex systems like OAuth2, Identities, and Permissions.

My contribution:

• Completely redesigned the welcome page to provide a clearer entry point for new users
• Restructured getting-started guides to follow a logical progression
• Added detailed installation steps that were previously missing or assumed
• Implemented a "Learning from Scratch" section for users new to identity management
• Created framework-specific integration guides for React and Next.js

Impact: Improved discoverability of key documentation sections, leading to a better onboarding experience. Users could more easily understand how Ory's components fit together and find the specific implementation guidance they needed.

Context: MonoConnect.js is a JavaScript SDK for integrating secure bank account linking. When I started, documentation was limited to an unstructured GitHub README, leading to numerous developer issues.

My contribution:

• Conducted a full documentation audit based on source code, README, and GitHub issues
• Migrated content from GitHub to a structured Mintlify documentation site
• Created framework-specific integration guides for React, Angular, and Next.js
• Implemented a CI pipeline to test all code examples, preventing documentation rot
• Built a comprehensive API reference with method signatures and examples

Impact: The new documentation portal provided clear navigation, working code examples, and framework-specific guidance, reducing integration time for developers and decreasing support requests.

Context: When Docker released its Docker Init feature, Node.js developers struggled with implementation. The existing documentation didn't provide clear guidance for real-world applications.

My contribution:

• Built a working example project demonstrating Docker Init with Node.js in a real application context
• Created step-by-step instructions explaining the process and decisions
• Published a GitHub repository with starter code for hands-on learning
• Added visual aids showing terminal output and configuration details
• Included best practices for container optimization specific to Node.js applications

Impact: The article now ranks #1 on Google for "docker init nodejs," positioned above the official documentation, and serves as the primary reference for Node.js developers implementing Docker Init.

Context: Many DevOps beginners struggle with the fundamentals of Linux commands when they first start working in terminal environments.

My contribution:

• Created a beginner-friendly guide to essential Linux commands for DevOps engineers
• Covered key concepts like file manipulation, process management, networking and SSH basics
• Included practical examples showing real-world usage of each command
• Provided clear explanations focusing on specifically DevOps-relevant use cases

Impact: The article has helped engineers transitioning to DevOps roles understand Linux fundamentals in a practical, hands-on context.

Current project: I'm developing an AI writing assistant for technical documentation, using embeddings and vector search to generate content that follows documentation best practices.

Key features:

• Training on my documentation corpus to capture writing patterns and style
• Integration with documentation systems via API
• Consistency checking against style guides and terminology
• Code example verification against API specifications

Goal: Create a tool that helps technical writers maintain consistency across large documentation projects while adhering to quality standards and technical accuracy.

Context: Code examples in documentation often become outdated as APIs evolve, leading to frustrating developer experiences.

My contribution:

• Developed a testing framework for automatically extracting and validating code examples from documentation
• Created a CI pipeline that flags broken examples when APIs change
• Implemented a reporting system that helps documentation teams prioritize fixes

Impact: Reduced documentation errors by catching issues before they reached production, improving developer trust in the documentation.