[Hyde 1.0] Plugins

[Lakshmi]

Hello All,

Bundling the plugins in hyde was following the "batteries included" nature of python. However, this has been 

problematic for hyde at so many levels, the worst of which is the cost of maintenance and documentation.

So my tentative plan for handling plugins in 1.0:

1) `hyde.plugins` will become a namespace package.

2) hyde will bundle essential and lean plugins[A] others will be in their own github repo and will have 

    their own package on pypi.

3) Plugin authors may choose to install in the `hyde.plugins` namespace

4) No differences in the API, behavior of plugins. They will have to be explicitly specified in `site.yaml` 

    despite the extra installation step.

I see the following benefits with this approach:

* Plugins and their dependencies are managed by the plugin package. No explicit documentation is needed to clarify 

  what dependencies are needed for a plugin.

* Plugin maintenance is taken care of by the plugin authors and maintainers.

* Plugin documentation is separate and focussed on the plugin

* Hyde repository becomes more manageable

The downside to this is that changes to hyde need to be done with care and tested with as many plugins as possible

to avoid breaking changes. I don't see that as a major issue.

--------------------------------------

A) What are essential and lean plugins:

=============================

* Leanness is directly related to dependencies weighed in this order:

   1. No dependencies at all

   2. Python only dependencies

   3. Easily installable non python dependencies 

   4. Others (*cough*nodejs*cough*) 

* What are essential

================

My list is limited to:

1) Organization: Sorter, Tagger, Grouper, Paginator, Flattener, Depends

2) Multilanguage

3) Media management: combine, clevercss (?), jsmin (?), imageoptim (?)

Plugins like meta and urlcleaner ought to be a part of hyde and will be in core.

Thanks

Lakshmi

[Lakshmi Vyas]

Thanks everyone for the kind and encouraging words.

Fantastic!  Let us know where we can help!

My task for today (in a 1.0 branch of hyde) is to move as many plugins out from hyde 

as possible while making sure that hyde can be used as is for most purposes.

These are the plugins I use for most of my websites:

- Organization: Sorter, Tagger, Grouper

- Text: Blockdown, Syntext

- Media: Combine, Stylus, Uglify

However, I want to get rid of plugins with nodejs dependencies from hyde core 

and I am trying to figure out the best defaults.

* https://github.com/Kronuz/pyScss - Seems to be the best bet for a well rounded python CSS compiler

* https://bitbucket.org/dcs/jsmin - JS Minifier

What plugins do you guys use? What would you like/expect to see as bundled 

plugins when you install hyde?

Thanks

Lakshmi

--
You received this message because you are subscribed to the Google Groups "Hyde" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hyde-dev+u...@googlegroups.com.
To post to this group, send email to hyde...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/hyde-dev/-/v5uzJYM2_zkJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Derek Ashley Thomas]

I would definitely find myself using pyscss as part of hyde for all of my websites.