Tip: Try writing your Pro Config .JSON in VS Code

[autumn maple]

Having trouble keeping track of what is what in your Pro Config .json? Is it growing out of control & hard to manage?

I've seen several different approaches to configuring an efficient workspace for writing .json, & I tried a few before I landed on this.

Here's my workspace of preference:
Working in VS Code with the aptly titled JSON Extension allows really helpful ways to view your data & grasp large projects. (See attached image.) There is a collapsible view of all your data, making it easy to jump to the right spot, or "zoom out" & visualize things in a better way. Try it out if you haven't found a nice home for your work yet.

Bonus tips:

• JSON Crack is also a popular way to work with these files, & there's a JSON Crack Extension for VS Code as well! Might hit a paywall with that one though, depending on how much you want out of it...

• If you want to open source your work (which I plan on doing), you can publish to git repos directly within VS Code, if that suits you!

• Make sure you turn on all them rainbow bracket thingies to really make it easy to read as well!

Cheers!

Don't pay too much attention to the actual code in that image, btw. It's half baked at best. lmao

[worthy pawn]

Can the developers of the myshell project add the ability to upload local images, audio, and short videos to enrich the Intro message on the bot creation page?

[gritty belfry]

Is already possible, look around in the forum for guides on it.

[autumn maple]

Sorry, this is a million years later, but you can host images on a multitude of other sites, & bring them in with markdown syntax, like so:

![](https://raw.githubusercontent.com/symmetricalboy/myshell-assistant/main/images/intro_message.gif)

Putting this at the top of my intro message loads up the .gif I made for just such a thing. I'm using GitHub as a hosting method, but you may need to find other services to suit your needs.