Field descriptions are missing.

From the little I can find the only possible descriptions would be template specific and not generic

I don't know if the new Leading Class and Blog class fields are really necessary, any override can be done by adding a class in the PAGE GLASS field.

I propose adding the column options for desktops, tablets and phones. Because in J3 if you choose 3 columns on the tablets it gets too squashed.

@leoalv I believe that is resolved if you know the super secret classes that can be used here. But until someone is so kind as to actually tell the world what they are .......

If this PR #31570 get merged, we will have global classes that can be used by template developers to set columns again.
Since it is not finished, it is difficult to write it in the docs.

It's not about template developers. Its about site builders.

I've always had problems with columns and many end users don't even know CSS and always ask how to solve their needs. Since then I work with an Override for Blog view and they no longer ask about the column issue. Maybe it does not matter but here I leave you the capture of how it looks.

If this PR #31570 get merged, we will have global classes that can be used by template developers to set columns again.
Since it is not finished, it is difficult to write it in the docs.

Hmm, not exactly. #31570 only updates the settings from J3 to the CSS classes that already exist in Cassiopeia. The columns-X and masonry-X classes already exist and can be documented and used.

My bad, I misinterpreted the PR

We need to copy the explanations from here #18319 to the docs

We need to copy the explanations from here #18319 to the docs

That really is not enough

It was never expected that the current situation would be the final UI #18319 (comment)

How is this not a release blocker?

A major piece of joomla functionality is currently completely unusable

How is this not a release blocker?

maybe much more a document blocker
?

Thinking this can be resolved by documentation is wrong.

We had a anlternative PR ##30910
It was less sophisticated and brought back dependencies , which is less flexible.

#27478 should be re-opened. It was a release blocker and was only closed as there was a PR but that has been closed so the Release Blocker has not been resolved.

#27478 reopened

From a user perspective, this is how I would like this to work in principle.
Put the templates available modifier classes in to the templateDetails.xml, in groups they belong to.
If other template providers want to use this functionality they can do the same.

In each of the blog class fields there should be a "build" button.
This button open a dialogue form with a dropdown listing the installed front end templates.
If the selected template does not have modifier classes in the xml, inform the user that this is not available for this template.
Else, populate the dialogue form with radio buttons in groups as defined in the xml.

Column Layout

• none
  o columns-1
  o columns-2
  o columns-3
  etc etc

Styling

• none
  o boxed

Image Location

• none
  o image-left
  o image-right
  o image-bottom

When the user has selected the preferred option in each group and hit the ok button, the selected modifier classes are written to the class field and the dialogue close.

This is the issue that we raised a year ago, under the concept that "new users" have not idea about "classes" and their use, and the Blog Layout should have column and ordering controls built in [no classes needed], just like previous Joomla versions. The configuration of the layouts should be controlled by selectable fields and not "classes' that novice users know nothing about.

So we have now issue #27478 and this one here, both release blockers, and both about the blog layouts, only maybe with different idea about what would be the right way to solve it. Isn't that duplicate somehow, or am I missing something? Does it need 2 issues for that?

just merged the #27478 here

This is absolutely a release blocker. And for me a J4 blocker. I don't get involved in Git but had to come and speak up about this. This takes my control as a site builder without big coding skills and leaves me at the mercy of a template to say how many columns my articles will be displayed in. How on earth is this not a massive break for migration?

Agree with @AlisonAMG
Removing the choice of the number of column makes the whole menu system loosing flexibility

I think we need to have the J3 Blog layout as legacy view for an easier update from J3. I think I am not the only one who has used a blog as base and made some overwrites for specific reasons. If we only have the css way (not a bad one to be clear) it will put some more burden on the shoulders of sitebuilder to migrate to J4.

sadly my pleas on the importance of this have fallen on deaf ears for 3 years, ever since the counters were destroyed by people who believe you must be a front end designer and css guru to be allowed to build a web site with joomla

In my opinion, the main problem is that here the design is mixed with the logic. These settings belong to the template not to the component.

@sonnemondundsterne I suggest you think a little bit harder

imho this is, barely a release blocker for j4
..cause..
no one will update to j4 from j3 on day-0
will you do it?

@sonnemondundsterne Your idea is not correct, this solution has to be implemented in the component, because com_content is not only used to display a simple blog, it is used for much more along with custom fields. And the number of columns setting is important and should remain no matter what templates you use.

I really don't understand, when you want to implement something so necessary to improve Joomla they refuse, claiming that they don't want to break anything. And when should they keep something so basic and necessary there if they don't mind breaking thousands of sites. Are they really in favor of the users? Or are they against? because if what they are talking about is that to use Joomla you have to be NASA Engineers, then let's burn everything and let's go.

@alikon it is NOT about upgrades.

Cat blog menu link currently is amazing. Great options for a site builder to change layouts without having to delve into code

this is, barely a release blocker for j4

Nobody in their right mind would release a new car model without a decent paint job and all the gauges and switches in place.
I could swear there was a steering wheel here before. Maybe it's mind controlled now?
Where have all the UI people gone?

Honestly, if the numbers of columns are not there anymore it might be better to remove the blog layout altogether and let's use the category layout only.

Suggestion 1:
Or we could just add the old number fields and have a native blog layout with simple choices for column numbers in simple drop downs. Like when children try to change it, they can do it.
Give these numbers as params to the template and let the template do the rest (classes).

Suggestion 2:
Keep the Blog Class(es) additionally, but rename them:
"Blog Class (Leading Articles)" to "Leading Articles Class",
it's the class for the leading articles,
"Blog Class" to "Intro Articles Class",
it's the class for the intro articles.

Don't call a child "Arthur" and then refer to it as Toni.

@rdeutz something like this

Closed - please see #32943