Skip to content

Commit

Permalink
Add "next" CTAs to the front page
Browse files Browse the repository at this point in the history
  • Loading branch information
gadenbuie committed Mar 27, 2024
1 parent cf14710 commit 365e072
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -97,4 +97,12 @@ Users like Kendall and Jacqui will interact with `brand.yml` in three primary wa
7. Because the `brand.yml` is by design incomplete for any given output format, it needs to fit into a workflow that makes specific outputs formats shareable and reproducible.

1. This could mean that `brand.yml` tooling is flexible enough to store format-specific options, e.g. to encompass additional assets used in Shiny apps or Quarto websites, or format-specific options for Quarto PDF documents, etc.
2. Alternatively, `brand.yml` tooling could fit into larger, existing tools for sharing settings and formats, like R packages, Quarto custom formats, or a Shiny `html_dependency()`.
2. Alternatively, `brand.yml` tooling could fit into larger, existing tools for sharing settings and formats, like R packages, Quarto custom formats, or a Shiny `html_dependency()`.

## Next

Jump to [brand.yml syntax](brand/index.qmd) to see the proposed structure the `brand.yml` file.

I've also collected some [cross-cutting open questions](brand/open-questions.qmd) that need further thinking.

Finally, I've included some [examples of brand guidelines](examples/index.qmd) found in the wild, as well as [examples of design systems](examples/index.qmd#design-systems) to provide inspiration.

0 comments on commit 365e072

Please sign in to comment.