search

icelab / dry-web-skeleton

Application prototype for Ruby web apps using ROM and Roda
MIT License
41 stars 7 forks source link

newbie guidance: indicate where to place new assets so that the webpack process adopts them #62

Open lonniev opened 7 years ago

lonniev commented 7 years ago

For those unfamiliar with the magic of webpack and webpack-dev-server, include a brief paragraph on where to store new assets (like a materialize.css) in the project structure so that page processing pipeline will adopt and inject those new assets into app-specific views.

I thought @imports in the app's index.css might do the trick but, out of the box, that file isn't processed.

lonniev commented 7 years ago

Also, it isn't real clear who is responsible for spinning up the webpack-dev-server: the docs say "we spin up...". Does that mean that guys in the Icelab Cabana make sure someone starts the server or does the bundle shotgun run fire it up each time it is needed?

Apologies for being ignorant about this app infrastructure stuff.

lonniev commented 7 years ago

For example, if I want to remove the following slim link element from a template (and have a local copy of the .css file) where do I store the stylesheet so that the webpack-magic consumes it?

link href="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.8/css/materialize.min.css" rel="stylesheet" type="text/css" /