Share your config.js right here....

[broberg]

@johnnyboy wouldn’t the visualization of how modules are place be equally as good with the sample config file that is included in the MM package?

It shows you what the format is, but yes a thorough explanation of why it looks like it does would probably help new users to avoid many configuration mistakes. But then again, showing others many different config files wouldn’t really help if they don’t understand why others config files work and theirs don’t.

I think there will be more issues copying and pasting other configurations if there is a lot of 3rd party modules in there. For an example all 3rd party modules that require other dependencies and need the user to do a npm install in the module folder. They might just to a git pull like the other modules and then they are confused why it didn’t work because they missed the read me file for the module.

I think it’s better if there was a educative way to explain the basics of why the config files look like they do, maybe someone can do a video explaining why. I think it was @strawberry-3-141 that perfectly explained the use of commas in lines with the shopping list reference.

Stuff like that would be great for the non-experienced users out there that wants to build their own mirrors!

[johnnyboy]

@broberg said in Share your config.js right here....:

@cowboysdude The showing your mirror category should only be for each mirror made, not general sharing threads.
I think it will get confusing and cluttered if there is ANY other threads than project threads in there.

Agree that it could get cluttered with people asking quite a lot of points about that particular build, and certain points gets lost (This is why Mykle1 will soon reach 1M views… lol ) also if the Author is no longer here, or not online to answer any questions, and is then cluttered with other posters replying to help out.

I suppose the only way that could possibly work, is if the post was locked after pictures and files were posted, (But still leaving the option to Up vote the build) and directing users to then post their question(s) in the relevant place(s) pertaining to their question(s)?
But at least they would see how the Author had laid out his Config.js, etc, so they would have that to compare to, and refer back to, very easily.

If they are directed to the relevant thread for an answer, then it would be there that they could be told the relevant info they need, in order to get the result they want, while subconsciously understanding what is required, having seen the relevant files beforehand… which would also give those helping, a good reference point?
And possibly a Highlighter option so helpers can actually highlight certain areas within the full area picture of the file? Like a virtual finger pointing directly to where, and what, should be done.

I don’t know?.. I’m just throwing some ideas and reasons into the pot… from a newbies eyes.

[1uke_]

@lolobyte I think it needs to be a downloadable file, then everyone get’s the best of both worlds.

People can still see and pick out the bits they want once they have downloaded it.

[1uke_]

Hey @lolobyte, @cowboysdude, @Fonfon, @Mykle1, @slametps @Jopyth, @broberg @johnnyboy

Thanks to everyone for replying.

For this to work I was thinking it could be different to a forum and perhaps needs an interface and layout of it’s own.

Something visual so it’s easy to pick out the information and see how it looks.

I have mocked something up - would love to get your feedback on this

[Mykle1]

@johnnyboy said in Share your config.js right here....:

This is why Mykle1 will soon reach 1M views

My name seems to be getting dropped quite a bit lately

[pugsly]

@1uke_ I would also add a place to download the custom.css file as well.

[cowboysdude]

@1uke_ I like that idea!!!

[1uke_]

@pugsly said in Share your config.js right here....:

@1uke_ I would also add a place to download the custom.css file as well.

Perhaps that could be a button below the download config file?