As part of the move, I'd like to move the validator to use a parser that better understands Jekyll/Kramdown internally. If anyone has experience manipulating kramdown-style markdown in python, I'd be curious to hear recommendations.
(In particular, for the special markdown extensions that aren't part of the CommonMark standard) Thanks, -Andy Boughton [email protected] On Thu, Jun 25, 2015 at 10:44 AM, Greg Wilson < [email protected]> wrote: > Everyone seems to be in favor, but we'll need some help to make this > change: > > 1. tools/check.py in https://github.com/swcarpentry/lesson-template needs > to be modified to parse Markdown with trailing styles ( > https://github.com/swcarpentry/lesson-template/issues/276). > > 2. The code that turns R Markdown into plain old Markdown needs to be > modified to generate Markdown with trailing styles ( > https://github.com/swcarpentry/lesson-template/issues/277) > > 3. We need code to turn Jupyter Notebooks into plain old Markdown with > trailing styles (https://github.com/swcarpentry/lesson-template/issues/278 > ) > > If you'd like to make this happen for the mid-August release, please grab > a ticket and dive in. > > Thanks, > Greg > > -- > Dr. Greg Wilson | [email protected] > Software Carpentry | http://software-carpentry.org > > > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
