Giter Club home page Giter Club logo

webassets's Introduction

Web Assets: A Plugin for Pelican

Build Status PyPI Version License

This Pelican plugin allows you to use the webassets module to perform a number of useful asset management functions on your web site, such as:

  • CSS minification (cssmin, yui_css, ...)
  • CSS compiling (less, sass, ...)
  • JS building (uglifyjs, yui_js, closure, ...)

Some other interesting abilities of webassets include:

  • URL Expiry or "cache-busting", allowing you to set the cache headers for your assets long into the future, saving bandwidth and reducing page load-times
  • a spritemapper function to automatically combine multiple icons into one large image with corresponding position slices
  • a datauri function to minimize the number of HTTP requests by replacing url() references in your stylesheets with internal in-line data URIs

For the complete list of what webassets can do, check out the included filters section in the webassets documentation.

Installation

Getting started with webassets couldn't be easier thanks to pip:

python -m pip install pelican-webassets

For more detailed plugin installation instructions, please refer to the Pelican Plugin Documentation.

💡 Keep in Mind: Each function you use in your {% asset filters %} arguments (more on this later) will need to be installed separately. For example, if you wanted to use the libsass filter, you will need to pip install libsass. You can even create a custom filter if you wanted.

Usage

With the plugin installed, include one or more {% assets %} tags into your web site's templates to generate everything your web page will need. For example, something like this in your template…

{% assets filters="libsass,cssmin", output="css/style.min.css", "css/style.scss" %}
  <link rel="stylesheet" href="{{SITEURL}}/{{ASSET_URL}}">
{% endassets %}

… will tell webassets to use libsass and cssmin to compile and minify the css/style.scss file in your theme, and save the compiled stylesheet as css/style.min.css in the output of your finished website, along with the link element like this in your web page:

<link href="{SITEURL}/{THEME_STATIC_DIR}/css/style.min.css?b3a7c807" rel="stylesheet">

🌠 The More You Know: The ASSET_URL variable is the concatenation of your Pelican THEME_STATIC_DIR setting, the output argument, and the "cache-busting" variable we already talked about.

JavaScript Example

As another example, we can use the webassets closure_js function to combine, minify, and compress two files in your web site's theme, js/jQuery.js and js/widgets.js:

{% assets filters="closure_js", output="js/packed.js", "js/jQuery.js", "js/widgets.js" %}
 <script src="{{SITEURL}}/{{ASSET_URL}}"></script>
{% endassets %}

The resulting output will be a single script tag and its corresponding file in your web site's generated output:

<script src="{SITEURL}/{THEME_STATIC_DIR}/js/packed.js?00703b9d"></script>

Configuration

Being a very small wrapper around the webassets module, there are only a few options that you may need.

WEBASSETS_DEBUG

By default, if Pelican is in DEBUG mode (pelican -D ...), this plugin will put webassets in DEBUG mode, to help you with debugging. To override this behavior, set WEBASSETS_DEBUG = False to always process files regardless of Pelican's DEBUG flag, or True to always force webassets into DEBUG mode.

# put webassets into DEBUG mode if Pelican is
WEBASSETS_DEBUG = logger.getEffectiveLevel() <= logging.DEBUG

WEBASSETS_CONFIG

Some webassets filters require extra configuration options to function properly. You can use WEBASSETS_CONFIG to specify these options in a list of (key, value) tuples that are passed along to the webassets environment.

WEBASSETS_CONFIG = [
  ("closure_compressor_optimization", "ADVANCED_OPTIMIZATIONS"),
  ("libsass_style", "compressed")
]

WEBASSETS_BUNDLES

Bundles are a convenient way to group a collection of assets together along with the information on how to properly process the files. The WEBASSETS_BUNDLES option allows us to make these Bundles by taking a list of (name, args, kwargs) arguments that will be passed to the webassets environment.

WEBASSETS_BUNDLES = (
     ("my_bundle", ("colors.scss", "style.scss"),
     {"output": "style.min.css", "filters": ["libsass", "cssmin"]}),
)

Allowing you to simplify something like this in your web site's templates…

{% assets filters="libsass,cssmin", output="style.min.css", "colors.scss", "style.scss" %}

… into this:

{% assets 'my_bundle' %}

WEBASSETS_SOURCE_PATHS

If your raw assets are in directories other than your THEME_STATIC_PATHS, you can supply additional directories to search in with WEBASSETS_SOURCE_PATHS.

WEBASSETS_SOURCE_PATHS = ["stylehseets", "javascript"]

Contributing

Contributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting on existing issues.

To start contributing to this plugin, review the Contributing to Pelican documentation, beginning with the Contributing Code section.

License

This project is licensed under the AGPL-3.0 license

AGPL-3.0

webassets's People

Contributors

avaris avatar botpub avatar bryanbrattlof avatar fbeutel avatar graffic avatar ikeviny avatar justinmayer avatar kdeldycke avatar kernc avatar lucas-c avatar malept avatar pre-commit-ci[bot] avatar robclancy avatar ssteinerx avatar tarasmatsyk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

webassets's Issues

{{ ASSET_URL }} contains unnecessary leading slash

Ported from getpelican/pelican-plugins#1018

{{ ASSET_URL }} contains a leading slash, which is inconsistent with the provided example usage pattern {{ SITEURL }}/{{ ASSET_URL }} that can be found in the readme. This turns into https://example.org//path/to/asset instead of the expected https://example.org/path/to/asset. Either the examples should be updated to not contain a slash between {{ SITEURL }} and {{ ASSET_URL }}, or {{ ASSET_URL }} should not contain a leading slash, which would be more consistent with the rest of Pelican (but I understand this can be a problem because the variable is provided by the webassets dependency).

Release pelican-webassets v2.0.0 on PyPI

This is a ticket to keep track of the packaging and PyPi distribution of the next 2.0.0 version:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.