Status of beez3 in Joomla 4?

Question

Status of beez3 in Joomla 4?

zero-24 opened this issue 9 years ago · 7 comments

Should beez3 removed as well as hathor or stay in joomla 4?

Answer 1 · 2015-10-14T19:17:36.000Z

I don't think either frontend template stays in J4. The question really should be whether we ship multiple templates or not.

Hathor's already on the dump list since it's essentially been broken since 3.0 released and is actually less accessible (from what I've heard) than Isis is now.

Answer 2 · 2015-10-14T19:56:07.000Z

So there is currently no decision on that? beez3 is mostly broken as well ;)

Answer 3 · 2015-10-14T20:05:34.000Z

Hathor was pretty much a "just do it" pull request. I'm not so sure if anyone's discussed front-end templates but at this point I'd assume that Beez3 and Protostar (and even Isis) won't be present in any form once v4 starts taking shape.

Answer 4 · 2015-10-14T20:27:31.000Z

ok so the J4 team let us know if there is the time to do that pulls ;)

Answer 5 · 2015-10-15T07:32:52.000Z

If half of what we discussed in the sprint is implemented neither Protostar nor Beez3 will make any sense. We'll need a different kind of template.

As for the back-end template I suspect we'll have to refactor it, not start from scratch. It depends on what the UX team comes up with in the following months.

Answer 6 · 2015-10-15T09:05:54.000Z

The current templates will have to work using the LegacyRenderer (don't know yet how, but the 'little pain' paradigma demands it).

However, they will surely not be shipped with 4.0.

Answer 7 · 2015-10-15T09:22:04.000Z

I am mostly worried about how the legacy main content + module positions will translate into the "bento box" paradigm of the page builder. Programmatically it can be mapped by assigning an ad hoc name to the main content area but that will most definitely break the intuitive page builder since what you see is not what you get. Of course this depends on how deep we can go in the first iteration of the page builder. Lots of conditionals here :p I trust that you'll find a way to maintain a modicum of b/c for templates and extensions. We definitely must work with the marketing team to manage the expectations of our users :)