Rebranding ModernBB: Welcome to Luna

As you might know, we’re rebranding ModernBB to Luna in our future version. And through a member on our forum spoiled it, I would like to introduce to you our new brand and logo.

So, yeah, as a reminder, and before we start, lets take a look at our current brand, ModernBB. We kicked off with “ModernBB” back in April 2013, a nice 1,5 year ago. Back then, we had this weird blue-ish color, and prety much the same wordmark we have now, just not capitalized. As ModernBB evolved, On 12 February, we departed from this blue-ish color, together with a new website, we updated our brand. It now futured the currently used “ModernBB Blue” color. And just a while ago, when moving on to ModernBB 3.3. We altered our wordmark to make the “m” and “bb” capitals. Ending up, with this:


Our blog headers kept using the old wordmark through. Anyway, that’s for the main logo. Our slogan, however, also changed through time. We started with “Modern. Light. Simple.” and not soon thereafter, we changed that to “Express Yourself”. A while ago, we changed this again to “You can do anything”, and we’re still going with it, and yes, Luna will use this slogan too. However, our logo, didn’t feature much inspiration. After all, it was just plain text in the Segoe UI font. Nothing more, and I did try to create some logos for it, but I never felt realy happy about them, and thus never used them.

The brand itself is another inspirationless piece of work of mine. And to say the truth, I regret ever starting of with it. I should have tought of a better brand from the start. Sure, ModernBB sounds nice and all, but like I said, its inspiration lacking and “BB” just… well… it doesn’t feel right. And thus, that’s going to end next year.

Because we’re rebranding. Our new name? Luna. Our new slogan? Nothing new, just “You can do anything”. Our new color? Luna Blue. And do we have a logo this time? Yes. And it’s already on top of this post, but here is it again:


Luna is a reference to the Latin name of Earths moon. And that brings us to our logo prety quickly. It’s quiet the no-brainer if you ask me. Through I’ve made a couple of different logos. One thing was certain: the color would be this kind of blue, the brand would be Luna, and the logo should be able to adapt to other colors easly. And this logo covers all of it. You’ll slowly see our new brand take over the ModernBB one. For starters, like an user on the forums pointed out, the sites live tile generated this logo instead of the usual ModernBB wordmark (this has been reverted already, through). As soon as the first preview of Luna is available (version 0.1), you’ll start to see this logo appear more often on our main site.

Our site will be trimmed down, by the way. This includes the removal of the ModernBB 3.3 docs. Information regarding Luna and more. Luna, will get its own site (somewhere on the world wide web, more later). And that’s when the real fun begins. Preview time. However, before we get to that, I just want to say that we will sillently release a pre-preview. This build will suddenly appear in the version history list under “Downloads”. And will be a preview of Preview 1. It, of course, won’t be feature completed and highly unstable. But it’s just to show what we’ve got! Also, we will soon kick off a new series of blog posts where I’ll explain new capabilities of Luna. Stay tuned!

ModernBB/Luna & Bootstrap/jQuery

oday, the Bootstrap developers released Bootstrap 3.3. This is the final major release for Bootstap 3 before moving on to Bootstrap 4. And well I would like to talk a little bit about that (a little, realy). We’re planning to bring Bootstrap 3.3.0 to the next update for ModenrBB 3.5 (version 3.5.3 that is), and obviously, to the latest Luna development version. TrentUI in the later one will be replaced with Bootstrap 3.3. However, Bootstrap announced their plans for Bootstrap 4 today too, and we’ve decided to not bring Bootstrap 4 to ModernBB. we will continue to update ModernBB with the latest version of Bootstrap 3 as long as it last. Bootstrap 4 will only be used for Luna, as it will require (according to their plans) for our project a lot of changes (we’re using panels a lot, and guess what’s going to change drasticaly).

However, the guys over at Bootstrap weren’t the only once to announce some drastic changes. The people at the jQuery Foundation announced jQuery 3, killing of jQuery 1.x and 2.x (we’re currently using 2.1). Once again, ModernBB 3.5 will not be provided with an update to this major revision, but only to jQuery 2.2 (if that ever gets released). Luna on the other hand will start using jQuery 3 as soon as it is available in the test branch.

With some luck, we will be able to include Bootstrap 4 and jQuery 3 in the final release of Luna 1.0 mid next year. If not, we might dedict a whole major update on simply upgrading to Bootstrap 4 and jQuery 3 (yes, it’s going to be that drasticaly


So I decided to take a look at ModernBB’s ModernCount control panel (we’ve got other software besides ModernBB you know), where we track the downloads. And today I saw the counter standing on 9.984 downloads. Which is a very impressive thing, because that means that 10.000 downloads is a very close milestone.

And thus we hit that milestone. Today, 18 November 2014. 19 months after ModernBB was founded, 14 months after the first real release (ModernBB 2.0). And let’s make it clear: I couldn’t be more happy! 10.000 is quiet the archivement. It’s nothing compared to others, for instance, if WordPress would have an avarage of 10.000 downloads every day, it’s a bad day for them. We got it in 14 months together.

And I’ve got a lot to thank Coder’s Guid and Neil for this. After they started using ModernBB and made an installation tutorial about ModernBB 3.1, our donwloads made a hole in the roof. Mutliple times a week. Now, a bunch of months later, I’m still feeling the consequences of that. So for this, thanks! However, it’s not only because of CG that we got to the 10.000 of course. No, I also have to thank all the 9.998 other people (the first download was by myself, later downloads I made aren’t counted by ModernCount) that downloaded ModernBB.

I hope all of you enjoyed it so far, and I hope all of you are helping me out with the next 10.000, and let’s hope they come faster than the previous 10.000 (let’s try to do it in less then a year)! I’ll be fine if it takes as much time, but let’s hope that it doesn’t take more time. Anyway, I’m sure that the downloads will continue to grow as we are on the edge of releasing the first real Luna Preview. And in just 3 weeks, we also have our third update to ModernBB 3.5. Stay tuned!

Announcing ModernBB 3.5 Update 3: An update for your eyes

In ModernBB 3.3, we revamped the black-blue Backstage interface into a brighter and white-color (because you’re free to choose a color) design. This made the interface quiet bright. ModernBB 3.5 once again revamped the design, making the navbar white too. Making the interface even brighter. And well, we got some comment on that, so our next update, ModernBB 3.5 Update 3 is about to revamp the Backstage interface once again.

And we’ll do that with a couple of small changes. First of, the navbar will use the color accent you choose once again. This already breaks the majorly white design of the Backstage. However, that still makes up for a rather bright interface. And that’s not easy for the eye, and is power consuming for both you and your device. That’s why we change the white background into a dark grey. This matches the color we use in Luna a bit, but it fixes the problems we have with it.

But improvements for colors isn’t the only change that ModernBB 3.5 Update 3 will bring. We will make it more easy for large touchscreens, that do not get the hamburger-menu, to navigate the navbar thanks to improvements to the dropdown lists for touch. Another (major) change is that we’re now using Bootstrap 3.3.1 instead of ModernBB 3.5 Update 2 and earliers Bootstrap 3.2.0.

Further, ModernBB 3.5 Update 3 will bring small improvements to security. Unlike Update 1 and Update 2, Update 3 will not patch a security hole, but improve generated passwords. What brings us to the next point: this update will also bring the ability of ModernBB to check the strength of passwords. Finaly, ModernBB 3.5.3 will be able to recognize a FluxBB 1.4 and 1.5 and a ModernBB 1.6 and 1.7 database, so you can update from these systems again. This is due to we won’t support updating from these releases to Luna 1.0, and thus, ModernBB 3.5.x is a required stop if you want to update from ModernBB to Luna. And last but not least: we’re also fixing a couple of bugs (3 for now).

Stay tuned for this update, which will be released on 9 December 2014! Is it the final update for ModernBB 3.5? No, after this, we will simply move on to ModernBB 3.5 Update 4, which is planned for February. If you’re now using ModernBB 3.5 Update 1 or lower, and especialy ModernBB 3.5 and lower, remember to upgrade as soon as possible to ModernBB 3.5 Update 2. Update 1 and 2 fix important security issues! So do not wait for ModernBB 3.5 Update 3 to be released.

A year with Random and what’s ahead for it

Whoho! Today, we’re celebrating the first aniversary of Random. Random has been our default style through the existence of the second generation of ModernBB (that includes, but isn’t limited to ModernBB 2.0, 2.1, 2.2, 3.0, 3.1, 3.2, 3.3, 3.4 and 3.5). Through the current design language was introduced in ModerrnBB 2.2, which was released November 30th, 2013. So yes, we’re also celebrating 1 year ModernBB 2.2.

A brief history
Random, introduced as Randomness 1.0, together with Kindness, Awesomeness and Radicalness, was the default theme of ModernBB 2.0. It was a major redesign and completely different from ModernBB 1.6’s Air design. However, we weren’t to happy with the design and thus, ModernBB 2.1 focused on doing it all over again. This release, Randomness 2.0, introduced the general structure of the design as you still get it today.

Randomness 2.1 however, the version of Randomness that contains the currently used design guidelines, was released with ModernBB 2.2, while originaly made for ModernBB 3.0, and made improvements to performance, brought a brighter design and made other major improvements. Randomness 2.2 was the ModernBB 3.0 release and mainly focussed on making Randomness compatible with the new ModernBB 3 features.

Randomness 2.3 was part of ModernBB 3.1 and introduced some ideas from Vanellope (the project, not the ModernBB version), resulting in a major design enhancement to the topic view (and we got good comments on that one). Due to the good comments, the rest of ModernBB couldn’t stay behind, and thus, Randomness 2.5, part of ModernBB 3.2, redesigned all other pages, still staying true to the Original guidelines from Randomness 2.1.

Random 3.0 was released with ModernBB 3.3, it wasn’t a major difference for the eye, through Random 3.0 introduced support for ModernBB’s new style engine. Random 3.1 would improve further upon with ModernBB 3.4, including support for the new editor and other features. Finaly, the current Random 3.2 also brought support for the new ModernBB 3.5 features, but no major changes where applied.

Random 4.0
With the upcoming update to ModernBB, we will celebrate Random’s 1st anniversary with a redesign of the styles. This includes the default styles Random, Kind, Awesome and Radical, but also Luna, Pinkie, Shy, Happy and Magic, which you can download from These styles will (for now) support ModernBB 3.4.1 and up (so if you’re running an older version but want to use these new styles, your in luck, through you should update).

These new versions of the default styles will also include Improved information about them (updated screenshot, new logo, etc.).

2014 was awesome!

2014 has come to an end. And to be fair: for ModernBB, it was a rather awesome year. Let’s take a quick look at a year of work!

Last year, we ended with the development of ModernBB 3 beeing at full swing. We released 40 new version of ModernBB and Luna in the past year, the first one beeing the ModernBB 3 Alpha 1 (core During 2014, 5 development releases of ModernBB, 6 pre-releases of ModernBB, 22 stable ModernBB releases and 7 development releases of Luna followed. The most recent one beeing Luna 1.0 Preview 2 DEVED (core 0.2.3478), earlier this month. And later today, you’ll be able to enjoy Luna 1.0 Preview 2 NEWED (core 0.2.3573)!

40 new versions is a lot. During 2013, we only released 23 versions of ModernBB. Note that ModernBB came to existence in April 2013 through, and that the real development actualy kicked of in late June 2013. So, on avarage per active month, we have released a lot more releases last year.

But releases aren’t what matter. Neither are downloads, through we’ve seen some realy nice numbers the past year! We closed of 2013 with 2045 downloads in total, making an avarage of 227 download each month since April. 2014, however, closed of with 11.780 downloads in total, making an avarage of 811 download each month. December 2014 was our best month up until now, with 1309 downloads. This means that, if we do not shrink in downloads, the amount of avarage downloads can be doubled during 2015 (let’s hope even better!). 2013 to 2014 was over 3 (almost 4) times more download per month!

But like I said, numbers doesn’t matter. Well, there is one number that does: the number of happy people. And we hope that we did make some people happy with all the work that is beeing done to ModernBB 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7 and Luna 0.0, 0.1 and 0.2 during the past year. A lot of features have joined the fun since last years final 2.2 release. And in fact, a lot of features are joining right now since the 3.x branch in Luna. Next year arround this time, I hope to be looking back at a beautiful Luna 1.0 and Luna 1.1 release (yeah, only 2 major releases planned for next year, 3 if you count ModernBB 3.7 (but that’s planned to be not such a major release) 4 if we might get to Luna 1.2, it feels weird!).

Well, I wish you a Merry Chrismas (a little bit late, but I already did this on Twitter too) and a Happy New Year! Enjoy the fun! I’m out for this year!

ModernBB 3: What will come next

Last year, we released the 6th big update to ModernBB 3, with Luna in development however, what will be next for ModernBB? Will there be a ModernBB 3.7?

Well, to kick off. We plan to put the final release of ModernBB into a LTS release, similar to ModernBB 1.6, which got 6 updates (1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5 and 1.7.0), it will be supported for over a year. Especialy for security fixes, we will continue to support ModernBB into the future. However, only the last one, the big question is: which ModernBB release will be the last one?

I didn’t plan a ModernBB 3.6 release at first, but due to 3.5.3 becoming to big, I decided to do it anyway. With this new scheme, I do hope that ModernBB 3.6 won’t be the last major update to ModernBB. A ModernBB 3.7 is already in the planning. I’ve decided to not continue the idea I had with ModernBB 3.4 and 3.5 to release new features in the smaller patches, instead, these will be part of ModernBB 3.7 instead.

ModernBB 3.7 won’t be a big update. In fact, it might be just bug fixes, I’ll try to get some small features in there. I hope you guys understand that ModernBB isn’t my focus point anymore, Luna is. Anyway, ModernBB 3.7 will come, and unless we release it before Luna, it will be our final minor version jump. Otherwise, ModernBB 3.8 will be released. Why do we need a minor version bump after Luna? Because that would be our LTS release. So, if ModernBB 3.7 will be released after Luna 1.0, it will be ModernBB 3.7 LTS. If before, it will be ModernBB 3.7, and we’ll release a ModernBB 3.8 LTS after Luna (or perhaps the same day). In such a case, 3.8 will be bug fixes only.

What’s In A Codename?

So today, I discovered that there is a Wikipedia article about ModernBB (which also covers Luna). Awesome! Thumbs up for the guy that’s keeping the information on it up-to-date. Anyway, I decided to read through the whole lemma, and then, I came across this:

Similar to other software, like WordPress, main releases are named with code names. However, the logic used for ModernBB’s code names is unknown. Some releases share the same code name.

It sure knew to steal my attention. Why? Because it’s right. There is no logic in the ModernBB codenames. Will there be any kind of logic in Luna codenames? Probably, but remember, they are what the name says: codenames. Nothing more, nothing less.

ModernBB Codenames
While ModernBB 1.6 is called Blythe, it didn’t had a codename until ModernBB 2.0 was named Zoe. Both codenames came from the same source: Hasbro (that big entertainment company, you know, like Monopoly and stuff). 1.7 just took the 1.6 codename due to it not being such a big release. However, releases being small isn’t the only reason we stick to a codename. 2.1 and 2.2 where both named Zoe, too. There is no reason for that naming convention.

ModernBB 3.0 was named Odd. Because it was version 3, and uneven number, which is also called “odd”. Also, “Odd” is a name in some countries. ModernBB 3.1 and 3.2 where both named Mellow. These 2 releases sharing a name, did have a reason. Both releases putted the focus on revamping the front-end design. Its codename wasn’t ment to be the word “mellow”, through. It actualy comes from “marshmallow”. But we thought that was to long and shortened it to “Mallow” and then we switched the a for an e. I didn’t even realize at the moment it was an actual word.

ModernBB 3.3 was named Vanellope, after the Vanellope project I did in the months prior to it, of which it also got a lot of code. Anyway, that project’s name on its own was from Wreck-it Ralph, a Disney movie. One of the characters was named “Vanellope von Sweetz” (or something). ModernBB 3.4 was named Neon, and at that point, we did plan to introduce a logic in naming our releases: after the elements. Didn’t happen, through. The next version, ModernBB 3.5, was named Kate. ModernBB 3.6 and 3.7 are both named Blue. We just took names, there really is no reason behind these names. 3.6 and 3.7 share the same name because we don’t think it’s worth it to give it new names.

Luna Codenames
Luna continues to use codenames. Aero is an example, the codename for Luna 1.0. “Luna” as a name itself was a codename until it became our final name. We currently call our 1.1 milestone Luna 1.1 Bittersweet Shimmer. Another update, that currently doesn’t have a version number is Luna Denim. There is an updated planned in between Bittersweet Shimmer and Denim, so that’s going to be something with a C. Anyway, for the people that didn’t notice it: Aero, Bittersweet Shimmer and Denim are all colors. In alphabetic order. So there you have our logic. Finally.

Developing Luna #10 – The Road to Preview 4 and 5

Yesterday, we’ve closed off the Preview 3-stage of the Luna development, now, we’re working  on the first Preview 4-release, for which we’ve planned 3 updates. And than comes Preview 5, perhaps better known as Luna 1.0 Beta 1 (Luna v0.5). Why are we talking about Preview 4 and 5 this time around and not just 4? Let me explain:

First off, with Preview 3 Update 2, we kick off our weekly updates. This means that next Saturday, you guys will be able to enjoy Preview 4 already, we’ll release a new build of Luna every Saturday until we get to the final release. With this, we like to indicate that the now +8 months of Luna development are coming to a close. We’re left with 10 more previews (Preview 4, 4.1, 4.2, 4.3, 5, 6, 7, 8 and 9), through we might add a couple of additional previews. Either way, Luna 1.0 is now set for a 9 May 2015 release. Get hyped!

Final features
Preview 4 and its 3 updates will be all about finishing off the features we’ve included in the previous previews. Some other small additions might make it into the software, but don’t put your hopes on it. At this point, we start stabelizing our code, getting everything ready for translation, adding Random 5, and more. It’s not for now, but when we hit Preview 9, you’ll see us remove a couple of developer codes (like the “Core” message in the Backstage and all information in About about Preview-updates).

Further, we’ll be working on improving Sunrise and Sunset, extending the Notifications (the actions you have to do that will trigger notifications) and so on. Something else that is now on our main radar is the documentation, and while Preview 3 Update 2 already comes with a first draft of the documentation, it’s far from finished, and thus, more is coming. Finally, you’ll see us fix a faire amount of bugs.

When Preview 4.3 (“Preview 4 Update 3″) is released, we’re going in to our final week of feature development. After that, we’re on a feature freeze that will bring you guys Preview 5, perhaps better known as Luna 1.0 Beta 1 or Luna 0.5 (but we’ll officially continue to name them “Preview”, both betas and release candidates). Preview 5, 6 and 7 will all focus on finishing the new features, but they will mainly fix bugs. Preview 8 will be our first release candidate and with some good luck, Preview 9 will be our last. Followed by Luna 1.0 some time after (we’ve currently planned a week between Preview 9 and Luna 1.0, but we do not expect it to take that long).

End of the line, or road, pick what you prefer
And with that, the end of the road is in sight. I can see it, it’s still a distance, but it’s there. And we’re closing in. Finally. And what’s at the end of this road? Well, a brand new one. Bittersweet Shimmer Avenue, yeah, let’s call it that. If that doesn’t ring a bell, I’m referring to Luna 1.1. Guys, we’re coming close to the end, it was an amazing ride, and I hope you all are ready for the next one, because Bittersweet Shimmer isn’t the only road over there. Not even close.

The art of going beyond the Edge

While we’re still in the Preview 3 stage for Aero, when it comes to features, the development of our very first release is drawing to a close, with the expected final release in May, which makes up for 10 months of development and already over 800 commits to the core since the start. Either way, we’ve talked about it in our last blog post: we’ve planned more stuff. Let’s talk about that.

Aero – 1.0
Aero is, as you know our first stable release. We’re currently hard at work on it, and our weekly releases prove that. We’ll continue this schedual until we reach our first stable release. Either way, it’s a major improvement over ModernBB.

Bittersweet Shimmer – 1.1
Bittersweet Shimmer is going to be our first minor feature update to Luna. It will go by the number of version 1.1. Our main focus will be on improving upon the changes made in Luna 1.0, and we expect it rather quick after Aero is released. Do not expect much new features in version 1.1. You, however, can expect the kick-off of some major changes for later versions. This will also be the first Luna release to be developed with our new Git-structure. We’ll also be more specific in ticket items.

Cornflower Blue – 1.2
A couple of days ago, we’ve given our C-update a name: “Cornflower Blue”. Cornflower Blue will introduce a major revamp to the installer and update mechanics of Luna. These 2 systems are set to become completely rewritten and modular from the Luna core. The new components (as they will become components) will be released under their own license, the MIT license, that is. They will be completely separate from the original Luna core, and are our first steps towards a brand new core, which we like to call Edge. Further Cornflower Blue will introduce other small changes, but more on that later. As we follow semantic versioning, this will be Luna 1.2 and this update is planned for fall 2015.

Denim – 2.0
Next up is Denim. This will continue the work we did in Cornflower. But not for the installer and updater. No. You’ll see our Backstage being rebuild from scratch. A thing we’ve already started working on. Just like the installer from 1.2, the Backstage will become a separate component, as modular as possible, and released under a new license – again MIT. This will leave only the Mainstage behind on GPLv3, something we will fix later. Denim is supposed to introduce support for plugins in the Backstage (not the Mainstage). This major revamp of the Backstage will bring us to Luna 2.0 (as semantic versioning requires us to do so).

Emerald – 2.1
Our final planned update for now is Emerald. This update will have the same function to Denim as Bittersweet Shimmer had to Aero: it’s a minor all around improvement update. And thus we’ll probably go with version 2.1 for it. This update will focus on improving Edge (the name of our core for the installer, updater and Backstage by then). It’s currently planned to be the first update for 2016.

Early communication is good communication
So now you know what we’ve up to our sleaves. With Aero, Bittersweet Shimmer, Cornflower Blue, Denim and Emerald, we hope to keep ourselves buzzy for a while, and we hope to keep you guys happy for a while, until we’re ready to go to Luna “F” and beyond. And I guess that after reading this post, you guys might know what our plans are for the next major update after Aero (Luna 1.0) and Denim (Luna 2.0). On the other hand, note that codenames are not related to their respective version, and only in order of the releases.

We’re talking this early about our plans – which are subject to change – because we think that it is important to include our community in the development process as early as possible, so that’s what we do. And now, back to the development table for Aero.