Closed jaredmorgs closed 1 year ago
I totally agree. My plan was to do this as soon as I get version 1.0.0 of the plugin released.
We should move the current master to the 3.x branch, then upgrade and reconfigure master.
That sounds like a good idea. It's been a "fun" week trying to get Middleman to play nicely with AsciiDoc.
Having something at 4.0 ready to go would have saved me some time and probably would have made me fight harder to move away from the prolific Middleman 3 templates floating around out there.
On Thu, 11 Aug 2016, 19:13 Dan Allen notifications@github.com wrote:
I totally agree. My plan was to do this as soon as I get version 1.0.0 of the plugin released.
We should move the current master to the 3.x branch, then upgrade and reconfigure master.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/opendevise/middleman-asciidoc-example/issues/1#issuecomment-239109911, or mute the thread https://github.com/notifications/unsubscribe-auth/AA6J2XxVmEUdVqrxt2PLHyNYbopy6oJmks5qeueagaJpZM4JhxmT .
Sent from Mobile.
Finally done, at long last. We were waiting on the release of the AsciiDoc extension, but that happened a long time ago.
This is pointing to 3.x gems still. It would be great to spin this up with MM4 so folks could see middleman-asciidoc working with the latest and greatest.