Markdown templates

Start from a template

12 ready-to-use Markdown documents. Open one in the editor — it is added as a new document, so your existing drafts are never overwritten.

Meeting notes — Project sync

Date: 2026-01-15 · Attendees: Alex, Sam, Priya

Agenda
1. Status updates
2. Launch checklist
3. Open questions
Notes
- Design review is complete; two minor fixes remain.
- QA found no blocking issues in the release candidate.
Decisions
- Launch moves to Tuesday to avoid the holiday weekend.
Action items
- @Alex — fix the two design issues (Mon)
- @Sam — publish the release notes (Tue)
- @Priya — schedule the retro (Fri)
Work
Meeting notes
Agenda, decisions, and action items with owners and due dates.
Open in editor
Weekly report — Week 3

Highlights
- Shipped share links to all users
- Cut PDF export time by 40%
Progress

Goal Status Notes

Word export ✅ Released Wednesday

Offline mode 🟡 Testing on mobile

Templates 🔴 Waiting on copy

Next week
- Finish offline testing
- Draft the launch post
Blockers

Need final copy for the templates page by Thursday.
Work
Weekly status report
What shipped, what is next, and what is blocked — in one page.
Open in editor
PRD: Feature name

Owner Your name

Status Draft

Target release Q2

Problem

Describe the user problem in two or three sentences. Who has it, and how do we know?

Goals
- Goal one
- Goal two
Non-goals
- What this project deliberately will not do
User stories
- As a writer, I want to … so that …
- As an admin, I want to … so that …
Requirements

# Requirement Priority

1 The user can … P0

2 The system shows … P1

Success metrics
- Metric and target, e.g. weekly active users +10%
Open questions
- Question one
Work
Product requirements (PRD)
Problem, goals, user stories, requirements, and success metrics.
Open in editor
project-name

One-line description of what the project does.

Installation
```
npm install project-name
```
Usage
```
import project from 'project-name';

project.run({ verbose: true });
```
Features
- Fast and lightweight
- Zero configuration
- Works offline
Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

License

MIT
Engineering
Project README
A clean GitHub README with install, usage, and contributing sections.
Open in editor
Changelog

All notable changes to this project are documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Added
- New feature
[1.1.0] - 2026-01-15

Added
- Share links for documents
Changed
- Faster PDF export
Fixed
- Tables in Word import
[1.0.0] - 2026-01-01
- Initial release
Engineering
Changelog
Keep a Changelog format with Added, Changed, and Fixed sections.
Open in editor
Bug: Short description

Steps to reproduce
1. Go to …
2. Click …
3. See error
Expected behaviour

What you expected to happen.

Actual behaviour

What actually happened. Include the error message:
```
Paste the error or log output here
```
Environment

Browser Chrome 130

OS macOS 15

Version 1.2.3

Additional context

Screenshots, links, or anything else that helps.
Engineering
Bug report
Steps to reproduce, expected vs. actual behaviour, and environment.
Open in editor
GET /api/v1/users/{id}

Returns a single user.

Parameters

Name In Type Required Description

id path string ✅ The user ID

fields query string Comma-separated fields to return

Example request
```
curl https://api.example.com/api/v1/users/42 \
  -H "Authorization: Bearer $TOKEN"
```
Response
```
{
  "id": "42",
  "name": "Ada Lovelace",
  "email": "[email protected]"
}
```
Errors

Status Meaning

401 Missing or invalid token

404 User not found
Engineering
API endpoint docs
Request, parameters, response, and errors for one endpoint.
Open in editor
Your post title

Published January 15, 2026 · 5 min read

Open with a hook: a question, a surprising fact, or a short story.

The problem

Explain what the reader is struggling with.

The solution

Walk through your answer step by step.
1. First step
2. Second step
3. Third step
Pull out one memorable quote or key takeaway.

Wrapping up

Summarise the main point and tell the reader what to do next.
Writing
Blog post
A hook, structured sections, a key takeaway, and a call to action.
Open in editor
Your Name

Software Engineer · [email protected] · github.com/you · City, Country

Summary

Engineer with 5 years of experience building fast, accessible web applications.

Experience

Senior Engineer — Company A

2023 – present
- Led the rebuild of the editor, cutting load time by 50%
- Mentored four engineers
Engineer — Company B

2020 – 2023
- Built the export pipeline used by 100k users
Skills

TypeScript · React · Node.js · Accessibility · Performance

Education

B.Sc. Computer Science — University Name, 2020
Personal
Résumé
A one-page résumé that exports cleanly to PDF and Word.
Open in editor
Your Name [email protected] · City, Country

January 15, 2026

Dear Hiring Manager,

I am excited to apply for the Role position at Company. I have spent the last five years doing exactly the kind of work your team describes.

In my current role I specific achievement with a number. Before that, I another relevant achievement.

What draws me to Company is something specific about them. I would love to bring your strength to their goal.

Thank you for your time. I look forward to talking.

Sincerely, Your Name

Personal
Cover letter
A short, structured cover letter you can tailor in minutes.
Open in editor
Topic: Linear regression

Key ideas
- Fits a line that minimises squared error
- Assumes a roughly linear relationship
Formula

$$ \hat{y} = \beta_0 + \beta_1 x $$

The slope is $\beta_1 = \frac{\sum (x_i - \bar{x})(y_i - \bar{y})}{\sum (x_i - \bar{x})^2}$.

Process
```
graph LR
  A[Collect data] --> B[Fit model]
  B --> C[Check residuals]
  C --> D[Predict]
```
Review questions
- What does $R^2$ measure?
- When is linear regression a poor fit?
Personal
Study notes
Key ideas, formulas, and review questions — with math support.
Open in editor
Trip to Lisbon 🇵🇹

Dates: May 3 – May 8

Itinerary

Day Plan

Sat Arrive, Alfama walk

Sun Sintra day trip

Mon Belém, pastéis de nata

Bookings
- ✈️ Flight: ABC123
- 🏨 Hotel: confirmation 98765
Packing
- Passport
- Charger and adapter
- Comfortable shoes
Personal
Trip planner
Itinerary, bookings, and a packing checklist.
Open in editor

Goal	Status	Notes
Word export	✅	Released Wednesday
Offline mode	🟡	Testing on mobile
Templates	🔴	Waiting on copy


Owner	Your name
Status	Draft
Target release	Q2

#	Requirement	Priority
1	The user can …	P0
2	The system shows …	P1


Browser	Chrome 130
OS	macOS 15
Version	1.2.3

Name	In	Type	Required	Description
`id`	path	string	✅	The user ID
`fields`	query	string		Comma-separated fields to return

Status	Meaning
401	Missing or invalid token
404	User not found

Day	Plan
Sat	Arrive, Alfama walk
Sun	Sintra day trip
Mon	Belém, pastéis de nata

Why start from a Markdown template?

A good template removes the blank-page problem and keeps recurring documents consistent. Meeting notes always capture decisions and owners, bug reports always include steps to reproduce, and every README answers the same three questions: what is it, how do I install it, and how do I use it.

Because these templates are plain Markdown, they work anywhere: GitHub, GitLab, Notion, Obsidian, static site generators, and of course the Markdown editor on this site, where you can export them to PDF, Word, or HTML. Need a README tailored to your project? Try theREADME generator.

Start from a template

Meeting notes

Weekly status report

Product requirements (PRD)

Project README

Changelog

Bug report

API endpoint docs

Blog post

Résumé

Cover letter

Study notes

Trip planner

Why start from a Markdown template?