Angel Fernando Quiroz Campos 3b433e2036 Update bower assets %!s(int64=8) %!d(string=hai) anos
..
_includes 3b433e2036 Update bower assets %!s(int64=8) %!d(string=hai) anos
_layouts cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos
_sass e0adf91451 Updating based in bower.json %!s(int64=8) %!d(string=hai) anos
css e0adf91451 Updating based in bower.json %!s(int64=8) %!d(string=hai) anos
images 3b433e2036 Update bower assets %!s(int64=8) %!d(string=hai) anos
.gitignore cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos
README.md cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos
announcements-4.0.html e0adf91451 Updating based in bower.json %!s(int64=8) %!d(string=hai) anos
browserconfig.xml 3b433e2036 Update bower assets %!s(int64=8) %!d(string=hai) anos
community.html cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos
examples.html e0adf91451 Updating based in bower.json %!s(int64=8) %!d(string=hai) anos
index.html 3b433e2036 Update bower assets %!s(int64=8) %!d(string=hai) anos
options-old.html cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos
options.html cf9703b2a5 add static assets %!s(int64=9) %!d(string=hai) anos

README.md

Select2 Documentation

This repository holds the latest documentation for Select2.

What is this?

The documentation is automatically extracted from the docs directory at the Select2 source repository. This is done periodically by the maintainers of Select2.

How can I fix an issue in these docs?

If you are reading this from the source repository, within the docs directory, then you're already in the right place. You can fork the source repository, commit your changes, and then make a pull request and it will be reviewed.

If you are reading this from the documentation repository, you are in the wrong place. Pull requests made directly to the documentation repository will be ignored and eventually closed, so don't do that.

How can I build these docs manually?

In the main Select2 repository, you can build the documentation by executing

grunt docs

Which will start up the documentation on port 4000. You will need Jekyll installed to build the documentation.