I agree, gitbook or similar would be a great way to manage the docs for 5.x.
@Bruce any luck with the extract of the current bits so can play around ? Sent from my iPhone > On 12 Dec 2017, at 16:19, Clebert Suconic <[email protected]> wrote: > > I wanted to emphasize an idea I spoke here: > > > Instead of converting the AMQ5 docs back into website format.. I think > it would be great to have the docs into a MD format so it would be > just a like a documentation format. gitbook convertible. > > > is there a requirement to keep the docs as website? we could think > differently here, right? > > > > >> On Fri, Dec 8, 2017 at 11:26 AM, Martyn Taylor <[email protected]> wrote: >> Yes. I had been chatting with Michael for a while about website updates. >> We had a bit of back and forth with this design. Code is always a good >> place to start. Cheers. >> >>> On Fri, Dec 8, 2017 at 2:16 PM, Bruce Snyder <[email protected]> wrote: >>> >>> I agree with the idea of making the site the landing page for all the >>> sub-projects within the overall ActiveMQ project. >>> >>> You should take a look at the message from Michael Andre Pearce to see his >>> mockup using the new logo, it's an excellent starting point for a >>> discussion. Be sure to follow the instructions in the BUILD.md: >>> >>> https://github.com/michaelandrepearce/activemq- >>> site/blob/master/site/BUILD.md >>> >>> Bruce >>> >>>> On Fri, Dec 8, 2017 at 3:48 AM, Martyn Taylor <[email protected]> wrote: >>>> >>>> Some ideas to kick off design discussion. >>>> >>>> Really what I am trying to convey here is that ActiveMQ is the home of a >>>> more than just 5.x series. And to have clear links to each project, >>>> clicking through would take you to landing page for the project. This >>>> essentially would be the landing page for top level ActiveMQ. >>>> >>>> I realise the text in the message needs more work (it's also probably >>>> worth having a bit of info for each project on the landing page too). >>>> >>>> On Fri, Dec 8, 2017 at 1:23 AM, Bruce Snyder <[email protected]> >>>> wrote: >>>> >>>>> This looks great, Michael. It's also a great proof-of-concept, nice >>> work. >>>>> I >>>>> like the look of it, but I don't think we want to completely copy the >>>>> Metron site, so we will need to change it up. >>>>> >>>>> I'm working on getting the exported HTML from the ActiveMQ Confluence >>>>> space >>>>> and I will dump it into a new git repo. >>>>> >>>>> Bruce >>>>> >>>>> On Thu, Dec 7, 2017 at 9:55 AM, Michael André Pearce < >>>>> [email protected]> wrote: >>>>> >>>>>> Agree on jekyll. >>>>>> >>>>>> Here’s a sample I’ve mocked up with an activemq look and feel (and >>> much >>>>>> lighter) based around the new logo >>>>>> >>>>>> https://github.com/michaelandrepearce/activemq-site/tree/master/site >>>>>> >>>>>> I forked from metrons to get most of the bits like Jekyll etc which is >>>>>> already working. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 7 Dec 2017, at 16:49, Bruce Snyder <[email protected]> >>> wrote: >>>>>>> >>>>>>> I would prefer to use Markdown with the Jekyll framework ( >>>>>>> https://jekyllrb.com/). Jekyll handles Markdown, it handles CSS >>> (via >>>>>> SASS) >>>>>>> and it would allow the site to live in a git repo. >>>>>>> >>>>>>> Also, I found that other projects use Jekyll with great success, >>> here >>>>> is >>>>>>> just one example in the Flink project: >>>>>>> >>>>>>> https://flink.apache.org/ >>>>>>> >>>>>>> Nice looking site, clearly more modern and fully customizable. >>>>>>> >>>>>>> Bruce >>>>>>> >>>>>>> On Thu, Dec 7, 2017 at 9:42 AM, Clebert Suconic < >>>>>> [email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> I like the Markdown (or whatever easy format.. non xml based). We >>>>> will >>>>>>>> need to choose a framework for that. do you have anything in mind? >>>>>>>> >>>>>>>> I also think we should have a consistent look and feel. >>>>>>>> >>>>>>>> >>>>>>>> I will be supportive on this... >>>>>>>> >>>>>>>> >>>>>>>> First thing will be to have a framework chosen.. >>>>>>>> Second to have a github we collaborate... >>>>>>>> Third.. maybe we could use one of those video calls to talk about >>>>> how to >>>>>>>> do it. >>>>>>>> >>>>>>>> On Wed, Dec 6, 2017 at 11:20 PM, Bruce Snyder < >>>>> [email protected]> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> >>>> >>>> >>> >>> >>> -- >>> 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
