+1 for amq5 docs part gitbook is really clean and tidy.
Sent from my iPhone > On 7 Dec 2017, at 16:50, Clebert Suconic <[email protected]> wrote: > > What about this.. there's a lot of stuff that's doc... > > > What if we made docs for AMQ5 instead of converting to another > format.. it's the same work regardless.. and Markdown for docs it's > easier. > >> On Thu, Dec 7, 2017 at 11:39 AM, Bruce Snyder <[email protected]> wrote: >> I have poked through some of the exported HTML pages from Confluence and >> there is so much cruft in there. E.g., large amounts of content wrapped in >> tables -- blech! I've also experimented with the text2html Python script >> and it does not convert these HTML files to Markdown very well, even if I >> skip tables. If we were to resort to hacking the HTML by hand to convert to >> Markdown, this is a *tremendous* amount of work. I grabbed the HTML, got >> rid of the duplicates that I saw and I still have 1600+ files. >> >> Bruce >> >>> On Thu, Dec 7, 2017 at 9:26 AM, Matt Pavlovich <[email protected]> wrote: >>> >>> If we can settle on a target format, I'd be up for dedicating time for a >>> hack-a-thon to just blaze through it. While painful, I believe we could get >>> it done quickly. >>> >>> >>> >>>> On 12/6/17 10:20 PM, Bruce Snyder wrote: >>>> >>>> Several opinions have been expressed recently that the ActiveMQ website >>>> needs some attention and that Artemis should be made more prominent. I'd >>>> like to discuss some ideas to see what we could achieve on this topic. >>>> >>>> If we are going to make Artemis more prominent, the first concern I >>>> identified is that the ActiveMQ website and the Artemis website are >>>> authored differently. The ActiveMQ website is authored in the Confluence >>>> wiki and exported to HTML automagically whereas the Artemis website is >>>> authored in raw HTML. As a result, the two sites have a very different >>>> look >>>> and feel to them. This presents some challenges to using the content >>>> between the two. >>>> >>>> But this presents other questions -- do we want the two sites to look >>>> similar or different? When someone looks at Artemis content, do we want >>>> the >>>> user to immediately know that they are looking at ActiveMQ content vs. >>>> Artemis based content solely due to the look and feel of the site? Should >>>> there even be two different sites? >>>> >>>> I would prefer to have the site authored in a language that is easier to >>>> write than HTML (such as Markdown). I would also like the files comprising >>>> the site to live in a git repo. To give the site a modern look and feel >>>> means using CSS (e.g., SASS, etc.). All these things can be achieved using >>>> Jekyll, but first we would need to convert the raw HTML files to Mardown >>>> to >>>> put in git. I have experimented with some tools to convert HTML to >>>> Markdown >>>> and they are less than ideal. Does anyone have any experience with this? >>>> >>>> Sorry for the rambling. Anyone else interested to help tackle this thorny >>>> set of issues? >>>> >>>> Bruce >>>> >>>> >>> >> >> >> -- >> perl -e 'print >> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' >> >> ActiveMQ in Action: http://bit.ly/2je6cQ >> Blog: http://bsnyder.org/ <http://bruceblog.org/> >> Twitter: http://twitter.com/brucesnyder > > > > -- > Clebert Suconic
