Design comparison
Solution retrospective
In most of the documentation for Angular multiple theme approach people have used material, or they have added the dark/light classes in the component hmtl. Material is a good and convenient sollution, but adding theme class on component is not very useful if you have lots of component. So in this approach the theme variable I have loaded gloabally only once, then that can be used anywhere in the application.
What challenges did you encounter, and how did you overcome them?Dual theme without material felt very much exciting. In this approach I am dynamically appending css theme files to the dom. It took some time to figuring out the exact way, but it was worth. :)
Community feedback
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord