Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mention milligram in the guides #4570

Merged
merged 3 commits into from Oct 29, 2021
Merged

Mention milligram in the guides #4570

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
da8ed09
Mention Milligram in guides
H12 Oct 29, 2021
2c6a9ba
Remove potentially-confusing acronym
H12 Oct 29, 2021
9e5ee30
Update guides/directory_structure.md
josevalim Oct 29, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 3 additions & 1 deletion guides/directory_structure.md
View file
Open in desktop
Expand Up @@ -129,6 +129,8 @@ The `assets` directory contains source files related to front-end assets, such a

Your other static assets are placed in the `priv/static` folder, where `priv/static/assets` is kept for generated assets. Everything in `priv/static` is served by the `Plug.Static` plug configured in `lib/hello_web/endpoint.ex`. When running in dev mode (`MIX_ENV=dev`), Phoenix watches for any changes you make in the `assets` directory, and then takes care of updating your front end application in your browser as you work.

**NB:** When you first create your Phoenix app using `mix phx.new` it is possible to specify options that will affect the presence and layout of the `assets` directory. In fact, Phoenix apps can bring their own front end tools or not have a front-end at all (handy if you're writing an API for example). For more information you can run `mix help phx.new` or see the documentation in [Mix tasks](mix_tasks.html).
Note that when you first create your Phoenix app using `mix phx.new` it is possible to specify options that will affect the presence and layout of the `assets` directory. In fact, Phoenix apps can bring their own front end tools or not have a front-end at all (handy if you're writing an API for example). For more information you can run `mix help phx.new` or see the documentation in [Mix tasks](mix_tasks.html).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an extremely minor change that is outside the scope of this PR.

I added it because until reading this paragraph I had never seen the acronym "NB" before and had to google it, which slightly increased my friction when reading these docs.


If the default esbuild integration does not cover your needs, for example because you want to use another build tool, you can switch to a [custom assets build](asset_management.html#custom_builds).

As for CSS, Phoenix ships with a handful of custom styles as well as the [Milligram CSS Framework](https://milligram.io/), providing a minimal setup for projects. You may move to any CSS framework of your choice. Additional references can be found in the [asset management](asset_management.md#css) guide.