Skip to content

Commit

Permalink
Add convention on asset retention (#11381)
Browse files Browse the repository at this point in the history
**Why**
While authoring a different feature, it became apparent that we do not store multiple variants of asset "just in case". We can re-export from our authoring tools (i.e., Figma) if need be.

This adds a note why we do not do this for developers from the future.

[skip changelog]
  • Loading branch information
lmgeorge authored and colter-nattrass committed Oct 23, 2024
1 parent a4d3166 commit 2c4f828
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/frontend.md
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,10 @@ For example, consider a **Password Input** component:
- A web component would be named `PasswordInputElement`
- A web components file would be named `app/javascript/packages/password-input/password-input-element.ts`

#### Graphical Assets

Web graphic assets like images, GIFs, and videos are artifacts authored in other tools. As such, there is no need to keep multiple variants of an asset (e.g., SVG and PNG) in the repository if they are not in use.

## Testing

### Stylelint
Expand Down

0 comments on commit 2c4f828

Please sign in to comment.