You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Bruce Snyder <br...@gmail.com> on 2017/12/07 04:20:50 UTC

Thoughts on refactoring the ActiveMQ website

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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
I'm not opposed to doing a call, but let's try to work further via email
before we take this route. I can dump what I have into a git repo as a
sandbox and we can start to play around with it.

Bruce

On Thu, Dec 7, 2017 at 9:49 AM, Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> +1 on Matt’s idea, maybe we get a base website design and some sample
> pages migrated, and agreed on with this group first.
>
> Is it worth maybe having a virtual meetup to discuss the design etc (maybe
> some form of webex or Skype call?) to try work to some sample? What time
> zone Matt and Bruce are you in?
>
> then we could do his hackathon idea to get through the cruft manually,
> 1600+ some of that must be out dated or irrelevant.
>
>
>
>
>
>
>
>
>
>
>
> Sent from my iPhone
>
> > On 7 Dec 2017, at 16:39, Bruce Snyder <br...@gmail.com> 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 <ma...@gmail.com>
> 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
>



-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
+1 on Matt’s idea, maybe we get a base website design and some sample pages migrated, and agreed on with this group first.

Is it worth maybe having a virtual meetup to discuss the design etc (maybe some form of webex or Skype call?) to try work to some sample? What time zone Matt and Bruce are you in? 

then we could do his hackathon idea to get through the cruft manually, 1600+ some of that must be out dated or irrelevant.











Sent from my iPhone

> On 7 Dec 2017, at 16:39, Bruce Snyder <br...@gmail.com> 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 <ma...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
Bruce, could you take what you have and put it up somewhere, perhaps in Git
so we can take a look?  Cheers.

On Thu, Dec 7, 2017 at 4:39 PM, Bruce Snyder <br...@gmail.com> 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 <ma...@gmail.com> 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Matt Pavlovich <ma...@gmail.com>.
Yep.. its going to be painful. Thanks for digging into it and having 
numbers.

I still think putting smart-eyes on it (with a plan on where it should 
go) is the best for the long run. One big painful push and then be in a 
happy place going forward... hopefully..  ;-)



On 12/7/17 10:39 AM, Bruce Snyder 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 <ma...@gmail.com> 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
>>>
>>>
>


Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
+1 for amq5 docs part gitbook is really clean and tidy.




Sent from my iPhone

> On 7 Dec 2017, at 16:50, Clebert Suconic <cl...@gmail.com> 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 <br...@gmail.com> 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 <ma...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Clebert Suconic <cl...@gmail.com>.
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 <br...@gmail.com> 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 <ma...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
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 <ma...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Matt Pavlovich <ma...@gmail.com>.
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
>


Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
Hi Bruce,

As per the other mail thread, I'd like to put my hand up to this effort.

I agree with comments around the site needing to live in GitHub so a more PR style and contribution approach can be had.

Likewise +1 re markdown (or similar) , there will need to be some HTML obviously but large amounts of content should be in a markdown or simple editorial form.

My personal feelings (but not strongly opinionated) it should be a single site but separate clear sections for:

ActiveMQ 5.x (I think during the big discussion on the vote someone called it "Classic" I quite liked that nice way to call it)
ActiveMQ Artemis
CMS
NMS.

I think the site needs to reflect the new logo (colours and style) and it be great to have its designer on board   (looks at Martyn Taylor)

Is it maybe worth setting up a GitHub repo with the current content exported from confluence, even if it's in html for now, that way either we can find a tool to convert it or at least we can share the manual burden of handling it.

Cheers
Mike

Sent from my iPad

> On 7 Dec 2017, at 04:20, Bruce Snyder <br...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Thanks for pointing this out, Dan. I was about to try PanDoc last night but
ran out of time. I will spend some time trying out PanDoc today. I will
also get the raw HTML exported from Confluence into an ASF git repo for all
to see.

Bruce

On Thu, Dec 7, 2017 at 9:59 AM, Daniel Kulp <dk...@apache.org> wrote:

> There are some things available to convert the confluence xhtml to
> markdown:
>
> Example:
> https://www.npmjs.com/package/confluence-to-github-markdown
>
>
> I’m not sure how good of a job they do, but it might be better than
> nothing.
>
> Dan
>
>
>
> > On Dec 7, 2017, at 11:50 AM, Bruce Snyder <br...@gmail.com>
> wrote:
> >
> > That's the big hurdle I have identified, the initial conversion to
> > Markdown. Perhaps a manual hackathon is the best way.
> >
> > Bruce
> >
> > On Thu, Dec 7, 2017 at 9:48 AM, Christopher Shannon <
> > christopher.l.shannon@gmail.com> wrote:
> >
> >> I agree that Markdown would be a good idea if we can figure out a good
> way
> >> to convert it.
> >>
> >> On Thu, Dec 7, 2017 at 11:42 AM, Clebert Suconic <
> >> clebert.suconic@gmail.com>
> >> 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 <br...@gmail.com>
> >>> 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
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>


-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Daniel Kulp <dk...@apache.org>.
There are some things available to convert the confluence xhtml to markdown:

Example:
https://www.npmjs.com/package/confluence-to-github-markdown


I’m not sure how good of a job they do, but it might be better than nothing.

Dan



> On Dec 7, 2017, at 11:50 AM, Bruce Snyder <br...@gmail.com> wrote:
> 
> That's the big hurdle I have identified, the initial conversion to
> Markdown. Perhaps a manual hackathon is the best way.
> 
> Bruce
> 
> On Thu, Dec 7, 2017 at 9:48 AM, Christopher Shannon <
> christopher.l.shannon@gmail.com> wrote:
> 
>> I agree that Markdown would be a good idea if we can figure out a good way
>> to convert it.
>> 
>> On Thu, Dec 7, 2017 at 11:42 AM, Clebert Suconic <
>> clebert.suconic@gmail.com>
>> 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 <br...@gmail.com>
>>> 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

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
That's the big hurdle I have identified, the initial conversion to
Markdown. Perhaps a manual hackathon is the best way.

Bruce

On Thu, Dec 7, 2017 at 9:48 AM, Christopher Shannon <
christopher.l.shannon@gmail.com> wrote:

> I agree that Markdown would be a good idea if we can figure out a good way
> to convert it.
>
> On Thu, Dec 7, 2017 at 11:42 AM, Clebert Suconic <
> clebert.suconic@gmail.com>
> 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 <br...@gmail.com>
> > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Christopher Shannon <ch...@gmail.com>.
I agree that Markdown would be a good idea if we can figure out a good way
to convert it.

On Thu, Dec 7, 2017 at 11:42 AM, Clebert Suconic <cl...@gmail.com>
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 <br...@gmail.com>
> 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Arthur Naseef <ar...@amlinv.com>.
Yes, I understand. 

Hope my feedback is constructive.  If there are specifics on which feedback would by more helpful, please don’t hesitate to let me know. 

FYI - just saying the following in an attempt to clarify my point-of-view, not critizing...  the goals of this effort are vague for me. All I can think of is to “modernize” the site - whatever that really means. 

Art

Sent from my iPhone

> On Mar 29, 2018, at 8:23 PM, Bruce Snyder <br...@gmail.com> wrote:
> 
> Did you read what I said in my email?
> 
>> Everyone should take a look at the gitbook that Mike put together. It's a
> great first example.
> 
> Nothing is complete. He is giving us an early preview.
> 
> Bruce
> 
>> On Thu, Mar 22, 2018 at 11:28 AM, Arthur Naseef <ar...@amlinv.com> wrote:
>> 
>> I pulled down Michael's git repo and browsed it.  Here are my initial
>> impressions:
>> 
>> The Good
>> * The look-and-feel is a little cleaner than the existing site
>> * I see a lot of promise with this new layout.
>> 
>> The Bad
>> * While I believe it is expected at this point, I feel it needs to be said
>> -- a lot of formatting is lacking
>> * Over time, for ongoing users, I believe the technical reference pages
>> (e.g. the failover transport page) are most useful; the lack of formatting
>> there makes them hard to consume
>> * It is hard to find several pages - although I suspect not much harder
>> than the current site, except that google finds the pages quickly (e.g.
>> searching on "failover activemq" brings up this link right away - for me at
>> least - http://activemq.apache.org/failover-transport-reference.html)
>> 
>> So overall, I would say it currently looks like a good, early start at the
>> effort.  Nothing showing up that is an obvious concern to the effort.
>> 
>> With that said, it would greatly help to have a small representative set of
>> pages that get closer to a final state in order to respond to that.  For
>> example, once the failover transport reference is formatted, then it will
>> be easier to gauge how easy it is to find important information on that
>> page.
>> 
>> Art
>> 
>> 
>>> On Fri, Mar 16, 2018 at 2:52 AM, Martyn Taylor <mt...@redhat.com> wrote:
>>> 
>>> Bruce, All
>>> 
>>> We organised a webex discussion on the dev list[1] where we discussed
>>> Michael's proposal and created a bunch of JIRA[2] that we think are
>> needed
>>> in order to move forward with the proposal.  Unfortunately only a handful
>>> of people attended.  There is concern that a lot of work will be put into
>>> building a new site based on Michael's proposal only for it to get -1 at
>>> the last minute.  For this reason, can I suggest that people take some
>> time
>>> to look into what has been done already by checking out the git repo as
>>> Bruce suggested, or we schedule another webex session where Michael can
>>> talk about his proposal.  We can then take a vote as to whether or not
>> this
>>> is an approach we want to move forward with and what the requirements are
>>> to go live.
>>> 
>>> Thanks
>>> 
>>> [1] http://activemq.2283324.n4.nabble.com/Website-Discussion-
>>> td4737173.html
>>> [2] https://issues.apache.org/jira/browse/AMQ-6912
>>> 
>>> 
>>> 
>>> On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>> 
>>>> Everyone should take a look at the gitbook that Mike put together.
>> It's a
>>>> great first example.
>>>> 
>>>> https://github.com/apache/activemq-web/pull/3
>>>> 
>>>> Please take 10 minutes to clone the repo, switch to the branch, install
>>>> gitbook, run gitbook and peruse the docs.
>>>> 
>>>> Bruce
>>>> 
>>>> On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
>>>> wrote:
>>>> 
>>>>> I'm sorry about the long delays in getting the official export from
>>>>> Confluence, but it took this long to get some resolution on the
>> issue.
>>>>> 
>>>>> I now have a full HTML export from Confluence with the exception of
>> the
>>>>> Navigation page. You can grab the zip file of the HTML at the
>> following
>>>> URL:
>>>>> 
>>>>> https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
>>>>> oDtZxt8mFZlX/view?usp=sharing
>>>>> 
>>>>> Bruce
>>>>> 
>>>>> On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <
>> bruce.snyder@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> +1
>>>>>> 
>>>>>> Bruce
>>>>>> 
>>>>>> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
>>>>>> michael.andre.pearce@me.com> wrote:
>>>>>> 
>>>>>>> Hi All,
>>>>>>> 
>>>>>>> It’s been a bit quiet on the front of this effort.
>>>>>>> 
>>>>>>> I’d like to bump this a bit to get some feedback on the current
>>>>>>> examples, and try agree a plan going forwards and spread the work.
>>>>>>> 
>>>>>>> I was speaking with Martyn the other week and we think maybe a
>> brief
>>>>>>> webex to demo what’s been done so far and then discuss.
>>>>>>> Martyn’s offered he can host this using his bluejeans account
>>> (thanks)
>>>>>>> 
>>>>>>> We are thinking of organising this for the week of 19th Feb.
>>>>>>> 
>>>>>>> Any specific people who want to be involved can or cannot make? If
>>> not
>>>>>>> I’ll sync up with Martyn to agree and then post a time and date.
>>>>>>> 
>>>>>>> Cheers
>>>>>>> Mike
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> Sent from my iPhone
>>>>>>> 
>>>>>>>> On 20 Dec 2017, at 01:26, Michael André Pearce <
>>>>>>> michael.andre.pearce@me.com> wrote:
>>>>>>>> 
>>>>>>>> Just FYI have sent a PR with a link to my branch of this export
>> now
>>>> in
>>>>>>> a GitBook form still needs a lot of TLC but have tried to get a
>> large
>>>> bulk
>>>>>>> done. To provide some skeleton for 5.x documents.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Sent from my iPhone
>>>>>>>> 
>>>>>>>>> On 18 Dec 2017, at 20:26, Michael André Pearce <
>>>>>>> michael.andre.pearce@me.com> wrote:
>>>>>>>>> 
>>>>>>>>> Yeah, unfortunately the tool i found wanted just html it blew up
>>>> when
>>>>>>> trying to use modified.
>>>>>>>>> 
>>>>>>>>> Like wise there was a couple of pages it couldn’t convert due
>> to a
>>>>>>> css file on import issue but this wasn’t that many.
>>>>>>>>> 
>>>>>>>>> Sent from my iPhone
>>>>>>>>> 
>>>>>>>>>> On 18 Dec 2017, at 19:15, Bruce Snyder <bruce.snyder@gmail.com
>>> 
>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Nice job, based on my spot check of a handful of files, it
>> looks
>>>> much
>>>>>>>>>> better. But we will still need to manually fix all the valid
>>>> tables.
>>>>>>>>>> 
>>>>>>>>>> Have you had a chance to look at the other branches that Dan
>> Kulp
>>>>>>> provided?
>>>>>>>>>> 
>>>>>>>>>> Bruce
>>>>>>>>>> 
>>>>>>>>>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>>>>>>>>>> michael.andre.pearce@me.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> I’ve had some luck auto generating MD files.
>>>>>>>>>>> 
>>>>>>>>>>> Needs some cleanup which probably the worst can be bash
>>> scripted.
>>>>>>>>>>> 
>>>>>>>>>>> Have sent a PR back to the activemq-web on github for others
>> to
>>>> see.
>>>>>>>>>>> 
>>>>>>>>>>> Mike
>>>>>>>>>>> 
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>> 
>>>>>>>>>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <
>> bruce.snyder@gmail.com
>>>> 
>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Thanks, Dan. So far I only see the body.storage branch (the
>>>> others
>>>>>>> should
>>>>>>>>>>>> propagate in time). But I see that it's already more
>>>> comprehensive
>>>>>>> than
>>>>>>>>>>> the
>>>>>>>>>>>> HTML that I pushed because it contains all the directories.
>> We
>>>>>>> should
>>>>>>>>>>>> probably wipe out the master branch and choose one of yours
>> as
>>>> the
>>>>>>> new
>>>>>>>>>>>> master branch.
>>>>>>>>>>>> 
>>>>>>>>>>>> Bruce
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <
>>> dkulp@apache.org>
>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I hacked the Confluence exporter a bit to grab the page
>>> content
>>>> in
>>>>>>>>>>>>> different formats so we can see if one is easier to migrate
>> or
>>>>>>>>>>> similar.   I
>>>>>>>>>>>>> just pushed 3 new branches to this repo:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> body.only - this is basically the same HTML, but with all
>> the
>>>>>>> “wrapper”
>>>>>>>>>>>>> stuff removed.   Just the HTML of the body content.   So no
>>>>>>> navigation
>>>>>>>>>>> or
>>>>>>>>>>>>> header/footer, etc…
>>>>>>>>>>>>> 
>>>>>>>>>>>>> body.storage - this is the raw storage format of the data
>> from
>>>>>>>>>>>>> confluence.   Things like code snippets are in storage
>> format
>>>>>>>>>>>>> (<structured-macro name=“code” …>), etc.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> body.view - confluence has a “body.view” mode that is
>> between
>>>> the
>>>>>>>>>>>>> “storage” format and not really the exported HTML.     The
>>>>>>> structured
>>>>>>>>>>>>> macros are expanded a bit (<script class=“brush: java”…),
>> but
>>>> not
>>>>>>>>>>> really in
>>>>>>>>>>>>> final HTML form either.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Anyway, if interested in converting content, one of the
>> above
>>>>>>> might be a
>>>>>>>>>>>>> better starting point.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Dan
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
>>>>>>> bruce.snyder@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> The HTML is available in the repo now. This HTML is just
>>> what I
>>>>>>> grabbed
>>>>>>>>>>>>>> from the public directory. Even if it's not comprehensive,
>>> it's
>>>>>>> good
>>>>>>>>>>>>> enough
>>>>>>>>>>>>>> for hacking around to figure out what we'd like to do.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> In the meantime, I'm still working with ASF Infra to figure
>>> out
>>>>>>> why the
>>>>>>>>>>>>>> Confluence export is failing.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
>>>>>>> bruce.snyder@gmail.com
>>>>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Yep, that is correct, Dan:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I pushed my changes to the repo. Now they just need to
>>>>>>> propagate to
>>>>>>>>>>> the
>>>>>>>>>>>>>>> Github web UI.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
>>>>>>> dkulp@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Isn’t the push address supposed to be:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Dan
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
>>>>>>> bruce.snyder@gmail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Thank you for the suggestion, but it looks like I do not
>>>> have
>>>>>>>>>>>>>>>> permissions
>>>>>>>>>>>>>>>>> either. I will contact ASF Infra for assistance.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
>>>>>>> mtaylor@redhat.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>>>>>>>>>>>>> bruce.snyder@gmail.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I had the following empty git repo created to hold the
>>>> HTML
>>>>>>> from
>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> current website:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> https://github.com/apache/activemq-web
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> However, I have a conundrum -- content cannot be
>> pushed
>>>>>>> directly
>>>>>>>>>>> to
>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>>>> Github ASF repo. Content can only be added via pull
>>>> request
>>>>>>> but
>>>>>>>>>>>>> Github
>>>>>>>>>>>>>>>>>> does
>>>>>>>>>>>>>>>>>>> not allow a pull request on an empty repo.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
>>>> i.e.
>>>>>>>>>>> git://
>>>>>>>>>>>>>>>>>> git.apache.org/activemq-web.git
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> This is the workflow we currently use, we push directly
>>> to
>>>>>>> the ASF
>>>>>>>>>>>>>>>> repo.
>>>>>>>>>>>>>>>>>> PRs are really only used for review and discussion.  I
>>>> tried
>>>>>>> to
>>>>>>>>>>> push
>>>>>>>>>>>>>>>>>> directly this morning but looks like I don't have write
>>>>>>>>>>> permissions.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I
>> guess
>>> I
>>>>>>> could
>>>>>>>>>>> ask
>>>>>>>>>>>>>>>> ASF
>>>>>>>>>>>>>>>>>>> Infra to push it.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>>>>>>>>>>>>> bruce.snyder@gmail.com
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> I'm going to address all the questions to me in this
>>>> single
>>>>>>>>>>> reply.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> My original suggestion was that we export the HTML
>> from
>>>>>>>>>>> Confluence,
>>>>>>>>>>>>>>>>>>>> convert to Markdown and put the Markdown and the
>> images
>>>> in
>>>>>>> a git
>>>>>>>>>>>>>>>> repo.
>>>>>>>>>>>>>>>>>>>> Markdown is much easier to edit than raw HTML,
>>> especially
>>>>>>> the
>>>>>>>>>>> HTML
>>>>>>>>>>>>>>>>>>> exported
>>>>>>>>>>>>>>>>>>>> from Confluence (blech!). The idea was that we could
>>> use
>>>>>>> Jekyll +
>>>>>>>>>>>>>>>> SAAS
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
>>>>>>> produced a
>>>>>>>>>>>>> mockup
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>> this using the Apache Metro website as an example
>>>> (because
>>>>>>> it
>>>>>>>>>>>>> already
>>>>>>>>>>>>>>>>>>> makes
>>>>>>>>>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me
>>> that
>>>> we
>>>>>>>>>>> should
>>>>>>>>>>>>>>>> take
>>>>>>>>>>>>>>>>>>>> this path, so I started looking into doing a full,
>> new
>>>>>>> export of
>>>>>>>>>>>>>>>>>>> Confluence
>>>>>>>>>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup,
>>> you
>>>>>>> should
>>>>>>>>>>>>>>>> really
>>>>>>>>>>>>>>>>>>>> take a look.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> So, I manually grabbed the raw HTML that is
>>> automagically
>>>>>>>>>>> exported
>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>> Confluence and is hosting the current site that we
>> see
>>> at
>>>>>>>>>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
>>>> using
>>>>>>>>>>>>> text2html
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>> the conversion it does is pretty awful and would
>>> require
>>>> a
>>>>>>> lot of
>>>>>>>>>>>>>>>> hand
>>>>>>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>>>>>>> to fix it. So, we discussed the point that there are
>>>> 1600+
>>>>>>> pages
>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> HTML
>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> manually edit. But I later realized that it was only
>>>> about
>>>>>>> 950
>>>>>>>>>>> HTML
>>>>>>>>>>>>>>>>>> pages
>>>>>>>>>>>>>>>>>>>> (from what I can tell so far).
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
>>>>>>> converter
>>>>>>>>>>> built
>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>> top
>>>>>>>>>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the
>>> HTML
>>>>>>> from
>>>>>>>>>>>>>>>>>> Confluence
>>>>>>>>>>>>>>>>>>>> in order to try out the PanDoc converter (it works
>>> based
>>>>>>> on the
>>>>>>>>>>>>>>>>>>> Confluence
>>>>>>>>>>>>>>>>>>>> export function which is different from how the HTML
>> is
>>>>>>>>>>>>> automagically
>>>>>>>>>>>>>>>>>>>> converted). Unfortunately, I am running into a
>>>>>>>>>>> NullPointerException
>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is
>> due
>>>> to
>>>>>>> the
>>>>>>>>>>>>> CDATA
>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> search function on the Navigation page and is
>>> suggesting
>>>>>>> that the
>>>>>>>>>>>>>>>>>>> solution
>>>>>>>>>>>>>>>>>>>> is to remove the Navigation page. The problem with
>> this
>>>>>>>>>>> suggestion
>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>> it would fundamentally remove all the navigation on
>> the
>>>>>>>>>>> right-hand
>>>>>>>>>>>>>>>> side
>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>> the site -- not what we want.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> I have also given some thought to the idea that
>>> removing
>>>>>>> the
>>>>>>>>>>>>> current
>>>>>>>>>>>>>>>>>> site
>>>>>>>>>>>>>>>>>>>> will break all links to old site. This is something
>>> that
>>>>>>> cannot
>>>>>>>>>>> be
>>>>>>>>>>>>>>>>>>>> overlooked and must be prevented as we do not want to
>>>>>>> leave users
>>>>>>>>>>>>> who
>>>>>>>>>>>>>>>>>>> have
>>>>>>>>>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
>>>>>>> problem to
>>>>>>>>>>>>>>>> solve
>>>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
>>>> Infra
>>>>>>> is
>>>>>>>>>>>>> willing
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> allow us to deploy such custom rules. This should be
>>>>>>> investigated
>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>>>>>> get to that point, but we are not there yet. First,
>> we
>>>>>>> need to
>>>>>>>>>>>>> decide
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> best path forward based on what I have described
>> above
>>> in
>>>>>>> the
>>>>>>>>>>>>>>>> preceding
>>>>>>>>>>>>>>>>>>>> paragraphs.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>>>>>>>>>>>>> mtaylor@redhat.com>
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> I was thinking there would be a single css file for
>>> all
>>>>>>> the
>>>>>>>>>>> pages.
>>>>>>>>>>>>>>>>>> But
>>>>>>>>>>>>>>>>>>> I
>>>>>>>>>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
>>>> when
>>>>>>> Bruce
>>>>>>>>>>>>>>>> pushes
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> export.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>>>>>>>>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I agree it will be easier to covert to md than to
>>> start
>>>>>>> doing
>>>>>>>>>>> css
>>>>>>>>>>>>>>>>>>>>> styles.
>>>>>>>>>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that
>> far
>>>>>>> off.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not
>>> all
>>>>>>> just to
>>>>>>>>>>>>> try
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>> see what it is like.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>>>>>>>>>>>>>>> clebert.suconic@gmail.com>
>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems
>> like a
>>>> big
>>>>>>>>>>> task, I
>>>>>>>>>>>>>>>>>>>>> suspect
>>>>>>>>>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
>>>>>>> issues.
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> At least initially, how about we just create a
>> nice
>>>>>>> landing
>>>>>>>>>>>>> page
>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site
>> together,
>>>> and
>>>>>>>>>>>>>>>>>>> refresh/align
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
>>>>>>> thought that
>>>>>>>>>>>>>>>>>>>>>>> converting these pages into a doc would be easier
>>> than
>>>>>>>>>>>>> converting
>>>>>>>>>>>>>>>>>>> them
>>>>>>>>>>>>>>>>>>>>>>> to another .css...
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
>>>>>>> thought .md
>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Daniel Kulp
>>>>>>>>>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>>>>>>>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Daniel Kulp
>>>>>>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>>>>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> 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
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Did you read what I said in my email?

> Everyone should take a look at the gitbook that Mike put together. It's a
great first example.

Nothing is complete. He is giving us an early preview.

Bruce

On Thu, Mar 22, 2018 at 11:28 AM, Arthur Naseef <ar...@amlinv.com> wrote:

> I pulled down Michael's git repo and browsed it.  Here are my initial
> impressions:
>
> The Good
> * The look-and-feel is a little cleaner than the existing site
> * I see a lot of promise with this new layout.
>
> The Bad
> * While I believe it is expected at this point, I feel it needs to be said
> -- a lot of formatting is lacking
> * Over time, for ongoing users, I believe the technical reference pages
> (e.g. the failover transport page) are most useful; the lack of formatting
> there makes them hard to consume
> * It is hard to find several pages - although I suspect not much harder
> than the current site, except that google finds the pages quickly (e.g.
> searching on "failover activemq" brings up this link right away - for me at
> least - http://activemq.apache.org/failover-transport-reference.html)
>
> So overall, I would say it currently looks like a good, early start at the
> effort.  Nothing showing up that is an obvious concern to the effort.
>
> With that said, it would greatly help to have a small representative set of
> pages that get closer to a final state in order to respond to that.  For
> example, once the failover transport reference is formatted, then it will
> be easier to gauge how easy it is to find important information on that
> page.
>
> Art
>
>
> On Fri, Mar 16, 2018 at 2:52 AM, Martyn Taylor <mt...@redhat.com> wrote:
>
> > Bruce, All
> >
> > We organised a webex discussion on the dev list[1] where we discussed
> > Michael's proposal and created a bunch of JIRA[2] that we think are
> needed
> > in order to move forward with the proposal.  Unfortunately only a handful
> > of people attended.  There is concern that a lot of work will be put into
> > building a new site based on Michael's proposal only for it to get -1 at
> > the last minute.  For this reason, can I suggest that people take some
> time
> > to look into what has been done already by checking out the git repo as
> > Bruce suggested, or we schedule another webex session where Michael can
> > talk about his proposal.  We can then take a vote as to whether or not
> this
> > is an approach we want to move forward with and what the requirements are
> > to go live.
> >
> > Thanks
> >
> > [1] http://activemq.2283324.n4.nabble.com/Website-Discussion-
> > td4737173.html
> > [2] https://issues.apache.org/jira/browse/AMQ-6912
> >
> >
> >
> > On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> > > Everyone should take a look at the gitbook that Mike put together.
> It's a
> > > great first example.
> > >
> > > https://github.com/apache/activemq-web/pull/3
> > >
> > > Please take 10 minutes to clone the repo, switch to the branch, install
> > > gitbook, run gitbook and peruse the docs.
> > >
> > > Bruce
> > >
> > > On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
> > > wrote:
> > >
> > > > I'm sorry about the long delays in getting the official export from
> > > > Confluence, but it took this long to get some resolution on the
> issue.
> > > >
> > > > I now have a full HTML export from Confluence with the exception of
> the
> > > > Navigation page. You can grab the zip file of the HTML at the
> following
> > > URL:
> > > >
> > > > https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
> > > > oDtZxt8mFZlX/view?usp=sharing
> > > >
> > > > Bruce
> > > >
> > > > On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <
> bruce.snyder@gmail.com>
> > > > wrote:
> > > >
> > > >> +1
> > > >>
> > > >> Bruce
> > > >>
> > > >> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
> > > >> michael.andre.pearce@me.com> wrote:
> > > >>
> > > >>> Hi All,
> > > >>>
> > > >>> It’s been a bit quiet on the front of this effort.
> > > >>>
> > > >>> I’d like to bump this a bit to get some feedback on the current
> > > >>> examples, and try agree a plan going forwards and spread the work.
> > > >>>
> > > >>> I was speaking with Martyn the other week and we think maybe a
> brief
> > > >>> webex to demo what’s been done so far and then discuss.
> > > >>> Martyn’s offered he can host this using his bluejeans account
> > (thanks)
> > > >>>
> > > >>> We are thinking of organising this for the week of 19th Feb.
> > > >>>
> > > >>> Any specific people who want to be involved can or cannot make? If
> > not
> > > >>> I’ll sync up with Martyn to agree and then post a time and date.
> > > >>>
> > > >>> Cheers
> > > >>> Mike
> > > >>>
> > > >>>
> > > >>>
> > > >>> Sent from my iPhone
> > > >>>
> > > >>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
> > > >>> michael.andre.pearce@me.com> wrote:
> > > >>> >
> > > >>> > Just FYI have sent a PR with a link to my branch of this export
> now
> > > in
> > > >>> a GitBook form still needs a lot of TLC but have tried to get a
> large
> > > bulk
> > > >>> done. To provide some skeleton for 5.x documents.
> > > >>> >
> > > >>> >
> > > >>> > Sent from my iPhone
> > > >>> >
> > > >>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
> > > >>> michael.andre.pearce@me.com> wrote:
> > > >>> >>
> > > >>> >> Yeah, unfortunately the tool i found wanted just html it blew up
> > > when
> > > >>> trying to use modified.
> > > >>> >>
> > > >>> >> Like wise there was a couple of pages it couldn’t convert due
> to a
> > > >>> css file on import issue but this wasn’t that many.
> > > >>> >>
> > > >>> >> Sent from my iPhone
> > > >>> >>
> > > >>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <bruce.snyder@gmail.com
> >
> > > >>> wrote:
> > > >>> >>>
> > > >>> >>> Nice job, based on my spot check of a handful of files, it
> looks
> > > much
> > > >>> >>> better. But we will still need to manually fix all the valid
> > > tables.
> > > >>> >>>
> > > >>> >>> Have you had a chance to look at the other branches that Dan
> Kulp
> > > >>> provided?
> > > >>> >>>
> > > >>> >>> Bruce
> > > >>> >>>
> > > >>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> > > >>> >>> michael.andre.pearce@me.com> wrote:
> > > >>> >>>
> > > >>> >>>> I’ve had some luck auto generating MD files.
> > > >>> >>>>
> > > >>> >>>> Needs some cleanup which probably the worst can be bash
> > scripted.
> > > >>> >>>>
> > > >>> >>>> Have sent a PR back to the activemq-web on github for others
> to
> > > see.
> > > >>> >>>>
> > > >>> >>>> Mike
> > > >>> >>>>
> > > >>> >>>> Sent from my iPhone
> > > >>> >>>>
> > > >>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <
> bruce.snyder@gmail.com
> > >
> > > >>> wrote:
> > > >>> >>>>>
> > > >>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the
> > > others
> > > >>> should
> > > >>> >>>>> propagate in time). But I see that it's already more
> > > comprehensive
> > > >>> than
> > > >>> >>>> the
> > > >>> >>>>> HTML that I pushed because it contains all the directories.
> We
> > > >>> should
> > > >>> >>>>> probably wipe out the master branch and choose one of yours
> as
> > > the
> > > >>> new
> > > >>> >>>>> master branch.
> > > >>> >>>>>
> > > >>> >>>>> Bruce
> > > >>> >>>>>
> > > >>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <
> > dkulp@apache.org>
> > > >>> wrote:
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>> I hacked the Confluence exporter a bit to grab the page
> > content
> > > in
> > > >>> >>>>>> different formats so we can see if one is easier to migrate
> or
> > > >>> >>>> similar.   I
> > > >>> >>>>>> just pushed 3 new branches to this repo:
> > > >>> >>>>>>
> > > >>> >>>>>> body.only - this is basically the same HTML, but with all
> the
> > > >>> “wrapper”
> > > >>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
> > > >>> navigation
> > > >>> >>>> or
> > > >>> >>>>>> header/footer, etc…
> > > >>> >>>>>>
> > > >>> >>>>>> body.storage - this is the raw storage format of the data
> from
> > > >>> >>>>>> confluence.   Things like code snippets are in storage
> format
> > > >>> >>>>>> (<structured-macro name=“code” …>), etc.
> > > >>> >>>>>>
> > > >>> >>>>>> body.view - confluence has a “body.view” mode that is
> between
> > > the
> > > >>> >>>>>> “storage” format and not really the exported HTML.     The
> > > >>> structured
> > > >>> >>>>>> macros are expanded a bit (<script class=“brush: java”…),
> but
> > > not
> > > >>> >>>> really in
> > > >>> >>>>>> final HTML form either.
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>> Anyway, if interested in converting content, one of the
> above
> > > >>> might be a
> > > >>> >>>>>> better starting point.
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>> Dan
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
> > > >>> bruce.snyder@gmail.com>
> > > >>> >>>>>> wrote:
> > > >>> >>>>>>>
> > > >>> >>>>>>> The HTML is available in the repo now. This HTML is just
> > what I
> > > >>> grabbed
> > > >>> >>>>>>> from the public directory. Even if it's not comprehensive,
> > it's
> > > >>> good
> > > >>> >>>>>> enough
> > > >>> >>>>>>> for hacking around to figure out what we'd like to do.
> > > >>> >>>>>>>
> > > >>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure
> > out
> > > >>> why the
> > > >>> >>>>>>> Confluence export is failing.
> > > >>> >>>>>>>
> > > >>> >>>>>>> Bruce
> > > >>> >>>>>>>
> > > >>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
> > > >>> bruce.snyder@gmail.com
> > > >>> >>>>>
> > > >>> >>>>>>> wrote:
> > > >>> >>>>>>>
> > > >>> >>>>>>>> Yep, that is correct, Dan:
> > > >>> >>>>>>>>
> > > >>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > > >>> >>>>>>>>
> > > >>> >>>>>>>> I pushed my changes to the repo. Now they just need to
> > > >>> propagate to
> > > >>> >>>> the
> > > >>> >>>>>>>> Github web UI.
> > > >>> >>>>>>>>
> > > >>> >>>>>>>> Bruce
> > > >>> >>>>>>>>
> > > >>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
> > > >>> dkulp@apache.org>
> > > >>> >>>> wrote:
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>> Isn’t the push address supposed to be:
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>> Dan
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
> > > >>> bruce.snyder@gmail.com>
> > > >>> >>>>>>>>> wrote:
> > > >>> >>>>>>>>>>
> > > >>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not
> > > have
> > > >>> >>>>>>>>> permissions
> > > >>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
> > > >>> >>>>>>>>>>
> > > >>> >>>>>>>>>> Bruce
> > > >>> >>>>>>>>>>
> > > >>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
> > > >>> mtaylor@redhat.com>
> > > >>> >>>>>>>>> wrote:
> > > >>> >>>>>>>>>>
> > > >>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> > > >>> >>>>>> bruce.snyder@gmail.com>
> > > >>> >>>>>>>>>>> wrote:
> > > >>> >>>>>>>>>>>
> > > >>> >>>>>>>>>>>> I had the following empty git repo created to hold the
> > > HTML
> > > >>> from
> > > >>> >>>> the
> > > >>> >>>>>>>>>>>> current website:
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>> https://github.com/apache/activemq-web
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be
> pushed
> > > >>> directly
> > > >>> >>>> to
> > > >>> >>>>>> a
> > > >>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull
> > > request
> > > >>> but
> > > >>> >>>>>> Github
> > > >>> >>>>>>>>>>> does
> > > >>> >>>>>>>>>>>> not allow a pull request on an empty repo.
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
> > > i.e.
> > > >>> >>>> git://
> > > >>> >>>>>>>>>>> git.apache.org/activemq-web.git
> > > >>> >>>>>>>>>>>
> > > >>> >>>>>>>>>>> This is the workflow we currently use, we push directly
> > to
> > > >>> the ASF
> > > >>> >>>>>>>>> repo.
> > > >>> >>>>>>>>>>> PRs are really only used for review and discussion.  I
> > > tried
> > > >>> to
> > > >>> >>>> push
> > > >>> >>>>>>>>>>> directly this morning but looks like I don't have write
> > > >>> >>>> permissions.
> > > >>> >>>>>>>>>>>
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I
> guess
> > I
> > > >>> could
> > > >>> >>>> ask
> > > >>> >>>>>>>>> ASF
> > > >>> >>>>>>>>>>>> Infra to push it.
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>> Bruce
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> > > >>> >>>>>> bruce.snyder@gmail.com
> > > >>> >>>>>>>>>>
> > > >>> >>>>>>>>>>>> wrote:
> > > >>> >>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> I'm going to address all the questions to me in this
> > > single
> > > >>> >>>> reply.
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> My original suggestion was that we export the HTML
> from
> > > >>> >>>> Confluence,
> > > >>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the
> images
> > > in
> > > >>> a git
> > > >>> >>>>>>>>> repo.
> > > >>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML,
> > especially
> > > >>> the
> > > >>> >>>> HTML
> > > >>> >>>>>>>>>>>> exported
> > > >>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could
> > use
> > > >>> Jekyll +
> > > >>> >>>>>>>>> SAAS
> > > >>> >>>>>>>>>>> to
> > > >>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
> > > >>> produced a
> > > >>> >>>>>> mockup
> > > >>> >>>>>>>>> of
> > > >>> >>>>>>>>>>>>> this using the Apache Metro website as an example
> > > (because
> > > >>> it
> > > >>> >>>>>> already
> > > >>> >>>>>>>>>>>> makes
> > > >>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me
> > that
> > > we
> > > >>> >>>> should
> > > >>> >>>>>>>>> take
> > > >>> >>>>>>>>>>>>> this path, so I started looking into doing a full,
> new
> > > >>> export of
> > > >>> >>>>>>>>>>>> Confluence
> > > >>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup,
> > you
> > > >>> should
> > > >>> >>>>>>>>> really
> > > >>> >>>>>>>>>>>>> take a look.
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is
> > automagically
> > > >>> >>>> exported
> > > >>> >>>>>>>>> from
> > > >>> >>>>>>>>>>>>> Confluence and is hosting the current site that we
> see
> > at
> > > >>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
> > > using
> > > >>> >>>>>> text2html
> > > >>> >>>>>>>>>>> and
> > > >>> >>>>>>>>>>>>> the conversion it does is pretty awful and would
> > require
> > > a
> > > >>> lot of
> > > >>> >>>>>>>>> hand
> > > >>> >>>>>>>>>>>> work
> > > >>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are
> > > 1600+
> > > >>> pages
> > > >>> >>>> of
> > > >>> >>>>>>>>>>> HTML
> > > >>> >>>>>>>>>>>> to
> > > >>> >>>>>>>>>>>>> manually edit. But I later realized that it was only
> > > about
> > > >>> 950
> > > >>> >>>> HTML
> > > >>> >>>>>>>>>>> pages
> > > >>> >>>>>>>>>>>>> (from what I can tell so far).
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
> > > >>> converter
> > > >>> >>>> built
> > > >>> >>>>>> on
> > > >>> >>>>>>>>>>> top
> > > >>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the
> > HTML
> > > >>> from
> > > >>> >>>>>>>>>>> Confluence
> > > >>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works
> > based
> > > >>> on the
> > > >>> >>>>>>>>>>>> Confluence
> > > >>> >>>>>>>>>>>>> export function which is different from how the HTML
> is
> > > >>> >>>>>> automagically
> > > >>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
> > > >>> >>>> NullPointerException
> > > >>> >>>>>>>>>>> from
> > > >>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is
> due
> > > to
> > > >>> the
> > > >>> >>>>>> CDATA
> > > >>> >>>>>>>>> in
> > > >>> >>>>>>>>>>>> the
> > > >>> >>>>>>>>>>>>> search function on the Navigation page and is
> > suggesting
> > > >>> that the
> > > >>> >>>>>>>>>>>> solution
> > > >>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with
> this
> > > >>> >>>> suggestion
> > > >>> >>>>>> is
> > > >>> >>>>>>>>>>>> that
> > > >>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on
> the
> > > >>> >>>> right-hand
> > > >>> >>>>>>>>> side
> > > >>> >>>>>>>>>>>> of
> > > >>> >>>>>>>>>>>>> the site -- not what we want.
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> I have also given some thought to the idea that
> > removing
> > > >>> the
> > > >>> >>>>>> current
> > > >>> >>>>>>>>>>> site
> > > >>> >>>>>>>>>>>>> will break all links to old site. This is something
> > that
> > > >>> cannot
> > > >>> >>>> be
> > > >>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
> > > >>> leave users
> > > >>> >>>>>> who
> > > >>> >>>>>>>>>>>> have
> > > >>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
> > > >>> problem to
> > > >>> >>>>>>>>> solve
> > > >>> >>>>>>>>>>>> this
> > > >>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
> > > Infra
> > > >>> is
> > > >>> >>>>>> willing
> > > >>> >>>>>>>>>>> to
> > > >>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
> > > >>> investigated
> > > >>> >>>>>>>>> when
> > > >>> >>>>>>>>>>> we
> > > >>> >>>>>>>>>>>>> get to that point, but we are not there yet. First,
> we
> > > >>> need to
> > > >>> >>>>>> decide
> > > >>> >>>>>>>>>>> the
> > > >>> >>>>>>>>>>>>> best path forward based on what I have described
> above
> > in
> > > >>> the
> > > >>> >>>>>>>>> preceding
> > > >>> >>>>>>>>>>>>> paragraphs.
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> Bruce
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> > > >>> >>>>>> mtaylor@redhat.com>
> > > >>> >>>>>>>>>>>>> wrote:
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>> I was thinking there would be a single css file for
> > all
> > > >>> the
> > > >>> >>>> pages.
> > > >>> >>>>>>>>>>> But
> > > >>> >>>>>>>>>>>> I
> > > >>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
> > > when
> > > >>> Bruce
> > > >>> >>>>>>>>> pushes
> > > >>> >>>>>>>>>>>> the
> > > >>> >>>>>>>>>>>>>> export.
> > > >>> >>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>> Cheers
> > > >>> >>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> > > >>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
> > > >>> >>>>>>>>>>>>>> wrote:
> > > >>> >>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to
> > start
> > > >>> doing
> > > >>> >>>> css
> > > >>> >>>>>>>>>>>>>> styles.
> > > >>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that
> far
> > > >>> off.
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not
> > all
> > > >>> just to
> > > >>> >>>>>> try
> > > >>> >>>>>>>>>>>> and
> > > >>> >>>>>>>>>>>>>>> see what it is like.
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> > > >>> >>>>>>>>>>> clebert.suconic@gmail.com>
> > > >>> >>>>>>>>>>>>>>> wrote:
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems
> like a
> > > big
> > > >>> >>>> task, I
> > > >>> >>>>>>>>>>>>>> suspect
> > > >>> >>>>>>>>>>>>>>> any
> > > >>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
> > > >>> issues.
> > > >>> >>>>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a
> nice
> > > >>> landing
> > > >>> >>>>>> page
> > > >>> >>>>>>>>>>>> that
> > > >>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site
> together,
> > > and
> > > >>> >>>>>>>>>>>> refresh/align
> > > >>> >>>>>>>>>>>>>>> the
> > > >>> >>>>>>>>>>>>>>>>> existing content with some CSS?
> > > >>> >>>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
> > > >>> thought that
> > > >>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier
> > than
> > > >>> >>>>>> converting
> > > >>> >>>>>>>>>>>> them
> > > >>> >>>>>>>>>>>>>>>> to another .css...
> > > >>> >>>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
> > > >>> thought .md
> > > >>> >>>>>> would
> > > >>> >>>>>>>>>>>> be
> > > >>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
> > > >>> >>>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>>
> > > >>> >>>>>>>>>>>>> --
> > > >>> >>>>>>>>>>>>> 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
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>> --
> > > >>> >>>>>>>>> Daniel Kulp
> > > >>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
> > > >>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>>
> > > >>> >>>>>>>>
> > > >>> >>>>>>>>
> > > >>> >>>>>>>> --
> > > >>> >>>>>>>> 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
> > > >>> >>>>>>
> > > >>> >>>>>> --
> > > >>> >>>>>> Daniel Kulp
> > > >>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
> > > >>> >>>>>> Talend Community Coder - http://coders.talend.com
> > > >>> >>>>>>
> > > >>> >>>>>>
> > > >>> >>>>>
> > > >>> >>>>>
> > > >>> >>>>> --
> > > >>> >>>>> 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
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Arthur Naseef <ar...@amlinv.com>.
I pulled down Michael's git repo and browsed it.  Here are my initial
impressions:

The Good
* The look-and-feel is a little cleaner than the existing site
* I see a lot of promise with this new layout.

The Bad
* While I believe it is expected at this point, I feel it needs to be said
-- a lot of formatting is lacking
* Over time, for ongoing users, I believe the technical reference pages
(e.g. the failover transport page) are most useful; the lack of formatting
there makes them hard to consume
* It is hard to find several pages - although I suspect not much harder
than the current site, except that google finds the pages quickly (e.g.
searching on "failover activemq" brings up this link right away - for me at
least - http://activemq.apache.org/failover-transport-reference.html)

So overall, I would say it currently looks like a good, early start at the
effort.  Nothing showing up that is an obvious concern to the effort.

With that said, it would greatly help to have a small representative set of
pages that get closer to a final state in order to respond to that.  For
example, once the failover transport reference is formatted, then it will
be easier to gauge how easy it is to find important information on that
page.

Art


On Fri, Mar 16, 2018 at 2:52 AM, Martyn Taylor <mt...@redhat.com> wrote:

> Bruce, All
>
> We organised a webex discussion on the dev list[1] where we discussed
> Michael's proposal and created a bunch of JIRA[2] that we think are needed
> in order to move forward with the proposal.  Unfortunately only a handful
> of people attended.  There is concern that a lot of work will be put into
> building a new site based on Michael's proposal only for it to get -1 at
> the last minute.  For this reason, can I suggest that people take some time
> to look into what has been done already by checking out the git repo as
> Bruce suggested, or we schedule another webex session where Michael can
> talk about his proposal.  We can then take a vote as to whether or not this
> is an approach we want to move forward with and what the requirements are
> to go live.
>
> Thanks
>
> [1] http://activemq.2283324.n4.nabble.com/Website-Discussion-
> td4737173.html
> [2] https://issues.apache.org/jira/browse/AMQ-6912
>
>
>
> On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > Everyone should take a look at the gitbook that Mike put together. It's a
> > great first example.
> >
> > https://github.com/apache/activemq-web/pull/3
> >
> > Please take 10 minutes to clone the repo, switch to the branch, install
> > gitbook, run gitbook and peruse the docs.
> >
> > Bruce
> >
> > On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> > > I'm sorry about the long delays in getting the official export from
> > > Confluence, but it took this long to get some resolution on the issue.
> > >
> > > I now have a full HTML export from Confluence with the exception of the
> > > Navigation page. You can grab the zip file of the HTML at the following
> > URL:
> > >
> > > https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
> > > oDtZxt8mFZlX/view?usp=sharing
> > >
> > > Bruce
> > >
> > > On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
> > > wrote:
> > >
> > >> +1
> > >>
> > >> Bruce
> > >>
> > >> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
> > >> michael.andre.pearce@me.com> wrote:
> > >>
> > >>> Hi All,
> > >>>
> > >>> It’s been a bit quiet on the front of this effort.
> > >>>
> > >>> I’d like to bump this a bit to get some feedback on the current
> > >>> examples, and try agree a plan going forwards and spread the work.
> > >>>
> > >>> I was speaking with Martyn the other week and we think maybe a brief
> > >>> webex to demo what’s been done so far and then discuss.
> > >>> Martyn’s offered he can host this using his bluejeans account
> (thanks)
> > >>>
> > >>> We are thinking of organising this for the week of 19th Feb.
> > >>>
> > >>> Any specific people who want to be involved can or cannot make? If
> not
> > >>> I’ll sync up with Martyn to agree and then post a time and date.
> > >>>
> > >>> Cheers
> > >>> Mike
> > >>>
> > >>>
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
> > >>> michael.andre.pearce@me.com> wrote:
> > >>> >
> > >>> > Just FYI have sent a PR with a link to my branch of this export now
> > in
> > >>> a GitBook form still needs a lot of TLC but have tried to get a large
> > bulk
> > >>> done. To provide some skeleton for 5.x documents.
> > >>> >
> > >>> >
> > >>> > Sent from my iPhone
> > >>> >
> > >>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
> > >>> michael.andre.pearce@me.com> wrote:
> > >>> >>
> > >>> >> Yeah, unfortunately the tool i found wanted just html it blew up
> > when
> > >>> trying to use modified.
> > >>> >>
> > >>> >> Like wise there was a couple of pages it couldn’t convert due to a
> > >>> css file on import issue but this wasn’t that many.
> > >>> >>
> > >>> >> Sent from my iPhone
> > >>> >>
> > >>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
> > >>> wrote:
> > >>> >>>
> > >>> >>> Nice job, based on my spot check of a handful of files, it looks
> > much
> > >>> >>> better. But we will still need to manually fix all the valid
> > tables.
> > >>> >>>
> > >>> >>> Have you had a chance to look at the other branches that Dan Kulp
> > >>> provided?
> > >>> >>>
> > >>> >>> Bruce
> > >>> >>>
> > >>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> > >>> >>> michael.andre.pearce@me.com> wrote:
> > >>> >>>
> > >>> >>>> I’ve had some luck auto generating MD files.
> > >>> >>>>
> > >>> >>>> Needs some cleanup which probably the worst can be bash
> scripted.
> > >>> >>>>
> > >>> >>>> Have sent a PR back to the activemq-web on github for others to
> > see.
> > >>> >>>>
> > >>> >>>> Mike
> > >>> >>>>
> > >>> >>>> Sent from my iPhone
> > >>> >>>>
> > >>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <bruce.snyder@gmail.com
> >
> > >>> wrote:
> > >>> >>>>>
> > >>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the
> > others
> > >>> should
> > >>> >>>>> propagate in time). But I see that it's already more
> > comprehensive
> > >>> than
> > >>> >>>> the
> > >>> >>>>> HTML that I pushed because it contains all the directories. We
> > >>> should
> > >>> >>>>> probably wipe out the master branch and choose one of yours as
> > the
> > >>> new
> > >>> >>>>> master branch.
> > >>> >>>>>
> > >>> >>>>> Bruce
> > >>> >>>>>
> > >>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <
> dkulp@apache.org>
> > >>> wrote:
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> I hacked the Confluence exporter a bit to grab the page
> content
> > in
> > >>> >>>>>> different formats so we can see if one is easier to migrate or
> > >>> >>>> similar.   I
> > >>> >>>>>> just pushed 3 new branches to this repo:
> > >>> >>>>>>
> > >>> >>>>>> body.only - this is basically the same HTML, but with all the
> > >>> “wrapper”
> > >>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
> > >>> navigation
> > >>> >>>> or
> > >>> >>>>>> header/footer, etc…
> > >>> >>>>>>
> > >>> >>>>>> body.storage - this is the raw storage format of the data from
> > >>> >>>>>> confluence.   Things like code snippets are in storage format
> > >>> >>>>>> (<structured-macro name=“code” …>), etc.
> > >>> >>>>>>
> > >>> >>>>>> body.view - confluence has a “body.view” mode that is between
> > the
> > >>> >>>>>> “storage” format and not really the exported HTML.     The
> > >>> structured
> > >>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but
> > not
> > >>> >>>> really in
> > >>> >>>>>> final HTML form either.
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> Anyway, if interested in converting content, one of the above
> > >>> might be a
> > >>> >>>>>> better starting point.
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> Dan
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com>
> > >>> >>>>>> wrote:
> > >>> >>>>>>>
> > >>> >>>>>>> The HTML is available in the repo now. This HTML is just
> what I
> > >>> grabbed
> > >>> >>>>>>> from the public directory. Even if it's not comprehensive,
> it's
> > >>> good
> > >>> >>>>>> enough
> > >>> >>>>>>> for hacking around to figure out what we'd like to do.
> > >>> >>>>>>>
> > >>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure
> out
> > >>> why the
> > >>> >>>>>>> Confluence export is failing.
> > >>> >>>>>>>
> > >>> >>>>>>> Bruce
> > >>> >>>>>>>
> > >>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com
> > >>> >>>>>
> > >>> >>>>>>> wrote:
> > >>> >>>>>>>
> > >>> >>>>>>>> Yep, that is correct, Dan:
> > >>> >>>>>>>>
> > >>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > >>> >>>>>>>>
> > >>> >>>>>>>> I pushed my changes to the repo. Now they just need to
> > >>> propagate to
> > >>> >>>> the
> > >>> >>>>>>>> Github web UI.
> > >>> >>>>>>>>
> > >>> >>>>>>>> Bruce
> > >>> >>>>>>>>
> > >>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
> > >>> dkulp@apache.org>
> > >>> >>>> wrote:
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> Isn’t the push address supposed to be:
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> Dan
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com>
> > >>> >>>>>>>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not
> > have
> > >>> >>>>>>>>> permissions
> > >>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Bruce
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
> > >>> mtaylor@redhat.com>
> > >>> >>>>>>>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> > >>> >>>>>> bruce.snyder@gmail.com>
> > >>> >>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>>> I had the following empty git repo created to hold the
> > HTML
> > >>> from
> > >>> >>>> the
> > >>> >>>>>>>>>>>> current website:
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> https://github.com/apache/activemq-web
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
> > >>> directly
> > >>> >>>> to
> > >>> >>>>>> a
> > >>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull
> > request
> > >>> but
> > >>> >>>>>> Github
> > >>> >>>>>>>>>>> does
> > >>> >>>>>>>>>>>> not allow a pull request on an empty repo.
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
> > i.e.
> > >>> >>>> git://
> > >>> >>>>>>>>>>> git.apache.org/activemq-web.git
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>> This is the workflow we currently use, we push directly
> to
> > >>> the ASF
> > >>> >>>>>>>>> repo.
> > >>> >>>>>>>>>>> PRs are really only used for review and discussion.  I
> > tried
> > >>> to
> > >>> >>>> push
> > >>> >>>>>>>>>>> directly this morning but looks like I don't have write
> > >>> >>>> permissions.
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess
> I
> > >>> could
> > >>> >>>> ask
> > >>> >>>>>>>>> ASF
> > >>> >>>>>>>>>>>> Infra to push it.
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Bruce
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> > >>> >>>>>> bruce.snyder@gmail.com
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> I'm going to address all the questions to me in this
> > single
> > >>> >>>> reply.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
> > >>> >>>> Confluence,
> > >>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images
> > in
> > >>> a git
> > >>> >>>>>>>>> repo.
> > >>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML,
> especially
> > >>> the
> > >>> >>>> HTML
> > >>> >>>>>>>>>>>> exported
> > >>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could
> use
> > >>> Jekyll +
> > >>> >>>>>>>>> SAAS
> > >>> >>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
> > >>> produced a
> > >>> >>>>>> mockup
> > >>> >>>>>>>>> of
> > >>> >>>>>>>>>>>>> this using the Apache Metro website as an example
> > (because
> > >>> it
> > >>> >>>>>> already
> > >>> >>>>>>>>>>>> makes
> > >>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me
> that
> > we
> > >>> >>>> should
> > >>> >>>>>>>>> take
> > >>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
> > >>> export of
> > >>> >>>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup,
> you
> > >>> should
> > >>> >>>>>>>>> really
> > >>> >>>>>>>>>>>>> take a look.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is
> automagically
> > >>> >>>> exported
> > >>> >>>>>>>>> from
> > >>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see
> at
> > >>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
> > using
> > >>> >>>>>> text2html
> > >>> >>>>>>>>>>> and
> > >>> >>>>>>>>>>>>> the conversion it does is pretty awful and would
> require
> > a
> > >>> lot of
> > >>> >>>>>>>>> hand
> > >>> >>>>>>>>>>>> work
> > >>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are
> > 1600+
> > >>> pages
> > >>> >>>> of
> > >>> >>>>>>>>>>> HTML
> > >>> >>>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> manually edit. But I later realized that it was only
> > about
> > >>> 950
> > >>> >>>> HTML
> > >>> >>>>>>>>>>> pages
> > >>> >>>>>>>>>>>>> (from what I can tell so far).
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
> > >>> converter
> > >>> >>>> built
> > >>> >>>>>> on
> > >>> >>>>>>>>>>> top
> > >>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the
> HTML
> > >>> from
> > >>> >>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works
> based
> > >>> on the
> > >>> >>>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> export function which is different from how the HTML is
> > >>> >>>>>> automagically
> > >>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
> > >>> >>>> NullPointerException
> > >>> >>>>>>>>>>> from
> > >>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due
> > to
> > >>> the
> > >>> >>>>>> CDATA
> > >>> >>>>>>>>> in
> > >>> >>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>> search function on the Navigation page and is
> suggesting
> > >>> that the
> > >>> >>>>>>>>>>>> solution
> > >>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
> > >>> >>>> suggestion
> > >>> >>>>>> is
> > >>> >>>>>>>>>>>> that
> > >>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
> > >>> >>>> right-hand
> > >>> >>>>>>>>> side
> > >>> >>>>>>>>>>>> of
> > >>> >>>>>>>>>>>>> the site -- not what we want.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> I have also given some thought to the idea that
> removing
> > >>> the
> > >>> >>>>>> current
> > >>> >>>>>>>>>>> site
> > >>> >>>>>>>>>>>>> will break all links to old site. This is something
> that
> > >>> cannot
> > >>> >>>> be
> > >>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
> > >>> leave users
> > >>> >>>>>> who
> > >>> >>>>>>>>>>>> have
> > >>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
> > >>> problem to
> > >>> >>>>>>>>> solve
> > >>> >>>>>>>>>>>> this
> > >>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
> > Infra
> > >>> is
> > >>> >>>>>> willing
> > >>> >>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
> > >>> investigated
> > >>> >>>>>>>>> when
> > >>> >>>>>>>>>>> we
> > >>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we
> > >>> need to
> > >>> >>>>>> decide
> > >>> >>>>>>>>>>> the
> > >>> >>>>>>>>>>>>> best path forward based on what I have described above
> in
> > >>> the
> > >>> >>>>>>>>> preceding
> > >>> >>>>>>>>>>>>> paragraphs.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Bruce
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> > >>> >>>>>> mtaylor@redhat.com>
> > >>> >>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> I was thinking there would be a single css file for
> all
> > >>> the
> > >>> >>>> pages.
> > >>> >>>>>>>>>>> But
> > >>> >>>>>>>>>>>> I
> > >>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
> > when
> > >>> Bruce
> > >>> >>>>>>>>> pushes
> > >>> >>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>>> export.
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> Cheers
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> > >>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
> > >>> >>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to
> start
> > >>> doing
> > >>> >>>> css
> > >>> >>>>>>>>>>>>>> styles.
> > >>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far
> > >>> off.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not
> all
> > >>> just to
> > >>> >>>>>> try
> > >>> >>>>>>>>>>>> and
> > >>> >>>>>>>>>>>>>>> see what it is like.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> > >>> >>>>>>>>>>> clebert.suconic@gmail.com>
> > >>> >>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a
> > big
> > >>> >>>> task, I
> > >>> >>>>>>>>>>>>>> suspect
> > >>> >>>>>>>>>>>>>>> any
> > >>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
> > >>> issues.
> > >>> >>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
> > >>> landing
> > >>> >>>>>> page
> > >>> >>>>>>>>>>>> that
> > >>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together,
> > and
> > >>> >>>>>>>>>>>> refresh/align
> > >>> >>>>>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>>>>>> existing content with some CSS?
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
> > >>> thought that
> > >>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier
> than
> > >>> >>>>>> converting
> > >>> >>>>>>>>>>>> them
> > >>> >>>>>>>>>>>>>>>> to another .css...
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
> > >>> thought .md
> > >>> >>>>>> would
> > >>> >>>>>>>>>>>> be
> > >>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> --
> > >>> >>>>>>>>>>>>> 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
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> --
> > >>> >>>>>>>>> Daniel Kulp
> > >>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
> > >>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>>>> --
> > >>> >>>>>>>> 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
> > >>> >>>>>>
> > >>> >>>>>> --
> > >>> >>>>>> Daniel Kulp
> > >>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
> > >>> >>>>>> Talend Community Coder - http://coders.talend.com
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>
> > >>> >>>>>
> > >>> >>>>> --
> > >>> >>>>> 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
> > >>
> > >
> > >
> > >
> > > --
> > > 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
> >
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Christopher Shannon <ch...@gmail.com>.
The work done so far looks good to me.

On Tue, Mar 20, 2018 at 12:17 PM, Bruce Snyder <br...@gmail.com> wrote:
> I'm sorry I missed the previous WebEx discuss on this topic. I will do my
> best to attend the next one.
>
> Bruce
>
> On Fri, Mar 16, 2018 at 3:52 AM, Martyn Taylor <mt...@redhat.com> wrote:
>
>> Bruce, All
>>
>> We organised a webex discussion on the dev list[1] where we discussed
>> Michael's proposal and created a bunch of JIRA[2] that we think are needed
>> in order to move forward with the proposal.  Unfortunately only a handful
>> of people attended.  There is concern that a lot of work will be put into
>> building a new site based on Michael's proposal only for it to get -1 at
>> the last minute.  For this reason, can I suggest that people take some time
>> to look into what has been done already by checking out the git repo as
>> Bruce suggested, or we schedule another webex session where Michael can
>> talk about his proposal.  We can then take a vote as to whether or not this
>> is an approach we want to move forward with and what the requirements are
>> to go live.
>>
>> Thanks
>>
>> [1] http://activemq.2283324.n4.nabble.com/Website-Discussion-
>> td4737173.html
>> [2] https://issues.apache.org/jira/browse/AMQ-6912
>>
>>
>>
>> On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
>> wrote:
>>
>> > Everyone should take a look at the gitbook that Mike put together. It's a
>> > great first example.
>> >
>> > https://github.com/apache/activemq-web/pull/3
>> >
>> > Please take 10 minutes to clone the repo, switch to the branch, install
>> > gitbook, run gitbook and peruse the docs.
>> >
>> > Bruce
>> >
>> > On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
>> > wrote:
>> >
>> > > I'm sorry about the long delays in getting the official export from
>> > > Confluence, but it took this long to get some resolution on the issue.
>> > >
>> > > I now have a full HTML export from Confluence with the exception of the
>> > > Navigation page. You can grab the zip file of the HTML at the following
>> > URL:
>> > >
>> > > https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
>> > > oDtZxt8mFZlX/view?usp=sharing
>> > >
>> > > Bruce
>> > >
>> > > On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
>> > > wrote:
>> > >
>> > >> +1
>> > >>
>> > >> Bruce
>> > >>
>> > >> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
>> > >> michael.andre.pearce@me.com> wrote:
>> > >>
>> > >>> Hi All,
>> > >>>
>> > >>> It’s been a bit quiet on the front of this effort.
>> > >>>
>> > >>> I’d like to bump this a bit to get some feedback on the current
>> > >>> examples, and try agree a plan going forwards and spread the work.
>> > >>>
>> > >>> I was speaking with Martyn the other week and we think maybe a brief
>> > >>> webex to demo what’s been done so far and then discuss.
>> > >>> Martyn’s offered he can host this using his bluejeans account
>> (thanks)
>> > >>>
>> > >>> We are thinking of organising this for the week of 19th Feb.
>> > >>>
>> > >>> Any specific people who want to be involved can or cannot make? If
>> not
>> > >>> I’ll sync up with Martyn to agree and then post a time and date.
>> > >>>
>> > >>> Cheers
>> > >>> Mike
>> > >>>
>> > >>>
>> > >>>
>> > >>> Sent from my iPhone
>> > >>>
>> > >>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
>> > >>> michael.andre.pearce@me.com> wrote:
>> > >>> >
>> > >>> > Just FYI have sent a PR with a link to my branch of this export now
>> > in
>> > >>> a GitBook form still needs a lot of TLC but have tried to get a large
>> > bulk
>> > >>> done. To provide some skeleton for 5.x documents.
>> > >>> >
>> > >>> >
>> > >>> > Sent from my iPhone
>> > >>> >
>> > >>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
>> > >>> michael.andre.pearce@me.com> wrote:
>> > >>> >>
>> > >>> >> Yeah, unfortunately the tool i found wanted just html it blew up
>> > when
>> > >>> trying to use modified.
>> > >>> >>
>> > >>> >> Like wise there was a couple of pages it couldn’t convert due to a
>> > >>> css file on import issue but this wasn’t that many.
>> > >>> >>
>> > >>> >> Sent from my iPhone
>> > >>> >>
>> > >>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
>> > >>> wrote:
>> > >>> >>>
>> > >>> >>> Nice job, based on my spot check of a handful of files, it looks
>> > much
>> > >>> >>> better. But we will still need to manually fix all the valid
>> > tables.
>> > >>> >>>
>> > >>> >>> Have you had a chance to look at the other branches that Dan Kulp
>> > >>> provided?
>> > >>> >>>
>> > >>> >>> Bruce
>> > >>> >>>
>> > >>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>> > >>> >>> michael.andre.pearce@me.com> wrote:
>> > >>> >>>
>> > >>> >>>> I’ve had some luck auto generating MD files.
>> > >>> >>>>
>> > >>> >>>> Needs some cleanup which probably the worst can be bash
>> scripted.
>> > >>> >>>>
>> > >>> >>>> Have sent a PR back to the activemq-web on github for others to
>> > see.
>> > >>> >>>>
>> > >>> >>>> Mike
>> > >>> >>>>
>> > >>> >>>> Sent from my iPhone
>> > >>> >>>>
>> > >>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <bruce.snyder@gmail.com
>> >
>> > >>> wrote:
>> > >>> >>>>>
>> > >>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the
>> > others
>> > >>> should
>> > >>> >>>>> propagate in time). But I see that it's already more
>> > comprehensive
>> > >>> than
>> > >>> >>>> the
>> > >>> >>>>> HTML that I pushed because it contains all the directories. We
>> > >>> should
>> > >>> >>>>> probably wipe out the master branch and choose one of yours as
>> > the
>> > >>> new
>> > >>> >>>>> master branch.
>> > >>> >>>>>
>> > >>> >>>>> Bruce
>> > >>> >>>>>
>> > >>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <
>> dkulp@apache.org>
>> > >>> wrote:
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>> I hacked the Confluence exporter a bit to grab the page
>> content
>> > in
>> > >>> >>>>>> different formats so we can see if one is easier to migrate or
>> > >>> >>>> similar.   I
>> > >>> >>>>>> just pushed 3 new branches to this repo:
>> > >>> >>>>>>
>> > >>> >>>>>> body.only - this is basically the same HTML, but with all the
>> > >>> “wrapper”
>> > >>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
>> > >>> navigation
>> > >>> >>>> or
>> > >>> >>>>>> header/footer, etc…
>> > >>> >>>>>>
>> > >>> >>>>>> body.storage - this is the raw storage format of the data from
>> > >>> >>>>>> confluence.   Things like code snippets are in storage format
>> > >>> >>>>>> (<structured-macro name=“code” …>), etc.
>> > >>> >>>>>>
>> > >>> >>>>>> body.view - confluence has a “body.view” mode that is between
>> > the
>> > >>> >>>>>> “storage” format and not really the exported HTML.     The
>> > >>> structured
>> > >>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but
>> > not
>> > >>> >>>> really in
>> > >>> >>>>>> final HTML form either.
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>> Anyway, if interested in converting content, one of the above
>> > >>> might be a
>> > >>> >>>>>> better starting point.
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>> Dan
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
>> > >>> bruce.snyder@gmail.com>
>> > >>> >>>>>> wrote:
>> > >>> >>>>>>>
>> > >>> >>>>>>> The HTML is available in the repo now. This HTML is just
>> what I
>> > >>> grabbed
>> > >>> >>>>>>> from the public directory. Even if it's not comprehensive,
>> it's
>> > >>> good
>> > >>> >>>>>> enough
>> > >>> >>>>>>> for hacking around to figure out what we'd like to do.
>> > >>> >>>>>>>
>> > >>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure
>> out
>> > >>> why the
>> > >>> >>>>>>> Confluence export is failing.
>> > >>> >>>>>>>
>> > >>> >>>>>>> Bruce
>> > >>> >>>>>>>
>> > >>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
>> > >>> bruce.snyder@gmail.com
>> > >>> >>>>>
>> > >>> >>>>>>> wrote:
>> > >>> >>>>>>>
>> > >>> >>>>>>>> Yep, that is correct, Dan:
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> I pushed my changes to the repo. Now they just need to
>> > >>> propagate to
>> > >>> >>>> the
>> > >>> >>>>>>>> Github web UI.
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> Bruce
>> > >>> >>>>>>>>
>> > >>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
>> > >>> dkulp@apache.org>
>> > >>> >>>> wrote:
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>> Isn’t the push address supposed to be:
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>> Dan
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
>> > >>> bruce.snyder@gmail.com>
>> > >>> >>>>>>>>> wrote:
>> > >>> >>>>>>>>>>
>> > >>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not
>> > have
>> > >>> >>>>>>>>> permissions
>> > >>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
>> > >>> >>>>>>>>>>
>> > >>> >>>>>>>>>> Bruce
>> > >>> >>>>>>>>>>
>> > >>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
>> > >>> mtaylor@redhat.com>
>> > >>> >>>>>>>>> wrote:
>> > >>> >>>>>>>>>>
>> > >>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>> > >>> >>>>>> bruce.snyder@gmail.com>
>> > >>> >>>>>>>>>>> wrote:
>> > >>> >>>>>>>>>>>
>> > >>> >>>>>>>>>>>> I had the following empty git repo created to hold the
>> > HTML
>> > >>> from
>> > >>> >>>> the
>> > >>> >>>>>>>>>>>> current website:
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>> https://github.com/apache/activemq-web
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
>> > >>> directly
>> > >>> >>>> to
>> > >>> >>>>>> a
>> > >>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull
>> > request
>> > >>> but
>> > >>> >>>>>> Github
>> > >>> >>>>>>>>>>> does
>> > >>> >>>>>>>>>>>> not allow a pull request on an empty repo.
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
>> > i.e.
>> > >>> >>>> git://
>> > >>> >>>>>>>>>>> git.apache.org/activemq-web.git
>> > >>> >>>>>>>>>>>
>> > >>> >>>>>>>>>>> This is the workflow we currently use, we push directly
>> to
>> > >>> the ASF
>> > >>> >>>>>>>>> repo.
>> > >>> >>>>>>>>>>> PRs are really only used for review and discussion.  I
>> > tried
>> > >>> to
>> > >>> >>>> push
>> > >>> >>>>>>>>>>> directly this morning but looks like I don't have write
>> > >>> >>>> permissions.
>> > >>> >>>>>>>>>>>
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess
>> I
>> > >>> could
>> > >>> >>>> ask
>> > >>> >>>>>>>>> ASF
>> > >>> >>>>>>>>>>>> Infra to push it.
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>> Bruce
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>> > >>> >>>>>> bruce.snyder@gmail.com
>> > >>> >>>>>>>>>>
>> > >>> >>>>>>>>>>>> wrote:
>> > >>> >>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> I'm going to address all the questions to me in this
>> > single
>> > >>> >>>> reply.
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
>> > >>> >>>> Confluence,
>> > >>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images
>> > in
>> > >>> a git
>> > >>> >>>>>>>>> repo.
>> > >>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML,
>> especially
>> > >>> the
>> > >>> >>>> HTML
>> > >>> >>>>>>>>>>>> exported
>> > >>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could
>> use
>> > >>> Jekyll +
>> > >>> >>>>>>>>> SAAS
>> > >>> >>>>>>>>>>> to
>> > >>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
>> > >>> produced a
>> > >>> >>>>>> mockup
>> > >>> >>>>>>>>> of
>> > >>> >>>>>>>>>>>>> this using the Apache Metro website as an example
>> > (because
>> > >>> it
>> > >>> >>>>>> already
>> > >>> >>>>>>>>>>>> makes
>> > >>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me
>> that
>> > we
>> > >>> >>>> should
>> > >>> >>>>>>>>> take
>> > >>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
>> > >>> export of
>> > >>> >>>>>>>>>>>> Confluence
>> > >>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup,
>> you
>> > >>> should
>> > >>> >>>>>>>>> really
>> > >>> >>>>>>>>>>>>> take a look.
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is
>> automagically
>> > >>> >>>> exported
>> > >>> >>>>>>>>> from
>> > >>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see
>> at
>> > >>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
>> > using
>> > >>> >>>>>> text2html
>> > >>> >>>>>>>>>>> and
>> > >>> >>>>>>>>>>>>> the conversion it does is pretty awful and would
>> require
>> > a
>> > >>> lot of
>> > >>> >>>>>>>>> hand
>> > >>> >>>>>>>>>>>> work
>> > >>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are
>> > 1600+
>> > >>> pages
>> > >>> >>>> of
>> > >>> >>>>>>>>>>> HTML
>> > >>> >>>>>>>>>>>> to
>> > >>> >>>>>>>>>>>>> manually edit. But I later realized that it was only
>> > about
>> > >>> 950
>> > >>> >>>> HTML
>> > >>> >>>>>>>>>>> pages
>> > >>> >>>>>>>>>>>>> (from what I can tell so far).
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
>> > >>> converter
>> > >>> >>>> built
>> > >>> >>>>>> on
>> > >>> >>>>>>>>>>> top
>> > >>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the
>> HTML
>> > >>> from
>> > >>> >>>>>>>>>>> Confluence
>> > >>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works
>> based
>> > >>> on the
>> > >>> >>>>>>>>>>>> Confluence
>> > >>> >>>>>>>>>>>>> export function which is different from how the HTML is
>> > >>> >>>>>> automagically
>> > >>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
>> > >>> >>>> NullPointerException
>> > >>> >>>>>>>>>>> from
>> > >>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due
>> > to
>> > >>> the
>> > >>> >>>>>> CDATA
>> > >>> >>>>>>>>> in
>> > >>> >>>>>>>>>>>> the
>> > >>> >>>>>>>>>>>>> search function on the Navigation page and is
>> suggesting
>> > >>> that the
>> > >>> >>>>>>>>>>>> solution
>> > >>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
>> > >>> >>>> suggestion
>> > >>> >>>>>> is
>> > >>> >>>>>>>>>>>> that
>> > >>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
>> > >>> >>>> right-hand
>> > >>> >>>>>>>>> side
>> > >>> >>>>>>>>>>>> of
>> > >>> >>>>>>>>>>>>> the site -- not what we want.
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> I have also given some thought to the idea that
>> removing
>> > >>> the
>> > >>> >>>>>> current
>> > >>> >>>>>>>>>>> site
>> > >>> >>>>>>>>>>>>> will break all links to old site. This is something
>> that
>> > >>> cannot
>> > >>> >>>> be
>> > >>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
>> > >>> leave users
>> > >>> >>>>>> who
>> > >>> >>>>>>>>>>>> have
>> > >>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
>> > >>> problem to
>> > >>> >>>>>>>>> solve
>> > >>> >>>>>>>>>>>> this
>> > >>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
>> > Infra
>> > >>> is
>> > >>> >>>>>> willing
>> > >>> >>>>>>>>>>> to
>> > >>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
>> > >>> investigated
>> > >>> >>>>>>>>> when
>> > >>> >>>>>>>>>>> we
>> > >>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we
>> > >>> need to
>> > >>> >>>>>> decide
>> > >>> >>>>>>>>>>> the
>> > >>> >>>>>>>>>>>>> best path forward based on what I have described above
>> in
>> > >>> the
>> > >>> >>>>>>>>> preceding
>> > >>> >>>>>>>>>>>>> paragraphs.
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> Bruce
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>> > >>> >>>>>> mtaylor@redhat.com>
>> > >>> >>>>>>>>>>>>> wrote:
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>> I was thinking there would be a single css file for
>> all
>> > >>> the
>> > >>> >>>> pages.
>> > >>> >>>>>>>>>>> But
>> > >>> >>>>>>>>>>>> I
>> > >>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
>> > when
>> > >>> Bruce
>> > >>> >>>>>>>>> pushes
>> > >>> >>>>>>>>>>>> the
>> > >>> >>>>>>>>>>>>>> export.
>> > >>> >>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>> Cheers
>> > >>> >>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>> > >>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
>> > >>> >>>>>>>>>>>>>> wrote:
>> > >>> >>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to
>> start
>> > >>> doing
>> > >>> >>>> css
>> > >>> >>>>>>>>>>>>>> styles.
>> > >>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far
>> > >>> off.
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not
>> all
>> > >>> just to
>> > >>> >>>>>> try
>> > >>> >>>>>>>>>>>> and
>> > >>> >>>>>>>>>>>>>>> see what it is like.
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>> > >>> >>>>>>>>>>> clebert.suconic@gmail.com>
>> > >>> >>>>>>>>>>>>>>> wrote:
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a
>> > big
>> > >>> >>>> task, I
>> > >>> >>>>>>>>>>>>>> suspect
>> > >>> >>>>>>>>>>>>>>> any
>> > >>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
>> > >>> issues.
>> > >>> >>>>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
>> > >>> landing
>> > >>> >>>>>> page
>> > >>> >>>>>>>>>>>> that
>> > >>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together,
>> > and
>> > >>> >>>>>>>>>>>> refresh/align
>> > >>> >>>>>>>>>>>>>>> the
>> > >>> >>>>>>>>>>>>>>>>> existing content with some CSS?
>> > >>> >>>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
>> > >>> thought that
>> > >>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier
>> than
>> > >>> >>>>>> converting
>> > >>> >>>>>>>>>>>> them
>> > >>> >>>>>>>>>>>>>>>> to another .css...
>> > >>> >>>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
>> > >>> thought .md
>> > >>> >>>>>> would
>> > >>> >>>>>>>>>>>> be
>> > >>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
>> > >>> >>>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>>
>> > >>> >>>>>>>>>>>>> --
>> > >>> >>>>>>>>>>>>> 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
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>> --
>> > >>> >>>>>>>>> Daniel Kulp
>> > >>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>> > >>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>>
>> > >>> >>>>>>>>
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> --
>> > >>> >>>>>>>> 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
>> > >>> >>>>>>
>> > >>> >>>>>> --
>> > >>> >>>>>> Daniel Kulp
>> > >>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
>> > >>> >>>>>> Talend Community Coder - http://coders.talend.com
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>> --
>> > >>> >>>>> 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
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
I'm sorry I missed the previous WebEx discuss on this topic. I will do my
best to attend the next one.

Bruce

On Fri, Mar 16, 2018 at 3:52 AM, Martyn Taylor <mt...@redhat.com> wrote:

> Bruce, All
>
> We organised a webex discussion on the dev list[1] where we discussed
> Michael's proposal and created a bunch of JIRA[2] that we think are needed
> in order to move forward with the proposal.  Unfortunately only a handful
> of people attended.  There is concern that a lot of work will be put into
> building a new site based on Michael's proposal only for it to get -1 at
> the last minute.  For this reason, can I suggest that people take some time
> to look into what has been done already by checking out the git repo as
> Bruce suggested, or we schedule another webex session where Michael can
> talk about his proposal.  We can then take a vote as to whether or not this
> is an approach we want to move forward with and what the requirements are
> to go live.
>
> Thanks
>
> [1] http://activemq.2283324.n4.nabble.com/Website-Discussion-
> td4737173.html
> [2] https://issues.apache.org/jira/browse/AMQ-6912
>
>
>
> On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > Everyone should take a look at the gitbook that Mike put together. It's a
> > great first example.
> >
> > https://github.com/apache/activemq-web/pull/3
> >
> > Please take 10 minutes to clone the repo, switch to the branch, install
> > gitbook, run gitbook and peruse the docs.
> >
> > Bruce
> >
> > On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> > > I'm sorry about the long delays in getting the official export from
> > > Confluence, but it took this long to get some resolution on the issue.
> > >
> > > I now have a full HTML export from Confluence with the exception of the
> > > Navigation page. You can grab the zip file of the HTML at the following
> > URL:
> > >
> > > https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
> > > oDtZxt8mFZlX/view?usp=sharing
> > >
> > > Bruce
> > >
> > > On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
> > > wrote:
> > >
> > >> +1
> > >>
> > >> Bruce
> > >>
> > >> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
> > >> michael.andre.pearce@me.com> wrote:
> > >>
> > >>> Hi All,
> > >>>
> > >>> It’s been a bit quiet on the front of this effort.
> > >>>
> > >>> I’d like to bump this a bit to get some feedback on the current
> > >>> examples, and try agree a plan going forwards and spread the work.
> > >>>
> > >>> I was speaking with Martyn the other week and we think maybe a brief
> > >>> webex to demo what’s been done so far and then discuss.
> > >>> Martyn’s offered he can host this using his bluejeans account
> (thanks)
> > >>>
> > >>> We are thinking of organising this for the week of 19th Feb.
> > >>>
> > >>> Any specific people who want to be involved can or cannot make? If
> not
> > >>> I’ll sync up with Martyn to agree and then post a time and date.
> > >>>
> > >>> Cheers
> > >>> Mike
> > >>>
> > >>>
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
> > >>> michael.andre.pearce@me.com> wrote:
> > >>> >
> > >>> > Just FYI have sent a PR with a link to my branch of this export now
> > in
> > >>> a GitBook form still needs a lot of TLC but have tried to get a large
> > bulk
> > >>> done. To provide some skeleton for 5.x documents.
> > >>> >
> > >>> >
> > >>> > Sent from my iPhone
> > >>> >
> > >>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
> > >>> michael.andre.pearce@me.com> wrote:
> > >>> >>
> > >>> >> Yeah, unfortunately the tool i found wanted just html it blew up
> > when
> > >>> trying to use modified.
> > >>> >>
> > >>> >> Like wise there was a couple of pages it couldn’t convert due to a
> > >>> css file on import issue but this wasn’t that many.
> > >>> >>
> > >>> >> Sent from my iPhone
> > >>> >>
> > >>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
> > >>> wrote:
> > >>> >>>
> > >>> >>> Nice job, based on my spot check of a handful of files, it looks
> > much
> > >>> >>> better. But we will still need to manually fix all the valid
> > tables.
> > >>> >>>
> > >>> >>> Have you had a chance to look at the other branches that Dan Kulp
> > >>> provided?
> > >>> >>>
> > >>> >>> Bruce
> > >>> >>>
> > >>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> > >>> >>> michael.andre.pearce@me.com> wrote:
> > >>> >>>
> > >>> >>>> I’ve had some luck auto generating MD files.
> > >>> >>>>
> > >>> >>>> Needs some cleanup which probably the worst can be bash
> scripted.
> > >>> >>>>
> > >>> >>>> Have sent a PR back to the activemq-web on github for others to
> > see.
> > >>> >>>>
> > >>> >>>> Mike
> > >>> >>>>
> > >>> >>>> Sent from my iPhone
> > >>> >>>>
> > >>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <bruce.snyder@gmail.com
> >
> > >>> wrote:
> > >>> >>>>>
> > >>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the
> > others
> > >>> should
> > >>> >>>>> propagate in time). But I see that it's already more
> > comprehensive
> > >>> than
> > >>> >>>> the
> > >>> >>>>> HTML that I pushed because it contains all the directories. We
> > >>> should
> > >>> >>>>> probably wipe out the master branch and choose one of yours as
> > the
> > >>> new
> > >>> >>>>> master branch.
> > >>> >>>>>
> > >>> >>>>> Bruce
> > >>> >>>>>
> > >>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <
> dkulp@apache.org>
> > >>> wrote:
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> I hacked the Confluence exporter a bit to grab the page
> content
> > in
> > >>> >>>>>> different formats so we can see if one is easier to migrate or
> > >>> >>>> similar.   I
> > >>> >>>>>> just pushed 3 new branches to this repo:
> > >>> >>>>>>
> > >>> >>>>>> body.only - this is basically the same HTML, but with all the
> > >>> “wrapper”
> > >>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
> > >>> navigation
> > >>> >>>> or
> > >>> >>>>>> header/footer, etc…
> > >>> >>>>>>
> > >>> >>>>>> body.storage - this is the raw storage format of the data from
> > >>> >>>>>> confluence.   Things like code snippets are in storage format
> > >>> >>>>>> (<structured-macro name=“code” …>), etc.
> > >>> >>>>>>
> > >>> >>>>>> body.view - confluence has a “body.view” mode that is between
> > the
> > >>> >>>>>> “storage” format and not really the exported HTML.     The
> > >>> structured
> > >>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but
> > not
> > >>> >>>> really in
> > >>> >>>>>> final HTML form either.
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> Anyway, if interested in converting content, one of the above
> > >>> might be a
> > >>> >>>>>> better starting point.
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>> Dan
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com>
> > >>> >>>>>> wrote:
> > >>> >>>>>>>
> > >>> >>>>>>> The HTML is available in the repo now. This HTML is just
> what I
> > >>> grabbed
> > >>> >>>>>>> from the public directory. Even if it's not comprehensive,
> it's
> > >>> good
> > >>> >>>>>> enough
> > >>> >>>>>>> for hacking around to figure out what we'd like to do.
> > >>> >>>>>>>
> > >>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure
> out
> > >>> why the
> > >>> >>>>>>> Confluence export is failing.
> > >>> >>>>>>>
> > >>> >>>>>>> Bruce
> > >>> >>>>>>>
> > >>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com
> > >>> >>>>>
> > >>> >>>>>>> wrote:
> > >>> >>>>>>>
> > >>> >>>>>>>> Yep, that is correct, Dan:
> > >>> >>>>>>>>
> > >>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > >>> >>>>>>>>
> > >>> >>>>>>>> I pushed my changes to the repo. Now they just need to
> > >>> propagate to
> > >>> >>>> the
> > >>> >>>>>>>> Github web UI.
> > >>> >>>>>>>>
> > >>> >>>>>>>> Bruce
> > >>> >>>>>>>>
> > >>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
> > >>> dkulp@apache.org>
> > >>> >>>> wrote:
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> Isn’t the push address supposed to be:
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> Dan
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
> > >>> bruce.snyder@gmail.com>
> > >>> >>>>>>>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not
> > have
> > >>> >>>>>>>>> permissions
> > >>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Bruce
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
> > >>> mtaylor@redhat.com>
> > >>> >>>>>>>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> > >>> >>>>>> bruce.snyder@gmail.com>
> > >>> >>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>>> I had the following empty git repo created to hold the
> > HTML
> > >>> from
> > >>> >>>> the
> > >>> >>>>>>>>>>>> current website:
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> https://github.com/apache/activemq-web
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
> > >>> directly
> > >>> >>>> to
> > >>> >>>>>> a
> > >>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull
> > request
> > >>> but
> > >>> >>>>>> Github
> > >>> >>>>>>>>>>> does
> > >>> >>>>>>>>>>>> not allow a pull request on an empty repo.
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
> > i.e.
> > >>> >>>> git://
> > >>> >>>>>>>>>>> git.apache.org/activemq-web.git
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>> This is the workflow we currently use, we push directly
> to
> > >>> the ASF
> > >>> >>>>>>>>> repo.
> > >>> >>>>>>>>>>> PRs are really only used for review and discussion.  I
> > tried
> > >>> to
> > >>> >>>> push
> > >>> >>>>>>>>>>> directly this morning but looks like I don't have write
> > >>> >>>> permissions.
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess
> I
> > >>> could
> > >>> >>>> ask
> > >>> >>>>>>>>> ASF
> > >>> >>>>>>>>>>>> Infra to push it.
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Bruce
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> > >>> >>>>>> bruce.snyder@gmail.com
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> I'm going to address all the questions to me in this
> > single
> > >>> >>>> reply.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
> > >>> >>>> Confluence,
> > >>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images
> > in
> > >>> a git
> > >>> >>>>>>>>> repo.
> > >>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML,
> especially
> > >>> the
> > >>> >>>> HTML
> > >>> >>>>>>>>>>>> exported
> > >>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could
> use
> > >>> Jekyll +
> > >>> >>>>>>>>> SAAS
> > >>> >>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
> > >>> produced a
> > >>> >>>>>> mockup
> > >>> >>>>>>>>> of
> > >>> >>>>>>>>>>>>> this using the Apache Metro website as an example
> > (because
> > >>> it
> > >>> >>>>>> already
> > >>> >>>>>>>>>>>> makes
> > >>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me
> that
> > we
> > >>> >>>> should
> > >>> >>>>>>>>> take
> > >>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
> > >>> export of
> > >>> >>>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup,
> you
> > >>> should
> > >>> >>>>>>>>> really
> > >>> >>>>>>>>>>>>> take a look.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is
> automagically
> > >>> >>>> exported
> > >>> >>>>>>>>> from
> > >>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see
> at
> > >>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
> > using
> > >>> >>>>>> text2html
> > >>> >>>>>>>>>>> and
> > >>> >>>>>>>>>>>>> the conversion it does is pretty awful and would
> require
> > a
> > >>> lot of
> > >>> >>>>>>>>> hand
> > >>> >>>>>>>>>>>> work
> > >>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are
> > 1600+
> > >>> pages
> > >>> >>>> of
> > >>> >>>>>>>>>>> HTML
> > >>> >>>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> manually edit. But I later realized that it was only
> > about
> > >>> 950
> > >>> >>>> HTML
> > >>> >>>>>>>>>>> pages
> > >>> >>>>>>>>>>>>> (from what I can tell so far).
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
> > >>> converter
> > >>> >>>> built
> > >>> >>>>>> on
> > >>> >>>>>>>>>>> top
> > >>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the
> HTML
> > >>> from
> > >>> >>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works
> based
> > >>> on the
> > >>> >>>>>>>>>>>> Confluence
> > >>> >>>>>>>>>>>>> export function which is different from how the HTML is
> > >>> >>>>>> automagically
> > >>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
> > >>> >>>> NullPointerException
> > >>> >>>>>>>>>>> from
> > >>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due
> > to
> > >>> the
> > >>> >>>>>> CDATA
> > >>> >>>>>>>>> in
> > >>> >>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>> search function on the Navigation page and is
> suggesting
> > >>> that the
> > >>> >>>>>>>>>>>> solution
> > >>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
> > >>> >>>> suggestion
> > >>> >>>>>> is
> > >>> >>>>>>>>>>>> that
> > >>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
> > >>> >>>> right-hand
> > >>> >>>>>>>>> side
> > >>> >>>>>>>>>>>> of
> > >>> >>>>>>>>>>>>> the site -- not what we want.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> I have also given some thought to the idea that
> removing
> > >>> the
> > >>> >>>>>> current
> > >>> >>>>>>>>>>> site
> > >>> >>>>>>>>>>>>> will break all links to old site. This is something
> that
> > >>> cannot
> > >>> >>>> be
> > >>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
> > >>> leave users
> > >>> >>>>>> who
> > >>> >>>>>>>>>>>> have
> > >>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
> > >>> problem to
> > >>> >>>>>>>>> solve
> > >>> >>>>>>>>>>>> this
> > >>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
> > Infra
> > >>> is
> > >>> >>>>>> willing
> > >>> >>>>>>>>>>> to
> > >>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
> > >>> investigated
> > >>> >>>>>>>>> when
> > >>> >>>>>>>>>>> we
> > >>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we
> > >>> need to
> > >>> >>>>>> decide
> > >>> >>>>>>>>>>> the
> > >>> >>>>>>>>>>>>> best path forward based on what I have described above
> in
> > >>> the
> > >>> >>>>>>>>> preceding
> > >>> >>>>>>>>>>>>> paragraphs.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Bruce
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> > >>> >>>>>> mtaylor@redhat.com>
> > >>> >>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> I was thinking there would be a single css file for
> all
> > >>> the
> > >>> >>>> pages.
> > >>> >>>>>>>>>>> But
> > >>> >>>>>>>>>>>> I
> > >>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
> > when
> > >>> Bruce
> > >>> >>>>>>>>> pushes
> > >>> >>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>>> export.
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> Cheers
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> > >>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
> > >>> >>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to
> start
> > >>> doing
> > >>> >>>> css
> > >>> >>>>>>>>>>>>>> styles.
> > >>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far
> > >>> off.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not
> all
> > >>> just to
> > >>> >>>>>> try
> > >>> >>>>>>>>>>>> and
> > >>> >>>>>>>>>>>>>>> see what it is like.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> > >>> >>>>>>>>>>> clebert.suconic@gmail.com>
> > >>> >>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a
> > big
> > >>> >>>> task, I
> > >>> >>>>>>>>>>>>>> suspect
> > >>> >>>>>>>>>>>>>>> any
> > >>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
> > >>> issues.
> > >>> >>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
> > >>> landing
> > >>> >>>>>> page
> > >>> >>>>>>>>>>>> that
> > >>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together,
> > and
> > >>> >>>>>>>>>>>> refresh/align
> > >>> >>>>>>>>>>>>>>> the
> > >>> >>>>>>>>>>>>>>>>> existing content with some CSS?
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
> > >>> thought that
> > >>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier
> than
> > >>> >>>>>> converting
> > >>> >>>>>>>>>>>> them
> > >>> >>>>>>>>>>>>>>>> to another .css...
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
> > >>> thought .md
> > >>> >>>>>> would
> > >>> >>>>>>>>>>>> be
> > >>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> --
> > >>> >>>>>>>>>>>>> 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
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> --
> > >>> >>>>>>>>> Daniel Kulp
> > >>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
> > >>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
> > >>> >>>>>>>>>
> > >>> >>>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>>>> --
> > >>> >>>>>>>> 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
> > >>> >>>>>>
> > >>> >>>>>> --
> > >>> >>>>>> Daniel Kulp
> > >>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
> > >>> >>>>>> Talend Community Coder - http://coders.talend.com
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>
> > >>> >>>>>
> > >>> >>>>> --
> > >>> >>>>> 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
> > >>
> > >
> > >
> > >
> > > --
> > > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
Bruce, All

We organised a webex discussion on the dev list[1] where we discussed
Michael's proposal and created a bunch of JIRA[2] that we think are needed
in order to move forward with the proposal.  Unfortunately only a handful
of people attended.  There is concern that a lot of work will be put into
building a new site based on Michael's proposal only for it to get -1 at
the last minute.  For this reason, can I suggest that people take some time
to look into what has been done already by checking out the git repo as
Bruce suggested, or we schedule another webex session where Michael can
talk about his proposal.  We can then take a vote as to whether or not this
is an approach we want to move forward with and what the requirements are
to go live.

Thanks

[1] http://activemq.2283324.n4.nabble.com/Website-Discussion-td4737173.html
[2] https://issues.apache.org/jira/browse/AMQ-6912



On Fri, Mar 16, 2018 at 2:29 AM, Bruce Snyder <br...@gmail.com>
wrote:

> Everyone should take a look at the gitbook that Mike put together. It's a
> great first example.
>
> https://github.com/apache/activemq-web/pull/3
>
> Please take 10 minutes to clone the repo, switch to the branch, install
> gitbook, run gitbook and peruse the docs.
>
> Bruce
>
> On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > I'm sorry about the long delays in getting the official export from
> > Confluence, but it took this long to get some resolution on the issue.
> >
> > I now have a full HTML export from Confluence with the exception of the
> > Navigation page. You can grab the zip file of the HTML at the following
> URL:
> >
> > https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
> > oDtZxt8mFZlX/view?usp=sharing
> >
> > Bruce
> >
> > On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> Bruce
> >>
> >> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
> >> michael.andre.pearce@me.com> wrote:
> >>
> >>> Hi All,
> >>>
> >>> It’s been a bit quiet on the front of this effort.
> >>>
> >>> I’d like to bump this a bit to get some feedback on the current
> >>> examples, and try agree a plan going forwards and spread the work.
> >>>
> >>> I was speaking with Martyn the other week and we think maybe a brief
> >>> webex to demo what’s been done so far and then discuss.
> >>> Martyn’s offered he can host this using his bluejeans account (thanks)
> >>>
> >>> We are thinking of organising this for the week of 19th Feb.
> >>>
> >>> Any specific people who want to be involved can or cannot make? If not
> >>> I’ll sync up with Martyn to agree and then post a time and date.
> >>>
> >>> Cheers
> >>> Mike
> >>>
> >>>
> >>>
> >>> Sent from my iPhone
> >>>
> >>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
> >>> michael.andre.pearce@me.com> wrote:
> >>> >
> >>> > Just FYI have sent a PR with a link to my branch of this export now
> in
> >>> a GitBook form still needs a lot of TLC but have tried to get a large
> bulk
> >>> done. To provide some skeleton for 5.x documents.
> >>> >
> >>> >
> >>> > Sent from my iPhone
> >>> >
> >>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
> >>> michael.andre.pearce@me.com> wrote:
> >>> >>
> >>> >> Yeah, unfortunately the tool i found wanted just html it blew up
> when
> >>> trying to use modified.
> >>> >>
> >>> >> Like wise there was a couple of pages it couldn’t convert due to a
> >>> css file on import issue but this wasn’t that many.
> >>> >>
> >>> >> Sent from my iPhone
> >>> >>
> >>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
> >>> wrote:
> >>> >>>
> >>> >>> Nice job, based on my spot check of a handful of files, it looks
> much
> >>> >>> better. But we will still need to manually fix all the valid
> tables.
> >>> >>>
> >>> >>> Have you had a chance to look at the other branches that Dan Kulp
> >>> provided?
> >>> >>>
> >>> >>> Bruce
> >>> >>>
> >>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> >>> >>> michael.andre.pearce@me.com> wrote:
> >>> >>>
> >>> >>>> I’ve had some luck auto generating MD files.
> >>> >>>>
> >>> >>>> Needs some cleanup which probably the worst can be bash scripted.
> >>> >>>>
> >>> >>>> Have sent a PR back to the activemq-web on github for others to
> see.
> >>> >>>>
> >>> >>>> Mike
> >>> >>>>
> >>> >>>> Sent from my iPhone
> >>> >>>>
> >>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com>
> >>> wrote:
> >>> >>>>>
> >>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the
> others
> >>> should
> >>> >>>>> propagate in time). But I see that it's already more
> comprehensive
> >>> than
> >>> >>>> the
> >>> >>>>> HTML that I pushed because it contains all the directories. We
> >>> should
> >>> >>>>> probably wipe out the master branch and choose one of yours as
> the
> >>> new
> >>> >>>>> master branch.
> >>> >>>>>
> >>> >>>>> Bruce
> >>> >>>>>
> >>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org>
> >>> wrote:
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>> I hacked the Confluence exporter a bit to grab the page content
> in
> >>> >>>>>> different formats so we can see if one is easier to migrate or
> >>> >>>> similar.   I
> >>> >>>>>> just pushed 3 new branches to this repo:
> >>> >>>>>>
> >>> >>>>>> body.only - this is basically the same HTML, but with all the
> >>> “wrapper”
> >>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
> >>> navigation
> >>> >>>> or
> >>> >>>>>> header/footer, etc…
> >>> >>>>>>
> >>> >>>>>> body.storage - this is the raw storage format of the data from
> >>> >>>>>> confluence.   Things like code snippets are in storage format
> >>> >>>>>> (<structured-macro name=“code” …>), etc.
> >>> >>>>>>
> >>> >>>>>> body.view - confluence has a “body.view” mode that is between
> the
> >>> >>>>>> “storage” format and not really the exported HTML.     The
> >>> structured
> >>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but
> not
> >>> >>>> really in
> >>> >>>>>> final HTML form either.
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>> Anyway, if interested in converting content, one of the above
> >>> might be a
> >>> >>>>>> better starting point.
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>> Dan
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
> >>> bruce.snyder@gmail.com>
> >>> >>>>>> wrote:
> >>> >>>>>>>
> >>> >>>>>>> The HTML is available in the repo now. This HTML is just what I
> >>> grabbed
> >>> >>>>>>> from the public directory. Even if it's not comprehensive, it's
> >>> good
> >>> >>>>>> enough
> >>> >>>>>>> for hacking around to figure out what we'd like to do.
> >>> >>>>>>>
> >>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure out
> >>> why the
> >>> >>>>>>> Confluence export is failing.
> >>> >>>>>>>
> >>> >>>>>>> Bruce
> >>> >>>>>>>
> >>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
> >>> bruce.snyder@gmail.com
> >>> >>>>>
> >>> >>>>>>> wrote:
> >>> >>>>>>>
> >>> >>>>>>>> Yep, that is correct, Dan:
> >>> >>>>>>>>
> >>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>> >>>>>>>>
> >>> >>>>>>>> I pushed my changes to the repo. Now they just need to
> >>> propagate to
> >>> >>>> the
> >>> >>>>>>>> Github web UI.
> >>> >>>>>>>>
> >>> >>>>>>>> Bruce
> >>> >>>>>>>>
> >>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
> >>> dkulp@apache.org>
> >>> >>>> wrote:
> >>> >>>>>>>>>
> >>> >>>>>>>>>
> >>> >>>>>>>>> Isn’t the push address supposed to be:
> >>> >>>>>>>>>
> >>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>> >>>>>>>>>
> >>> >>>>>>>>>
> >>> >>>>>>>>> Dan
> >>> >>>>>>>>>
> >>> >>>>>>>>>
> >>> >>>>>>>>>
> >>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
> >>> bruce.snyder@gmail.com>
> >>> >>>>>>>>> wrote:
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not
> have
> >>> >>>>>>>>> permissions
> >>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> Bruce
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
> >>> mtaylor@redhat.com>
> >>> >>>>>>>>> wrote:
> >>> >>>>>>>>>>
> >>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> >>> >>>>>> bruce.snyder@gmail.com>
> >>> >>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>>> I had the following empty git repo created to hold the
> HTML
> >>> from
> >>> >>>> the
> >>> >>>>>>>>>>>> current website:
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> https://github.com/apache/activemq-web
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
> >>> directly
> >>> >>>> to
> >>> >>>>>> a
> >>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull
> request
> >>> but
> >>> >>>>>> Github
> >>> >>>>>>>>>>> does
> >>> >>>>>>>>>>>> not allow a pull request on an empty repo.
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.
> i.e.
> >>> >>>> git://
> >>> >>>>>>>>>>> git.apache.org/activemq-web.git
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>> This is the workflow we currently use, we push directly to
> >>> the ASF
> >>> >>>>>>>>> repo.
> >>> >>>>>>>>>>> PRs are really only used for review and discussion.  I
> tried
> >>> to
> >>> >>>> push
> >>> >>>>>>>>>>> directly this morning but looks like I don't have write
> >>> >>>> permissions.
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I
> >>> could
> >>> >>>> ask
> >>> >>>>>>>>> ASF
> >>> >>>>>>>>>>>> Infra to push it.
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Bruce
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> >>> >>>>>> bruce.snyder@gmail.com
> >>> >>>>>>>>>>
> >>> >>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>>> I'm going to address all the questions to me in this
> single
> >>> >>>> reply.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
> >>> >>>> Confluence,
> >>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images
> in
> >>> a git
> >>> >>>>>>>>> repo.
> >>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially
> >>> the
> >>> >>>> HTML
> >>> >>>>>>>>>>>> exported
> >>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use
> >>> Jekyll +
> >>> >>>>>>>>> SAAS
> >>> >>>>>>>>>>> to
> >>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
> >>> produced a
> >>> >>>>>> mockup
> >>> >>>>>>>>> of
> >>> >>>>>>>>>>>>> this using the Apache Metro website as an example
> (because
> >>> it
> >>> >>>>>> already
> >>> >>>>>>>>>>>> makes
> >>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that
> we
> >>> >>>> should
> >>> >>>>>>>>> take
> >>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
> >>> export of
> >>> >>>>>>>>>>>> Confluence
> >>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you
> >>> should
> >>> >>>>>>>>> really
> >>> >>>>>>>>>>>>> take a look.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
> >>> >>>> exported
> >>> >>>>>>>>> from
> >>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see at
> >>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it
> using
> >>> >>>>>> text2html
> >>> >>>>>>>>>>> and
> >>> >>>>>>>>>>>>> the conversion it does is pretty awful and would require
> a
> >>> lot of
> >>> >>>>>>>>> hand
> >>> >>>>>>>>>>>> work
> >>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are
> 1600+
> >>> pages
> >>> >>>> of
> >>> >>>>>>>>>>> HTML
> >>> >>>>>>>>>>>> to
> >>> >>>>>>>>>>>>> manually edit. But I later realized that it was only
> about
> >>> 950
> >>> >>>> HTML
> >>> >>>>>>>>>>> pages
> >>> >>>>>>>>>>>>> (from what I can tell so far).
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
> >>> converter
> >>> >>>> built
> >>> >>>>>> on
> >>> >>>>>>>>>>> top
> >>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML
> >>> from
> >>> >>>>>>>>>>> Confluence
> >>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works based
> >>> on the
> >>> >>>>>>>>>>>> Confluence
> >>> >>>>>>>>>>>>> export function which is different from how the HTML is
> >>> >>>>>> automagically
> >>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
> >>> >>>> NullPointerException
> >>> >>>>>>>>>>> from
> >>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due
> to
> >>> the
> >>> >>>>>> CDATA
> >>> >>>>>>>>> in
> >>> >>>>>>>>>>>> the
> >>> >>>>>>>>>>>>> search function on the Navigation page and is suggesting
> >>> that the
> >>> >>>>>>>>>>>> solution
> >>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
> >>> >>>> suggestion
> >>> >>>>>> is
> >>> >>>>>>>>>>>> that
> >>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
> >>> >>>> right-hand
> >>> >>>>>>>>> side
> >>> >>>>>>>>>>>> of
> >>> >>>>>>>>>>>>> the site -- not what we want.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> I have also given some thought to the idea that removing
> >>> the
> >>> >>>>>> current
> >>> >>>>>>>>>>> site
> >>> >>>>>>>>>>>>> will break all links to old site. This is something that
> >>> cannot
> >>> >>>> be
> >>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
> >>> leave users
> >>> >>>>>> who
> >>> >>>>>>>>>>>> have
> >>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
> >>> problem to
> >>> >>>>>>>>> solve
> >>> >>>>>>>>>>>> this
> >>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF
> Infra
> >>> is
> >>> >>>>>> willing
> >>> >>>>>>>>>>> to
> >>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
> >>> investigated
> >>> >>>>>>>>> when
> >>> >>>>>>>>>>> we
> >>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we
> >>> need to
> >>> >>>>>> decide
> >>> >>>>>>>>>>> the
> >>> >>>>>>>>>>>>> best path forward based on what I have described above in
> >>> the
> >>> >>>>>>>>> preceding
> >>> >>>>>>>>>>>>> paragraphs.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> Bruce
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> >>> >>>>>> mtaylor@redhat.com>
> >>> >>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> I was thinking there would be a single css file for all
> >>> the
> >>> >>>> pages.
> >>> >>>>>>>>>>> But
> >>> >>>>>>>>>>>> I
> >>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around
> when
> >>> Bruce
> >>> >>>>>>>>> pushes
> >>> >>>>>>>>>>>> the
> >>> >>>>>>>>>>>>>> export.
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> Cheers
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
> >>> >>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start
> >>> doing
> >>> >>>> css
> >>> >>>>>>>>>>>>>> styles.
> >>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far
> >>> off.
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all
> >>> just to
> >>> >>>>>> try
> >>> >>>>>>>>>>>> and
> >>> >>>>>>>>>>>>>>> see what it is like.
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> >>> >>>>>>>>>>> clebert.suconic@gmail.com>
> >>> >>>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a
> big
> >>> >>>> task, I
> >>> >>>>>>>>>>>>>> suspect
> >>> >>>>>>>>>>>>>>> any
> >>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
> >>> issues.
> >>> >>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
> >>> landing
> >>> >>>>>> page
> >>> >>>>>>>>>>>> that
> >>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together,
> and
> >>> >>>>>>>>>>>> refresh/align
> >>> >>>>>>>>>>>>>>> the
> >>> >>>>>>>>>>>>>>>>> existing content with some CSS?
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
> >>> thought that
> >>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
> >>> >>>>>> converting
> >>> >>>>>>>>>>>> them
> >>> >>>>>>>>>>>>>>>> to another .css...
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
> >>> thought .md
> >>> >>>>>> would
> >>> >>>>>>>>>>>> be
> >>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> --
> >>> >>>>>>>>>>>>> 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
> >>> >>>>>>>>>
> >>> >>>>>>>>> --
> >>> >>>>>>>>> Daniel Kulp
> >>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
> >>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
> >>> >>>>>>>>>
> >>> >>>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>> --
> >>> >>>>>>>> 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
> >>> >>>>>>
> >>> >>>>>> --
> >>> >>>>>> Daniel Kulp
> >>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
> >>> >>>>>> Talend Community Coder - http://coders.talend.com
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>
> >>> >>>>>
> >>> >>>>> --
> >>> >>>>> 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
> >>
> >
> >
> >
> > --
> > 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Everyone should take a look at the gitbook that Mike put together. It's a
great first example.

https://github.com/apache/activemq-web/pull/3

Please take 10 minutes to clone the repo, switch to the branch, install
gitbook, run gitbook and peruse the docs.

Bruce

On Wed, Feb 7, 2018 at 10:11 AM, Bruce Snyder <br...@gmail.com>
wrote:

> I'm sorry about the long delays in getting the official export from
> Confluence, but it took this long to get some resolution on the issue.
>
> I now have a full HTML export from Confluence with the exception of the
> Navigation page. You can grab the zip file of the HTML at the following URL:
>
> https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-
> oDtZxt8mFZlX/view?usp=sharing
>
> Bruce
>
> On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
>> +1
>>
>> Bruce
>>
>> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
>> michael.andre.pearce@me.com> wrote:
>>
>>> Hi All,
>>>
>>> It’s been a bit quiet on the front of this effort.
>>>
>>> I’d like to bump this a bit to get some feedback on the current
>>> examples, and try agree a plan going forwards and spread the work.
>>>
>>> I was speaking with Martyn the other week and we think maybe a brief
>>> webex to demo what’s been done so far and then discuss.
>>> Martyn’s offered he can host this using his bluejeans account (thanks)
>>>
>>> We are thinking of organising this for the week of 19th Feb.
>>>
>>> Any specific people who want to be involved can or cannot make? If not
>>> I’ll sync up with Martyn to agree and then post a time and date.
>>>
>>> Cheers
>>> Mike
>>>
>>>
>>>
>>> Sent from my iPhone
>>>
>>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
>>> michael.andre.pearce@me.com> wrote:
>>> >
>>> > Just FYI have sent a PR with a link to my branch of this export now in
>>> a GitBook form still needs a lot of TLC but have tried to get a large bulk
>>> done. To provide some skeleton for 5.x documents.
>>> >
>>> >
>>> > Sent from my iPhone
>>> >
>>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
>>> michael.andre.pearce@me.com> wrote:
>>> >>
>>> >> Yeah, unfortunately the tool i found wanted just html it blew up when
>>> trying to use modified.
>>> >>
>>> >> Like wise there was a couple of pages it couldn’t convert due to a
>>> css file on import issue but this wasn’t that many.
>>> >>
>>> >> Sent from my iPhone
>>> >>
>>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> Nice job, based on my spot check of a handful of files, it looks much
>>> >>> better. But we will still need to manually fix all the valid tables.
>>> >>>
>>> >>> Have you had a chance to look at the other branches that Dan Kulp
>>> provided?
>>> >>>
>>> >>> Bruce
>>> >>>
>>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>>> >>> michael.andre.pearce@me.com> wrote:
>>> >>>
>>> >>>> I’ve had some luck auto generating MD files.
>>> >>>>
>>> >>>> Needs some cleanup which probably the worst can be bash scripted.
>>> >>>>
>>> >>>> Have sent a PR back to the activemq-web on github for others to see.
>>> >>>>
>>> >>>> Mike
>>> >>>>
>>> >>>> Sent from my iPhone
>>> >>>>
>>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the others
>>> should
>>> >>>>> propagate in time). But I see that it's already more comprehensive
>>> than
>>> >>>> the
>>> >>>>> HTML that I pushed because it contains all the directories. We
>>> should
>>> >>>>> probably wipe out the master branch and choose one of yours as the
>>> new
>>> >>>>> master branch.
>>> >>>>>
>>> >>>>> Bruce
>>> >>>>>
>>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org>
>>> wrote:
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> I hacked the Confluence exporter a bit to grab the page content in
>>> >>>>>> different formats so we can see if one is easier to migrate or
>>> >>>> similar.   I
>>> >>>>>> just pushed 3 new branches to this repo:
>>> >>>>>>
>>> >>>>>> body.only - this is basically the same HTML, but with all the
>>> “wrapper”
>>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
>>> navigation
>>> >>>> or
>>> >>>>>> header/footer, etc…
>>> >>>>>>
>>> >>>>>> body.storage - this is the raw storage format of the data from
>>> >>>>>> confluence.   Things like code snippets are in storage format
>>> >>>>>> (<structured-macro name=“code” …>), etc.
>>> >>>>>>
>>> >>>>>> body.view - confluence has a “body.view” mode that is between the
>>> >>>>>> “storage” format and not really the exported HTML.     The
>>> structured
>>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but not
>>> >>>> really in
>>> >>>>>> final HTML form either.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> Anyway, if interested in converting content, one of the above
>>> might be a
>>> >>>>>> better starting point.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> Dan
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <
>>> bruce.snyder@gmail.com>
>>> >>>>>> wrote:
>>> >>>>>>>
>>> >>>>>>> The HTML is available in the repo now. This HTML is just what I
>>> grabbed
>>> >>>>>>> from the public directory. Even if it's not comprehensive, it's
>>> good
>>> >>>>>> enough
>>> >>>>>>> for hacking around to figure out what we'd like to do.
>>> >>>>>>>
>>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure out
>>> why the
>>> >>>>>>> Confluence export is failing.
>>> >>>>>>>
>>> >>>>>>> Bruce
>>> >>>>>>>
>>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
>>> bruce.snyder@gmail.com
>>> >>>>>
>>> >>>>>>> wrote:
>>> >>>>>>>
>>> >>>>>>>> Yep, that is correct, Dan:
>>> >>>>>>>>
>>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>> >>>>>>>>
>>> >>>>>>>> I pushed my changes to the repo. Now they just need to
>>> propagate to
>>> >>>> the
>>> >>>>>>>> Github web UI.
>>> >>>>>>>>
>>> >>>>>>>> Bruce
>>> >>>>>>>>
>>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <
>>> dkulp@apache.org>
>>> >>>> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>> Isn’t the push address supposed to be:
>>> >>>>>>>>>
>>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>> Dan
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
>>> bruce.snyder@gmail.com>
>>> >>>>>>>>> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not have
>>> >>>>>>>>> permissions
>>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
>>> >>>>>>>>>>
>>> >>>>>>>>>> Bruce
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
>>> mtaylor@redhat.com>
>>> >>>>>>>>> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>>> >>>>>> bruce.snyder@gmail.com>
>>> >>>>>>>>>>> wrote:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>> I had the following empty git repo created to hold the HTML
>>> from
>>> >>>> the
>>> >>>>>>>>>>>> current website:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> https://github.com/apache/activemq-web
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
>>> directly
>>> >>>> to
>>> >>>>>> a
>>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull request
>>> but
>>> >>>>>> Github
>>> >>>>>>>>>>> does
>>> >>>>>>>>>>>> not allow a pull request on an empty repo.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
>>> >>>> git://
>>> >>>>>>>>>>> git.apache.org/activemq-web.git
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> This is the workflow we currently use, we push directly to
>>> the ASF
>>> >>>>>>>>> repo.
>>> >>>>>>>>>>> PRs are really only used for review and discussion.  I tried
>>> to
>>> >>>> push
>>> >>>>>>>>>>> directly this morning but looks like I don't have write
>>> >>>> permissions.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I
>>> could
>>> >>>> ask
>>> >>>>>>>>> ASF
>>> >>>>>>>>>>>> Infra to push it.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Bruce
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>>> >>>>>> bruce.snyder@gmail.com
>>> >>>>>>>>>>
>>> >>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>> I'm going to address all the questions to me in this single
>>> >>>> reply.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
>>> >>>> Confluence,
>>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images in
>>> a git
>>> >>>>>>>>> repo.
>>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially
>>> the
>>> >>>> HTML
>>> >>>>>>>>>>>> exported
>>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use
>>> Jekyll +
>>> >>>>>>>>> SAAS
>>> >>>>>>>>>>> to
>>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce
>>> produced a
>>> >>>>>> mockup
>>> >>>>>>>>> of
>>> >>>>>>>>>>>>> this using the Apache Metro website as an example (because
>>> it
>>> >>>>>> already
>>> >>>>>>>>>>>> makes
>>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
>>> >>>> should
>>> >>>>>>>>> take
>>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
>>> export of
>>> >>>>>>>>>>>> Confluence
>>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you
>>> should
>>> >>>>>>>>> really
>>> >>>>>>>>>>>>> take a look.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
>>> >>>> exported
>>> >>>>>>>>> from
>>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see at
>>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>>> >>>>>> text2html
>>> >>>>>>>>>>> and
>>> >>>>>>>>>>>>> the conversion it does is pretty awful and would require a
>>> lot of
>>> >>>>>>>>> hand
>>> >>>>>>>>>>>> work
>>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+
>>> pages
>>> >>>> of
>>> >>>>>>>>>>> HTML
>>> >>>>>>>>>>>> to
>>> >>>>>>>>>>>>> manually edit. But I later realized that it was only about
>>> 950
>>> >>>> HTML
>>> >>>>>>>>>>> pages
>>> >>>>>>>>>>>>> (from what I can tell so far).
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML
>>> converter
>>> >>>> built
>>> >>>>>> on
>>> >>>>>>>>>>> top
>>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML
>>> from
>>> >>>>>>>>>>> Confluence
>>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works based
>>> on the
>>> >>>>>>>>>>>> Confluence
>>> >>>>>>>>>>>>> export function which is different from how the HTML is
>>> >>>>>> automagically
>>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
>>> >>>> NullPointerException
>>> >>>>>>>>>>> from
>>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to
>>> the
>>> >>>>>> CDATA
>>> >>>>>>>>> in
>>> >>>>>>>>>>>> the
>>> >>>>>>>>>>>>> search function on the Navigation page and is suggesting
>>> that the
>>> >>>>>>>>>>>> solution
>>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
>>> >>>> suggestion
>>> >>>>>> is
>>> >>>>>>>>>>>> that
>>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
>>> >>>> right-hand
>>> >>>>>>>>> side
>>> >>>>>>>>>>>> of
>>> >>>>>>>>>>>>> the site -- not what we want.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> I have also given some thought to the idea that removing
>>> the
>>> >>>>>> current
>>> >>>>>>>>>>> site
>>> >>>>>>>>>>>>> will break all links to old site. This is something that
>>> cannot
>>> >>>> be
>>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to
>>> leave users
>>> >>>>>> who
>>> >>>>>>>>>>>> have
>>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
>>> problem to
>>> >>>>>>>>> solve
>>> >>>>>>>>>>>> this
>>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra
>>> is
>>> >>>>>> willing
>>> >>>>>>>>>>> to
>>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
>>> investigated
>>> >>>>>>>>> when
>>> >>>>>>>>>>> we
>>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we
>>> need to
>>> >>>>>> decide
>>> >>>>>>>>>>> the
>>> >>>>>>>>>>>>> best path forward based on what I have described above in
>>> the
>>> >>>>>>>>> preceding
>>> >>>>>>>>>>>>> paragraphs.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Bruce
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>>> >>>>>> mtaylor@redhat.com>
>>> >>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> I was thinking there would be a single css file for all
>>> the
>>> >>>> pages.
>>> >>>>>>>>>>> But
>>> >>>>>>>>>>>> I
>>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when
>>> Bruce
>>> >>>>>>>>> pushes
>>> >>>>>>>>>>>> the
>>> >>>>>>>>>>>>>> export.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Cheers
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
>>> >>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start
>>> doing
>>> >>>> css
>>> >>>>>>>>>>>>>> styles.
>>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far
>>> off.
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all
>>> just to
>>> >>>>>> try
>>> >>>>>>>>>>>> and
>>> >>>>>>>>>>>>>>> see what it is like.
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>> >>>>>>>>>>> clebert.suconic@gmail.com>
>>> >>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
>>> >>>> task, I
>>> >>>>>>>>>>>>>> suspect
>>> >>>>>>>>>>>>>>> any
>>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
>>> issues.
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
>>> landing
>>> >>>>>> page
>>> >>>>>>>>>>>> that
>>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>> >>>>>>>>>>>> refresh/align
>>> >>>>>>>>>>>>>>> the
>>> >>>>>>>>>>>>>>>>> existing content with some CSS?
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
>>> thought that
>>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
>>> >>>>>> converting
>>> >>>>>>>>>>>> them
>>> >>>>>>>>>>>>>>>> to another .css...
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I
>>> thought .md
>>> >>>>>> would
>>> >>>>>>>>>>>> be
>>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> --
>>> >>>>>>>>>>>>> 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
>>> >>>>>>>>>
>>> >>>>>>>>> --
>>> >>>>>>>>> Daniel Kulp
>>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>> --
>>> >>>>>>>> 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
>>> >>>>>>
>>> >>>>>> --
>>> >>>>>> Daniel Kulp
>>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
>>> >>>>>> Talend Community Coder - http://coders.talend.com
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> --
>>> >>>>> 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
>>
>
>
>
> --
> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
I'm sorry about the long delays in getting the official export from
Confluence, but it took this long to get some resolution on the issue.

I now have a full HTML export from Confluence with the exception of the
Navigation page. You can grab the zip file of the HTML at the following URL:

https://drive.google.com/file/d/1qoTC9KMw8oIzGWwBW1X-oDtZxt8mFZlX/view?usp=sharing

Bruce

On Wed, Feb 7, 2018 at 10:06 AM, Bruce Snyder <br...@gmail.com>
wrote:

> +1
>
> Bruce
>
> On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
> michael.andre.pearce@me.com> wrote:
>
>> Hi All,
>>
>> It’s been a bit quiet on the front of this effort.
>>
>> I’d like to bump this a bit to get some feedback on the current examples,
>> and try agree a plan going forwards and spread the work.
>>
>> I was speaking with Martyn the other week and we think maybe a brief
>> webex to demo what’s been done so far and then discuss.
>> Martyn’s offered he can host this using his bluejeans account (thanks)
>>
>> We are thinking of organising this for the week of 19th Feb.
>>
>> Any specific people who want to be involved can or cannot make? If not
>> I’ll sync up with Martyn to agree and then post a time and date.
>>
>> Cheers
>> Mike
>>
>>
>>
>> Sent from my iPhone
>>
>> > On 20 Dec 2017, at 01:26, Michael André Pearce <
>> michael.andre.pearce@me.com> wrote:
>> >
>> > Just FYI have sent a PR with a link to my branch of this export now in
>> a GitBook form still needs a lot of TLC but have tried to get a large bulk
>> done. To provide some skeleton for 5.x documents.
>> >
>> >
>> > Sent from my iPhone
>> >
>> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
>> michael.andre.pearce@me.com> wrote:
>> >>
>> >> Yeah, unfortunately the tool i found wanted just html it blew up when
>> trying to use modified.
>> >>
>> >> Like wise there was a couple of pages it couldn’t convert due to a css
>> file on import issue but this wasn’t that many.
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com>
>> wrote:
>> >>>
>> >>> Nice job, based on my spot check of a handful of files, it looks much
>> >>> better. But we will still need to manually fix all the valid tables.
>> >>>
>> >>> Have you had a chance to look at the other branches that Dan Kulp
>> provided?
>> >>>
>> >>> Bruce
>> >>>
>> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>> >>> michael.andre.pearce@me.com> wrote:
>> >>>
>> >>>> I’ve had some luck auto generating MD files.
>> >>>>
>> >>>> Needs some cleanup which probably the worst can be bash scripted.
>> >>>>
>> >>>> Have sent a PR back to the activemq-web on github for others to see.
>> >>>>
>> >>>> Mike
>> >>>>
>> >>>> Sent from my iPhone
>> >>>>
>> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> Thanks, Dan. So far I only see the body.storage branch (the others
>> should
>> >>>>> propagate in time). But I see that it's already more comprehensive
>> than
>> >>>> the
>> >>>>> HTML that I pushed because it contains all the directories. We
>> should
>> >>>>> probably wipe out the master branch and choose one of yours as the
>> new
>> >>>>> master branch.
>> >>>>>
>> >>>>> Bruce
>> >>>>>
>> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org>
>> wrote:
>> >>>>>>
>> >>>>>>
>> >>>>>> I hacked the Confluence exporter a bit to grab the page content in
>> >>>>>> different formats so we can see if one is easier to migrate or
>> >>>> similar.   I
>> >>>>>> just pushed 3 new branches to this repo:
>> >>>>>>
>> >>>>>> body.only - this is basically the same HTML, but with all the
>> “wrapper”
>> >>>>>> stuff removed.   Just the HTML of the body content.   So no
>> navigation
>> >>>> or
>> >>>>>> header/footer, etc…
>> >>>>>>
>> >>>>>> body.storage - this is the raw storage format of the data from
>> >>>>>> confluence.   Things like code snippets are in storage format
>> >>>>>> (<structured-macro name=“code” …>), etc.
>> >>>>>>
>> >>>>>> body.view - confluence has a “body.view” mode that is between the
>> >>>>>> “storage” format and not really the exported HTML.     The
>> structured
>> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but not
>> >>>> really in
>> >>>>>> final HTML form either.
>> >>>>>>
>> >>>>>>
>> >>>>>> Anyway, if interested in converting content, one of the above
>> might be a
>> >>>>>> better starting point.
>> >>>>>>
>> >>>>>>
>> >>>>>> Dan
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <bruce.snyder@gmail.com
>> >
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> The HTML is available in the repo now. This HTML is just what I
>> grabbed
>> >>>>>>> from the public directory. Even if it's not comprehensive, it's
>> good
>> >>>>>> enough
>> >>>>>>> for hacking around to figure out what we'd like to do.
>> >>>>>>>
>> >>>>>>> In the meantime, I'm still working with ASF Infra to figure out
>> why the
>> >>>>>>> Confluence export is failing.
>> >>>>>>>
>> >>>>>>> Bruce
>> >>>>>>>
>> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
>> bruce.snyder@gmail.com
>> >>>>>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> Yep, that is correct, Dan:
>> >>>>>>>>
>> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>> >>>>>>>>
>> >>>>>>>> I pushed my changes to the repo. Now they just need to propagate
>> to
>> >>>> the
>> >>>>>>>> Github web UI.
>> >>>>>>>>
>> >>>>>>>> Bruce
>> >>>>>>>>
>> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dkulp@apache.org
>> >
>> >>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Isn’t the push address supposed to be:
>> >>>>>>>>>
>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Dan
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
>> bruce.snyder@gmail.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not have
>> >>>>>>>>> permissions
>> >>>>>>>>>> either. I will contact ASF Infra for assistance.
>> >>>>>>>>>>
>> >>>>>>>>>> Bruce
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
>> mtaylor@redhat.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>> >>>>>> bruce.snyder@gmail.com>
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>>> I had the following empty git repo created to hold the HTML
>> from
>> >>>> the
>> >>>>>>>>>>>> current website:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> https://github.com/apache/activemq-web
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
>> directly
>> >>>> to
>> >>>>>> a
>> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull request
>> but
>> >>>>>> Github
>> >>>>>>>>>>> does
>> >>>>>>>>>>>> not allow a pull request on an empty repo.
>> >>>>>>>>>>>>
>> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
>> >>>> git://
>> >>>>>>>>>>> git.apache.org/activemq-web.git
>> >>>>>>>>>>>
>> >>>>>>>>>>> This is the workflow we currently use, we push directly to
>> the ASF
>> >>>>>>>>> repo.
>> >>>>>>>>>>> PRs are really only used for review and discussion.  I tried
>> to
>> >>>> push
>> >>>>>>>>>>> directly this morning but looks like I don't have write
>> >>>> permissions.
>> >>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I
>> could
>> >>>> ask
>> >>>>>>>>> ASF
>> >>>>>>>>>>>> Infra to push it.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Bruce
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>> >>>>>> bruce.snyder@gmail.com
>> >>>>>>>>>>
>> >>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> I'm going to address all the questions to me in this single
>> >>>> reply.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
>> >>>> Confluence,
>> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images in
>> a git
>> >>>>>>>>> repo.
>> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially
>> the
>> >>>> HTML
>> >>>>>>>>>>>> exported
>> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use
>> Jekyll +
>> >>>>>>>>> SAAS
>> >>>>>>>>>>> to
>> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced
>> a
>> >>>>>> mockup
>> >>>>>>>>> of
>> >>>>>>>>>>>>> this using the Apache Metro website as an example (because
>> it
>> >>>>>> already
>> >>>>>>>>>>>> makes
>> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
>> >>>> should
>> >>>>>>>>> take
>> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
>> export of
>> >>>>>>>>>>>> Confluence
>> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you
>> should
>> >>>>>>>>> really
>> >>>>>>>>>>>>> take a look.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
>> >>>> exported
>> >>>>>>>>> from
>> >>>>>>>>>>>>> Confluence and is hosting the current site that we see at
>> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>> >>>>>> text2html
>> >>>>>>>>>>> and
>> >>>>>>>>>>>>> the conversion it does is pretty awful and would require a
>> lot of
>> >>>>>>>>> hand
>> >>>>>>>>>>>> work
>> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+
>> pages
>> >>>> of
>> >>>>>>>>>>> HTML
>> >>>>>>>>>>>> to
>> >>>>>>>>>>>>> manually edit. But I later realized that it was only about
>> 950
>> >>>> HTML
>> >>>>>>>>>>> pages
>> >>>>>>>>>>>>> (from what I can tell so far).
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
>> >>>> built
>> >>>>>> on
>> >>>>>>>>>>> top
>> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML
>> from
>> >>>>>>>>>>> Confluence
>> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works based on
>> the
>> >>>>>>>>>>>> Confluence
>> >>>>>>>>>>>>> export function which is different from how the HTML is
>> >>>>>> automagically
>> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
>> >>>> NullPointerException
>> >>>>>>>>>>> from
>> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to
>> the
>> >>>>>> CDATA
>> >>>>>>>>> in
>> >>>>>>>>>>>> the
>> >>>>>>>>>>>>> search function on the Navigation page and is suggesting
>> that the
>> >>>>>>>>>>>> solution
>> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
>> >>>> suggestion
>> >>>>>> is
>> >>>>>>>>>>>> that
>> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
>> >>>> right-hand
>> >>>>>>>>> side
>> >>>>>>>>>>>> of
>> >>>>>>>>>>>>> the site -- not what we want.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> I have also given some thought to the idea that removing the
>> >>>>>> current
>> >>>>>>>>>>> site
>> >>>>>>>>>>>>> will break all links to old site. This is something that
>> cannot
>> >>>> be
>> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to leave
>> users
>> >>>>>> who
>> >>>>>>>>>>>> have
>> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
>> problem to
>> >>>>>>>>> solve
>> >>>>>>>>>>>> this
>> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra
>> is
>> >>>>>> willing
>> >>>>>>>>>>> to
>> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
>> investigated
>> >>>>>>>>> when
>> >>>>>>>>>>> we
>> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we need
>> to
>> >>>>>> decide
>> >>>>>>>>>>> the
>> >>>>>>>>>>>>> best path forward based on what I have described above in
>> the
>> >>>>>>>>> preceding
>> >>>>>>>>>>>>> paragraphs.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Bruce
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>> >>>>>> mtaylor@redhat.com>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I was thinking there would be a single css file for all the
>> >>>> pages.
>> >>>>>>>>>>> But
>> >>>>>>>>>>>> I
>> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when
>> Bruce
>> >>>>>>>>> pushes
>> >>>>>>>>>>>> the
>> >>>>>>>>>>>>>> export.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Cheers
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
>> >>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start
>> doing
>> >>>> css
>> >>>>>>>>>>>>>> styles.
>> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all
>> just to
>> >>>>>> try
>> >>>>>>>>>>>> and
>> >>>>>>>>>>>>>>> see what it is like.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>> >>>>>>>>>>> clebert.suconic@gmail.com>
>> >>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
>> >>>> task, I
>> >>>>>>>>>>>>>> suspect
>> >>>>>>>>>>>>>>> any
>> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content
>> issues.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
>> landing
>> >>>>>> page
>> >>>>>>>>>>>> that
>> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>> >>>>>>>>>>>> refresh/align
>> >>>>>>>>>>>>>>> the
>> >>>>>>>>>>>>>>>>> existing content with some CSS?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I
>> thought that
>> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
>> >>>>>> converting
>> >>>>>>>>>>>> them
>> >>>>>>>>>>>>>>>> to another .css...
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I thought
>> .md
>> >>>>>> would
>> >>>>>>>>>>>> be
>> >>>>>>>>>>>>>>>> easier and having a better final presentation.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> --
>> >>>>>>>>>>>>> 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
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Daniel Kulp
>> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>> >>>>>>>>> Talend Community Coder - http://coders.talend.com
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> 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
>> >>>>>>
>> >>>>>> --
>> >>>>>> Daniel Kulp
>> >>>>>> dkulp@apache.org - http://dankulp.com/blog
>> >>>>>> Talend Community Coder - http://coders.talend.com
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> 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
>



-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
+1

Bruce

On Sat, Feb 3, 2018 at 10:30 AM, Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> Hi All,
>
> It’s been a bit quiet on the front of this effort.
>
> I’d like to bump this a bit to get some feedback on the current examples,
> and try agree a plan going forwards and spread the work.
>
> I was speaking with Martyn the other week and we think maybe a brief webex
> to demo what’s been done so far and then discuss.
> Martyn’s offered he can host this using his bluejeans account (thanks)
>
> We are thinking of organising this for the week of 19th Feb.
>
> Any specific people who want to be involved can or cannot make? If not
> I’ll sync up with Martyn to agree and then post a time and date.
>
> Cheers
> Mike
>
>
>
> Sent from my iPhone
>
> > On 20 Dec 2017, at 01:26, Michael André Pearce <
> michael.andre.pearce@me.com> wrote:
> >
> > Just FYI have sent a PR with a link to my branch of this export now in a
> GitBook form still needs a lot of TLC but have tried to get a large bulk
> done. To provide some skeleton for 5.x documents.
> >
> >
> > Sent from my iPhone
> >
> >> On 18 Dec 2017, at 20:26, Michael André Pearce <
> michael.andre.pearce@me.com> wrote:
> >>
> >> Yeah, unfortunately the tool i found wanted just html it blew up when
> trying to use modified.
> >>
> >> Like wise there was a couple of pages it couldn’t convert due to a css
> file on import issue but this wasn’t that many.
> >>
> >> Sent from my iPhone
> >>
> >>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com> wrote:
> >>>
> >>> Nice job, based on my spot check of a handful of files, it looks much
> >>> better. But we will still need to manually fix all the valid tables.
> >>>
> >>> Have you had a chance to look at the other branches that Dan Kulp
> provided?
> >>>
> >>> Bruce
> >>>
> >>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> >>> michael.andre.pearce@me.com> wrote:
> >>>
> >>>> I’ve had some luck auto generating MD files.
> >>>>
> >>>> Needs some cleanup which probably the worst can be bash scripted.
> >>>>
> >>>> Have sent a PR back to the activemq-web on github for others to see.
> >>>>
> >>>> Mike
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com>
> wrote:
> >>>>>
> >>>>> Thanks, Dan. So far I only see the body.storage branch (the others
> should
> >>>>> propagate in time). But I see that it's already more comprehensive
> than
> >>>> the
> >>>>> HTML that I pushed because it contains all the directories. We should
> >>>>> probably wipe out the master branch and choose one of yours as the
> new
> >>>>> master branch.
> >>>>>
> >>>>> Bruce
> >>>>>
> >>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> >>>>>>
> >>>>>>
> >>>>>> I hacked the Confluence exporter a bit to grab the page content in
> >>>>>> different formats so we can see if one is easier to migrate or
> >>>> similar.   I
> >>>>>> just pushed 3 new branches to this repo:
> >>>>>>
> >>>>>> body.only - this is basically the same HTML, but with all the
> “wrapper”
> >>>>>> stuff removed.   Just the HTML of the body content.   So no
> navigation
> >>>> or
> >>>>>> header/footer, etc…
> >>>>>>
> >>>>>> body.storage - this is the raw storage format of the data from
> >>>>>> confluence.   Things like code snippets are in storage format
> >>>>>> (<structured-macro name=“code” …>), etc.
> >>>>>>
> >>>>>> body.view - confluence has a “body.view” mode that is between the
> >>>>>> “storage” format and not really the exported HTML.     The
> structured
> >>>>>> macros are expanded a bit (<script class=“brush: java”…), but not
> >>>> really in
> >>>>>> final HTML form either.
> >>>>>>
> >>>>>>
> >>>>>> Anyway, if interested in converting content, one of the above might
> be a
> >>>>>> better starting point.
> >>>>>>
> >>>>>>
> >>>>>> Dan
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> The HTML is available in the repo now. This HTML is just what I
> grabbed
> >>>>>>> from the public directory. Even if it's not comprehensive, it's
> good
> >>>>>> enough
> >>>>>>> for hacking around to figure out what we'd like to do.
> >>>>>>>
> >>>>>>> In the meantime, I'm still working with ASF Infra to figure out
> why the
> >>>>>>> Confluence export is failing.
> >>>>>>>
> >>>>>>> Bruce
> >>>>>>>
> >>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <
> bruce.snyder@gmail.com
> >>>>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Yep, that is correct, Dan:
> >>>>>>>>
> >>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>>>>>>>
> >>>>>>>> I pushed my changes to the repo. Now they just need to propagate
> to
> >>>> the
> >>>>>>>> Github web UI.
> >>>>>>>>
> >>>>>>>> Bruce
> >>>>>>>>
> >>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Isn’t the push address supposed to be:
> >>>>>>>>>
> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Dan
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <
> bruce.snyder@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thank you for the suggestion, but it looks like I do not have
> >>>>>>>>> permissions
> >>>>>>>>>> either. I will contact ASF Infra for assistance.
> >>>>>>>>>>
> >>>>>>>>>> Bruce
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <
> mtaylor@redhat.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> >>>>>> bruce.snyder@gmail.com>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> I had the following empty git repo created to hold the HTML
> from
> >>>> the
> >>>>>>>>>>>> current website:
> >>>>>>>>>>>>
> >>>>>>>>>>>> https://github.com/apache/activemq-web
> >>>>>>>>>>>>
> >>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed
> directly
> >>>> to
> >>>>>> a
> >>>>>>>>>>>> Github ASF repo. Content can only be added via pull request
> but
> >>>>>> Github
> >>>>>>>>>>> does
> >>>>>>>>>>>> not allow a pull request on an empty repo.
> >>>>>>>>>>>>
> >>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
> >>>> git://
> >>>>>>>>>>> git.apache.org/activemq-web.git
> >>>>>>>>>>>
> >>>>>>>>>>> This is the workflow we currently use, we push directly to the
> ASF
> >>>>>>>>> repo.
> >>>>>>>>>>> PRs are really only used for review and discussion.  I tried to
> >>>> push
> >>>>>>>>>>> directly this morning but looks like I don't have write
> >>>> permissions.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I
> could
> >>>> ask
> >>>>>>>>> ASF
> >>>>>>>>>>>> Infra to push it.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Bruce
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> >>>>>> bruce.snyder@gmail.com
> >>>>>>>>>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> I'm going to address all the questions to me in this single
> >>>> reply.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> My original suggestion was that we export the HTML from
> >>>> Confluence,
> >>>>>>>>>>>>> convert to Markdown and put the Markdown and the images in a
> git
> >>>>>>>>> repo.
> >>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially the
> >>>> HTML
> >>>>>>>>>>>> exported
> >>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use
> Jekyll +
> >>>>>>>>> SAAS
> >>>>>>>>>>> to
> >>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
> >>>>>> mockup
> >>>>>>>>> of
> >>>>>>>>>>>>> this using the Apache Metro website as an example (because it
> >>>>>> already
> >>>>>>>>>>>> makes
> >>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
> >>>> should
> >>>>>>>>> take
> >>>>>>>>>>>>> this path, so I started looking into doing a full, new
> export of
> >>>>>>>>>>>> Confluence
> >>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you
> should
> >>>>>>>>> really
> >>>>>>>>>>>>> take a look.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
> >>>> exported
> >>>>>>>>> from
> >>>>>>>>>>>>> Confluence and is hosting the current site that we see at
> >>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
> >>>>>> text2html
> >>>>>>>>>>> and
> >>>>>>>>>>>>> the conversion it does is pretty awful and would require a
> lot of
> >>>>>>>>> hand
> >>>>>>>>>>>> work
> >>>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+
> pages
> >>>> of
> >>>>>>>>>>> HTML
> >>>>>>>>>>>> to
> >>>>>>>>>>>>> manually edit. But I later realized that it was only about
> 950
> >>>> HTML
> >>>>>>>>>>> pages
> >>>>>>>>>>>>> (from what I can tell so far).
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
> >>>> built
> >>>>>> on
> >>>>>>>>>>> top
> >>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML
> from
> >>>>>>>>>>> Confluence
> >>>>>>>>>>>>> in order to try out the PanDoc converter (it works based on
> the
> >>>>>>>>>>>> Confluence
> >>>>>>>>>>>>> export function which is different from how the HTML is
> >>>>>> automagically
> >>>>>>>>>>>>> converted). Unfortunately, I am running into a
> >>>> NullPointerException
> >>>>>>>>>>> from
> >>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to
> the
> >>>>>> CDATA
> >>>>>>>>> in
> >>>>>>>>>>>> the
> >>>>>>>>>>>>> search function on the Navigation page and is suggesting
> that the
> >>>>>>>>>>>> solution
> >>>>>>>>>>>>> is to remove the Navigation page. The problem with this
> >>>> suggestion
> >>>>>> is
> >>>>>>>>>>>> that
> >>>>>>>>>>>>> it would fundamentally remove all the navigation on the
> >>>> right-hand
> >>>>>>>>> side
> >>>>>>>>>>>> of
> >>>>>>>>>>>>> the site -- not what we want.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I have also given some thought to the idea that removing the
> >>>>>> current
> >>>>>>>>>>> site
> >>>>>>>>>>>>> will break all links to old site. This is something that
> cannot
> >>>> be
> >>>>>>>>>>>>> overlooked and must be prevented as we do not want to leave
> users
> >>>>>> who
> >>>>>>>>>>>> have
> >>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy
> problem to
> >>>>>>>>> solve
> >>>>>>>>>>>> this
> >>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
> >>>>>> willing
> >>>>>>>>>>> to
> >>>>>>>>>>>>> allow us to deploy such custom rules. This should be
> investigated
> >>>>>>>>> when
> >>>>>>>>>>> we
> >>>>>>>>>>>>> get to that point, but we are not there yet. First, we need
> to
> >>>>>> decide
> >>>>>>>>>>> the
> >>>>>>>>>>>>> best path forward based on what I have described above in the
> >>>>>>>>> preceding
> >>>>>>>>>>>>> paragraphs.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Bruce
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> >>>>>> mtaylor@redhat.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> I was thinking there would be a single css file for all the
> >>>> pages.
> >>>>>>>>>>> But
> >>>>>>>>>>>> I
> >>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when
> Bruce
> >>>>>>>>> pushes
> >>>>>>>>>>>> the
> >>>>>>>>>>>>>> export.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Cheers
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >>>>>>>>>>>>>> michael.andre.pearce@me.com>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> What’s 1600 pages between friends....
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start
> doing
> >>>> css
> >>>>>>>>>>>>>> styles.
> >>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all
> just to
> >>>>>> try
> >>>>>>>>>>>> and
> >>>>>>>>>>>>>>> see what it is like.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> >>>>>>>>>>> clebert.suconic@gmail.com>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
> >>>> task, I
> >>>>>>>>>>>>>> suspect
> >>>>>>>>>>>>>>> any
> >>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> At least initially, how about we just create a nice
> landing
> >>>>>> page
> >>>>>>>>>>>> that
> >>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
> >>>>>>>>>>>> refresh/align
> >>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>> existing content with some CSS?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I thought
> that
> >>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
> >>>>>> converting
> >>>>>>>>>>>> them
> >>>>>>>>>>>>>>>> to another .css...
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I thought
> .md
> >>>>>> would
> >>>>>>>>>>>> be
> >>>>>>>>>>>>>>>> easier and having a better final presentation.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> 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
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Daniel Kulp
> >>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
> >>>>>>>>> Talend Community Coder - http://coders.talend.com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> 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
> >>>>>>
> >>>>>> --
> >>>>>> Daniel Kulp
> >>>>>> dkulp@apache.org - http://dankulp.com/blog
> >>>>>> Talend Community Coder - http://coders.talend.com
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
Hi All,

It’s been a bit quiet on the front of this effort. 

I’d like to bump this a bit to get some feedback on the current examples, and try agree a plan going forwards and spread the work.

I was speaking with Martyn the other week and we think maybe a brief webex to demo what’s been done so far and then discuss.
Martyn’s offered he can host this using his bluejeans account (thanks) 

We are thinking of organising this for the week of 19th Feb. 

Any specific people who want to be involved can or cannot make? If not I’ll sync up with Martyn to agree and then post a time and date.

Cheers
Mike



Sent from my iPhone

> On 20 Dec 2017, at 01:26, Michael André Pearce <mi...@me.com> wrote:
> 
> Just FYI have sent a PR with a link to my branch of this export now in a GitBook form still needs a lot of TLC but have tried to get a large bulk done. To provide some skeleton for 5.x documents. 
> 
> 
> Sent from my iPhone
> 
>> On 18 Dec 2017, at 20:26, Michael André Pearce <mi...@me.com> wrote:
>> 
>> Yeah, unfortunately the tool i found wanted just html it blew up when trying to use modified.
>> 
>> Like wise there was a couple of pages it couldn’t convert due to a css file on import issue but this wasn’t that many.
>> 
>> Sent from my iPhone
>> 
>>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com> wrote:
>>> 
>>> Nice job, based on my spot check of a handful of files, it looks much
>>> better. But we will still need to manually fix all the valid tables.
>>> 
>>> Have you had a chance to look at the other branches that Dan Kulp provided?
>>> 
>>> Bruce
>>> 
>>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>>> michael.andre.pearce@me.com> wrote:
>>> 
>>>> I’ve had some luck auto generating MD files.
>>>> 
>>>> Needs some cleanup which probably the worst can be bash scripted.
>>>> 
>>>> Have sent a PR back to the activemq-web on github for others to see.
>>>> 
>>>> Mike
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com> wrote:
>>>>> 
>>>>> Thanks, Dan. So far I only see the body.storage branch (the others should
>>>>> propagate in time). But I see that it's already more comprehensive than
>>>> the
>>>>> HTML that I pushed because it contains all the directories. We should
>>>>> probably wipe out the master branch and choose one of yours as the new
>>>>> master branch.
>>>>> 
>>>>> Bruce
>>>>> 
>>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:
>>>>>> 
>>>>>> 
>>>>>> I hacked the Confluence exporter a bit to grab the page content in
>>>>>> different formats so we can see if one is easier to migrate or
>>>> similar.   I
>>>>>> just pushed 3 new branches to this repo:
>>>>>> 
>>>>>> body.only - this is basically the same HTML, but with all the “wrapper”
>>>>>> stuff removed.   Just the HTML of the body content.   So no navigation
>>>> or
>>>>>> header/footer, etc…
>>>>>> 
>>>>>> body.storage - this is the raw storage format of the data from
>>>>>> confluence.   Things like code snippets are in storage format
>>>>>> (<structured-macro name=“code” …>), etc.
>>>>>> 
>>>>>> body.view - confluence has a “body.view” mode that is between the
>>>>>> “storage” format and not really the exported HTML.     The structured
>>>>>> macros are expanded a bit (<script class=“brush: java”…), but not
>>>> really in
>>>>>> final HTML form either.
>>>>>> 
>>>>>> 
>>>>>> Anyway, if interested in converting content, one of the above might be a
>>>>>> better starting point.
>>>>>> 
>>>>>> 
>>>>>> Dan
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> The HTML is available in the repo now. This HTML is just what I grabbed
>>>>>>> from the public directory. Even if it's not comprehensive, it's good
>>>>>> enough
>>>>>>> for hacking around to figure out what we'd like to do.
>>>>>>> 
>>>>>>> In the meantime, I'm still working with ASF Infra to figure out why the
>>>>>>> Confluence export is failing.
>>>>>>> 
>>>>>>> Bruce
>>>>>>> 
>>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <bruce.snyder@gmail.com
>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Yep, that is correct, Dan:
>>>>>>>> 
>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>>> 
>>>>>>>> I pushed my changes to the repo. Now they just need to propagate to
>>>> the
>>>>>>>> Github web UI.
>>>>>>>> 
>>>>>>>> Bruce
>>>>>>>> 
>>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org>
>>>> wrote:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Isn’t the push address supposed to be:
>>>>>>>>> 
>>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Dan
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Thank you for the suggestion, but it looks like I do not have
>>>>>>>>> permissions
>>>>>>>>>> either. I will contact ASF Infra for assistance.
>>>>>>>>>> 
>>>>>>>>>> Bruce
>>>>>>>>>> 
>>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>>>>>> bruce.snyder@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> I had the following empty git repo created to hold the HTML from
>>>> the
>>>>>>>>>>>> current website:
>>>>>>>>>>>> 
>>>>>>>>>>>> https://github.com/apache/activemq-web
>>>>>>>>>>>> 
>>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed directly
>>>> to
>>>>>> a
>>>>>>>>>>>> Github ASF repo. Content can only be added via pull request but
>>>>>> Github
>>>>>>>>>>> does
>>>>>>>>>>>> not allow a pull request on an empty repo.
>>>>>>>>>>>> 
>>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
>>>> git://
>>>>>>>>>>> git.apache.org/activemq-web.git
>>>>>>>>>>> 
>>>>>>>>>>> This is the workflow we currently use, we push directly to the ASF
>>>>>>>>> repo.
>>>>>>>>>>> PRs are really only used for review and discussion.  I tried to
>>>> push
>>>>>>>>>>> directly this morning but looks like I don't have write
>>>> permissions.
>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I could
>>>> ask
>>>>>>>>> ASF
>>>>>>>>>>>> Infra to push it.
>>>>>>>>>>>> 
>>>>>>>>>>>> Bruce
>>>>>>>>>>>> 
>>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>>>>>> bruce.snyder@gmail.com
>>>>>>>>>> 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> I'm going to address all the questions to me in this single
>>>> reply.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> My original suggestion was that we export the HTML from
>>>> Confluence,
>>>>>>>>>>>>> convert to Markdown and put the Markdown and the images in a git
>>>>>>>>> repo.
>>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially the
>>>> HTML
>>>>>>>>>>>> exported
>>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
>>>>>>>>> SAAS
>>>>>>>>>>> to
>>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
>>>>>> mockup
>>>>>>>>> of
>>>>>>>>>>>>> this using the Apache Metro website as an example (because it
>>>>>> already
>>>>>>>>>>>> makes
>>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
>>>> should
>>>>>>>>> take
>>>>>>>>>>>>> this path, so I started looking into doing a full, new export of
>>>>>>>>>>>> Confluence
>>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
>>>>>>>>> really
>>>>>>>>>>>>> take a look.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
>>>> exported
>>>>>>>>> from
>>>>>>>>>>>>> Confluence and is hosting the current site that we see at
>>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>>>>>> text2html
>>>>>>>>>>> and
>>>>>>>>>>>>> the conversion it does is pretty awful and would require a lot of
>>>>>>>>> hand
>>>>>>>>>>>> work
>>>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages
>>>> of
>>>>>>>>>>> HTML
>>>>>>>>>>>> to
>>>>>>>>>>>>> manually edit. But I later realized that it was only about 950
>>>> HTML
>>>>>>>>>>> pages
>>>>>>>>>>>>> (from what I can tell so far).
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
>>>> built
>>>>>> on
>>>>>>>>>>> top
>>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
>>>>>>>>>>> Confluence
>>>>>>>>>>>>> in order to try out the PanDoc converter (it works based on the
>>>>>>>>>>>> Confluence
>>>>>>>>>>>>> export function which is different from how the HTML is
>>>>>> automagically
>>>>>>>>>>>>> converted). Unfortunately, I am running into a
>>>> NullPointerException
>>>>>>>>>>> from
>>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
>>>>>> CDATA
>>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>>> search function on the Navigation page and is suggesting that the
>>>>>>>>>>>> solution
>>>>>>>>>>>>> is to remove the Navigation page. The problem with this
>>>> suggestion
>>>>>> is
>>>>>>>>>>>> that
>>>>>>>>>>>>> it would fundamentally remove all the navigation on the
>>>> right-hand
>>>>>>>>> side
>>>>>>>>>>>> of
>>>>>>>>>>>>> the site -- not what we want.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I have also given some thought to the idea that removing the
>>>>>> current
>>>>>>>>>>> site
>>>>>>>>>>>>> will break all links to old site. This is something that cannot
>>>> be
>>>>>>>>>>>>> overlooked and must be prevented as we do not want to leave users
>>>>>> who
>>>>>>>>>>>> have
>>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
>>>>>>>>> solve
>>>>>>>>>>>> this
>>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
>>>>>> willing
>>>>>>>>>>> to
>>>>>>>>>>>>> allow us to deploy such custom rules. This should be investigated
>>>>>>>>> when
>>>>>>>>>>> we
>>>>>>>>>>>>> get to that point, but we are not there yet. First, we need to
>>>>>> decide
>>>>>>>>>>> the
>>>>>>>>>>>>> best path forward based on what I have described above in the
>>>>>>>>> preceding
>>>>>>>>>>>>> paragraphs.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Bruce
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>>>>>> mtaylor@redhat.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I was thinking there would be a single css file for all the
>>>> pages.
>>>>>>>>>>> But
>>>>>>>>>>>> I
>>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
>>>>>>>>> pushes
>>>>>>>>>>>> the
>>>>>>>>>>>>>> export.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start doing
>>>> css
>>>>>>>>>>>>>> styles.
>>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
>>>>>> try
>>>>>>>>>>>> and
>>>>>>>>>>>>>>> see what it is like.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>>>>>>>> clebert.suconic@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
>>>> task, I
>>>>>>>>>>>>>> suspect
>>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> At least initially, how about we just create a nice landing
>>>>>> page
>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>>>>>>>>>>> refresh/align
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
>>>>>> converting
>>>>>>>>>>>> them
>>>>>>>>>>>>>>>> to another .css...
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I thought .md
>>>>>> would
>>>>>>>>>>>> be
>>>>>>>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Daniel Kulp
>>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> 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
>>>>>> 
>>>>>> --
>>>>>> Daniel Kulp
>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
Just FYI have sent a PR with a link to my branch of this export now in a GitBook form still needs a lot of TLC but have tried to get a large bulk done. To provide some skeleton for 5.x documents. 


Sent from my iPhone

> On 18 Dec 2017, at 20:26, Michael André Pearce <mi...@me.com> wrote:
> 
> Yeah, unfortunately the tool i found wanted just html it blew up when trying to use modified.
> 
> Like wise there was a couple of pages it couldn’t convert due to a css file on import issue but this wasn’t that many.
> 
> Sent from my iPhone
> 
>> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com> wrote:
>> 
>> Nice job, based on my spot check of a handful of files, it looks much
>> better. But we will still need to manually fix all the valid tables.
>> 
>> Have you had a chance to look at the other branches that Dan Kulp provided?
>> 
>> Bruce
>> 
>> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
>> michael.andre.pearce@me.com> wrote:
>> 
>>> I’ve had some luck auto generating MD files.
>>> 
>>> Needs some cleanup which probably the worst can be bash scripted.
>>> 
>>> Have sent a PR back to the activemq-web on github for others to see.
>>> 
>>> Mike
>>> 
>>> Sent from my iPhone
>>> 
>>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com> wrote:
>>>> 
>>>> Thanks, Dan. So far I only see the body.storage branch (the others should
>>>> propagate in time). But I see that it's already more comprehensive than
>>> the
>>>> HTML that I pushed because it contains all the directories. We should
>>>> probably wipe out the master branch and choose one of yours as the new
>>>> master branch.
>>>> 
>>>> Bruce
>>>> 
>>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:
>>>>> 
>>>>> 
>>>>> I hacked the Confluence exporter a bit to grab the page content in
>>>>> different formats so we can see if one is easier to migrate or
>>> similar.   I
>>>>> just pushed 3 new branches to this repo:
>>>>> 
>>>>> body.only - this is basically the same HTML, but with all the “wrapper”
>>>>> stuff removed.   Just the HTML of the body content.   So no navigation
>>> or
>>>>> header/footer, etc…
>>>>> 
>>>>> body.storage - this is the raw storage format of the data from
>>>>> confluence.   Things like code snippets are in storage format
>>>>> (<structured-macro name=“code” …>), etc.
>>>>> 
>>>>> body.view - confluence has a “body.view” mode that is between the
>>>>> “storage” format and not really the exported HTML.     The structured
>>>>> macros are expanded a bit (<script class=“brush: java”…), but not
>>> really in
>>>>> final HTML form either.
>>>>> 
>>>>> 
>>>>> Anyway, if interested in converting content, one of the above might be a
>>>>> better starting point.
>>>>> 
>>>>> 
>>>>> Dan
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> The HTML is available in the repo now. This HTML is just what I grabbed
>>>>>> from the public directory. Even if it's not comprehensive, it's good
>>>>> enough
>>>>>> for hacking around to figure out what we'd like to do.
>>>>>> 
>>>>>> In the meantime, I'm still working with ASF Infra to figure out why the
>>>>>> Confluence export is failing.
>>>>>> 
>>>>>> Bruce
>>>>>> 
>>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <bruce.snyder@gmail.com
>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> Yep, that is correct, Dan:
>>>>>>> 
>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>> 
>>>>>>> I pushed my changes to the repo. Now they just need to propagate to
>>> the
>>>>>>> Github web UI.
>>>>>>> 
>>>>>>> Bruce
>>>>>>> 
>>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org>
>>> wrote:
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Isn’t the push address supposed to be:
>>>>>>>> 
>>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Dan
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Thank you for the suggestion, but it looks like I do not have
>>>>>>>> permissions
>>>>>>>>> either. I will contact ASF Infra for assistance.
>>>>>>>>> 
>>>>>>>>> Bruce
>>>>>>>>> 
>>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>>>>> bruce.snyder@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> I had the following empty git repo created to hold the HTML from
>>> the
>>>>>>>>>>> current website:
>>>>>>>>>>> 
>>>>>>>>>>> https://github.com/apache/activemq-web
>>>>>>>>>>> 
>>>>>>>>>>> However, I have a conundrum -- content cannot be pushed directly
>>> to
>>>>> a
>>>>>>>>>>> Github ASF repo. Content can only be added via pull request but
>>>>> Github
>>>>>>>>>> does
>>>>>>>>>>> not allow a pull request on an empty repo.
>>>>>>>>>>> 
>>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
>>> git://
>>>>>>>>>> git.apache.org/activemq-web.git
>>>>>>>>>> 
>>>>>>>>>> This is the workflow we currently use, we push directly to the ASF
>>>>>>>> repo.
>>>>>>>>>> PRs are really only used for review and discussion.  I tried to
>>> push
>>>>>>>>>> directly this morning but looks like I don't have write
>>> permissions.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I could
>>> ask
>>>>>>>> ASF
>>>>>>>>>>> Infra to push it.
>>>>>>>>>>> 
>>>>>>>>>>> Bruce
>>>>>>>>>>> 
>>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>>>>> bruce.snyder@gmail.com
>>>>>>>>> 
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> I'm going to address all the questions to me in this single
>>> reply.
>>>>>>>>>>>> 
>>>>>>>>>>>> My original suggestion was that we export the HTML from
>>> Confluence,
>>>>>>>>>>>> convert to Markdown and put the Markdown and the images in a git
>>>>>>>> repo.
>>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially the
>>> HTML
>>>>>>>>>>> exported
>>>>>>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
>>>>>>>> SAAS
>>>>>>>>>> to
>>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
>>>>> mockup
>>>>>>>> of
>>>>>>>>>>>> this using the Apache Metro website as an example (because it
>>>>> already
>>>>>>>>>>> makes
>>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
>>> should
>>>>>>>> take
>>>>>>>>>>>> this path, so I started looking into doing a full, new export of
>>>>>>>>>>> Confluence
>>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
>>>>>>>> really
>>>>>>>>>>>> take a look.
>>>>>>>>>>>> 
>>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
>>> exported
>>>>>>>> from
>>>>>>>>>>>> Confluence and is hosting the current site that we see at
>>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>>>>> text2html
>>>>>>>>>> and
>>>>>>>>>>>> the conversion it does is pretty awful and would require a lot of
>>>>>>>> hand
>>>>>>>>>>> work
>>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages
>>> of
>>>>>>>>>> HTML
>>>>>>>>>>> to
>>>>>>>>>>>> manually edit. But I later realized that it was only about 950
>>> HTML
>>>>>>>>>> pages
>>>>>>>>>>>> (from what I can tell so far).
>>>>>>>>>>>> 
>>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
>>> built
>>>>> on
>>>>>>>>>> top
>>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
>>>>>>>>>> Confluence
>>>>>>>>>>>> in order to try out the PanDoc converter (it works based on the
>>>>>>>>>>> Confluence
>>>>>>>>>>>> export function which is different from how the HTML is
>>>>> automagically
>>>>>>>>>>>> converted). Unfortunately, I am running into a
>>> NullPointerException
>>>>>>>>>> from
>>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
>>>>> CDATA
>>>>>>>> in
>>>>>>>>>>> the
>>>>>>>>>>>> search function on the Navigation page and is suggesting that the
>>>>>>>>>>> solution
>>>>>>>>>>>> is to remove the Navigation page. The problem with this
>>> suggestion
>>>>> is
>>>>>>>>>>> that
>>>>>>>>>>>> it would fundamentally remove all the navigation on the
>>> right-hand
>>>>>>>> side
>>>>>>>>>>> of
>>>>>>>>>>>> the site -- not what we want.
>>>>>>>>>>>> 
>>>>>>>>>>>> I have also given some thought to the idea that removing the
>>>>> current
>>>>>>>>>> site
>>>>>>>>>>>> will break all links to old site. This is something that cannot
>>> be
>>>>>>>>>>>> overlooked and must be prevented as we do not want to leave users
>>>>> who
>>>>>>>>>>> have
>>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
>>>>>>>> solve
>>>>>>>>>>> this
>>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
>>>>> willing
>>>>>>>>>> to
>>>>>>>>>>>> allow us to deploy such custom rules. This should be investigated
>>>>>>>> when
>>>>>>>>>> we
>>>>>>>>>>>> get to that point, but we are not there yet. First, we need to
>>>>> decide
>>>>>>>>>> the
>>>>>>>>>>>> best path forward based on what I have described above in the
>>>>>>>> preceding
>>>>>>>>>>>> paragraphs.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Bruce
>>>>>>>>>>>> 
>>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>>>>> mtaylor@redhat.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> I was thinking there would be a single css file for all the
>>> pages.
>>>>>>>>>> But
>>>>>>>>>>> I
>>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
>>>>>>>> pushes
>>>>>>>>>>> the
>>>>>>>>>>>>> export.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I agree it will be easier to covert to md than to start doing
>>> css
>>>>>>>>>>>>> styles.
>>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
>>>>> try
>>>>>>>>>>> and
>>>>>>>>>>>>>> see what it is like.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>>>>>>> clebert.suconic@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
>>> task, I
>>>>>>>>>>>>> suspect
>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> At least initially, how about we just create a nice landing
>>>>> page
>>>>>>>>>>> that
>>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>>>>>>>>>> refresh/align
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>>>>>>>>>> converting these pages into a doc would be easier than
>>>>> converting
>>>>>>>>>>> them
>>>>>>>>>>>>>>> to another .css...
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> if the conversion needed to be done anyways... I thought .md
>>>>> would
>>>>>>>>>>> be
>>>>>>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> 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
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Daniel Kulp
>>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> 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
>>>>> 
>>>>> --
>>>>> Daniel Kulp
>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>> Talend Community Coder - http://coders.talend.com
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
Yeah, unfortunately the tool i found wanted just html it blew up when trying to use modified.

Like wise there was a couple of pages it couldn’t convert due to a css file on import issue but this wasn’t that many.

Sent from my iPhone

> On 18 Dec 2017, at 19:15, Bruce Snyder <br...@gmail.com> wrote:
> 
> Nice job, based on my spot check of a handful of files, it looks much
> better. But we will still need to manually fix all the valid tables.
> 
> Have you had a chance to look at the other branches that Dan Kulp provided?
> 
> Bruce
> 
> On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
> michael.andre.pearce@me.com> wrote:
> 
>> I’ve had some luck auto generating MD files.
>> 
>> Needs some cleanup which probably the worst can be bash scripted.
>> 
>> Have sent a PR back to the activemq-web on github for others to see.
>> 
>> Mike
>> 
>> Sent from my iPhone
>> 
>>> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com> wrote:
>>> 
>>> Thanks, Dan. So far I only see the body.storage branch (the others should
>>> propagate in time). But I see that it's already more comprehensive than
>> the
>>> HTML that I pushed because it contains all the directories. We should
>>> probably wipe out the master branch and choose one of yours as the new
>>> master branch.
>>> 
>>> Bruce
>>> 
>>>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:
>>>> 
>>>> 
>>>> I hacked the Confluence exporter a bit to grab the page content in
>>>> different formats so we can see if one is easier to migrate or
>> similar.   I
>>>> just pushed 3 new branches to this repo:
>>>> 
>>>> body.only - this is basically the same HTML, but with all the “wrapper”
>>>> stuff removed.   Just the HTML of the body content.   So no navigation
>> or
>>>> header/footer, etc…
>>>> 
>>>> body.storage - this is the raw storage format of the data from
>>>> confluence.   Things like code snippets are in storage format
>>>> (<structured-macro name=“code” …>), etc.
>>>> 
>>>> body.view - confluence has a “body.view” mode that is between the
>>>> “storage” format and not really the exported HTML.     The structured
>>>> macros are expanded a bit (<script class=“brush: java”…), but not
>> really in
>>>> final HTML form either.
>>>> 
>>>> 
>>>> Anyway, if interested in converting content, one of the above might be a
>>>> better starting point.
>>>> 
>>>> 
>>>> Dan
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
>>>> wrote:
>>>>> 
>>>>> The HTML is available in the repo now. This HTML is just what I grabbed
>>>>> from the public directory. Even if it's not comprehensive, it's good
>>>> enough
>>>>> for hacking around to figure out what we'd like to do.
>>>>> 
>>>>> In the meantime, I'm still working with ASF Infra to figure out why the
>>>>> Confluence export is failing.
>>>>> 
>>>>> Bruce
>>>>> 
>>>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <bruce.snyder@gmail.com
>>> 
>>>>> wrote:
>>>>> 
>>>>>> Yep, that is correct, Dan:
>>>>>> 
>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>> 
>>>>>> I pushed my changes to the repo. Now they just need to propagate to
>> the
>>>>>> Github web UI.
>>>>>> 
>>>>>> Bruce
>>>>>> 
>>>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org>
>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> Isn’t the push address supposed to be:
>>>>>>> 
>>>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>>>> 
>>>>>>> 
>>>>>>> Dan
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Thank you for the suggestion, but it looks like I do not have
>>>>>>> permissions
>>>>>>>> either. I will contact ASF Infra for assistance.
>>>>>>>> 
>>>>>>>> Bruce
>>>>>>>> 
>>>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>>>> bruce.snyder@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> I had the following empty git repo created to hold the HTML from
>> the
>>>>>>>>>> current website:
>>>>>>>>>> 
>>>>>>>>>> https://github.com/apache/activemq-web
>>>>>>>>>> 
>>>>>>>>>> However, I have a conundrum -- content cannot be pushed directly
>> to
>>>> a
>>>>>>>>>> Github ASF repo. Content can only be added via pull request but
>>>> Github
>>>>>>>>> does
>>>>>>>>>> not allow a pull request on an empty repo.
>>>>>>>>>> 
>>>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
>> git://
>>>>>>>>> git.apache.org/activemq-web.git
>>>>>>>>> 
>>>>>>>>> This is the workflow we currently use, we push directly to the ASF
>>>>>>> repo.
>>>>>>>>> PRs are really only used for review and discussion.  I tried to
>> push
>>>>>>>>> directly this morning but looks like I don't have write
>> permissions.
>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I could
>> ask
>>>>>>> ASF
>>>>>>>>>> Infra to push it.
>>>>>>>>>> 
>>>>>>>>>> Bruce
>>>>>>>>>> 
>>>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>>>> bruce.snyder@gmail.com
>>>>>>>> 
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> I'm going to address all the questions to me in this single
>> reply.
>>>>>>>>>>> 
>>>>>>>>>>> My original suggestion was that we export the HTML from
>> Confluence,
>>>>>>>>>>> convert to Markdown and put the Markdown and the images in a git
>>>>>>> repo.
>>>>>>>>>>> Markdown is much easier to edit than raw HTML, especially the
>> HTML
>>>>>>>>>> exported
>>>>>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
>>>>>>> SAAS
>>>>>>>>> to
>>>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
>>>> mockup
>>>>>>> of
>>>>>>>>>>> this using the Apache Metro website as an example (because it
>>>> already
>>>>>>>>>> makes
>>>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
>> should
>>>>>>> take
>>>>>>>>>>> this path, so I started looking into doing a full, new export of
>>>>>>>>>> Confluence
>>>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
>>>>>>> really
>>>>>>>>>>> take a look.
>>>>>>>>>>> 
>>>>>>>>>>> So, I manually grabbed the raw HTML that is automagically
>> exported
>>>>>>> from
>>>>>>>>>>> Confluence and is hosting the current site that we see at
>>>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>>>> text2html
>>>>>>>>> and
>>>>>>>>>>> the conversion it does is pretty awful and would require a lot of
>>>>>>> hand
>>>>>>>>>> work
>>>>>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages
>> of
>>>>>>>>> HTML
>>>>>>>>>> to
>>>>>>>>>>> manually edit. But I later realized that it was only about 950
>> HTML
>>>>>>>>> pages
>>>>>>>>>>> (from what I can tell so far).
>>>>>>>>>>> 
>>>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
>> built
>>>> on
>>>>>>>>> top
>>>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
>>>>>>>>> Confluence
>>>>>>>>>>> in order to try out the PanDoc converter (it works based on the
>>>>>>>>>> Confluence
>>>>>>>>>>> export function which is different from how the HTML is
>>>> automagically
>>>>>>>>>>> converted). Unfortunately, I am running into a
>> NullPointerException
>>>>>>>>> from
>>>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
>>>> CDATA
>>>>>>> in
>>>>>>>>>> the
>>>>>>>>>>> search function on the Navigation page and is suggesting that the
>>>>>>>>>> solution
>>>>>>>>>>> is to remove the Navigation page. The problem with this
>> suggestion
>>>> is
>>>>>>>>>> that
>>>>>>>>>>> it would fundamentally remove all the navigation on the
>> right-hand
>>>>>>> side
>>>>>>>>>> of
>>>>>>>>>>> the site -- not what we want.
>>>>>>>>>>> 
>>>>>>>>>>> I have also given some thought to the idea that removing the
>>>> current
>>>>>>>>> site
>>>>>>>>>>> will break all links to old site. This is something that cannot
>> be
>>>>>>>>>>> overlooked and must be prevented as we do not want to leave users
>>>> who
>>>>>>>>>> have
>>>>>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
>>>>>>> solve
>>>>>>>>>> this
>>>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
>>>> willing
>>>>>>>>> to
>>>>>>>>>>> allow us to deploy such custom rules. This should be investigated
>>>>>>> when
>>>>>>>>> we
>>>>>>>>>>> get to that point, but we are not there yet. First, we need to
>>>> decide
>>>>>>>>> the
>>>>>>>>>>> best path forward based on what I have described above in the
>>>>>>> preceding
>>>>>>>>>>> paragraphs.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Bruce
>>>>>>>>>>> 
>>>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>>>> mtaylor@redhat.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> I was thinking there would be a single css file for all the
>> pages.
>>>>>>>>> But
>>>>>>>>>> I
>>>>>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
>>>>>>> pushes
>>>>>>>>>> the
>>>>>>>>>>>> export.
>>>>>>>>>>>> 
>>>>>>>>>>>> Cheers
>>>>>>>>>>>> 
>>>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I agree it will be easier to covert to md than to start doing
>> css
>>>>>>>>>>>> styles.
>>>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
>>>> try
>>>>>>>>>> and
>>>>>>>>>>>>> see what it is like.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>>>>>> clebert.suconic@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
>> task, I
>>>>>>>>>>>> suspect
>>>>>>>>>>>>> any
>>>>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> At least initially, how about we just create a nice landing
>>>> page
>>>>>>>>>> that
>>>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>>>>>>>>> refresh/align
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>>>>>>>>> converting these pages into a doc would be easier than
>>>> converting
>>>>>>>>>> them
>>>>>>>>>>>>>> to another .css...
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> if the conversion needed to be done anyways... I thought .md
>>>> would
>>>>>>>>>> be
>>>>>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> 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
>>>>>>> 
>>>>>>> --
>>>>>>> Daniel Kulp
>>>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>>>> Talend Community Coder - http://coders.talend.com
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> 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
>>>> 
>>>> --
>>>> Daniel Kulp
>>>> dkulp@apache.org - http://dankulp.com/blog
>>>> Talend Community Coder - http://coders.talend.com
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Nice job, based on my spot check of a handful of files, it looks much
better. But we will still need to manually fix all the valid tables.

Have you had a chance to look at the other branches that Dan Kulp provided?

Bruce

On Mon, Dec 18, 2017 at 10:59 AM, Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> I’ve had some luck auto generating MD files.
>
> Needs some cleanup which probably the worst can be bash scripted.
>
> Have sent a PR back to the activemq-web on github for others to see.
>
> Mike
>
> Sent from my iPhone
>
> > On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com> wrote:
> >
> > Thanks, Dan. So far I only see the body.storage branch (the others should
> > propagate in time). But I see that it's already more comprehensive than
> the
> > HTML that I pushed because it contains all the directories. We should
> > probably wipe out the master branch and choose one of yours as the new
> > master branch.
> >
> > Bruce
> >
> >> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:
> >>
> >>
> >> I hacked the Confluence exporter a bit to grab the page content in
> >> different formats so we can see if one is easier to migrate or
> similar.   I
> >> just pushed 3 new branches to this repo:
> >>
> >> body.only - this is basically the same HTML, but with all the “wrapper”
> >> stuff removed.   Just the HTML of the body content.   So no navigation
> or
> >> header/footer, etc…
> >>
> >> body.storage - this is the raw storage format of the data from
> >> confluence.   Things like code snippets are in storage format
> >> (<structured-macro name=“code” …>), etc.
> >>
> >> body.view - confluence has a “body.view” mode that is between the
> >> “storage” format and not really the exported HTML.     The structured
> >> macros are expanded a bit (<script class=“brush: java”…), but not
> really in
> >> final HTML form either.
> >>
> >>
> >> Anyway, if interested in converting content, one of the above might be a
> >> better starting point.
> >>
> >>
> >> Dan
> >>
> >>
> >>
> >>
> >>
> >>
> >>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
> >> wrote:
> >>>
> >>> The HTML is available in the repo now. This HTML is just what I grabbed
> >>> from the public directory. Even if it's not comprehensive, it's good
> >> enough
> >>> for hacking around to figure out what we'd like to do.
> >>>
> >>> In the meantime, I'm still working with ASF Infra to figure out why the
> >>> Confluence export is failing.
> >>>
> >>> Bruce
> >>>
> >>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <bruce.snyder@gmail.com
> >
> >>> wrote:
> >>>
> >>>> Yep, that is correct, Dan:
> >>>>
> >>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>>>
> >>>> I pushed my changes to the repo. Now they just need to propagate to
> the
> >>>> Github web UI.
> >>>>
> >>>> Bruce
> >>>>
> >>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org>
> wrote:
> >>>>>
> >>>>>
> >>>>> Isn’t the push address supposed to be:
> >>>>>
> >>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>>>>
> >>>>>
> >>>>> Dan
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> Thank you for the suggestion, but it looks like I do not have
> >>>>> permissions
> >>>>>> either. I will contact ASF Infra for assistance.
> >>>>>>
> >>>>>> Bruce
> >>>>>>
> >>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
> >>>>> wrote:
> >>>>>>
> >>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> >> bruce.snyder@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> I had the following empty git repo created to hold the HTML from
> the
> >>>>>>>> current website:
> >>>>>>>>
> >>>>>>>> https://github.com/apache/activemq-web
> >>>>>>>>
> >>>>>>>> However, I have a conundrum -- content cannot be pushed directly
> to
> >> a
> >>>>>>>> Github ASF repo. Content can only be added via pull request but
> >> Github
> >>>>>>> does
> >>>>>>>> not allow a pull request on an empty repo.
> >>>>>>>>
> >>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.
> git://
> >>>>>>> git.apache.org/activemq-web.git
> >>>>>>>
> >>>>>>> This is the workflow we currently use, we push directly to the ASF
> >>>>> repo.
> >>>>>>> PRs are really only used for review and discussion.  I tried to
> push
> >>>>>>> directly this morning but looks like I don't have write
> permissions.
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Any ideas on how to get the HTML into the repo? I guess I could
> ask
> >>>>> ASF
> >>>>>>>> Infra to push it.
> >>>>>>>>
> >>>>>>>> Bruce
> >>>>>>>>
> >>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> >> bruce.snyder@gmail.com
> >>>>>>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> I'm going to address all the questions to me in this single
> reply.
> >>>>>>>>>
> >>>>>>>>> My original suggestion was that we export the HTML from
> Confluence,
> >>>>>>>>> convert to Markdown and put the Markdown and the images in a git
> >>>>> repo.
> >>>>>>>>> Markdown is much easier to edit than raw HTML, especially the
> HTML
> >>>>>>>> exported
> >>>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
> >>>>> SAAS
> >>>>>>> to
> >>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
> >> mockup
> >>>>> of
> >>>>>>>>> this using the Apache Metro website as an example (because it
> >> already
> >>>>>>>> makes
> >>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we
> should
> >>>>> take
> >>>>>>>>> this path, so I started looking into doing a full, new export of
> >>>>>>>> Confluence
> >>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
> >>>>> really
> >>>>>>>>> take a look.
> >>>>>>>>>
> >>>>>>>>> So, I manually grabbed the raw HTML that is automagically
> exported
> >>>>> from
> >>>>>>>>> Confluence and is hosting the current site that we see at
> >>>>>>>>> http://activemq.apache.org. I did some testing on it using
> >> text2html
> >>>>>>> and
> >>>>>>>>> the conversion it does is pretty awful and would require a lot of
> >>>>> hand
> >>>>>>>> work
> >>>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages
> of
> >>>>>>> HTML
> >>>>>>>> to
> >>>>>>>>> manually edit. But I later realized that it was only about 950
> HTML
> >>>>>>> pages
> >>>>>>>>> (from what I can tell so far).
> >>>>>>>>>
> >>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter
> built
> >> on
> >>>>>>> top
> >>>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
> >>>>>>> Confluence
> >>>>>>>>> in order to try out the PanDoc converter (it works based on the
> >>>>>>>> Confluence
> >>>>>>>>> export function which is different from how the HTML is
> >> automagically
> >>>>>>>>> converted). Unfortunately, I am running into a
> NullPointerException
> >>>>>>> from
> >>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
> >> CDATA
> >>>>> in
> >>>>>>>> the
> >>>>>>>>> search function on the Navigation page and is suggesting that the
> >>>>>>>> solution
> >>>>>>>>> is to remove the Navigation page. The problem with this
> suggestion
> >> is
> >>>>>>>> that
> >>>>>>>>> it would fundamentally remove all the navigation on the
> right-hand
> >>>>> side
> >>>>>>>> of
> >>>>>>>>> the site -- not what we want.
> >>>>>>>>>
> >>>>>>>>> I have also given some thought to the idea that removing the
> >> current
> >>>>>>> site
> >>>>>>>>> will break all links to old site. This is something that cannot
> be
> >>>>>>>>> overlooked and must be prevented as we do not want to leave users
> >> who
> >>>>>>>> have
> >>>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
> >>>>> solve
> >>>>>>>> this
> >>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
> >> willing
> >>>>>>> to
> >>>>>>>>> allow us to deploy such custom rules. This should be investigated
> >>>>> when
> >>>>>>> we
> >>>>>>>>> get to that point, but we are not there yet. First, we need to
> >> decide
> >>>>>>> the
> >>>>>>>>> best path forward based on what I have described above in the
> >>>>> preceding
> >>>>>>>>> paragraphs.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Bruce
> >>>>>>>>>
> >>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> >> mtaylor@redhat.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> I was thinking there would be a single css file for all the
> pages.
> >>>>>>> But
> >>>>>>>> I
> >>>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
> >>>>> pushes
> >>>>>>>> the
> >>>>>>>>>> export.
> >>>>>>>>>>
> >>>>>>>>>> Cheers
> >>>>>>>>>>
> >>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >>>>>>>>>> michael.andre.pearce@me.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> What’s 1600 pages between friends....
> >>>>>>>>>>>
> >>>>>>>>>>> I agree it will be easier to covert to md than to start doing
> css
> >>>>>>>>>> styles.
> >>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
> >>>>>>>>>>>
> >>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
> >> try
> >>>>>>>> and
> >>>>>>>>>>> see what it is like.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> >>>>>>> clebert.suconic@gmail.com>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big
> task, I
> >>>>>>>>>> suspect
> >>>>>>>>>>> any
> >>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> At least initially, how about we just create a nice landing
> >> page
> >>>>>>>> that
> >>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
> >>>>>>>> refresh/align
> >>>>>>>>>>> the
> >>>>>>>>>>>>> existing content with some CSS?
> >>>>>>>>>>>>
> >>>>>>>>>>>> I was just looking for the minimal effort task. I thought that
> >>>>>>>>>>>> converting these pages into a doc would be easier than
> >> converting
> >>>>>>>> them
> >>>>>>>>>>>> to another .css...
> >>>>>>>>>>>>
> >>>>>>>>>>>> if the conversion needed to be done anyways... I thought .md
> >> would
> >>>>>>>> be
> >>>>>>>>>>>> easier and having a better final presentation.
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> 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
> >>>>>
> >>>>> --
> >>>>> Daniel Kulp
> >>>>> dkulp@apache.org - http://dankulp.com/blog
> >>>>> Talend Community Coder - http://coders.talend.com
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org - http://dankulp.com/blog
> >> Talend Community Coder - http://coders.talend.com
> >>
> >>
> >
> >
> > --
> > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
I’ve had some luck auto generating MD files.

Needs some cleanup which probably the worst can be bash scripted.

Have sent a PR back to the activemq-web on github for others to see.

Mike

Sent from my iPhone

> On 14 Dec 2017, at 16:31, Bruce Snyder <br...@gmail.com> wrote:
> 
> Thanks, Dan. So far I only see the body.storage branch (the others should
> propagate in time). But I see that it's already more comprehensive than the
> HTML that I pushed because it contains all the directories. We should
> probably wipe out the master branch and choose one of yours as the new
> master branch.
> 
> Bruce
> 
>> On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:
>> 
>> 
>> I hacked the Confluence exporter a bit to grab the page content in
>> different formats so we can see if one is easier to migrate or similar.   I
>> just pushed 3 new branches to this repo:
>> 
>> body.only - this is basically the same HTML, but with all the “wrapper”
>> stuff removed.   Just the HTML of the body content.   So no navigation or
>> header/footer, etc…
>> 
>> body.storage - this is the raw storage format of the data from
>> confluence.   Things like code snippets are in storage format
>> (<structured-macro name=“code” …>), etc.
>> 
>> body.view - confluence has a “body.view” mode that is between the
>> “storage” format and not really the exported HTML.     The structured
>> macros are expanded a bit (<script class=“brush: java”…), but not really in
>> final HTML form either.
>> 
>> 
>> Anyway, if interested in converting content, one of the above might be a
>> better starting point.
>> 
>> 
>> Dan
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
>> wrote:
>>> 
>>> The HTML is available in the repo now. This HTML is just what I grabbed
>>> from the public directory. Even if it's not comprehensive, it's good
>> enough
>>> for hacking around to figure out what we'd like to do.
>>> 
>>> In the meantime, I'm still working with ASF Infra to figure out why the
>>> Confluence export is failing.
>>> 
>>> Bruce
>>> 
>>> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>> 
>>>> Yep, that is correct, Dan:
>>>> 
>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>> 
>>>> I pushed my changes to the repo. Now they just need to propagate to the
>>>> Github web UI.
>>>> 
>>>> Bruce
>>>> 
>>>>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org> wrote:
>>>>> 
>>>>> 
>>>>> Isn’t the push address supposed to be:
>>>>> 
>>>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>>>> 
>>>>> 
>>>>> Dan
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> Thank you for the suggestion, but it looks like I do not have
>>>>> permissions
>>>>>> either. I will contact ASF Infra for assistance.
>>>>>> 
>>>>>> Bruce
>>>>>> 
>>>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>>>>> wrote:
>>>>>> 
>>>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
>> bruce.snyder@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> I had the following empty git repo created to hold the HTML from the
>>>>>>>> current website:
>>>>>>>> 
>>>>>>>> https://github.com/apache/activemq-web
>>>>>>>> 
>>>>>>>> However, I have a conundrum -- content cannot be pushed directly to
>> a
>>>>>>>> Github ASF repo. Content can only be added via pull request but
>> Github
>>>>>>> does
>>>>>>>> not allow a pull request on an empty repo.
>>>>>>>> 
>>>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
>>>>>>> git.apache.org/activemq-web.git
>>>>>>> 
>>>>>>> This is the workflow we currently use, we push directly to the ASF
>>>>> repo.
>>>>>>> PRs are really only used for review and discussion.  I tried to push
>>>>>>> directly this morning but looks like I don't have write permissions.
>>>>>>> 
>>>>>>>> 
>>>>>>>> Any ideas on how to get the HTML into the repo? I guess I could ask
>>>>> ASF
>>>>>>>> Infra to push it.
>>>>>>>> 
>>>>>>>> Bruce
>>>>>>>> 
>>>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
>> bruce.snyder@gmail.com
>>>>>> 
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> I'm going to address all the questions to me in this single reply.
>>>>>>>>> 
>>>>>>>>> My original suggestion was that we export the HTML from Confluence,
>>>>>>>>> convert to Markdown and put the Markdown and the images in a git
>>>>> repo.
>>>>>>>>> Markdown is much easier to edit than raw HTML, especially the HTML
>>>>>>>> exported
>>>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
>>>>> SAAS
>>>>>>> to
>>>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
>> mockup
>>>>> of
>>>>>>>>> this using the Apache Metro website as an example (because it
>> already
>>>>>>>> makes
>>>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we should
>>>>> take
>>>>>>>>> this path, so I started looking into doing a full, new export of
>>>>>>>> Confluence
>>>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
>>>>> really
>>>>>>>>> take a look.
>>>>>>>>> 
>>>>>>>>> So, I manually grabbed the raw HTML that is automagically exported
>>>>> from
>>>>>>>>> Confluence and is hosting the current site that we see at
>>>>>>>>> http://activemq.apache.org. I did some testing on it using
>> text2html
>>>>>>> and
>>>>>>>>> the conversion it does is pretty awful and would require a lot of
>>>>> hand
>>>>>>>> work
>>>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages of
>>>>>>> HTML
>>>>>>>> to
>>>>>>>>> manually edit. But I later realized that it was only about 950 HTML
>>>>>>> pages
>>>>>>>>> (from what I can tell so far).
>>>>>>>>> 
>>>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built
>> on
>>>>>>> top
>>>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
>>>>>>> Confluence
>>>>>>>>> in order to try out the PanDoc converter (it works based on the
>>>>>>>> Confluence
>>>>>>>>> export function which is different from how the HTML is
>> automagically
>>>>>>>>> converted). Unfortunately, I am running into a NullPointerException
>>>>>>> from
>>>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
>> CDATA
>>>>> in
>>>>>>>> the
>>>>>>>>> search function on the Navigation page and is suggesting that the
>>>>>>>> solution
>>>>>>>>> is to remove the Navigation page. The problem with this suggestion
>> is
>>>>>>>> that
>>>>>>>>> it would fundamentally remove all the navigation on the right-hand
>>>>> side
>>>>>>>> of
>>>>>>>>> the site -- not what we want.
>>>>>>>>> 
>>>>>>>>> I have also given some thought to the idea that removing the
>> current
>>>>>>> site
>>>>>>>>> will break all links to old site. This is something that cannot be
>>>>>>>>> overlooked and must be prevented as we do not want to leave users
>> who
>>>>>>>> have
>>>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
>>>>> solve
>>>>>>>> this
>>>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
>> willing
>>>>>>> to
>>>>>>>>> allow us to deploy such custom rules. This should be investigated
>>>>> when
>>>>>>> we
>>>>>>>>> get to that point, but we are not there yet. First, we need to
>> decide
>>>>>>> the
>>>>>>>>> best path forward based on what I have described above in the
>>>>> preceding
>>>>>>>>> paragraphs.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Bruce
>>>>>>>>> 
>>>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
>> mtaylor@redhat.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> I was thinking there would be a single css file for all the pages.
>>>>>>> But
>>>>>>>> I
>>>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
>>>>> pushes
>>>>>>>> the
>>>>>>>>>> export.
>>>>>>>>>> 
>>>>>>>>>> Cheers
>>>>>>>>>> 
>>>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>>>> 
>>>>>>>>>>> I agree it will be easier to covert to md than to start doing css
>>>>>>>>>> styles.
>>>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>>>>>>> 
>>>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
>> try
>>>>>>>> and
>>>>>>>>>>> see what it is like.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>>>> clebert.suconic@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
>>>>>>>>>> suspect
>>>>>>>>>>> any
>>>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> At least initially, how about we just create a nice landing
>> page
>>>>>>>> that
>>>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>>>>>>> refresh/align
>>>>>>>>>>> the
>>>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>>>> 
>>>>>>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>>>>>>> converting these pages into a doc would be easier than
>> converting
>>>>>>>> them
>>>>>>>>>>>> to another .css...
>>>>>>>>>>>> 
>>>>>>>>>>>> if the conversion needed to be done anyways... I thought .md
>> would
>>>>>>>> be
>>>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> 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
>>>>> 
>>>>> --
>>>>> Daniel Kulp
>>>>> dkulp@apache.org - http://dankulp.com/blog
>>>>> Talend Community Coder - http://coders.talend.com
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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
>> 
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>> 
>> 
> 
> 
> -- 
> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Thanks, Dan. So far I only see the body.storage branch (the others should
propagate in time). But I see that it's already more comprehensive than the
HTML that I pushed because it contains all the directories. We should
probably wipe out the master branch and choose one of yours as the new
master branch.

Bruce

On Thu, Dec 14, 2017 at 7:56 AM, Daniel Kulp <dk...@apache.org> wrote:

>
> I hacked the Confluence exporter a bit to grab the page content in
> different formats so we can see if one is easier to migrate or similar.   I
> just pushed 3 new branches to this repo:
>
> body.only - this is basically the same HTML, but with all the “wrapper”
> stuff removed.   Just the HTML of the body content.   So no navigation or
> header/footer, etc…
>
> body.storage - this is the raw storage format of the data from
> confluence.   Things like code snippets are in storage format
> (<structured-macro name=“code” …>), etc.
>
> body.view - confluence has a “body.view” mode that is between the
> “storage” format and not really the exported HTML.     The structured
> macros are expanded a bit (<script class=“brush: java”…), but not really in
> final HTML form either.
>
>
> Anyway, if interested in converting content, one of the above might be a
> better starting point.
>
>
> Dan
>
>
>
>
>
>
> > On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com>
> wrote:
> >
> > The HTML is available in the repo now. This HTML is just what I grabbed
> > from the public directory. Even if it's not comprehensive, it's good
> enough
> > for hacking around to figure out what we'd like to do.
> >
> > In the meantime, I'm still working with ASF Infra to figure out why the
> > Confluence export is failing.
> >
> > Bruce
> >
> > On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> >> Yep, that is correct, Dan:
> >>
> >> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>
> >> I pushed my changes to the repo. Now they just need to propagate to the
> >> Github web UI.
> >>
> >> Bruce
> >>
> >> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org> wrote:
> >>
> >>>
> >>> Isn’t the push address supposed to be:
> >>>
> >>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
> >>>
> >>>
> >>> Dan
> >>>
> >>>
> >>>
> >>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
> >>> wrote:
> >>>>
> >>>> Thank you for the suggestion, but it looks like I do not have
> >>> permissions
> >>>> either. I will contact ASF Infra for assistance.
> >>>>
> >>>> Bruce
> >>>>
> >>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
> >>> wrote:
> >>>>
> >>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <
> bruce.snyder@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> I had the following empty git repo created to hold the HTML from the
> >>>>>> current website:
> >>>>>>
> >>>>>> https://github.com/apache/activemq-web
> >>>>>>
> >>>>>> However, I have a conundrum -- content cannot be pushed directly to
> a
> >>>>>> Github ASF repo. Content can only be added via pull request but
> Github
> >>>>> does
> >>>>>> not allow a pull request on an empty repo.
> >>>>>>
> >>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
> >>>>> git.apache.org/activemq-web.git
> >>>>>
> >>>>> This is the workflow we currently use, we push directly to the ASF
> >>> repo.
> >>>>> PRs are really only used for review and discussion.  I tried to push
> >>>>> directly this morning but looks like I don't have write permissions.
> >>>>>
> >>>>>>
> >>>>>> Any ideas on how to get the HTML into the repo? I guess I could ask
> >>> ASF
> >>>>>> Infra to push it.
> >>>>>>
> >>>>>> Bruce
> >>>>>>
> >>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <
> bruce.snyder@gmail.com
> >>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I'm going to address all the questions to me in this single reply.
> >>>>>>>
> >>>>>>> My original suggestion was that we export the HTML from Confluence,
> >>>>>>> convert to Markdown and put the Markdown and the images in a git
> >>> repo.
> >>>>>>> Markdown is much easier to edit than raw HTML, especially the HTML
> >>>>>> exported
> >>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
> >>> SAAS
> >>>>> to
> >>>>>>> craft a new website. In fact, Michael Andre Pearce produced a
> mockup
> >>> of
> >>>>>>> this using the Apache Metro website as an example (because it
> already
> >>>>>> makes
> >>>>>>> use of Jekyll + SAAS). It was enough to convince me that we should
> >>> take
> >>>>>>> this path, so I started looking into doing a full, new export of
> >>>>>> Confluence
> >>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
> >>> really
> >>>>>>> take a look.
> >>>>>>>
> >>>>>>> So, I manually grabbed the raw HTML that is automagically exported
> >>> from
> >>>>>>> Confluence and is hosting the current site that we see at
> >>>>>>> http://activemq.apache.org. I did some testing on it using
> text2html
> >>>>> and
> >>>>>>> the conversion it does is pretty awful and would require a lot of
> >>> hand
> >>>>>> work
> >>>>>>> to fix it. So, we discussed the point that there are 1600+ pages of
> >>>>> HTML
> >>>>>> to
> >>>>>>> manually edit. But I later realized that it was only about 950 HTML
> >>>>> pages
> >>>>>>> (from what I can tell so far).
> >>>>>>>
> >>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built
> on
> >>>>> top
> >>>>>>> of PanDoc. So, I have also been trying to export the HTML from
> >>>>> Confluence
> >>>>>>> in order to try out the PanDoc converter (it works based on the
> >>>>>> Confluence
> >>>>>>> export function which is different from how the HTML is
> automagically
> >>>>>>> converted). Unfortunately, I am running into a NullPointerException
> >>>>> from
> >>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the
> CDATA
> >>> in
> >>>>>> the
> >>>>>>> search function on the Navigation page and is suggesting that the
> >>>>>> solution
> >>>>>>> is to remove the Navigation page. The problem with this suggestion
> is
> >>>>>> that
> >>>>>>> it would fundamentally remove all the navigation on the right-hand
> >>> side
> >>>>>> of
> >>>>>>> the site -- not what we want.
> >>>>>>>
> >>>>>>> I have also given some thought to the idea that removing the
> current
> >>>>> site
> >>>>>>> will break all links to old site. This is something that cannot be
> >>>>>>> overlooked and must be prevented as we do not want to leave users
> who
> >>>>>> have
> >>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
> >>> solve
> >>>>>> this
> >>>>>>> using some mod_rewrite rules, the question is if ASF Infra is
> willing
> >>>>> to
> >>>>>>> allow us to deploy such custom rules. This should be investigated
> >>> when
> >>>>> we
> >>>>>>> get to that point, but we are not there yet. First, we need to
> decide
> >>>>> the
> >>>>>>> best path forward based on what I have described above in the
> >>> preceding
> >>>>>>> paragraphs.
> >>>>>>>
> >>>>>>>
> >>>>>>> Bruce
> >>>>>>>
> >>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <
> mtaylor@redhat.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> I was thinking there would be a single css file for all the pages.
> >>>>> But
> >>>>>> I
> >>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
> >>> pushes
> >>>>>> the
> >>>>>>>> export.
> >>>>>>>>
> >>>>>>>> Cheers
> >>>>>>>>
> >>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >>>>>>>> michael.andre.pearce@me.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> What’s 1600 pages between friends....
> >>>>>>>>>
> >>>>>>>>> I agree it will be easier to covert to md than to start doing css
> >>>>>>>> styles.
> >>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
> >>>>>>>>>
> >>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to
> try
> >>>>>> and
> >>>>>>>>> see what it is like.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> >>>>> clebert.suconic@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
> >>>>>>>> suspect
> >>>>>>>>> any
> >>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
> >>>>>>>>>>>
> >>>>>>>>>>> At least initially, how about we just create a nice landing
> page
> >>>>>> that
> >>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
> >>>>>> refresh/align
> >>>>>>>>> the
> >>>>>>>>>>> existing content with some CSS?
> >>>>>>>>>>
> >>>>>>>>>> I was just looking for the minimal effort task. I thought that
> >>>>>>>>>> converting these pages into a doc would be easier than
> converting
> >>>>>> them
> >>>>>>>>>> to another .css...
> >>>>>>>>>>
> >>>>>>>>>> if the conversion needed to be done anyways... I thought .md
> would
> >>>>>> be
> >>>>>>>>>> easier and having a better final presentation.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> 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
> >>>
> >>> --
> >>> Daniel Kulp
> >>> dkulp@apache.org - http://dankulp.com/blog
> >>> Talend Community Coder - http://coders.talend.com
> >>>
> >>>
> >>
> >>
> >> --
> >> 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
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>


-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Daniel Kulp <dk...@apache.org>.
I hacked the Confluence exporter a bit to grab the page content in different formats so we can see if one is easier to migrate or similar.   I just pushed 3 new branches to this repo:

body.only - this is basically the same HTML, but with all the “wrapper” stuff removed.   Just the HTML of the body content.   So no navigation or header/footer, etc…

body.storage - this is the raw storage format of the data from confluence.   Things like code snippets are in storage format (<structured-macro name=“code” …>), etc.   

body.view - confluence has a “body.view” mode that is between the “storage” format and not really the exported HTML.     The structured macros are expanded a bit (<script class=“brush: java”…), but not really in final HTML form either.


Anyway, if interested in converting content, one of the above might be a better starting point.   


Dan






> On Dec 13, 2017, at 4:49 PM, Bruce Snyder <br...@gmail.com> wrote:
> 
> The HTML is available in the repo now. This HTML is just what I grabbed
> from the public directory. Even if it's not comprehensive, it's good enough
> for hacking around to figure out what we'd like to do.
> 
> In the meantime, I'm still working with ASF Infra to figure out why the
> Confluence export is failing.
> 
> Bruce
> 
> On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <br...@gmail.com>
> wrote:
> 
>> Yep, that is correct, Dan:
>> 
>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>> 
>> I pushed my changes to the repo. Now they just need to propagate to the
>> Github web UI.
>> 
>> Bruce
>> 
>> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org> wrote:
>> 
>>> 
>>> Isn’t the push address supposed to be:
>>> 
>>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>> 
>>> 
>>> Dan
>>> 
>>> 
>>> 
>>>> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>>> 
>>>> Thank you for the suggestion, but it looks like I do not have
>>> permissions
>>>> either. I will contact ASF Infra for assistance.
>>>> 
>>>> Bruce
>>>> 
>>>> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>>> wrote:
>>>> 
>>>>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> I had the following empty git repo created to hold the HTML from the
>>>>>> current website:
>>>>>> 
>>>>>> https://github.com/apache/activemq-web
>>>>>> 
>>>>>> However, I have a conundrum -- content cannot be pushed directly to a
>>>>>> Github ASF repo. Content can only be added via pull request but Github
>>>>> does
>>>>>> not allow a pull request on an empty repo.
>>>>>> 
>>>>> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
>>>>> git.apache.org/activemq-web.git
>>>>> 
>>>>> This is the workflow we currently use, we push directly to the ASF
>>> repo.
>>>>> PRs are really only used for review and discussion.  I tried to push
>>>>> directly this morning but looks like I don't have write permissions.
>>>>> 
>>>>>> 
>>>>>> Any ideas on how to get the HTML into the repo? I guess I could ask
>>> ASF
>>>>>> Infra to push it.
>>>>>> 
>>>>>> Bruce
>>>>>> 
>>>>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <bruce.snyder@gmail.com
>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> I'm going to address all the questions to me in this single reply.
>>>>>>> 
>>>>>>> My original suggestion was that we export the HTML from Confluence,
>>>>>>> convert to Markdown and put the Markdown and the images in a git
>>> repo.
>>>>>>> Markdown is much easier to edit than raw HTML, especially the HTML
>>>>>> exported
>>>>>>> from Confluence (blech!). The idea was that we could use Jekyll +
>>> SAAS
>>>>> to
>>>>>>> craft a new website. In fact, Michael Andre Pearce produced a mockup
>>> of
>>>>>>> this using the Apache Metro website as an example (because it already
>>>>>> makes
>>>>>>> use of Jekyll + SAAS). It was enough to convince me that we should
>>> take
>>>>>>> this path, so I started looking into doing a full, new export of
>>>>>> Confluence
>>>>>>> pages to HTML. If you have not seen Michael's mockup, you should
>>> really
>>>>>>> take a look.
>>>>>>> 
>>>>>>> So, I manually grabbed the raw HTML that is automagically exported
>>> from
>>>>>>> Confluence and is hosting the current site that we see at
>>>>>>> http://activemq.apache.org. I did some testing on it using text2html
>>>>> and
>>>>>>> the conversion it does is pretty awful and would require a lot of
>>> hand
>>>>>> work
>>>>>>> to fix it. So, we discussed the point that there are 1600+ pages of
>>>>> HTML
>>>>>> to
>>>>>>> manually edit. But I later realized that it was only about 950 HTML
>>>>> pages
>>>>>>> (from what I can tell so far).
>>>>>>> 
>>>>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on
>>>>> top
>>>>>>> of PanDoc. So, I have also been trying to export the HTML from
>>>>> Confluence
>>>>>>> in order to try out the PanDoc converter (it works based on the
>>>>>> Confluence
>>>>>>> export function which is different from how the HTML is automagically
>>>>>>> converted). Unfortunately, I am running into a NullPointerException
>>>>> from
>>>>>>> Confluence. ASF Infra is telling me that the NPE is due to the CDATA
>>> in
>>>>>> the
>>>>>>> search function on the Navigation page and is suggesting that the
>>>>>> solution
>>>>>>> is to remove the Navigation page. The problem with this suggestion is
>>>>>> that
>>>>>>> it would fundamentally remove all the navigation on the right-hand
>>> side
>>>>>> of
>>>>>>> the site -- not what we want.
>>>>>>> 
>>>>>>> I have also given some thought to the idea that removing the current
>>>>> site
>>>>>>> will break all links to old site. This is something that cannot be
>>>>>>> overlooked and must be prevented as we do not want to leave users who
>>>>>> have
>>>>>>> bookmarked a page high and dry. This is a fairly easy problem to
>>> solve
>>>>>> this
>>>>>>> using some mod_rewrite rules, the question is if ASF Infra is willing
>>>>> to
>>>>>>> allow us to deploy such custom rules. This should be investigated
>>> when
>>>>> we
>>>>>>> get to that point, but we are not there yet. First, we need to decide
>>>>> the
>>>>>>> best path forward based on what I have described above in the
>>> preceding
>>>>>>> paragraphs.
>>>>>>> 
>>>>>>> 
>>>>>>> Bruce
>>>>>>> 
>>>>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> I was thinking there would be a single css file for all the pages.
>>>>> But
>>>>>> I
>>>>>>>> haven't seen the files yet. Let's have a play around when Bruce
>>> pushes
>>>>>> the
>>>>>>>> export.
>>>>>>>> 
>>>>>>>> Cheers
>>>>>>>> 
>>>>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>>>>> michael.andre.pearce@me.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> What’s 1600 pages between friends....
>>>>>>>>> 
>>>>>>>>> I agree it will be easier to covert to md than to start doing css
>>>>>>>> styles.
>>>>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>>>>> 
>>>>>>>>> It be good to get some samples (eg 50 pages) if not all just to try
>>>>>> and
>>>>>>>>> see what it is like.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>>>>> clebert.suconic@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
>>>>>>>> suspect
>>>>>>>>> any
>>>>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>>>>> 
>>>>>>>>>>> At least initially, how about we just create a nice landing page
>>>>>> that
>>>>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>>>>> refresh/align
>>>>>>>>> the
>>>>>>>>>>> existing content with some CSS?
>>>>>>>>>> 
>>>>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>>>>> converting these pages into a doc would be easier than converting
>>>>>> them
>>>>>>>>>> to another .css...
>>>>>>>>>> 
>>>>>>>>>> if the conversion needed to be done anyways... I thought .md would
>>>>>> be
>>>>>>>>>> easier and having a better final presentation.
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> 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
>>> 
>>> --
>>> Daniel Kulp
>>> dkulp@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>> 
>>> 
>> 
>> 
>> --
>> 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

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
The HTML is available in the repo now. This HTML is just what I grabbed
from the public directory. Even if it's not comprehensive, it's good enough
for hacking around to figure out what we'd like to do.

In the meantime, I'm still working with ASF Infra to figure out why the
Confluence export is failing.

Bruce

On Wed, Dec 13, 2017 at 12:51 PM, Bruce Snyder <br...@gmail.com>
wrote:

> Yep, that is correct, Dan:
>
> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>
> I pushed my changes to the repo. Now they just need to propagate to the
> Github web UI.
>
> Bruce
>
> On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> Isn’t the push address supposed to be:
>>
>> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>>
>>
>> Dan
>>
>>
>>
>> > On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
>> wrote:
>> >
>> > Thank you for the suggestion, but it looks like I do not have
>> permissions
>> > either. I will contact ASF Infra for assistance.
>> >
>> > Bruce
>> >
>> > On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
>> wrote:
>> >
>> >> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
>> >> wrote:
>> >>
>> >>> I had the following empty git repo created to hold the HTML from the
>> >>> current website:
>> >>>
>> >>> https://github.com/apache/activemq-web
>> >>>
>> >>> However, I have a conundrum -- content cannot be pushed directly to a
>> >>> Github ASF repo. Content can only be added via pull request but Github
>> >> does
>> >>> not allow a pull request on an empty repo.
>> >>>
>> >> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
>> >> git.apache.org/activemq-web.git
>> >>
>> >> This is the workflow we currently use, we push directly to the ASF
>> repo.
>> >> PRs are really only used for review and discussion.  I tried to push
>> >> directly this morning but looks like I don't have write permissions.
>> >>
>> >>>
>> >>> Any ideas on how to get the HTML into the repo? I guess I could ask
>> ASF
>> >>> Infra to push it.
>> >>>
>> >>> Bruce
>> >>>
>> >>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <bruce.snyder@gmail.com
>> >
>> >>> wrote:
>> >>>
>> >>>> I'm going to address all the questions to me in this single reply.
>> >>>>
>> >>>> My original suggestion was that we export the HTML from Confluence,
>> >>>> convert to Markdown and put the Markdown and the images in a git
>> repo.
>> >>>> Markdown is much easier to edit than raw HTML, especially the HTML
>> >>> exported
>> >>>> from Confluence (blech!). The idea was that we could use Jekyll +
>> SAAS
>> >> to
>> >>>> craft a new website. In fact, Michael Andre Pearce produced a mockup
>> of
>> >>>> this using the Apache Metro website as an example (because it already
>> >>> makes
>> >>>> use of Jekyll + SAAS). It was enough to convince me that we should
>> take
>> >>>> this path, so I started looking into doing a full, new export of
>> >>> Confluence
>> >>>> pages to HTML. If you have not seen Michael's mockup, you should
>> really
>> >>>> take a look.
>> >>>>
>> >>>> So, I manually grabbed the raw HTML that is automagically exported
>> from
>> >>>> Confluence and is hosting the current site that we see at
>> >>>> http://activemq.apache.org. I did some testing on it using text2html
>> >> and
>> >>>> the conversion it does is pretty awful and would require a lot of
>> hand
>> >>> work
>> >>>> to fix it. So, we discussed the point that there are 1600+ pages of
>> >> HTML
>> >>> to
>> >>>> manually edit. But I later realized that it was only about 950 HTML
>> >> pages
>> >>>> (from what I can tell so far).
>> >>>>
>> >>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on
>> >> top
>> >>>> of PanDoc. So, I have also been trying to export the HTML from
>> >> Confluence
>> >>>> in order to try out the PanDoc converter (it works based on the
>> >>> Confluence
>> >>>> export function which is different from how the HTML is automagically
>> >>>> converted). Unfortunately, I am running into a NullPointerException
>> >> from
>> >>>> Confluence. ASF Infra is telling me that the NPE is due to the CDATA
>> in
>> >>> the
>> >>>> search function on the Navigation page and is suggesting that the
>> >>> solution
>> >>>> is to remove the Navigation page. The problem with this suggestion is
>> >>> that
>> >>>> it would fundamentally remove all the navigation on the right-hand
>> side
>> >>> of
>> >>>> the site -- not what we want.
>> >>>>
>> >>>> I have also given some thought to the idea that removing the current
>> >> site
>> >>>> will break all links to old site. This is something that cannot be
>> >>>> overlooked and must be prevented as we do not want to leave users who
>> >>> have
>> >>>> bookmarked a page high and dry. This is a fairly easy problem to
>> solve
>> >>> this
>> >>>> using some mod_rewrite rules, the question is if ASF Infra is willing
>> >> to
>> >>>> allow us to deploy such custom rules. This should be investigated
>> when
>> >> we
>> >>>> get to that point, but we are not there yet. First, we need to decide
>> >> the
>> >>>> best path forward based on what I have described above in the
>> preceding
>> >>>> paragraphs.
>> >>>>
>> >>>>
>> >>>> Bruce
>> >>>>
>> >>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
>> >>>> wrote:
>> >>>>
>> >>>>> I was thinking there would be a single css file for all the pages.
>> >> But
>> >>> I
>> >>>>> haven't seen the files yet. Let's have a play around when Bruce
>> pushes
>> >>> the
>> >>>>> export.
>> >>>>>
>> >>>>> Cheers
>> >>>>>
>> >>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>> >>>>> michael.andre.pearce@me.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>>> What’s 1600 pages between friends....
>> >>>>>>
>> >>>>>> I agree it will be easier to covert to md than to start doing css
>> >>>>> styles.
>> >>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>> >>>>>>
>> >>>>>> It be good to get some samples (eg 50 pages) if not all just to try
>> >>> and
>> >>>>>> see what it is like.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>> >> clebert.suconic@gmail.com>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
>> >>>>> suspect
>> >>>>>> any
>> >>>>>>>> tool we use will cause a bunch of styling/content issues.
>> >>>>>>>>
>> >>>>>>>> At least initially, how about we just create a nice landing page
>> >>> that
>> >>>>>>>> brings the ActiveMQ site and Artemis site together, and
>> >>> refresh/align
>> >>>>>> the
>> >>>>>>>> existing content with some CSS?
>> >>>>>>>
>> >>>>>>> I was just looking for the minimal effort task. I thought that
>> >>>>>>> converting these pages into a doc would be easier than converting
>> >>> them
>> >>>>>>> to another .css...
>> >>>>>>>
>> >>>>>>> if the conversion needed to be done anyways... I thought .md would
>> >>> be
>> >>>>>>> easier and having a better final presentation.
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> 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
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
>
>
> --
> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Yep, that is correct, Dan:

https://git-wip-us.apache.org/repos/asf/activemq-web.git

I pushed my changes to the repo. Now they just need to propagate to the
Github web UI.

Bruce

On Wed, Dec 13, 2017 at 11:28 AM, Daniel Kulp <dk...@apache.org> wrote:

>
> Isn’t the push address supposed to be:
>
> https://git-wip-us.apache.org/repos/asf/activemq-web.git
>
>
> Dan
>
>
>
> > On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com>
> wrote:
> >
> > Thank you for the suggestion, but it looks like I do not have permissions
> > either. I will contact ASF Infra for assistance.
> >
> > Bruce
> >
> > On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com>
> wrote:
> >
> >> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
> >> wrote:
> >>
> >>> I had the following empty git repo created to hold the HTML from the
> >>> current website:
> >>>
> >>> https://github.com/apache/activemq-web
> >>>
> >>> However, I have a conundrum -- content cannot be pushed directly to a
> >>> Github ASF repo. Content can only be added via pull request but Github
> >> does
> >>> not allow a pull request on an empty repo.
> >>>
> >> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
> >> git.apache.org/activemq-web.git
> >>
> >> This is the workflow we currently use, we push directly to the ASF repo.
> >> PRs are really only used for review and discussion.  I tried to push
> >> directly this morning but looks like I don't have write permissions.
> >>
> >>>
> >>> Any ideas on how to get the HTML into the repo? I guess I could ask ASF
> >>> Infra to push it.
> >>>
> >>> Bruce
> >>>
> >>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <br...@gmail.com>
> >>> wrote:
> >>>
> >>>> I'm going to address all the questions to me in this single reply.
> >>>>
> >>>> My original suggestion was that we export the HTML from Confluence,
> >>>> convert to Markdown and put the Markdown and the images in a git repo.
> >>>> Markdown is much easier to edit than raw HTML, especially the HTML
> >>> exported
> >>>> from Confluence (blech!). The idea was that we could use Jekyll + SAAS
> >> to
> >>>> craft a new website. In fact, Michael Andre Pearce produced a mockup
> of
> >>>> this using the Apache Metro website as an example (because it already
> >>> makes
> >>>> use of Jekyll + SAAS). It was enough to convince me that we should
> take
> >>>> this path, so I started looking into doing a full, new export of
> >>> Confluence
> >>>> pages to HTML. If you have not seen Michael's mockup, you should
> really
> >>>> take a look.
> >>>>
> >>>> So, I manually grabbed the raw HTML that is automagically exported
> from
> >>>> Confluence and is hosting the current site that we see at
> >>>> http://activemq.apache.org. I did some testing on it using text2html
> >> and
> >>>> the conversion it does is pretty awful and would require a lot of hand
> >>> work
> >>>> to fix it. So, we discussed the point that there are 1600+ pages of
> >> HTML
> >>> to
> >>>> manually edit. But I later realized that it was only about 950 HTML
> >> pages
> >>>> (from what I can tell so far).
> >>>>
> >>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on
> >> top
> >>>> of PanDoc. So, I have also been trying to export the HTML from
> >> Confluence
> >>>> in order to try out the PanDoc converter (it works based on the
> >>> Confluence
> >>>> export function which is different from how the HTML is automagically
> >>>> converted). Unfortunately, I am running into a NullPointerException
> >> from
> >>>> Confluence. ASF Infra is telling me that the NPE is due to the CDATA
> in
> >>> the
> >>>> search function on the Navigation page and is suggesting that the
> >>> solution
> >>>> is to remove the Navigation page. The problem with this suggestion is
> >>> that
> >>>> it would fundamentally remove all the navigation on the right-hand
> side
> >>> of
> >>>> the site -- not what we want.
> >>>>
> >>>> I have also given some thought to the idea that removing the current
> >> site
> >>>> will break all links to old site. This is something that cannot be
> >>>> overlooked and must be prevented as we do not want to leave users who
> >>> have
> >>>> bookmarked a page high and dry. This is a fairly easy problem to solve
> >>> this
> >>>> using some mod_rewrite rules, the question is if ASF Infra is willing
> >> to
> >>>> allow us to deploy such custom rules. This should be investigated when
> >> we
> >>>> get to that point, but we are not there yet. First, we need to decide
> >> the
> >>>> best path forward based on what I have described above in the
> preceding
> >>>> paragraphs.
> >>>>
> >>>>
> >>>> Bruce
> >>>>
> >>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
> >>>> wrote:
> >>>>
> >>>>> I was thinking there would be a single css file for all the pages.
> >> But
> >>> I
> >>>>> haven't seen the files yet. Let's have a play around when Bruce
> pushes
> >>> the
> >>>>> export.
> >>>>>
> >>>>> Cheers
> >>>>>
> >>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >>>>> michael.andre.pearce@me.com>
> >>>>> wrote:
> >>>>>
> >>>>>> What’s 1600 pages between friends....
> >>>>>>
> >>>>>> I agree it will be easier to covert to md than to start doing css
> >>>>> styles.
> >>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
> >>>>>>
> >>>>>> It be good to get some samples (eg 50 pages) if not all just to try
> >>> and
> >>>>>> see what it is like.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
> >> clebert.suconic@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
> >>>>> suspect
> >>>>>> any
> >>>>>>>> tool we use will cause a bunch of styling/content issues.
> >>>>>>>>
> >>>>>>>> At least initially, how about we just create a nice landing page
> >>> that
> >>>>>>>> brings the ActiveMQ site and Artemis site together, and
> >>> refresh/align
> >>>>>> the
> >>>>>>>> existing content with some CSS?
> >>>>>>>
> >>>>>>> I was just looking for the minimal effort task. I thought that
> >>>>>>> converting these pages into a doc would be easier than converting
> >>> them
> >>>>>>> to another .css...
> >>>>>>>
> >>>>>>> if the conversion needed to be done anyways... I thought .md would
> >>> be
> >>>>>>> easier and having a better final presentation.
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>


-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Daniel Kulp <dk...@apache.org>.
Isn’t the push address supposed to be:

https://git-wip-us.apache.org/repos/asf/activemq-web.git


Dan



> On Dec 13, 2017, at 1:15 PM, Bruce Snyder <br...@gmail.com> wrote:
> 
> Thank you for the suggestion, but it looks like I do not have permissions
> either. I will contact ASF Infra for assistance.
> 
> Bruce
> 
> On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com> wrote:
> 
>> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
>> wrote:
>> 
>>> I had the following empty git repo created to hold the HTML from the
>>> current website:
>>> 
>>> https://github.com/apache/activemq-web
>>> 
>>> However, I have a conundrum -- content cannot be pushed directly to a
>>> Github ASF repo. Content can only be added via pull request but Github
>> does
>>> not allow a pull request on an empty repo.
>>> 
>> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
>> git.apache.org/activemq-web.git
>> 
>> This is the workflow we currently use, we push directly to the ASF repo.
>> PRs are really only used for review and discussion.  I tried to push
>> directly this morning but looks like I don't have write permissions.
>> 
>>> 
>>> Any ideas on how to get the HTML into the repo? I guess I could ask ASF
>>> Infra to push it.
>>> 
>>> Bruce
>>> 
>>> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <br...@gmail.com>
>>> wrote:
>>> 
>>>> I'm going to address all the questions to me in this single reply.
>>>> 
>>>> My original suggestion was that we export the HTML from Confluence,
>>>> convert to Markdown and put the Markdown and the images in a git repo.
>>>> Markdown is much easier to edit than raw HTML, especially the HTML
>>> exported
>>>> from Confluence (blech!). The idea was that we could use Jekyll + SAAS
>> to
>>>> craft a new website. In fact, Michael Andre Pearce produced a mockup of
>>>> this using the Apache Metro website as an example (because it already
>>> makes
>>>> use of Jekyll + SAAS). It was enough to convince me that we should take
>>>> this path, so I started looking into doing a full, new export of
>>> Confluence
>>>> pages to HTML. If you have not seen Michael's mockup, you should really
>>>> take a look.
>>>> 
>>>> So, I manually grabbed the raw HTML that is automagically exported from
>>>> Confluence and is hosting the current site that we see at
>>>> http://activemq.apache.org. I did some testing on it using text2html
>> and
>>>> the conversion it does is pretty awful and would require a lot of hand
>>> work
>>>> to fix it. So, we discussed the point that there are 1600+ pages of
>> HTML
>>> to
>>>> manually edit. But I later realized that it was only about 950 HTML
>> pages
>>>> (from what I can tell so far).
>>>> 
>>>> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on
>> top
>>>> of PanDoc. So, I have also been trying to export the HTML from
>> Confluence
>>>> in order to try out the PanDoc converter (it works based on the
>>> Confluence
>>>> export function which is different from how the HTML is automagically
>>>> converted). Unfortunately, I am running into a NullPointerException
>> from
>>>> Confluence. ASF Infra is telling me that the NPE is due to the CDATA in
>>> the
>>>> search function on the Navigation page and is suggesting that the
>>> solution
>>>> is to remove the Navigation page. The problem with this suggestion is
>>> that
>>>> it would fundamentally remove all the navigation on the right-hand side
>>> of
>>>> the site -- not what we want.
>>>> 
>>>> I have also given some thought to the idea that removing the current
>> site
>>>> will break all links to old site. This is something that cannot be
>>>> overlooked and must be prevented as we do not want to leave users who
>>> have
>>>> bookmarked a page high and dry. This is a fairly easy problem to solve
>>> this
>>>> using some mod_rewrite rules, the question is if ASF Infra is willing
>> to
>>>> allow us to deploy such custom rules. This should be investigated when
>> we
>>>> get to that point, but we are not there yet. First, we need to decide
>> the
>>>> best path forward based on what I have described above in the preceding
>>>> paragraphs.
>>>> 
>>>> 
>>>> Bruce
>>>> 
>>>> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
>>>> wrote:
>>>> 
>>>>> I was thinking there would be a single css file for all the pages.
>> But
>>> I
>>>>> haven't seen the files yet. Let's have a play around when Bruce pushes
>>> the
>>>>> export.
>>>>> 
>>>>> Cheers
>>>>> 
>>>>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>>>>> michael.andre.pearce@me.com>
>>>>> wrote:
>>>>> 
>>>>>> What’s 1600 pages between friends....
>>>>>> 
>>>>>> I agree it will be easier to covert to md than to start doing css
>>>>> styles.
>>>>>> It’s all from a wiki anyhow so it’s can’t be that far off.
>>>>>> 
>>>>>> It be good to get some samples (eg 50 pages) if not all just to try
>>> and
>>>>>> see what it is like.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 12 Dec 2017, at 17:04, Clebert Suconic <
>> clebert.suconic@gmail.com>
>>>>>> wrote:
>>>>>> 
>>>>>>>> Exporting to MD and creating a gitbook seems like a big task, I
>>>>> suspect
>>>>>> any
>>>>>>>> tool we use will cause a bunch of styling/content issues.
>>>>>>>> 
>>>>>>>> At least initially, how about we just create a nice landing page
>>> that
>>>>>>>> brings the ActiveMQ site and Artemis site together, and
>>> refresh/align
>>>>>> the
>>>>>>>> existing content with some CSS?
>>>>>>> 
>>>>>>> I was just looking for the minimal effort task. I thought that
>>>>>>> converting these pages into a doc would be easier than converting
>>> them
>>>>>>> to another .css...
>>>>>>> 
>>>>>>> if the conversion needed to be done anyways... I thought .md would
>>> be
>>>>>>> easier and having a better final presentation.
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
Thank you for the suggestion, but it looks like I do not have permissions
either. I will contact ASF Infra for assistance.

Bruce

On Wed, Dec 13, 2017 at 2:41 AM, Martyn Taylor <mt...@redhat.com> wrote:

> On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > I had the following empty git repo created to hold the HTML from the
> > current website:
> >
> > https://github.com/apache/activemq-web
> >
> > However, I have a conundrum -- content cannot be pushed directly to a
> > Github ASF repo. Content can only be added via pull request but Github
> does
> > not allow a pull request on an empty repo.
> >
> Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
> git.apache.org/activemq-web.git
>
> This is the workflow we currently use, we push directly to the ASF repo.
> PRs are really only used for review and discussion.  I tried to push
> directly this morning but looks like I don't have write permissions.
>
> >
> > Any ideas on how to get the HTML into the repo? I guess I could ask ASF
> > Infra to push it.
> >
> > Bruce
> >
> > On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <br...@gmail.com>
> > wrote:
> >
> > > I'm going to address all the questions to me in this single reply.
> > >
> > > My original suggestion was that we export the HTML from Confluence,
> > > convert to Markdown and put the Markdown and the images in a git repo.
> > > Markdown is much easier to edit than raw HTML, especially the HTML
> > exported
> > > from Confluence (blech!). The idea was that we could use Jekyll + SAAS
> to
> > > craft a new website. In fact, Michael Andre Pearce produced a mockup of
> > > this using the Apache Metro website as an example (because it already
> > makes
> > > use of Jekyll + SAAS). It was enough to convince me that we should take
> > > this path, so I started looking into doing a full, new export of
> > Confluence
> > > pages to HTML. If you have not seen Michael's mockup, you should really
> > > take a look.
> > >
> > > So, I manually grabbed the raw HTML that is automagically exported from
> > > Confluence and is hosting the current site that we see at
> > > http://activemq.apache.org. I did some testing on it using text2html
> and
> > > the conversion it does is pretty awful and would require a lot of hand
> > work
> > > to fix it. So, we discussed the point that there are 1600+ pages of
> HTML
> > to
> > > manually edit. But I later realized that it was only about 950 HTML
> pages
> > > (from what I can tell so far).
> > >
> > > Then, Dan Kulp found a Confluence HTML to raw HTML converter built on
> top
> > > of PanDoc. So, I have also been trying to export the HTML from
> Confluence
> > > in order to try out the PanDoc converter (it works based on the
> > Confluence
> > > export function which is different from how the HTML is automagically
> > > converted). Unfortunately, I am running into a NullPointerException
> from
> > > Confluence. ASF Infra is telling me that the NPE is due to the CDATA in
> > the
> > > search function on the Navigation page and is suggesting that the
> > solution
> > > is to remove the Navigation page. The problem with this suggestion is
> > that
> > > it would fundamentally remove all the navigation on the right-hand side
> > of
> > > the site -- not what we want.
> > >
> > > I have also given some thought to the idea that removing the current
> site
> > > will break all links to old site. This is something that cannot be
> > > overlooked and must be prevented as we do not want to leave users who
> > have
> > > bookmarked a page high and dry. This is a fairly easy problem to solve
> > this
> > > using some mod_rewrite rules, the question is if ASF Infra is willing
> to
> > > allow us to deploy such custom rules. This should be investigated when
> we
> > > get to that point, but we are not there yet. First, we need to decide
> the
> > > best path forward based on what I have described above in the preceding
> > > paragraphs.
> > >
> > >
> > > Bruce
> > >
> > > On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
> > > wrote:
> > >
> > >> I was thinking there would be a single css file for all the pages.
> But
> > I
> > >> haven't seen the files yet. Let's have a play around when Bruce pushes
> > the
> > >> export.
> > >>
> > >> Cheers
> > >>
> > >> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> > >> michael.andre.pearce@me.com>
> > >> wrote:
> > >>
> > >> > What’s 1600 pages between friends....
> > >> >
> > >> > I agree it will be easier to covert to md than to start doing css
> > >> styles.
> > >> > It’s all from a wiki anyhow so it’s can’t be that far off.
> > >> >
> > >> > It be good to get some samples (eg 50 pages) if not all just to try
> > and
> > >> > see what it is like.
> > >> >
> > >> >
> > >> >
> > >> > On 12 Dec 2017, at 17:04, Clebert Suconic <
> clebert.suconic@gmail.com>
> > >> > wrote:
> > >> >
> > >> > >> Exporting to MD and creating a gitbook seems like a big task, I
> > >> suspect
> > >> > any
> > >> > >> tool we use will cause a bunch of styling/content issues.
> > >> > >>
> > >> > >> At least initially, how about we just create a nice landing page
> > that
> > >> > >> brings the ActiveMQ site and Artemis site together, and
> > refresh/align
> > >> > the
> > >> > >> existing content with some CSS?
> > >> > >
> > >> > > I was just looking for the minimal effort task. I thought that
> > >> > > converting these pages into a doc would be easier than converting
> > them
> > >> > > to another .css...
> > >> > >
> > >> > > if the conversion needed to be done anyways... I thought .md would
> > be
> > >> > > easier and having a better final presentation.
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
On Wed, Dec 13, 2017 at 4:00 AM, Bruce Snyder <br...@gmail.com>
wrote:

> I had the following empty git repo created to hold the HTML from the
> current website:
>
> https://github.com/apache/activemq-web
>
> However, I have a conundrum -- content cannot be pushed directly to a
> Github ASF repo. Content can only be added via pull request but Github does
> not allow a pull request on an empty repo.
>
Bruce, have you tried pushing directly to the ASF repo.  i.e.  git://
git.apache.org/activemq-web.git

This is the workflow we currently use, we push directly to the ASF repo.
PRs are really only used for review and discussion.  I tried to push
directly this morning but looks like I don't have write permissions.

>
> Any ideas on how to get the HTML into the repo? I guess I could ask ASF
> Infra to push it.
>
> Bruce
>
> On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > I'm going to address all the questions to me in this single reply.
> >
> > My original suggestion was that we export the HTML from Confluence,
> > convert to Markdown and put the Markdown and the images in a git repo.
> > Markdown is much easier to edit than raw HTML, especially the HTML
> exported
> > from Confluence (blech!). The idea was that we could use Jekyll + SAAS to
> > craft a new website. In fact, Michael Andre Pearce produced a mockup of
> > this using the Apache Metro website as an example (because it already
> makes
> > use of Jekyll + SAAS). It was enough to convince me that we should take
> > this path, so I started looking into doing a full, new export of
> Confluence
> > pages to HTML. If you have not seen Michael's mockup, you should really
> > take a look.
> >
> > So, I manually grabbed the raw HTML that is automagically exported from
> > Confluence and is hosting the current site that we see at
> > http://activemq.apache.org. I did some testing on it using text2html and
> > the conversion it does is pretty awful and would require a lot of hand
> work
> > to fix it. So, we discussed the point that there are 1600+ pages of HTML
> to
> > manually edit. But I later realized that it was only about 950 HTML pages
> > (from what I can tell so far).
> >
> > Then, Dan Kulp found a Confluence HTML to raw HTML converter built on top
> > of PanDoc. So, I have also been trying to export the HTML from Confluence
> > in order to try out the PanDoc converter (it works based on the
> Confluence
> > export function which is different from how the HTML is automagically
> > converted). Unfortunately, I am running into a NullPointerException from
> > Confluence. ASF Infra is telling me that the NPE is due to the CDATA in
> the
> > search function on the Navigation page and is suggesting that the
> solution
> > is to remove the Navigation page. The problem with this suggestion is
> that
> > it would fundamentally remove all the navigation on the right-hand side
> of
> > the site -- not what we want.
> >
> > I have also given some thought to the idea that removing the current site
> > will break all links to old site. This is something that cannot be
> > overlooked and must be prevented as we do not want to leave users who
> have
> > bookmarked a page high and dry. This is a fairly easy problem to solve
> this
> > using some mod_rewrite rules, the question is if ASF Infra is willing to
> > allow us to deploy such custom rules. This should be investigated when we
> > get to that point, but we are not there yet. First, we need to decide the
> > best path forward based on what I have described above in the preceding
> > paragraphs.
> >
> >
> > Bruce
> >
> > On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
> > wrote:
> >
> >> I was thinking there would be a single css file for all the pages.  But
> I
> >> haven't seen the files yet. Let's have a play around when Bruce pushes
> the
> >> export.
> >>
> >> Cheers
> >>
> >> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> >> michael.andre.pearce@me.com>
> >> wrote:
> >>
> >> > What’s 1600 pages between friends....
> >> >
> >> > I agree it will be easier to covert to md than to start doing css
> >> styles.
> >> > It’s all from a wiki anyhow so it’s can’t be that far off.
> >> >
> >> > It be good to get some samples (eg 50 pages) if not all just to try
> and
> >> > see what it is like.
> >> >
> >> >
> >> >
> >> > On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com>
> >> > wrote:
> >> >
> >> > >> Exporting to MD and creating a gitbook seems like a big task, I
> >> suspect
> >> > any
> >> > >> tool we use will cause a bunch of styling/content issues.
> >> > >>
> >> > >> At least initially, how about we just create a nice landing page
> that
> >> > >> brings the ActiveMQ site and Artemis site together, and
> refresh/align
> >> > the
> >> > >> existing content with some CSS?
> >> > >
> >> > > I was just looking for the minimal effort task. I thought that
> >> > > converting these pages into a doc would be easier than converting
> them
> >> > > to another .css...
> >> > >
> >> > > if the conversion needed to be done anyways... I thought .md would
> be
> >> > > easier and having a better final presentation.
> >> >
> >>
> >
> >
> >
> > --
> > 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
I had the following empty git repo created to hold the HTML from the
current website:

https://github.com/apache/activemq-web

However, I have a conundrum -- content cannot be pushed directly to a
Github ASF repo. Content can only be added via pull request but Github does
not allow a pull request on an empty repo.

Any ideas on how to get the HTML into the repo? I guess I could ask ASF
Infra to push it.

Bruce

On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder <br...@gmail.com>
wrote:

> I'm going to address all the questions to me in this single reply.
>
> My original suggestion was that we export the HTML from Confluence,
> convert to Markdown and put the Markdown and the images in a git repo.
> Markdown is much easier to edit than raw HTML, especially the HTML exported
> from Confluence (blech!). The idea was that we could use Jekyll + SAAS to
> craft a new website. In fact, Michael Andre Pearce produced a mockup of
> this using the Apache Metro website as an example (because it already makes
> use of Jekyll + SAAS). It was enough to convince me that we should take
> this path, so I started looking into doing a full, new export of Confluence
> pages to HTML. If you have not seen Michael's mockup, you should really
> take a look.
>
> So, I manually grabbed the raw HTML that is automagically exported from
> Confluence and is hosting the current site that we see at
> http://activemq.apache.org. I did some testing on it using text2html and
> the conversion it does is pretty awful and would require a lot of hand work
> to fix it. So, we discussed the point that there are 1600+ pages of HTML to
> manually edit. But I later realized that it was only about 950 HTML pages
> (from what I can tell so far).
>
> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on top
> of PanDoc. So, I have also been trying to export the HTML from Confluence
> in order to try out the PanDoc converter (it works based on the Confluence
> export function which is different from how the HTML is automagically
> converted). Unfortunately, I am running into a NullPointerException from
> Confluence. ASF Infra is telling me that the NPE is due to the CDATA in the
> search function on the Navigation page and is suggesting that the solution
> is to remove the Navigation page. The problem with this suggestion is that
> it would fundamentally remove all the navigation on the right-hand side of
> the site -- not what we want.
>
> I have also given some thought to the idea that removing the current site
> will break all links to old site. This is something that cannot be
> overlooked and must be prevented as we do not want to leave users who have
> bookmarked a page high and dry. This is a fairly easy problem to solve this
> using some mod_rewrite rules, the question is if ASF Infra is willing to
> allow us to deploy such custom rules. This should be investigated when we
> get to that point, but we are not there yet. First, we need to decide the
> best path forward based on what I have described above in the preceding
> paragraphs.
>
>
> Bruce
>
> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com>
> wrote:
>
>> I was thinking there would be a single css file for all the pages.  But I
>> haven't seen the files yet. Let's have a play around when Bruce pushes the
>> export.
>>
>> Cheers
>>
>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>> michael.andre.pearce@me.com>
>> wrote:
>>
>> > What’s 1600 pages between friends....
>> >
>> > I agree it will be easier to covert to md than to start doing css
>> styles.
>> > It’s all from a wiki anyhow so it’s can’t be that far off.
>> >
>> > It be good to get some samples (eg 50 pages) if not all just to try and
>> > see what it is like.
>> >
>> >
>> >
>> > On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com>
>> > wrote:
>> >
>> > >> Exporting to MD and creating a gitbook seems like a big task, I
>> suspect
>> > any
>> > >> tool we use will cause a bunch of styling/content issues.
>> > >>
>> > >> At least initially, how about we just create a nice landing page that
>> > >> brings the ActiveMQ site and Artemis site together, and refresh/align
>> > the
>> > >> existing content with some CSS?
>> > >
>> > > I was just looking for the minimal effort task. I thought that
>> > > converting these pages into a doc would be easier than converting them
>> > > to another .css...
>> > >
>> > > if the conversion needed to be done anyways... I thought .md would be
>> > > easier and having a better final presentation.
>> >
>>
>
>
>
> --
> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
I'm going to address all the questions to me in this single reply.

My original suggestion was that we export the HTML from Confluence, convert
to Markdown and put the Markdown and the images in a git repo. Markdown is
much easier to edit than raw HTML, especially the HTML exported from
Confluence (blech!). The idea was that we could use Jekyll + SAAS to craft
a new website. In fact, Michael Andre Pearce produced a mockup of this
using the Apache Metro website as an example (because it already makes use
of Jekyll + SAAS). It was enough to convince me that we should take this
path, so I started looking into doing a full, new export of Confluence
pages to HTML. If you have not seen Michael's mockup, you should really
take a look.

So, I manually grabbed the raw HTML that is automagically exported from
Confluence and is hosting the current site that we see at
http://activemq.apache.org. I did some testing on it using text2html and
the conversion it does is pretty awful and would require a lot of hand work
to fix it. So, we discussed the point that there are 1600+ pages of HTML to
manually edit. But I later realized that it was only about 950 HTML pages
(from what I can tell so far).

Then, Dan Kulp found a Confluence HTML to raw HTML converter built on top
of PanDoc. So, I have also been trying to export the HTML from Confluence
in order to try out the PanDoc converter (it works based on the Confluence
export function which is different from how the HTML is automagically
converted). Unfortunately, I am running into a NullPointerException from
Confluence. ASF Infra is telling me that the NPE is due to the CDATA in the
search function on the Navigation page and is suggesting that the solution
is to remove the Navigation page. The problem with this suggestion is that
it would fundamentally remove all the navigation on the right-hand side of
the site -- not what we want.

I have also given some thought to the idea that removing the current site
will break all links to old site. This is something that cannot be
overlooked and must be prevented as we do not want to leave users who have
bookmarked a page high and dry. This is a fairly easy problem to solve this
using some mod_rewrite rules, the question is if ASF Infra is willing to
allow us to deploy such custom rules. This should be investigated when we
get to that point, but we are not there yet. First, we need to decide the
best path forward based on what I have described above in the preceding
paragraphs.


Bruce

On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor <mt...@redhat.com> wrote:

> I was thinking there would be a single css file for all the pages.  But I
> haven't seen the files yet. Let's have a play around when Bruce pushes the
> export.
>
> Cheers
>
> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> michael.andre.pearce@me.com>
> wrote:
>
> > What’s 1600 pages between friends....
> >
> > I agree it will be easier to covert to md than to start doing css styles.
> > It’s all from a wiki anyhow so it’s can’t be that far off.
> >
> > It be good to get some samples (eg 50 pages) if not all just to try and
> > see what it is like.
> >
> >
> >
> > On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com>
> > wrote:
> >
> > >> Exporting to MD and creating a gitbook seems like a big task, I
> suspect
> > any
> > >> tool we use will cause a bunch of styling/content issues.
> > >>
> > >> At least initially, how about we just create a nice landing page that
> > >> brings the ActiveMQ site and Artemis site together, and refresh/align
> > the
> > >> existing content with some CSS?
> > >
> > > I was just looking for the minimal effort task. I thought that
> > > converting these pages into a doc would be easier than converting them
> > > to another .css...
> > >
> > > if the conversion needed to be done anyways... I thought .md would be
> > > easier and having a better final presentation.
> >
>



-- 
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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
I was thinking there would be a single css file for all the pages.  But I
haven't seen the files yet. Let's have a play around when Bruce pushes the
export.

Cheers

On 12 Dec 2017 5:30 pm, "Michael André Pearce" <mi...@me.com>
wrote:

> What’s 1600 pages between friends....
>
> I agree it will be easier to covert to md than to start doing css styles.
> It’s all from a wiki anyhow so it’s can’t be that far off.
>
> It be good to get some samples (eg 50 pages) if not all just to try and
> see what it is like.
>
>
>
> On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com>
> wrote:
>
> >> Exporting to MD and creating a gitbook seems like a big task, I suspect
> any
> >> tool we use will cause a bunch of styling/content issues.
> >>
> >> At least initially, how about we just create a nice landing page that
> >> brings the ActiveMQ site and Artemis site together, and refresh/align
> the
> >> existing content with some CSS?
> >
> > I was just looking for the minimal effort task. I thought that
> > converting these pages into a doc would be easier than converting them
> > to another .css...
> >
> > if the conversion needed to be done anyways... I thought .md would be
> > easier and having a better final presentation.
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Andy Taylor <an...@gmail.com>.
Id be happy to spend some time helping

On 12 December 2017 at 17:30, Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> What’s 1600 pages between friends....
>
> I agree it will be easier to covert to md than to start doing css styles.
> It’s all from a wiki anyhow so it’s can’t be that far off.
>
> It be good to get some samples (eg 50 pages) if not all just to try and
> see what it is like.
>
>
>
> On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com>
> wrote:
>
> >> Exporting to MD and creating a gitbook seems like a big task, I suspect
> any
> >> tool we use will cause a bunch of styling/content issues.
> >>
> >> At least initially, how about we just create a nice landing page that
> >> brings the ActiveMQ site and Artemis site together, and refresh/align
> the
> >> existing content with some CSS?
> >
> > I was just looking for the minimal effort task. I thought that
> > converting these pages into a doc would be easier than converting them
> > to another .css...
> >
> > if the conversion needed to be done anyways... I thought .md would be
> > easier and having a better final presentation.
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
What’s 1600 pages between friends....

I agree it will be easier to covert to md than to start doing css styles. It’s all from a wiki anyhow so it’s can’t be that far off. 

It be good to get some samples (eg 50 pages) if not all just to try and see what it is like. 



On 12 Dec 2017, at 17:04, Clebert Suconic <cl...@gmail.com> wrote:

>> Exporting to MD and creating a gitbook seems like a big task, I suspect any
>> tool we use will cause a bunch of styling/content issues.
>> 
>> At least initially, how about we just create a nice landing page that
>> brings the ActiveMQ site and Artemis site together, and refresh/align the
>> existing content with some CSS?
> 
> I was just looking for the minimal effort task. I thought that
> converting these pages into a doc would be easier than converting them
> to another .css...
> 
> if the conversion needed to be done anyways... I thought .md would be
> easier and having a better final presentation.

Re: Thoughts on refactoring the ActiveMQ website

Posted by Clebert Suconic <cl...@gmail.com>.
> Exporting to MD and creating a gitbook seems like a big task, I suspect any
> tool we use will cause a bunch of styling/content issues.
>
> At least initially, how about we just create a nice landing page that
> brings the ActiveMQ site and Artemis site together, and refresh/align the
> existing content with some CSS?

I was just looking for the minimal effort task. I thought that
converting these pages into a doc would be easier than converting them
to another .css...

if the conversion needed to be done anyways... I thought .md would be
easier and having a better final presentation.

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
On Tue, Dec 12, 2017 at 4:46 PM, Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> I agree, gitbook or similar would be a great way to manage the docs for
> 5.x.
>
Exporting to MD and creating a gitbook seems like a big task, I suspect any
tool we use will cause a bunch of styling/content issues.

At least initially, how about we just create a nice landing page that
brings the ActiveMQ site and Artemis site together, and refresh/align the
existing content with some CSS?

>
> @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 <cl...@gmail.com>
> 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 <mt...@redhat.com>
> 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 <br...@gmail.com>
> 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 <mt...@redhat.com>
> 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 <br...@gmail.com>
> >>>> 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 <
> >>>>> michael.andre.pearce@me.com> 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 <br...@gmail.com>
> >>> 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 <
> >>>>>> clebert.suconic@gmail.com>
> >>>>>>> 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 <
> >>>>> bruce.snyder@gmail.com>
> >>>>>>>> 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Clebert Suconic <cl...@gmail.com>.
we would need to keep the current ones hidden somewhere.. these links
are 10+ years old.. it would break anyone referring linked docs. Think
of your customers with bookmarks.

@Bruce: WDYT?

On Tue, Dec 12, 2017 at 11:46 AM, Michael André Pearce
<mi...@me.com> wrote:
> 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 <cl...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com>
>>>>> 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 <
>>>>>> michael.andre.pearce@me.com> 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 <br...@gmail.com>
>>>> 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 <
>>>>>>> clebert.suconic@gmail.com>
>>>>>>>> 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 <
>>>>>> bruce.snyder@gmail.com>
>>>>>>>>> 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



-- 
Clebert Suconic

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
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 <cl...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com>
>>>> 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 <
>>>>> michael.andre.pearce@me.com> 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 <br...@gmail.com>
>>> 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 <
>>>>>> clebert.suconic@gmail.com>
>>>>>>> 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 <
>>>>> bruce.snyder@gmail.com>
>>>>>>>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Clebert Suconic <cl...@gmail.com>.
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 <mt...@redhat.com> 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 <br...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com>
>> > 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 <
>> >> michael.andre.pearce@me.com> 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 <br...@gmail.com>
>> 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 <
>> >> > clebert.suconic@gmail.com>
>> >> > > 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 <
>> >> bruce.snyder@gmail.com>
>> >> > >> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
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 <br...@gmail.com> 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 <mt...@redhat.com> 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 <br...@gmail.com>
> > 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 <
> >> michael.andre.pearce@me.com> 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 <br...@gmail.com>
> 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 <
> >> > clebert.suconic@gmail.com>
> >> > > 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 <
> >> bruce.snyder@gmail.com>
> >> > >> 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
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 <mt...@redhat.com> 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 <br...@gmail.com>
> 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 <
>> michael.andre.pearce@me.com> 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 <br...@gmail.com> 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 <
>> > clebert.suconic@gmail.com>
>> > > 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 <
>> bruce.snyder@gmail.com>
>> > >> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
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 <br...@gmail.com> 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 <
> michael.andre.pearce@me.com> 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 <br...@gmail.com> 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 <
> > clebert.suconic@gmail.com>
> > > 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 <bruce.snyder@gmail.com
> >
> > >> 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
>

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
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 <
michael.andre.pearce@me.com> 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 <br...@gmail.com> 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 <
> clebert.suconic@gmail.com>
> > 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 <br...@gmail.com>
> >> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Michael André Pearce <mi...@me.com>.
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 <br...@gmail.com> 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 <cl...@gmail.com>
> 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 <br...@gmail.com>
>> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Bruce Snyder <br...@gmail.com>.
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 <cl...@gmail.com>
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 <br...@gmail.com>
> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Clebert Suconic <cl...@gmail.com>.
+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 <br...@gmail.com> 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

Re: Thoughts on refactoring the ActiveMQ website

Posted by Martyn Taylor <mt...@redhat.com>.
Thanks for starting this thread.

On Thu, Dec 7, 2017 at 4:20 AM, Bruce Snyder <br...@gmail.com> 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?

I would prefer the site to have a consistent look and feel.

> 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 think we need to direct users to a single place for all things ActiveMQ,
Artemis being part of that.  And have a clear message on the home page
about the projects and how things are related.  We could then offer links
to Artemis, ActiveMQ or NMS client etc..

>
> 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.

Don't care too much about the specific technologies used, but it would be
good to have this managed in Git so we can follow workflows used for other
projects.

> 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?
>
I'm happy to get involved and do some of the work here.

The current website is almost embarrassing, let's get it fixed up :)

>
> 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
>