Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/collective/collective.lazysizes

Integration of lazysizes, a lightweight lazy loader, into Plone.
https://github.com/collective/collective.lazysizes

Last synced: 3 months ago
JSON representation

Integration of lazysizes, a lightweight lazy loader, into Plone.

Lists

README 

        
********************

collective.lazysizes

********************



.. contents:: Table of Contents



Life, the Universe, and Everything

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



This package integrates `lazysizes `_, a lightweight lazy loader, into Plone.



`lazysizes`_ is a fast, SEO-friendly and self-initializing lazyloader for images (including responsive images picture/srcset), iframes, scripts/widgets and much more.

It also prioritizes resources by differentiating between crucial in view and near view elements to make perceived performance even faster.



By using this package you can expect reductions of up to 80% in load time, 75% in page size and 50% in number of requests.



Mostly Harmless

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



.. image:: https://img.shields.io/pypi/v/collective.lazysizes.svg

   :target: https://pypi.python.org/pypi/collective.lazysizes



.. image:: https://img.shields.io/travis/collective/collective.lazysizes/master.svg

    :target: https://travis-ci.org/collective/collective.lazysizes



.. image:: https://img.shields.io/codacy/grade/13edd837b059493ab64d8186f5fe6cf4.svg

    :target: https://app.codacy.com/project/hvelarde/collective.lazysizes/dashboard



.. image:: https://img.shields.io/coveralls/collective/collective.lazysizes/master.svg

    :target: https://coveralls.io/r/collective/collective.lazysizes



These are some sites using ``collective.lazysizes``:



* `Brazilian Government `_ (BR)

* `Brazilian Presidency `_ (BR)

* `CartaCapital `_ (BR)

* `Conversa Afiada `_ (BR)

* `Portal Brasil 2016 `_ (BR)



As long as `we have tested `_, `lazysizes`_ seems not to interfere with image indexing made by crawlers like Googlebot.



Got an idea? Found a bug? Let us know by `opening a support ticket `_.



Don't Panic

===========



Installation

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



To enable this package in a buildout-based installation:



#. Edit your buildout.cfg and add ``collective.lazysizes`` to the list of eggs to install:



.. code-block:: ini



    [buildout]

    ...

    eggs =

        collective.lazysizes



After updating the configuration you need to run ''bin/buildout'', which will take care of updating your system.



Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.



Check the box next to ``collective.lazysizes`` and click the 'Activate' button.



How does it work

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



This package adds a transformer to the transform chain to integrate `lazysizes`_ into Plone.



The transformer looks for all the ````, ```` and ``
`` tags inside the content and does the following:



* appends a ``lazyload`` class

* if the tag is an ````, transforms the ``src`` attribute into a ``data-src`` and uses a gray square in its place to maintain valid HTML code (this placeholder is loaded using the data URI scheme to avoid a new request to the server)

* if the tag is an ````, transforms the ``src`` attribute into a ``data-src``

* if the tag is a ``
`` `containing a tweet `_, it adds a ``data-twitter`` attribute and removes the ```` tag associated with the Twitter widget to avoid a useless request



These transforms can be applied to all users or only to anonymous.



Look Ma! No Resource Registries

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



This add-on uses a very opinionated approach on how to handle static resources in Plone.

We just deprecated resource registries in favor of a simpler approach: a viewlet in ``plone.htmlhead``.

This simplifies maintainance among multiple Plone versions and avoids bundling of unrelated resources.



Development

-----------



We use `webpack <https://webpack.js.org/>`_ to process static resources on this package.

`webpack`_ processes SCSS and JS files, minifies the resulting CSS and JS, and optimizes all images.



To contribute, you should start the instance in one shell and start webpack watcher on another with the following command:



.. code-block:: console



    $ bin/watch-lazysizes



Then go to ``webpack/app`` folder and edit SCSS and JS files;

`webpack`_ watcher will automatically create the final resources in the right place.



There are also other commands added to handle more complex scenarios.



The following command will set the buildout node installation in the system PATH,

this way you can use `webpack`_ as described on their documentation.



.. code-block:: console



    $ bin/env-lazysizes



The following command generates JS and CSS without the minify step (it can be used to check the code being generated in a human readable way).



.. code-block:: console



    $ bin/debug-lazysizes



The following command rebuilds static files and exit (insted of keep watching the changes):



.. code-block:: console



    $ bin/build-lazysizes



Releasing using zest.releaser

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



Static resources on this package are generated using `webpack`_ and aren't included in VCS.

If you release using zest.releaser you have to `upload manually the files to PyPI <https://github.com/zestsoftware/zest.releaser/issues/261>`_ or you will end with a broken distribution:



* run ``longtest`` and ``fullrelease``, as usually

* answer "no" when asked to upload to PyPI and continue normally

* do a checkout to the tag you're releasing

* run ``bin/build-lazysizes`` to update static files

* create the distribution files using ``python setup.py sdist bdist_wheel`` as usual

* upload the files using ``twine upload dist/*``



In case of errors you will have to create a new release as the PyPI Warehouse `doesn't allow for a filename to be reused <https://upload.pypi.org/help/#file-name-reuse>`_.