Sorry for the relatively noob question - just trying to decode how to bolt things into an existing app. Django 1.11, Python 3, using MaterializeCSS 1.0 Alpha. I've cloned the demo over from Github. Looks like I replicate the whole tree under app Material into my project, replicate demo.py to get a material.base import and 3 class definitions as my own appname.py, put material, material.frontend and material.admin as INSTALLED_APPS up front in my apps settings.py and - is that it?
Just agonising over bits and bobs in the demo as it's still referencing jQuery in places, which I thought had gone away as a MaterializeCSS dependency. And wondering if I put the materialize/1.0.0-alpha.2 minified CSS and js includes off their CDN or use the ones left in the material/admin/css and /js directories?
Any help or guidance really appreciated.
pip install django-materialand then follow: http://docs.viewflow.io/material_frontend.html
Django 2.0 support Drop Material Admin
Stuck on the real basics. I have a project called say "project_fred", have an app in there called "fred", do a pip install of django-material. The project and app already have customisations to have email address as the sole authentication method. Done the addition of material, material.frontend and material.admin to installed apps. Is there a way to scaffold out the material support files if I already have an app defined?
I'm suspect there's a missing fred.apps.fredConfig needed in INSTALLED_APPS along the way too.
fredcontain models, views, urls, templates? is it in your project settings?
TEMPLATES. As for the static files, you have to run manage.py collectstatic in your production. Regarding the FredConfig, well, before installing django-material you should have had FredConfig in the installed apps already, otherwise your project would not know that it should use/display the fred app.
index.htmlis simply a template and usually you put it in
project/templates/fred/index.html. I suggest the first one as it means you will be able to locate all your app templates quickly (ie. each app has template folder), as opposed to having 1 massive templates folder in your project directory (it's still useful to have it, for some project wide stuff).