Re: [DISCUSS] Updating the C* website design

[Ekaterina Dimitrova <e....@gmail.com>]

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, 29 Jul 2020 at 18:23, Lorina Poland <lo...@datastax.com> wrote:

> 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 my initial scribblings. Certainly
> collaboration would be welcome.
>
> Lorina Poland
>
>
>
>
> On Wed, Jul 29, 2020 at 2:13 PM Mick Semb Wever <mc...@apache.org> wrote:
>
> > > 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 studies page.
> >
> >
> > Couldn't agree more Melissa. If we can come up with a list of
> > content/pages we are currently missing, and agree on it, that's going
> > to make this process easier. The more we can define and spec, the
> > better.
> >
> >
> > > like say, https://spark.apache.org or https://ignite.apache.org/,
> >
> > For the sake of brainstorming, my favourite two apache project
> > websites are skywalking.apache.org and ignite.apache.org
> > But I don't think we should limit what's possible, I certainly am not
> > a designer.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>