[w3ctag/design-reviews] Require markdown for explainers, and some more (#381)

The rationale for suggesting this in a template monkeypatch instead of the explainer explainer is to signify a key difference we'd like to see between what is done in standard Chromium process.

I'm not particular about the Markdown requirement, but it was suggested and hence incorporated.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3ctag/design-reviews/pull/381

-- Commit Summary --

  * Require markdown for explainers, and some more

-- File Changes --

    M ISSUE_TEMPLATE.md (5)

-- Patch Links --

https://github.com/w3ctag/design-reviews/pull/381.patch
https://github.com/w3ctag/design-reviews/pull/381.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/pull/381