As some of you probably know, right now, I’m building a file manager plugin and I want to, somehow, “rebuild” hugo plugin to make it better. But, let’s see something: what does the hugo plugin offer?
- Browse, rename, edit and upload files
- Change hugo settings, edit markdown toml/json/yaml files for hugo
- Run Hugo
Oh… you’re seeing it now. The only thing that differs between hugo and filemanager plugins is the hugo part. So, what are you thinking Henrique? I was thinking about hugo plugin being a filemanager plugin! A plugin for a plugin!!! Got it?
Imagine this situation:
In this case, hugo plugin would somehow require the filemanager plugin on
henriquedias.com folder and then let the filemanager plugin answer all requests except the ones related to markdown files and/or settings. And the best: as I’m the developer of both plugins they could have a very consistent interface and work very nice together.
The problem is: can I require another plugin inside a plugin?
Thank you everyone! What do you think?