getpopper/website

Code of getpopper.io website

website's Issues

Incorporate new content created for canopie paper/slides

add to website/README/readthedocs content from the canopie slides/paper, specially design principles and diagrams

create big rock - user engagement

add vision and community mission statements

add community value statement

add list of past events

tutorials and invited talks

plan landing page changes

in addition to #3 , add others based on https://youtu.be/x5iJn8k08Hw?t=969

create user persona

add get involved section

Add new section to readthedocs with:

• add images to library repository
• new workflows in examples repository
• contribute to the blog
• write a guide

Then add links from website.

add screencast with demo

show installation, content of a workflow, execution.

create big rock - content delivery

create big rock - onboarding

add link to guides on top bar

the guides markdown file is quite big, so we can break it down into one file per guide.

We can also then add a link on the top bar.

write use cases

Some ideas for use cases:

• Dev environment
• CI
• Performance regressions
• Test case selection (test only relevant changes).
• monorepos. Linked with above

some other ideas here or here.

Once done, there are a couple of things that can be done as part of this:

• add section in the readthedocs documentation about use cases
• add a section in the README about use cases.
• add a link on the top bar of the website. If this is too much then we can make Documentation a menu with:
  • Getting Started
  • Use cases
  • Guides
  • Reference

first version

This new website is using Hugo and the Docsy theme, and it's built/deployed/tested as described in the README.

For this issue, we'll work on having a basic landing page with links to documentation, blog, repo, slack, twitter, google groups that is served at https://getpopper.github.io/website

improve UI for community page

based on feedback in #10

create contributor persona