With more than 4 years in the making, this release started “better late then never”, but it turned out to so much more than that.
With the community spark re-ignited, this has become the biggest release since probably 1.0. And as such a very worthy release to carry the 2.0 crown.
Elegant v 2.0 is finally here!¶
A lot has happened since the last release of elegant theme and a great effort was also done and new steps for the future have been set as the way forward.
V2 is not only a new set of bytes but also features and probably, the most important step has been evolving elegant into a community effort.
Talha, who created the elegant theme, helped this movement by setting a new home for the repository and the documentation as well as adding some next steps towards evolving the theme faster in the future by removing some dependencies.
A brave set of collaborators have helped shape this future via new issue creation, review of pending pull requests and defining how the community and project should continue.
This has been noticed in the last months activity in the repository, the opened issues, and zapping the old ones not to lose any contribution, either from their original authors or resubmitting them on their behalf.
A lot of things are remain to be done that will allow pelican 4.0 compatibility, removal of legacy code inherited from bootstrap, etc
Don’t hesitate to give Elegant a new try, testing the new version or experimenting it at our brand new documentation/demo site at https://pelican-elegant.github.io.
And of course let us know if something is not as you would expect or wish so that we can have Elegant become your pelican theme.
Thanks to all our contributors mentioned either at Authors document https://github.com/Pelican-Elegant/elegant/blob/master/AUTHORS.md or at https://github.com/Pelican-Elegant/elegant/graphs/contributors
119 issues were closed in the 2.0 release – an impressive number, even if we take into account that many of the bugs were of an organizational nature, as Pelican Elegant has changed the development and governance model (more on that in a separate post). Compare that to 1.3 release, which consisted of 4 issues, or the total amount of closed issues so far, which amount to 133.
From 1.3 release until the 2.0 release there were 316 new commits in total and divided as follows (excluding merge commits):
- Talha Mansoor – “talha131”: 264 commits
- Pablo Iranzo Gómez – “iranzo”: 8 commits
- Calf Zhou – “calfzhou”: 7 commits
- Andrew Wegner – “AWegnerGitHub”: 6 commits
- Matija Šuklje – “silverhook”: 5 commits
- Jeremy Thurgood – “jerith”: 1 commit
- Mobile Developer – “0x8BADFOOD”: 1 commit
- Leo Torres – “leotrs”: 1 commit
- Gan Shen – “gshen42”: 1 commit
- Gert van Dijk – “gertvdijk”: 1 commit
- Miguel Lechón – “debiatan”: 1 commit
As we can clearly see, by any metric this is a huge milestone for Elegant.
Most issues belonged to bugs and dependency updates, amongst the biggest:
- support for HTTPS out of the box by making the links protocol agnostic
- fix for search to work again
- fix of accordion menus not opening up – fixes both issues with categories and comments
- fix of table of content
- much improved build speed
- support for Jinja 2.9 (and newer)
But also new features were added. To list just a few:
- article summaries in recent posts
- added links to social networks (if so desired)
- support for several analytics providers
- support for the
seriesplugin (instead of the deprecated
- non-English languages are now possible as default, as well as having translations of articles
- big steps towards full W3C compliance
- support of LaTeX as input format
- support for Disqus comments
- new website and documentation (more on that in a separate post)
For a full CHANGELOG, see below.
Below is the full CHANGELOG:
- Link to your social profiles
- Upgraded to Twitter Bootstrap 2.3.2
- Upgraded to Tipue Search 3.1
- Support for
- Stat Counter Analytics support
- Google Universal Analytics support
- Support for custom icons for social profiles
- Support for Pelican (>3.3) new metadata
- Support for Social Media Tags
- Support for Google Authorship
- Translations support
COMMENTS_INTRO. Now you can define article specific comments introduction
- Add Disqus comments to Pages
- All customizable variables consolidated in a single
_defaults.html, making it easier for you to customize or even localize the theme
- Adds author blurbs at the end of the article
- 4x faster output
- Reduce number of HTTP requests using
- Shortcut icons, like favicon, are disabled by default. Set
USE_SHORTCUT_ICONSto true to enable it
- Email newsletter subscriber form style matches rest of the theme
- Article images have a visible border
- Block quotes have a quote icon instead of a thick line on left
- Article’s paragraph font size is bigger, for better readability
- Remove unnecessary padding in sidebar’s tag list
- Archives page and recent posts on home page have better presentation
- Time stamps in categories and tags pages are justified
- Line number in code block is hidden on tablets and phones to save space for content
- More sizes of image for Apple Touch icons
- Fixed: Nested lists have different font sizes
- Fixed: CSS style rules for literal block in reST is missing
- Fixed: Long lines in code block will wrap to next line
- Fixed: Code block will not play nice with line numbers
- Fixed: Subscribe button changes its size on smaller screens
- Fixed: Articles under tag heading on tags page are not sorted
- Fixed: URL scheme for blogs which are not published to the root folder
- Fixed: Footer is always under the fold even on smaller length web pages
- Fixed: Site Name and top navigation menu move to left on wide displays
- Fixed: Page link is not active in the navbar if
SAVE_PAGE_ASis not set to default
neighborplugin to show next and previous articles
assetsplugin to minify CSS and JS files
- Support for
- Support for
- Support for
- Search results link open in the same window, which is consistent with internet search engines
- Comments section message changes when user toggles it
- Fixed: Clicking Search button in 404.html does not trigger search