Closed tomas-zemres closed 5 years ago
Materialize library could be installed with npm
And what about "question 2":
Why are the sass/* files exposed to public static directory in every django project installing "django-material"?
It
Materialize library could be installed with npm
But I must manually synchronize correct version of "npm packages" vs. correct version of python package "django-material".
I have currently installed material-css from npm + material-design-icons, but It lead to duplicated files (css, js, fonts, ... ) in public static dir - partially from package "material/static" and partially from npm packages
When I try to use "sass/materialize.scss" for build own css-style (using djang-sass-processor)
I have own "main.scss", it contains:
@import "material/sass/materialize.scss"
But compiling scss failed due to:
"@import "materialize-css/sass/components/..."
in your materialize.scssbecause this path does not exist in your package.
Nice would be If django-material package (installed using pip) contains also all "materialize-css" required for sass processesor to generate complete css file.
Question 1: Why there are only some *.scss files are part of "django-material" package?
Question 2: Why are the sass/* files exposed to public static directory in every django project installing "django-material"?