New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using Hoedown #31
Comments
Waiting until API v2 gets released to start migrating. ;) |
@devinus good news #32 (comment) |
I'd like to have working bindings before Hoedown v3. So I suggest we deprecate this and create official Hoedown bindings for Node. |
@jmendeth Done. |
Wow, thanks! For some reason I can't push to it, though. 2014-03-25 18:57 GMT+01:00 Devin Torres notifications@github.com:
|
I have pushed an initial commit to https://github.com/jmendeth/node-hoedown.git, can you push it to the official repo? git clone https://github.com/jmendeth/node-hoedown.git && cd node-hoedown
git push https://github.com/hoedown/node-hoedown.git master After that, I should be able to push to it as usual. |
Done. |
👍 👍 |
Oh, I just realized you need to add the repositories to the Contributors team. >.< |
Done. |
Fine, I can now push to it. One last thing: could you update the repo's description to
like in the temporary repo? That'd be all. |
OK. Also, I've added collabs to the spec repo as well. |
Yeah, spec needs some love too. |
Done! 🎉 Already published in NPM, version * Except the autolinker, I'm still not familiar with its API. PD: @devinus it'd be interesting to use the node-hoedown's docs for the official ones, especially the flag / extension descriptions. |
I have revived Sundown into an improved library called Hoedown!
https://github.com/hoedown/hoedown
Here, I merged long languishing pull requests from Sundown, merged improvements from Redcarpet, merged improvements from Rinku and Houdini, greatly improved and standardized the API, and fixed many potential bugs.
Full list of changes: hoedown/hoedown@vmg:master...master
Sundown had a rich collection of bindings and it would truly be a shame if we couldn't all benefit from a single library in the future.
The text was updated successfully, but these errors were encountered: