We propose a simplified syntax to allow arugments for all named admonitions. The syntax allows an argument for any title of a named admonition like {tip}, to allow users to easily set the color and icon of an admonition while also having a custom title. The proposed syntax is: ```{note} Custom Note Title Body of the styled admonition. ``` Context The original RST directives for named admonitions attention, caution, danger, error, hint, important, note, tip, and warning are designed for a single line, and allow you have the entire named admonition in a compact form. Any text immediately following the directive indicator (on the same line and/or indented on following lines) is interpreted as a directive block and is parsed for normal body elements.

Moved to github: https://github.com/executablebooks/myst-enhancement-proposals/pull/10

NOTE: There is active conversaion here on a simplified process: https://github.com/executablebooks/meta/pull/843 What is a MEP? MEP stands for MyST Enhancement Proposal. A MEP is a design document providing information to the MyST community, or describing a new feature for MyST or its processes or environment. The MEP should provide a concise technical specification of the feature and a rationale for the feature.

Markedly Structured Text (MyST) is intended to provide: A human readable text format for writing technical and scientific documentation. A specification for an abstract intermediate representation, independent of the input and output formats. A specification for a reference parser implementation, which can be used to convert from the text format to the abstract intermediate representation. A specification for a reference renderer implementation, which can be used to convert from the abstract intermediate representation to a variety of output formats. Guiding principles and constraints In running this project, we aim to adhere to several principles that we believe will result in higher-quality technology that aligns with the core principles of the open source community. Here are a few key components:

::: danger The Executable Books team meeting is on the first Wednesday/Thursday of each month. By participating in this meeting, you are agreeing to abide by and uphold the Code of Conduct. Please take a second to read through it! :pray: ::: Video conference link Calendar for meetings Activity Board

This note is yours, feel free to play around. :video_game: Type on the left :arrow_left: and see the rendered result on the right. :arrow_right: :memo: Where do I start? Step 1: Wow and this is?! Ok. [x] Create my first HackMD note (this one!) [ ] Change its title [x] Add a tag