plugins VS shell-driver

We are also hoping to open up more of the codebase over time. For example, the plugins that we are launching soon will be OSS. The manual pages we launched this week are also OSS. We currently can't do it for all of our codebase because It's just very hard to maintain a large fully OSS codebase. As a startup with a small dev team, we simply don't have resources to do that right now and our efforts are currently concentrated on more critical things like supporting Linux and Windows.

For example, the plugins we are launching soon will be OSS.

I needed a way to document my shell scripts (or code snippets) and to quickly replace “parameters”. For example, if you want to download a YT video as mp3, you have to remember this command “youtube-dl --extract-audio --audio-format mp3 ” . You can use the autocomplete & history in the terminal but you still have to remember parts of the command and replace the old URL with the new one. You can also save it in a text file, and replace … too many select/replace/copy/paste ops…

A few months ago I made a good enough solution for my problem https://github.com/alexadam/reactive-doc - it saves ~ 10 minutes/day when I have to run complex devops scripts. And I can quickly share the ‘docs’ because they are just plain html files / or markdown.

Now I just finished the next iteration - better ‘syntax’ for input widgets, runnable @shell commands and a web based terminal https://github.com/alexadam/shell-driver with custom filters and selection actions (useful for me)

Next steps: add more features to the web based terminal -> convert history to scripts, autocomplete with parameters, command palette & context aware menus, multiple terminals (with tabs or panels). I also want to add support for React components in the MD editor.