@LukeCodewalker It seems the html is malformed and thus the markdown parser in unable to parse it correctly. It looks like the table contains white lines which are not allowed. If you run your markdown thru a markdown linter, you’ll see there is an issue with the markdown of that readme file.

If you work on such an installer. Make sure it’s based on the module infrastructure where possible. That we you can develop and test is, without the need of directly integrating it in mm2. If It’s fully up and running and tested, we can integrate it by adding it to the list of default modules.

By the way, this project is in a horrible raw early alpha stage … buttt, if someone is interested to contribute, the source code is available here: https://github.com/MichMich/MagicMirror-Website/tree/develop

Be advised: the code needs a lot of refactoring and misses a lot of commenting.

The frontend is a SPA based on Vue.js and a bit of Vuex. The Backend/Api is based on Laravel.

If you clone the repo, take the following steps to get it up and running:

• Run: composer install
• Run npm install
• Create an environment configuration: cp .env.example .env
• Run php artisan key:generate`
• Modify the database and github settings in the .env file. (You need to create a github app for testing.)
• Run php artisan migrate --seed to setup the database.

If you make any changes to /resources/assets/js or /resources/assets/sass, make sure to run gulp to compile.

I suggest you fork the project, implement the fix that works for you and send me a PR. That way you can test it and others can benefit from your solution. :)

@strawberry-3-141 Feel free to use it, BUT …

• Keep in mind the URL will change in the future.
• I can’t promise it will stay the same.
• Keep in mind that it will only give you a subset of the modules. (user query paramaters limit and offset to get more)

If it turns out external API usage will be too heavy, I might limit the access using API keys.

Yes it will be searchable. You can already click on a tag or category to filter.

The number you see in the link is the ID of the module in the database. This will anger change. Even if you change the name of your module, the link will remain working.

If you have multiple modules, you can also link to an overview of all your modules: click on your name in the top right, and choose “my modules”.

Because the number of modules you guys created grew FAR above what I expected when I started this project, I think it couldn’t hurt to improve the discoverability of the modules. Because of this, I’m working on a new and improved website which includes a module search …

In the future, I’ll add:

• Module suggestions based on the modules you like.
• Similar modules on a module page.
• Modules per user (“Other modules by this developer”)

If you have any suggestions, feel free to let me know, although I won’t promise anything…

It’s far beyond finished, but if you’re curious, feel free to check out the very early beta version:

http://beta.magicmirror.builders/modules

If you login with your github account, you should be able to add your modules. As a test I added some random modules.

Please note that I might need to reset the database in the future. So don’t spent too much time on adding your modules. (Although a filled database would be helpful in the development.)

I really really really like your setup! :) Nice work!

Just curious: which version of MM are you running?

Offtopic: It’s so freaking cool to see a Chinese(?) version of my mirror! :)