Re: [DISCUSS] Updating the C* website design

Thanks to those who provided input on the new site layout. #3 was the winner with some additional comments, which we'll work to integrate. In tandem with the new website design, page content has been updated and/or created as new. Input would be greatly appreciated. The content doc, plus next ste

Re: [DISCUSS] Updating the C* website design

Hi folks, As there were no dissenting votes, based on lazy consensus we have moved forward with the project as outlined in CASSANDRA-16115: https://issues.apache.org/jira/browse/CASSANDRA-16115 If you need a break from 4.0 debugging, would really love folks’ thoughts on new design concepts. Eleme

Re: [DISCUSS] Updating the C* website design

Seems like even Antora uses another SSG called middleman for their “marketing” home page. https://gitlab.com/antora/antora.org If the convenience of having both content and docs all in one SSG for code maintenance is compatible with the aesthetic/ content / taxonomy strategy need for the site

Re: [DISCUSS] Updating the C* website design

Folks, I applaud the choice of Antora for documentation but I’m not sure it is the best choice for generating an appealing site. Antora’s self professed strength is in technical documentation. Do we want to stick to a “documentation” / utility look for the front facing site or for a blog? htt

Re: [DISCUSS] Updating the C* website design

Thanks for the comments, Mick. Yes, I think you are correct in what you have to say about versioned vs non-versioned docs for the website. It's such an obvious comment that I can only say I must have been half-asleep when Anthony and I discussed the topic. (Maybe he was, too!) Since Antora is one

Re: [DISCUSS] Updating the C* website design

As part of the work, I think all content files should be moved to > cassandra/doc. This would give a clear separation of concerns; > - cassandra/doc contains the material (asciidoc) that is converted to the > website content. > - cassandra-website hosts the live content and contains all the UI >

Re: [DISCUSS] Updating the C* website design

Hi Lorina and Mick, I've raised CASSANDRA-16066 to capture the effort required to carry out the work of converting the markdown to asciidoc. As part of the work, I think all content files should be moved to cassandra/doc. This would give a cl

Re: [DISCUSS] Updating the C* website design

The one issue I see with your suggestion about versioned/non-versioned docs is that the cassandra/doc repo will have asciidoc files, and currently, all the items in the cassandra-website repo are in markdown. There are possible solutions (use antora for the website, put the non-versioned docs in th

Re: [DISCUSS] Updating the C* website design

> See that here: > https://docs.google.com/document/d/1aeNtgyPAsKcNa0GSKvl2ywlFEj30714ry4Sb5turWeE/edit?usp=sharing > > This outline is not complete, just my initial scribblings. Certainly > collaboration would be welcome. This is awesome Lorina. It would also be great to see all non-versione

Re: [DISCUSS] Updating the C* website design

Great idea and I think a new fresh design combined with new release gives a great vibe. The proposed incremental approach sounds reasonable to me. @Lorina - is the document open for comments or should we send any here? I will try to go through it in the next few days. Thank you Ekaterina On Wed,

Re: [DISCUSS] Updating the C* website design

Perhaps I should start another thread, but I have started to outline a more solution-based approach to the docs that I was considering implementing. See that here: https://docs.google.com/document/d/1aeNtgyPAsKcNa0GSKvl2ywlFEj30714ry4Sb5turWeE/edit?usp=sharing This outline is not complete, just m

Re: [DISCUSS] Updating the C* website design

> I would offer that design is important, but content matters more -- so > would suggest adding content strategy/development and information > architecture to the checkpoints list. For example, an ecosystem page could > be highly beneficial to end users (what does C* work with?), as well as a > use

Re: [DISCUSS] Updating the C* website design

That all makes sense, Lorina! My thought was to add a consideration for content/IA to the checklist Mick had shared (in addition to the UI/design), but no need if that's already being handled. On Wed, Jul 29, 2020 at 1:28 PM Brandon Williams wrote: > On Wed, Jul 29, 2020 at 3:06 PM Lorina Polan

Re: [DISCUSS] Updating the C* website design

On Wed, Jul 29, 2020 at 3:06 PM Lorina Poland wrote: > UI bundle, but I'm a copier of design, not a designer. To accomplish a UI > that is more modern, like say, https://spark.apache.org or Interesting choice, we used to look more like that in the past: https://web.archive.org/web/20100511183402

Re: [DISCUSS] Updating the C* website design

To address Melissa's comments - the main reason that this proposal is offered right now is that the Documentation renewal involves a change to a new static site generator, Antora (https://antora.org). Because of this change, the UI for cassandra.apache.org/doc must be rebuilt using the Antora UI (h

Re: [DISCUSS] Updating the C* website design

I would offer that design is important, but content matters more -- so would suggest adding content strategy/development and information architecture to the checkpoints list. For example, an ecosystem page could be highly beneficial to end users (what does C* work with?), as well as a use case/case

[DISCUSS] Updating the C* website design

We have funds on offer to the project to hire a contractor to update the website. Personally I think this is a fantastic opportunity, it would be great to see the website afresh in coordination with the 4.0 release. With no up-front defining goals or improvements specified, if we go forth with th