Improving Dask.org visibility and engagement

Overview

Google visibility

Website structure and opportunities

Social media and other channels

Google visibility

Google visibility - Wikipedia - the longer the better the more visible on Google

Dask

• One very short page
• Very few links and resources

Spark, TensorFlow

• Long page with many links and resources

Google visibility - how do we stack up

Youtube is #3 largest search engine in the world

Dask

• ~1,000 followers
• Not visible on the website
• Looks old and untouched

TensorFlow

• ~380,000 followers
• Visible on website
• Well presented

​

Kubernetes

• ~17,000 followers
• Well organised and presented

​

​

Navigation and engagement

Dask

• Navigation
• Once you click on ‘why Dask’ for example, you cannot go back to the main page
• Case studies/user stories are on a separate subdomain you can’t navigate from the main page to.
• No newsletter/mailing list
• No branding guidelines and citation guidelines

Others

• Case studies are presented immediately https://www.tensorflow.org/about/case-studies)
• ​

​

• https://rapids.ai/branding.html

Schedule

February

Initial concepts, defining scope, presenting to the larger group and getting approval

March

Start developing a new environment; researching documentation tools more visible and searchable by Google

April

Presenting phase 1 to the larger group (scope tbd)

May

Presenting phase 2 to the larger group (scope tbd)

June

Presenting phase 3 to the larger group (scope tbd). Go live!

Next steps

Agree on platform

Wordpress vs. Webflow

Agree on style and theme

To be presented as part of initial phase

Agree on scope and timeline

​

Goals for next meeting

1. Lorem ipsum dolor sit amet, consectetur adipiscing elit
2. Sed do eiusmod tempor incididunt ut labore
3. Ut enim ad minim veniam, quis nostrud exercitation