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 <m...@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-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
