All 60 tasks, level by level

The real graded Technical Writing tasks the portal assigns, grouped into three levels.

The portal assigns these Technical Writing tasks. Finish Level 1 before Level 2 and Level 2 before Level 3. Your mentor may mark some tasks as required for the certificate.

Level 1: Foundations (24 tasks)

Task	What to do
What technical writers do	Explain the technical writer role and the main document types: tutorials, how-to guides, reference and explanations.
Plain English	Rewrite 5 confusing paragraphs (from manuals or terms pages) in short, clear sentences.
Know your audience	Write the same instruction for a beginner, a developer and a manager, and explain the differences.
Markdown	Write a README in Markdown using headings, lists, links, images, tables and code blocks.
Style guide basics	Summarise 15 rules from the Google developer documentation style guide or Microsoft Writing Style Guide.
Step-by-step how-to	Write a how-to guide for installing Git on Windows with numbered steps and screenshots.
Screenshots and images	Take, crop and annotate screenshots for your guide, with alt text for each.
`Edit someone else's writing`	Edit a classmate's README for clarity, grammar and structure, and list your changes.
Glossary	Write a glossary of 20 terms for beginners in web development.
Git for writers	Keep your docs in a Git repo named techwriting-internship, using branches and pull requests.
Release notes	Write release notes for an imaginary app update with new features, fixes and known issues.
FAQ page	Write an FAQ with 10 real questions students ask about internships.
Rewrite an error message set	Rewrite 10 confusing error messages so they explain what happened and what to do.
Command-line docs	Document a CLI tool's commands, flags and examples.
Changelog	Write a changelog following Keep a Changelog for three versions of a project.
Contributing guide	Write a CONTRIBUTING.md for an open-source project.
Code comments review	Improve comments and docstrings in a small codebase.
Readability check	Check five documents with a readability tool and improve their scores.
Inclusive language	Review a document for non-inclusive terms and replace them.
Templates	Create templates for a how-to guide, a tutorial and a reference page.
Screenshots style guide	Write rules for screenshots: size, highlighting, sample data and alt text.
Short video guide	Record a 2-minute screen recording with captions for a simple task.
Docs search test	Search for 10 common tasks in a docs site and note which searches fail.
User feedback widget	Add a 'Was this page helpful?' feedback option to your docs site.

Level 2: Building real features (20 tasks)

Task	What to do
API reference	Document a public REST API endpoint fully: method, URL, parameters, request, response and errors.
OpenAPI	Write or improve an OpenAPI file for a small API and render it with Swagger UI or Redoc.
Tutorial	Write a beginner tutorial that ends with a working result (for example a to-do app), and test it with someone new.
Docs as code	Publish your docs as a site with MkDocs, Docusaurus or Hugo.
Information architecture	Plan the navigation and page structure of a documentation site for a product.
Diagrams	Draw an architecture diagram and a flowchart with Mermaid or draw.io and embed them in your docs.
Contribute to open source docs	Find a docs issue in an open-source project and submit a pull request to fix it.
Knowledge base article	Write 3 help-centre articles for a common support problem with clear titles and steps.
Video script	Write a script and storyboard for a 2-minute product tutorial video.
Usability test for docs	Watch 2 people follow your tutorial, note where they get stuck, and fix those parts.
SDK reference from code	Generate reference docs from code comments (JSDoc, Sphinx or Javadoc).
Architecture overview for developers	Write an architecture overview of a project for new developers.
Migration guide	Write a migration guide for a breaking change between two versions.
Docs CI	Add link checking and spell checking to your docs in CI.
Versioned docs	Publish docs for two versions of a product on your docs site.
Interview an engineer	Interview an engineer about a feature and turn the notes into a doc they approve.
Concept explainer with diagrams	Write a conceptual explanation of OAuth or DNS with two diagrams.
Help centre structure	Organise 20 help articles into categories with clear titles.
Writing for Indian languages	Translate a short guide into an Indian language and note the challenges.
Docs metrics dashboard	Show page views, feedback and search terms for your docs in a simple dashboard.

Level 3: Professional work and capstone (16 tasks)

Task	What to do
Docs review checklist	Create a checklist for reviewing technical docs (accuracy, clarity, examples, links, accessibility).
SDK quickstart	Write a quickstart for using an SDK or library in two programming languages.
Troubleshooting guide	Write a troubleshooting guide with symptoms, causes and fixes for 8 common errors.
Docs metrics	Define how you would measure documentation quality (search success, feedback, support tickets).
Writing with AI responsibly	Use an AI tool to draft a page, then fact-check and rewrite it. Document what the AI got wrong.
Localisation-ready writing	Prepare a guide for translation: simple sentences, no idioms, and a term list.
Real company docs	Write or improve a user guide page for a Training Trains, W3AppDevelopers or DomainHostly feature.
Capstone: documentation portfolio	Publish a docs site with a tutorial, how-to guides, API reference and explanation page, plus a portfolio page linking all your work.
Docs strategy	Write a documentation strategy for a startup: audiences, doc types, tools and ownership.
Content audit	Audit an existing docs site: outdated pages, gaps and duplicates, with a priority list.
API docs with try-it-now	Publish API docs where readers can make test calls.
Docs for AI assistants	Structure docs (llms.txt, clear headings) so AI tools can answer from them correctly.
Training program	Create a short training for developers on writing good READMEs.
Accessibility audit of docs	Audit your docs site for accessibility and fix issues.
Portfolio case study	Write a case study about one docs project: problem, process and results.
Capstone 2: docs for a real product	Produce complete documentation for a real open-source project or a Training Trains/W3/DH feature, reviewed and accepted by its owners.

← Tools and first-week setup Submitting tasks and earning your certificate →