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

Migrate assets to the resources directory #197

Open
euantorano opened this issue Mar 17, 2016 · 1 comment
Open

Migrate assets to the resources directory #197

euantorano opened this issue Mar 17, 2016 · 1 comment
Labels
p:normal s:confirmed t:code-quality

Comments

@euantorano
Copy link
Member

Larval conventions have raw assets being placed under the resources directory. We should stick to conventions wherever possible.
@euantorano
Copy link
Member Author

Also, we should try and migrate away from bower and rely solely on npm. Most of the packages we use are on npm and I'd rather rely on one service than two.

euantorano added a commit that referenced this issue Mar 17, 2016
@euantorano
Move clear fix to a mixing, add _mixins.scss.
efe28c5 
Move towards elixir and NPM to simplify the management of static
resources for #197 and #196.
@euantorano euantorano mentioned this issue Mar 17, 2016
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
p:normal s:confirmed t:code-quality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@euantorano @JordanMussi