Skip to content
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.

Find out the best way to make “shouts” #8

Open
1 of 4 tasks
kizu opened this issue Apr 5, 2013 · 0 comments
Open
1 of 4 tasks

Find out the best way to make “shouts” #8

kizu opened this issue Apr 5, 2013 · 0 comments

Comments

@kizu
Copy link
Member

kizu commented Apr 5, 2013

The best way is when you don't need to write classes in markdown.

So, there could be at least three ways to make creating shouts more convenient:

  1. Use a variable that would convert all h2 to shouts and h3 to articles etc.
  2. Make this automagically by checking if there are h3 used.
  3. Add some way to markup shouts using nested markdown, like ## **shout** — so strong inside header would transform to shout.
  4. When there is a header without content it could become a shout.

Ideally all three ways could be made at the same time.

kizu added a commit that referenced this issue Apr 16, 2013
kizu added a commit that referenced this issue Apr 17, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant