Luna 2.0.9 and 2.1 Preview 2

Also… documentation announcement

I know that it hasn’t even been a week, but we’re happy to say that the next update to Luna, version 2.0.9, is now available to download! And to make sure that people the 2.1 Preview are not missing out on all the fixes and enhancements we’re releasing 2.1 Preview 2 as well with the same fixes as 2.0.9 and a number of other improvements.

Luna 2.0.9

Luna 2.0.9 is just a minor update with a bunch of bugfixes and other minor improvements. Here’s what to look out for:

  • More improvements for PHP 7.2 support
  • A number of fixes for localization
  • Site descriptions can now be 300 characters (up from 255)
  • Improved error for invalid search queries
  • Fixes the in 2.0.8 introduced bug where a space was missing between a name and “wrote” in a quoted comment
  • Updates references to GetLuna.org to match our updated website (see below)
  • Updates the “Check for updates” feature
  • A set of bug fixes

Since Luna 2.0.8 we use the by Git (and GitHub) generated zip-files as downloads from our website. However, we didn’t think this one through since Git also includes a number of irrelevant files (like .gitignore) that should not be part of production versions. Today’s update rectifies that and Git will now leave such files out of the download.

Another GitHub-related change is the inclusion of a number of files in our repository for issue templates, pull request templates, etc. But also the GPL v2 license. Except of the license, non of these files actually make a difference to the package you download, but it does make reporting issues and requesting features easier on GitHub.

For more details I would like to refer to the release notes.

Luna 2.1 Preview 2

Luna 2.1 Preview 2 contains the same set of fixes and improvements as Luna 2.0.9, but of course it also bring a number of other features and enhancements to the table. The most notable changes since Preview 1 are:

  • Forum icons can now be set to be either Solid, Regular or Brand icons from Font Awesome Free, if you enabled Font Awesome Pro, you can also choose the Light icons
  • Improved night mode with better contrast and a darker design for the mainstage
  • Fifteen and Sunrise have been rewritten in SCSS and the CSS file included in the download is now compressed resulting in smaller stylesheets and thus faster loading times, this also makes these themes easier to maintain
  • Fifteen has an updated sidebar design in threads to take less vertical space on small devices
  • Spoilers now use the Bootstrap collapse plugin instead of a custom implementation
  • General enhancements to the Backstage design update, including the start of using bolder fonts
  • Fixes an issue in Preview 1 where the Backstage accent color selector in profile was broken
  • Fixes a number of icons that didn’t exist in Font Awesome 5
  • Branding update, because Luna’s logo got a little bit bolder
  • MySQL 5.5 is now the minimum required version if you are using a MySQL database
  • We updated the Backstage logo to use our new, bolder typeface
  • Like with Luna 2.0.9, irrelevant files are now excluded from the generated download, for Luna 2.1 this includes the LESS and SCSS files used to generate the CSS for the Backstage and Mainstage

For Luna 2.1 Preview 2 I would also like to redirect you to the release notes for more information. We still have some more things to come for Luna 2.1. This includes, but is not limited to:

  • User avatar as profile menu icon (instead of the generic user-icon)
  • Font Awesome Pro system icon set selection
  • Converting the Backstage stylesheets from LESS to SCSS
  • Typography
  • Backstage night mode improvements
  • A big update to our documentation (see below)

As always it is recommended to update, but make a backup!

Website and documentation updates

Now, there is one more thing I’d like to talk about. And that is the documentation. Our documentation has always lagged behind, in true FluxBB-fashion. However, I’m making moves now to change that. And step one was dropping the whole HTML-mess that was the documentation and rewrite it in Markdown. “Rewrite” as in “I changed all html-tags to Markdown”, not “The whole thing has new content”. The documentation is available on GitHub for everyone to collaborate on!

Additionally, the website got updated to dynamically show the sidebar menu and the page content depending on what page you visit. As a result, the documentation can fully be managed from the GitHub repository’s content. This should make maintaining the documentation a lot easier for 2 reasons: Markdown is much better fit for writing documents than HTML and much less prone to markup errors, and updating the documentation no longer requires directly messing with the sites code.

Everyone is free to help out with the documentation now. If you want, of course. And “helping out” doesn’t mean you have to write it, if you see an error or would like to see some documentation about something in Luna, you can also create a new ticket on GitHub.

Before Luna 2.1 goes out the door, I really want to spend some serious time on the documentation and start maintaining it properly from there on out. This has lacked for years, and it is really time to change that.

And to close it all of: we made a number of improvements to our website’s design, mainly for small screens. We also fixed the broken download buttons for the Luna 1.0 preview releases.