2018-06-30, 04:34 PM
Just wanted to comment about the latest blog post from MyBB.
https://blog.mybb.com/2018/06/28/mybb-2-...t-on-hold/
I'm glad that MyBB has finally put 2.0 on hold. It was always imho a stretch of the imagination for the resources of MyBB team and was going to break everyone's existing plugins and themes all at once. That's not an upgrade, that's a new software. We all pretty much love how 1.8x is for the most part and we're both familiar and comfortable with the coding and theme designing.
I can applaud the new changes and direction. Going to Twig seems a very reasonable solution as well update using Composer and Docker. Incorporating current technologies should be done regularly. Replacing that awful SCEditor is also a huge win. It's buggy and imho just sucks. The old MyBB editor imho worked very well and just needed a way to extend it. Still unsure how well TinyMCE will do but it can't be much worse the SCEditor.
The need for responsive these should be the highest priority though and I've expressed this over and over again but I will not be silent and I want to make sure that any new changes first deal with the problem of mobile compatibility for MyBB. And btw, I like the 1.9x concept theme at MyBB. Decent base to work from. MyBB doesn't have to have a complicated base theme. It just needs the default templates to be non-table based and responsive. Let designers do the bulk of the CSS changes. Just make sure MyBB functions and features work.
IMHO if MyBB changes to Twig and gets the theme to be responsive that's 1.9.0 and should be released so that the brave can upgrade and be immediately responsive and designers can make new themes. The changes for the editor, swiftmailer, and other parts of MyBB should be done in 1.9x updates in increments. This lowers the development and release time for 1.9.0. Please please please consider that. I don't think you'd get any admin to disagree with the urgency for responsive design as default. We are suffering in search results and losing ground to mobile compatible sites. Google has more or less removed rank from MyBB forums because they are not responsive and by default fail their mobile test.
Notice the "significant impact" part? Google results are now mobile-first for SEO. I used to have 10 million pages in Google. Now I have 300k. And before you say "why should we care about HF" please note that if this is effecting me this drastically then it's effecting everyone else too that does not have a responsive theme. So if MyBB gives a crap about admins having success with their software they need to address this problem very quickly.
A plan seems to be in place, and I like the plan. But please release 1.9.0 ASAP even if it's just the TWIG and responsive theme and heck, even if it's a little buggy. The faster you release the quicker we can get to 1.9.6 (6th update probably 12-18 months) which is where most of the bug are found, reported, and fixed.
Thank you for the blog post and the changes to the policy.
https://blog.mybb.com/2018/06/28/mybb-2-...t-on-hold/
I'm glad that MyBB has finally put 2.0 on hold. It was always imho a stretch of the imagination for the resources of MyBB team and was going to break everyone's existing plugins and themes all at once. That's not an upgrade, that's a new software. We all pretty much love how 1.8x is for the most part and we're both familiar and comfortable with the coding and theme designing.
I can applaud the new changes and direction. Going to Twig seems a very reasonable solution as well update using Composer and Docker. Incorporating current technologies should be done regularly. Replacing that awful SCEditor is also a huge win. It's buggy and imho just sucks. The old MyBB editor imho worked very well and just needed a way to extend it. Still unsure how well TinyMCE will do but it can't be much worse the SCEditor.
The need for responsive these should be the highest priority though and I've expressed this over and over again but I will not be silent and I want to make sure that any new changes first deal with the problem of mobile compatibility for MyBB. And btw, I like the 1.9x concept theme at MyBB. Decent base to work from. MyBB doesn't have to have a complicated base theme. It just needs the default templates to be non-table based and responsive. Let designers do the bulk of the CSS changes. Just make sure MyBB functions and features work.
IMHO if MyBB changes to Twig and gets the theme to be responsive that's 1.9.0 and should be released so that the brave can upgrade and be immediately responsive and designers can make new themes. The changes for the editor, swiftmailer, and other parts of MyBB should be done in 1.9x updates in increments. This lowers the development and release time for 1.9.0. Please please please consider that. I don't think you'd get any admin to disagree with the urgency for responsive design as default. We are suffering in search results and losing ground to mobile compatible sites. Google has more or less removed rank from MyBB forums because they are not responsive and by default fail their mobile test.
Google Wrote:Starting April 21, 2015, Google Search will be expanding its use of mobile-friendliness as a ranking signal. This change will affect mobile searches in all languages worldwide and will have a significant impact in Google Search results. Users will find it easier to get relevant, high quality search results optimized for their devices.
Notice the "significant impact" part? Google results are now mobile-first for SEO. I used to have 10 million pages in Google. Now I have 300k. And before you say "why should we care about HF" please note that if this is effecting me this drastically then it's effecting everyone else too that does not have a responsive theme. So if MyBB gives a crap about admins having success with their software they need to address this problem very quickly.
A plan seems to be in place, and I like the plan. But please release 1.9.0 ASAP even if it's just the TWIG and responsive theme and heck, even if it's a little buggy. The faster you release the quicker we can get to 1.9.6 (6th update probably 12-18 months) which is where most of the bug are found, reported, and fixed.
Thank you for the blog post and the changes to the policy.