:Title: <REQUIRED: proposal title>
:Author: <REQUIRED: list of authors' real names and optionally, email addrs>
:Discussions-To: docutils-develop@lists.sf.net, <enhancement ticket URL>
:Status: <REQUIRED: Draft | Active | Accepted | Provisional | Deferred | Rejected | Withdrawn | Final | Superseded>
:Type: <REQUIRED: API | Informational | Process>
:Created: <date created on, in dd-mmm-yyyy format>
:Docutils-Version: <version number>
:Replaces: current policy/API document
:Resolution: <url>


Abstract
========

.. A short (<~200 word) description of the technical issue being addressed.


Motivation
==========

.. Clearly explain why the existing specification is inadequate to
   address the problem that the proposal solves.


Rationale
=========

.. Describe why particular design decisions were made.


Specification
=============

.. Describe the syntax and semantics of any new feature.


Backwards Compatibility
=======================

.. Describe potential impact and severity on pre-existing code.


Security Implications
=====================

.. How could a malicious user take advantage of this new feature?


How to Teach This
=================

.. How to teach users, new and experienced, how to apply the proposal to
   their work.


Reference Implementation
========================

.. Link to any existing implementation and details about its state, e.g.
   proof-of-concept.


Rejected Ideas
==============

.. Why certain ideas that were brought while discussing this proposal
   were not ultimately pursued.


Open Issues
===========

.. Any points that are still being decided/discussed.


References
==========

.. A collection of URLs used as references through the proposal.


Copyright
=========

This document is placed in the public domain or under the
CC0-1.0-Universal license, whichever is more permissive.



..
    Local Variables:
    mode: indented-text
    indent-tabs-mode: nil
    sentence-end-double-space: t
    fill-column: 70
    coding: utf-8
    End:
