(In-progress) Streamline creation of development environment and add usage documentation.

[theKnightsOfRohan]

I've noticed that, in the process of getting started with banana and writing my own pages, that the setting up of the development environment is a little more difficult than some other development-based plugins, mostly because of banana's novel approach. So, I've started this pull request in order to document the creation of the documentation, as it were.

Here are my plans:

• Fix bug in tree-sitter initialization where filetypes were not registers
• Create initial docs for devenv and plugin development
• Consolidate highest-module lua functions into setup method (setup_plugin() and setup_env()?)
• Further develop usage page as I get comfortable with using raw html and maybe make some examples

I'm making this PR early so that you know what types of changes I will be making. I would appreciate if you could make sure I don't do anything which conflicts with your vision of this plugin. Feel free to let me know if there's anything else related you want me to work on as well!

[CWood-sdf]

This all seems really great! There is not much documentation right now because I have been spending most of my time on core html features (currently I'm working on css grid display, after that I'll probably do

then maybe transitions and animations), so the documentation is not really great right now.

I think consolidating the high level modules into the require('banana') path is a great idea. afaik right now, the only real require needed for a plugin is require("banana.instance").newInstance(), then banana does all the work after that

[CWood-sdf]

Most of this seems really great, thank you so much for doing this!

However, there are a few things that you have setup that I disagree with:

• the remapping in the jumpstart.lua file should be done in the plugin's setup method
• the instance could probably be lazily loaded to not trigger unnecessary parsing (this can be done with an if instance == nil ... in the keymap)
• when you say "all of your lua scripts are called from the index.nml file", i think it might need to be clarified that the banana specific lua scripts are called from the index.nml file. plugin authors will still need their own lua scripts with setup methods, apis and the like. my vision with banana is that a good plugin has a really good api that the plugin author uses for the banana pages (i essentially want banana to incentivize having a good api)

[CWood-sdf]

One other thing: maybe have a top and left property on the nml selector just to show that the user can change the position with those properties

The rest of this all looks really great and I'm really looking forward to when I can merge this into main

[theKnightsOfRohan]

Yeah, I'll specify that the jumpstart file should not be part of the actual plugin, it's just a way to open the page itself for simpler projects. That's why I had it outside the normal project file structure. I haven't had as much time as I would like to work on the docs due to being out of the country, but now I can incorporate your feedback!

[CWood-sdf]

gotcha, thanks for clarifying, I was a bit confused by that

[CWood-sdf]

I just created an example banana plugin if you want to look at that for how I envision laying out banana plugins

link