# What makes a good MWE?

Actually, when I was thinking about my next question and about to include one *.tex and one *.bib file in my MWE, I was looking for a MWE template here, but could not find one.

But everyone here should know how to construct a Minimal working example, especially newbies like me.

Thus, despite knowing that there is not ONE good MWE for asking questions, I wonder what would be the most minimal, yet working skeleton for:

• General Questions
• Questions with bibtex/biblatex
• Typo related questions
• Questions with international reach (i.e. encoding, language-specifics)

This question is supposed to help all newbies, so help me making it good!

-

## migrated from tex.stackexchange.comMar 1 '13 at 18:49

This question came from our site for users of TeX, LaTeX, ConTeXt, and related typesetting systems.

\documentclass{article} \begin{document} \end{document} – Alexander Mar 1 '13 at 18:48
@Alexander I guess you made a joke, but if taken seriously your example is wrong in the sense “minimal” is meant here, cf. I've just been asked to write a minimal example, what is that?. – Speravir Mar 1 '13 at 18:53
Martin, please take a look on I've just been asked to write a minimal example, what is that? an say, if one of your points is not regarded. Otherwise we should close your question as duplicate. – Speravir Mar 1 '13 at 18:55

A good minimal example is one which shows that someone really used his/her brain and invested some time and effort to make a clear and concise question. You don't need a template to realize that an \input is problematic - you only need to really think about "what helps others to understand my question" and "what could hinder them". There are some elements like the filecontents environment which are useful to know - but large headers and unneeded text are much more problematic than an missing filecontents.

-

The following resources are a good place to start:

In general, just make an example that demonstrates the error but doesn't contain any code unrelated to the error.

Unfortunately, it's hard to provide an MWE for the things you mentioned, since it's really context dependent.

-

A good MWE is some compilable, "to-the-point" code that clearly isolates the problem and contains no superfluous clutter and only a limited amount of jargon from the particular area.

-