add weather templates#366
Merged
Merged
Conversation
Contributor
|
MMM-Theme?????? |
Contributor
Yes, it makes sense to include them, even if they are not real modules.
I can imagine that themes would also make sense for some other modules (especially calendar) and that we might expand it accordingly at some point. In that case, a general naming concept would be nice. I don't have a good idea yet, but just for the sake of discussion here, here's a prefix suggestion (similar to khassels's second one) for all default modules:
Or (like khassel's first suggestion) simply use MMT and instruct the creators to choose a name that makes it clear which module it is for. |
KristjanESPERANTO
approved these changes
Mar 9, 2026
Collaborator
Author
|
I don't think we get so much templates for other modules, I will use |
khassel
added a commit
that referenced
this pull request
Apr 1, 2026
* docs: improve autostart guide with user systemd service for full Electron UI (#345) * Update autostart.md Improve autostart documentation: add user systemd service for full Electron UI with logging and environment variables * Update autostart.md docs: address PR feedback — clarify display server and disable logging by default * Update autostart.md docs: verified the environment inherited by systemd --user, ensured DISPLAY=:0 and WAYLAND_DISPLAY=wayland-0 is set up automatically * Update autostart.md docs: updated Troubleshooting section * clarify systemd service behavior + minor changes - Add platform note: Clarify guide is for Raspberry Pi OS Desktop - Fix typo: WAYLAND_DIAPLAY → WAYLAND_DISPLAY - Fix misleading comment: System services start on boot, not after user login - Remove trailing whitespace and newline --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> * style: set carbon ads background color to inherit (#350) * location of default modules changed (#353) see MagicMirrorOrg/MagicMirror#4019 * move custom.css from css to config (#354) * update variables in config * add secrets.md * fix typo * add missing " * node_modules/vitepress/types/default-theme.d.ts * apply Prettier formatting * handle cspell issues * add weatherapi options to weather module configuration (#359) * docs(compliments): clarify remoteFile path resolution and limitations (#360) * docs: correct loaded() - server-side only, not a client-side hook (#361) Document that loaded() belongs to node_helper, not Module. Add async/Promise support to the start() docs as the correct way to handle asynchronous module initialization. * docs: clarify that public folder requires node_helper.js (#362) * docs: explain physical concept and hardware scope on landing page (#365) Add a short paragraph to index.md that explains what a MagicMirror physically is, clarifies that this documentation covers the software side only, and points newcomers to the community showcase for hardware build inspiration. Closes MagicMirrorOrg/MagicMirror#3282 * add weather templates (#366) * weather: add themes example * calendar: align showEnd and dateEndFormat defaults (#368) * fix failing tests --------- Co-authored-by: Github Actions <actions@github.com> Co-authored-by: Станислав <52878917+vectorman115@users.noreply.github.com> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: veeck <gitkraken@veeck.de> Co-authored-by: sam detweiler <sdetweil@gmail.com> Co-authored-by: Andrés Vanegas Jiménez <142350+angeldeejay@users.noreply.github.com>
khassel
added a commit
that referenced
this pull request
Apr 30, 2026
* docs: improve autostart guide with user systemd service for full Electron UI (#345) * Update autostart.md Improve autostart documentation: add user systemd service for full Electron UI with logging and environment variables * Update autostart.md docs: address PR feedback — clarify display server and disable logging by default * Update autostart.md docs: verified the environment inherited by systemd --user, ensured DISPLAY=:0 and WAYLAND_DISPLAY=wayland-0 is set up automatically * Update autostart.md docs: updated Troubleshooting section * clarify systemd service behavior + minor changes - Add platform note: Clarify guide is for Raspberry Pi OS Desktop - Fix typo: WAYLAND_DIAPLAY → WAYLAND_DISPLAY - Fix misleading comment: System services start on boot, not after user login - Remove trailing whitespace and newline --------- Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> * style: set carbon ads background color to inherit (#350) * location of default modules changed (#353) see MagicMirrorOrg/MagicMirror#4019 * move custom.css from css to config (#354) * update variables in config * add secrets.md * fix typo * add missing " * node_modules/vitepress/types/default-theme.d.ts * apply Prettier formatting * handle cspell issues * add weatherapi options to weather module configuration (#359) * docs(compliments): clarify remoteFile path resolution and limitations (#360) * docs: correct loaded() - server-side only, not a client-side hook (#361) Document that loaded() belongs to node_helper, not Module. Add async/Promise support to the start() docs as the correct way to handle asynchronous module initialization. * docs: clarify that public folder requires node_helper.js (#362) * docs: explain physical concept and hardware scope on landing page (#365) Add a short paragraph to index.md that explains what a MagicMirror physically is, clarifies that this documentation covers the software side only, and points newcomers to the community showcase for hardware build inspiration. Closes MagicMirrorOrg/MagicMirror#3282 * add weather templates (#366) * weather: add themes example * calendar: align showEnd and dateEndFormat defaults (#368) * fix failing tests * documentation for secrets and cors (#374) --------- Co-authored-by: Github Actions <actions@github.com> Co-authored-by: Станислав <52878917+vectorman115@users.noreply.github.com> Co-authored-by: Kristjan ESPERANTO <35647502+KristjanESPERANTO@users.noreply.github.com> Co-authored-by: veeck <gitkraken@veeck.de> Co-authored-by: sam detweiler <sdetweil@gmail.com> Co-authored-by: Andrés Vanegas Jiménez <142350+angeldeejay@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I will add an example for themes later (have to set it up first).
Other questions:
How do we handle themes? Are these "special" modules and should be added to the module list? If yes, maybe as own "category"?
Example: I have an existing module MMM-WeatherBridge which I now want to convert to a theme.
First thing is I prefer to begin a new git repo for this because otherwise it would break existing installs (they would pull as usual and everything would be broken).
Next thing is naming: Should we use a new prefix beside MMM?