Thanks for starting this thread.
On Thu, Dec 7, 2017 at 4:20 AM, Bruce Snyder <[email protected]> wrote:
> Several opinions have been expressed recently that the ActiveMQ website
> needs some attention and that Artemis should be made more prominent. I'd
> like to discuss some ideas to see what we could achieve on this topic.
>
> If we are going to make Artemis more prominent, the first concern I
> identified is that the ActiveMQ website and the Artemis website are
> authored differently. The ActiveMQ website is authored in the Confluence
> wiki and exported to HTML automagically whereas the Artemis website is
> authored in raw HTML. As a result, the two sites have a very different look
> and feel to them. This presents some challenges to using the content
> between the two.
>
> But this presents other questions -- do we want the two sites to look
> similar or different?
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
>
