> > My name is Sharan Foga and I am new to the Apache Cassandra community.
> >
> > I would like to contribute to the project but am not a developer so am
> > looking for ways to contribute that are not coding related (e.g helping
> > out with things like community building, documentation, events, meetups,
> > etc). As a start I will take a look through the project website, wiki
> > space and the existing documentation and see if I can find something to
> > work on :-)
Hi Sharan! Thanks for connecting. We are honoured to have an ASF Board
Director reach out!
The project is ramping up on a number of non-coding fronts: website,
documentation, social media, events, and project governance (from CEPs to
voting to methods for contributor recognition…)
Repeating Benjamin, with 4.0 we landed a new website and documentation. An
immense amount of work has gone into this, but it is still very new and
needs many small fixes and eyeballs. All, and any, help we can get there is
most welcome. It should be a super easy place for a non coder contributor
to get started, and it is definitely intended to be that very soon, but for
the moment we are blocked and still working on merging CASSANDRA-16763.
To build the website, you need docker, and to run the following steps:
```
git clone https://github.com/apache/cassandra-website.git
cd cassandra-website
./run.sh website-ui bundle
./run.sh website build -i -b cassandra:trunk,cassandra-3.11 -u
cassandra:https://github.com/polandll/cassandra.git -z
./site-ui/build/ui-bundle.zip
# preview in your browser
open site-content/build/html/_/index.html
```
(Note the second run.sh step will switch to use the official repo fork and
branches once 16763 is merged.)
There's a number of tickets that have been created that relate to the new
website and docs, under CASSANDRA-16761.
Otherwise, the docs are asciidoc that are easy enough to directly edit and
open a PR against; so just reach out on #cassandra-website slack and the
folk there will be very happy to help out in any way they can. There, and
also on #cassandra-events, is where the activity around events and social
media is happening too. There's been some interesting discussions there the
past month around our twitter account, hashtags, and having a content
pipeline in place.
Beyond such hands-on non-coding type of contributions, we are also looking
for inspiration on how better to recognise non-coding contributors, and
even if the idea of non-coding committers has a place in the project. Ideas
and examples on how other projects have done this would be a real
contribution.
