Hi Jakub! I know this repo has not seen much activity lately, but it has inspired me to finally shift all of my own AsciiDoc tools to favor a proper semantic HTML converter. In the process, I've coded some tweaks to your templates/helpers, and now I'm checking if you want me to PR this back upstream.
However, I realize having someone come out of nowhere wanting to contribute to an older project can be jarring, so please don't feel pressured by this sudden activity. Also, for what it's worth, some of my changes address issues already on your board, including #20, #25, and #26. These weren't approved work tickets, but implementing them felt productive.
I want to be mindful of your wishes, and I don't want to over-propose anything. So first I'm just going to link to my own fork with a branch containing just the changes to templates/examples/helpers, so you can see the 4 changes I'm proposing (the PR is internal on my fork just so as not to hit you out of the blue with a pending PR on this repo). DocOps#1
As for how to move forward, I leave that up to your lead. If I don't hear from you, I expect to just maintain my own fork at DocOps/asciidoctor-html5s and not rename or release to npm or RubyGems.
If you want any of this issued as PRs, I'll default to creating a PR for each change. Let me know if you want them combined into one, and let me know if you want me to issue another PR for a 0.6.0 release, with some updated libraries, docs, version bump, etc.
Also maybe of note, the immediate downstream library I needed this for is going to be a stylesheet framework for AsciiDoc-sourced HTML in BOTH your html5s and the standard/legacy output, which I've seen discussed in your issues. I am close to releasing that, and it will actually accommodate html5s-0.5.x output just fine. I've spent a while hopefully achieving a flexible base for adaptive CSS that modifies/unifies the rendering of both converters, which is what motivated these changes.
Hi Jakub! I know this repo has not seen much activity lately, but it has inspired me to finally shift all of my own AsciiDoc tools to favor a proper semantic HTML converter. In the process, I've coded some tweaks to your templates/helpers, and now I'm checking if you want me to PR this back upstream.
However, I realize having someone come out of nowhere wanting to contribute to an older project can be jarring, so please don't feel pressured by this sudden activity. Also, for what it's worth, some of my changes address issues already on your board, including #20, #25, and #26. These weren't approved work tickets, but implementing them felt productive.
I want to be mindful of your wishes, and I don't want to over-propose anything. So first I'm just going to link to my own fork with a branch containing just the changes to templates/examples/helpers, so you can see the 4 changes I'm proposing (the PR is internal on my fork just so as not to hit you out of the blue with a pending PR on this repo). DocOps#1
As for how to move forward, I leave that up to your lead. If I don't hear from you, I expect to just maintain my own fork at
DocOps/asciidoctor-html5sand not rename or release to npm or RubyGems.If you want any of this issued as PRs, I'll default to creating a PR for each change. Let me know if you want them combined into one, and let me know if you want me to issue another PR for a 0.6.0 release, with some updated libraries, docs, version bump, etc.
Also maybe of note, the immediate downstream library I needed this for is going to be a stylesheet framework for AsciiDoc-sourced HTML in BOTH your html5s and the standard/legacy output, which I've seen discussed in your issues. I am close to releasing that, and it will actually accommodate html5s-0.5.x output just fine. I've spent a while hopefully achieving a flexible base for adaptive CSS that modifies/unifies the rendering of both converters, which is what motivated these changes.