Readme revamp

[rvlb]

Closes #282
Closes #275
Closes #277

[fjsj]

POLL_INTERVAL is ignored when CACHE is True? If so, please clarify here.

[rvlb]

Updated this section with more explanation

django-webpack-loader/README.md

Lines 86 to 92 in 1609967

	For that setup, we're using the `DEBUG` variable provided by Django when bootstraping a new project. Since in a production environment (`DEBUG = False`) the assets files won't constantly change, we can safely cache the results (`CACHE=True`) and optimize our flow, as `django-webpack-loader` will read the stats file only once and store the assets files paths in memory. From that point pnwards, it will use these stored paths as the source of truth. If `CACHE=False`, we'll always read the stats file to get the assets paths.
	> If `CACHE=True`, any changes made in the assets files will only be read when the web workers are restarted.
	During development, when the stats file changes a lot, we want to always poll for its updated version (in our case, we'll fetch it every 0.1s, as defined on `POLL_INTERVAL`).
	> In production (`DEBUG=False`), we'll only fetch the stats file once, so `POLL_INTERVAL` is ignored.
	While `CACHE` isn't directly related to `POLL_INTERVAL`, it's interesting to keep `CACHE` binded to the `DEBUG` logic value (in this case, the negation of the logic value) in order to only cache the assets in production, as we'd not continuously poll the stats file in that environment.

[fjsj]

It's worth including this again.

[rvlb]

It was moved to here (the section title changed) https://github.com/django-webpack/django-webpack-loader/pull/298/files/b1b517f29d7ae36a44054e925d68e2426ab0c839#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R196

[fjsj]

Does this still exist?

[rvlb]

It does, re-added this section to the readme

[fjsj]

Please check comments.

[fjsj]

LGTM

[ChrisCrossCrash]

Thanks a lot for this! I tried the tutorial linked in the README a few months ago, but I couldn't get it working. I'll give it a shot following the new README.