Talk to us on GitHub
MakeItMarkdown is developed in the open. Everything — bug reports, format requests, questions, code — goes through the project repository:
github.com/L-Sangmin/makeitmarkdown
Reporting a bug
Use the bug report template. The two things that make a fix fast:
- The exact error text — copy the error card or the browser console line verbatim.
- A sample file that reproduces it. Our parsers are test-driven; a failing sample usually becomes a regression test the same day. One caution: files attached to a GitHub issue are uploaded to GitHub and publicly visible — strip anything confidential first. (Files you convert on the site itself never leave your browser; see privacy.)
Requesting a format
Use the format request template. Tell us what you feed the file to and what breaks when you convert it by hand — that's how we decide what the Markdown should look like. Two constraints shape what's feasible: conversion must run entirely in the browser (no server), and any library involved must be MIT, BSD or Apache-2.0 licensed.
What to expect
This is a small independent project, so there's no support desk — but every issue is read, and new issues get an automated first-pass triage that tries to reproduce bugs against the test suite and assesses format requests for browser-side feasibility. Honest expectation: clear reports with samples move quickly; vague ones wait for clarification.
Not sure it's a bug? Convert the file and read the fidelity report first — known limits show up there as warnings.