[ReSpec] release v11.7.0 `

[Marcos Caceres]

Hi ReSpec users,

Just released v11.7.0, the tl;dr:

 💖 Introduced a "github:" config option.
 💖 Feedback to mailing-list no longer required.
 💖 overhauled markdown support.


## "github:"

Long overdue! Allows you to provide a URL to your spec's github
repository. This automatically generates a "Participate" entry at the
top of the document with links to:

 * link to the repository
 * link to commit history
 * latest editor's draft (based on github pages)

It basically does away for the need of "otherLinks".

Example
```
const respecConfig = {
  github: "https://github.com/w3c/browser-payment-api"
}
```
More details and examples at:
https://github.com/w3c/respec/wiki/github


## Mailing list
If you prefer to have feedback sent to Github instead of a WG mailing
list, simply remove "wgPublicList". Thanks @chaals for this one.

You might still want to add a note in the Status of the Doc letting
people know they should send feedback to github.

## Markdown

I overhauled the way we do markdown processing, which fixed a bunch of
outstanding bugs.

See: https://github.com/w3c/respec/wiki/format


As always, feedback, issues, help, and kind words, welcome!
https://github.com/w3c/respec

Happy spec'in.

[Ian Jacobs]

Thanks, Marcos!!

Ian

Post by Marcos Caceres
Hi ReSpec users,
💖 Introduced a "github:" config option.
💖 Feedback to mailing-list no longer required.
💖 overhauled markdown support.
## "github:"
Long overdue! Allows you to provide a URL to your spec's github
repository. This automatically generates a "Participate" entry at the
* link to the repository
* link to commit history
* latest editor's draft (based on github pages)
It basically does away for the need of "otherLinks".
Example
```
const respecConfig = {
github: "https://github.com/w3c/browser-payment-api"
}
```
https://github.com/w3c/respec/wiki/github
## Mailing list
If you prefer to have feedback sent to Github instead of a WG mailing
You might still want to add a note in the Status of the Doc letting
people know they should send feedback to github.
## Markdown
I overhauled the way we do markdown processing, which fixed a bunch of
outstanding bugs.
See: https://github.com/w3c/respec/wiki/format
As always, feedback, issues, help, and kind words, welcome!
https://github.com/w3c/respec
Happy spec'in.

--
Ian Jacobs <***@w3.org>
https://www.w3.org/People/Jacobs/
Tel: [phone]