Hey Alex. Pelican maintainer here. By adding the legacy monolithic Pelican Plugins repository as a submodule in this theme, anybody who follows the instructions listed on the legacy monolithic Pelican Plugins repository README…
… will end up with the entire contents of the legacy monolithic Pelican Plugins repository recursively downloaded along with the Flex theme. This is probably not what they want to happen.
Any chance you might consider removing that submodule from the project?
The text was updated successfully, but these errors were encountered:
Hey Alex. Pelican maintainer here. By adding the legacy monolithic Pelican Plugins repository as a submodule in this theme, anybody who follows the instructions listed on the legacy monolithic Pelican Plugins repository README…
… will end up with the entire contents of the legacy monolithic Pelican Plugins repository recursively downloaded along with the Flex theme. This is probably not what they want to happen.
Any chance you might consider removing that submodule from the project?
The text was updated successfully, but these errors were encountered: