Open BDFife opened 10 years ago
willkg
commented
10 years ago The plugins/ directory is just for your plugins. There are a bunch of plugins that come with Douglas and those stay in the Douglas codebase because they get updates and fixes and all that with Douglas. This reduces the pain in maintaining your blog over the long term.
So this is a documentation fix. Which parts of the documentation do you think led you to this conclusion?
BDFife
commented
10 years ago In the config.py, there was no mention of "built-in" plugins that I noticed. It's possible I overlooked the mention in the section that specifies enabled plugins and plugin paths.
Also, from plugins.rst: Finding plugins
As of 1.5, Douglas comes with a core set of plugins. Documentation for
these plugins is in
:ref:part-twohttps://github.com/willkg/douglas/blob/master/docs/plugins.rst#id3
.
It does look like I missed the helpful 'plugins' folder in the docs directory. So, most of what I needed was accessible.
On Thu, Nov 28, 2013 at 8:52 PM, Will Kahn-Greene notifications@github.comwrote:
The plugins/ directory is just for your plugins. There are a bunch of plugins that come with Douglas and those stay in the Douglas codebase because they get updates and fixes and all that with Douglas. This reduces the pain in maintaining your blog over the long term.
So this is a documentation fix. Which parts of the documentation do you think led you to this conclusion?
— Reply to this email directly or view it on GitHubhttps://github.com/willkg/douglas/issues/17#issuecomment-29492084 .
After installing the latest build and setting up a default blog with the command 'douglas-cmd create', I found the 'plugins' directory was empty.
It seems like, after reading the documentation, the code for the default plugins should be located in the plugins directory (paginate, draft_folder, tags, yeararchives, published_date).