Convert informal, narrative blog posts into structured, professional technical documentation. This command transforms conversational content into precise, reference-quality documentation.
Converts informal blog posts into structured, professional technical documentation with proper hierarchy and formatting.
/plugin marketplace add danielrosehill/writing-editing-plugin/plugin install security-checkup@danielrosehillformat-conversion/Convert informal, narrative blog posts into structured, professional technical documentation. This command transforms conversational content into precise, reference-quality documentation.
Take the user's blog post content and convert it into technical documentation with these characteristics:
Blog Post Style:
Hey everyone! Today I want to share this awesome trick I discovered for speeding up your Docker builds. So basically, you know how Docker builds can be super slow sometimes? Well, I found that if you use multi-stage builds, you can cut down the time significantly. Let me show you how I do it...
Technical Documentation Style:
# Multi-Stage Docker Builds
## Overview
Multi-stage builds reduce Docker image build time and final image size by separating the build environment from the runtime environment.
## Prerequisites
- Docker Engine 17.05 or later
- Basic understanding of Dockerfiles
## Implementation
### Syntax
Multi-stage builds use multiple `FROM` statements in a single Dockerfile:
```dockerfile
FROM node:16 AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
FROM node:16-alpine
WORKDIR /app
COPY --from=builder /app/node_modules ./node_modules
## Output Format
Provide the converted technical documentation in clean markdown format, ready for inclusion in a documentation repository or wiki.
Paste the blog post content you'd like to convert to technical documentation.