-
Notifications
You must be signed in to change notification settings - Fork 5
Add calls to action to the landing page #21
Comments
https://github.com/chef-cookbooks/chef-client/blob/master/README.md#maintainers example in readme of chef cookbooks |
what happened to our index page? |
if I change <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 |
Deeply rough content inventory:
|
Inspirational sites: |
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". |
Homework pre-design consult:
|
Looks like |
A "how to build our cookbooks" might be helpful - a hand-holding page on how to converge/verify cookbooks locally. |
We should have big buttons and brief explanations for all the following use cases
The text was updated successfully, but these errors were encountered: