can I work on this issue?

Have no objection to anyone working on the issue.

We are not code capable, so appreciate your help.

Joomla! 3 had this option for the Blog Layout, yes?

If you refer back to 3, you will find a better configuration of choices for the Category Blog Layout.

We cannot figure out “why” the option choices were removed.

Understand that “classes” may have been added to configure this, but what beginning user knows anything about classes, let along which class is needed for which layout.

Replicating the same options on J! 3 seems to be a wiser course of action for Category Blog Layouts.

From: ankurshr01 notifications@github.com
Sent: Saturday, January 11, 2020 8:51 AM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: 200MPHMEDIA herb200mph@gmail.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] [4.0] Blog Layout Ordering (#27478)

can I work on this issue?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/joomla/joomla-cms/issues/27478?email_source=notifications&email_token=AHWFSXANE2TG7STFOA23YNTQ5HFEPA5CNFSM4KFSAHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWCMCQ#issuecomment-573318666 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWFSXF6X2TGBJVGHJ56DCLQ5HFEPANCNFSM4KFSAHVQ . https://github.com/notifications/beacon/AHWFSXFCJWGG5ZS2L2ZTBUTQ5HFEPA5CNFSM4KFSAHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWCMCQ.gif

There were already requests like yours. The decision was made that J4 will not have your requested settings.

It depends on the CSS "framework" that a template provides which CSS classes the user has to use.

Thus, it's the job of template developers to add a documentation to their templates or provide an additional framework plugin that makes the requested settings possible or to provide ready-to-use menu items overrides for this or that.

Joomla 4 core isn't tied as strictly as Joomla 3 to a specific base CSS system (like BS 2).

(I don't say that I liked this decision concerning classes instead of "settings" that could be "translated" to classes in the background according to template requirements. In a scenario where you use different templates the new approach is annoying for users. On the other hand it has some advantages (Maybe. Depends on the used CSS system.)).

OK, got all that. Like you, do not agree with that decision to “code up” layouts, which is instinctive of programmers and code guys.

They would rather write 100 lines of code vs. clicking on a backend button.

Anyway, for the default template, what are the “classes” to enter (and where to do it), to create some sort of flow options.

Appreciate your response. Thanks.

From: ReLater notifications@github.com
Sent: Saturday, January 11, 2020 1:15 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: 200MPHMEDIA herb200mph@gmail.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] [4.0] Blog Layout Ordering (#27478)

There were already requests like yours. The decision was made that J4 will not have your requested settings.

It depends on the CSS "framework" that a template provides which CSS classes the user has to use.

Thus, it's the job of template developers to add a documentation to their templates or provide an additional framework plugin that makes the requested settings possible or to provide ready-to-use menu items overrides for this or that.

Joomla 4 core isn't tied as strictly as Joomla 3 to a specific base CSS system (like BS 2).

(I don't say that I liked this decision concerning classes instead of "settings" that could be "translated" to classes in the background. In a scenario where you use different templates the new approach is annoying for users.)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/joomla/joomla-cms/issues/27478?email_source=notifications&email_token=AHWFSXAI4H3IZ3THXDKG3A3Q5IEBNA5CNFSM4KFSAHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWHZGA#issuecomment-573340824 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWFSXHQJ4ZD5P2XHBVUPTLQ5IEBNANCNFSM4KFSAHVQ . https://github.com/notifications/beacon/AHWFSXE2Z7DNGHSUKWW3RITQ5IEBNA5CNFSM4KFSAHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWHZGA.gif

Anyway, for the default template, what are the “classes” to enter (and where to do it), to create some sort of flow options.

I don't know if there's already a documentation. Maybe @ciar4n can help.

This is the PR that removed the layout options you speak of.. #18319

• Classes allow for an unlimited number of options
• Classes allow us to avoid future b/c breaks as they are coupled with the template (not core)
• Original parameters force templates to adhere to a set number of layout options

@ankurshr01 Rather than reverting previous work, it would be more forward-thinking if you implement something like what @mbabker suggests here... #18319 (comment). This would allow for user-friendly parameters while keeping the benefits of class-based options.

This is crazy, the end user is relegated to the background when he should be at the center of the project.

This is crazy, the end user is relegated to the background when he should be at the center of the project.

Bootstrap layout options have been replaced with #18319

So theses classes will replace the Blog layout parameter in the backend. Ok, thank you.
Is it functional now?
How the end user will know wich classes to use here?

Is it functionnal now?

Yes this should now be functional.

How the end user will know wich classes to use here?

Once J4 goes to beta I will write up some docs.

Thanks a lot for your answers.

• the CSS classes Boxed and Masonry are ok (good job) but not for the columns :/
• thanks for the doc and I really hope that end users will understand that now, they must read a doc first before using Joomla...

thanks for the doc and I really hope that end users will understand that now, they must read a doc first before using Joomla...

And if you use another template you have to read another doc and if you test serveral templates you have to read several docs and change the classes after each template switch or have to create several menu items for each template and ...

It will be very "funny" and "easy" for the end users, they will love this... (or not).
We'll see.

the CSS classes Boxed and Masonry are ok (good job) but not for the columns

If not working for columns could you please create an issue. Thank you.

And if you use another template you have to read another doc and if you test serveral templates you have to read several docs and change the classes after each template switch or have to create several menu items for each template and ..

What is your point? If you are happy to set a strict number of layout options for the sake of being able to have a dropdown to select from then just revert #18319

the CSS classes Boxed and Masonry are ok (good job) but not for the columns

If not working for columns could you please create an issue. Thank you.

Ok, I will

And if you use another template you have to read another doc and if you test serveral templates you have to read several docs and change the classes after each template switch or have to create several menu items for each template and ..

What is your point? If you are happy to set a strict number of layout options for the sake of being able to have a dropdown to select from then just revert #18319

In fact, you reply to a Joomla pro user who ask you end users questions (your grandmother, my neighbour, the friend of a friend, anyone who uses Joomla without being not familiar at all with Flexbox, CSS Grid...).
Yes, I can manage these classes and it will be fine for me (because I'm pro) but it will be different for many end users. And Joomla must think to them because they are many.

BTW, thanks for your help and for your hard work for J4 :)

Closed as we have a draft: #30910

This release blocker should be re-opened as the referenced PR was closed

better 1 only
please refer to #32012