Skip to content
This repository has been archived by the owner on Sep 3, 2023. It is now read-only.

Add calls to action to the landing page #21

Open
josephholsten opened this issue May 27, 2017 · 9 comments
Open

Add calls to action to the landing page #21

josephholsten opened this issue May 27, 2017 · 9 comments

Comments

@josephholsten
Copy link
Contributor

We should have big buttons and brief explanations for all the following use cases

  • know of something broken?
  • need to use a particular cookbook?
  • want to help review open issues/PRs for an particular cookbook?
  • need to report a license or code-of-conduct violation?
  • something else?
@damacus
Copy link
Contributor

damacus commented Jul 17, 2017

@josephholsten
Copy link
Contributor Author

what happened to our index page?

@josephholsten
Copy link
Contributor Author

if I change themes/hyde-y/layouts/partials/homepage.html to contain:

<section id="main-content" class="container main_content homepage">
  <header class="container header">
    {{ partial "bloc/content/h1-title" . }}
    {{ partial "bloc/content/lastupdate" . }}
  </header>

  {{ partial "bloc/content/content" . }}
  
  {{ $paginator := .Paginate (where .Data.Pages "Type" "post") }}
  {{ range $paginator.Pages }}
    {{ .Render "summary" }}
  {{ end }}
  {{ partial "bloc/content/pagination" . }}
</section>

Then I see a more interesting home page

@josephholsten
Copy link
Contributor Author

Deeply rough content inventory:

- Homepage
  - meeting minutes index
    - 2019-03-18
    - ...
  - contributir process index
    - how to ...
  - cookbook index
    - mongodb
      - supermarket
      - changelog
      - git repo
      - issues
    - ...
  - blog index
    - 2018-12-31-releases.md
    - ...


Where do these go?

- link to slack <- emphasis
- link to irc
- link to mailing list

@josephholsten
Copy link
Contributor Author

@josephholsten
Copy link
Contributor Author

josephholsten commented Mar 18, 2019

Ideally, the landing page design would have a single primary call-to-action, and a series of less prominent ones for each persona.

I suspect that the ideal primary call-to-action is something like "Found something wrong with our cookbooks?" "Chat with us".

@JohnRoesler
Copy link
Contributor

Homework pre-design consult:

  • what we want to highlight on the site in order of importance
  • a list of 3 to 5 websites that the team likes that do similar things with notes about what we like about each of the sites
  • a definition for sous-chefs brand
  • exact deliverable e.g. a full color sample screen shot of what the site would look like on desktop and mobile, actual usable images, other?

@JohnRoesler
Copy link
Contributor

Looks like what we want to highlight on the site in order of importance is done in the first comment of this issue

@wheresalice
Copy link

A "how to build our cookbooks" might be helpful - a hand-holding page on how to converge/verify cookbooks locally.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

4 participants