FAQ: new Branch with more component stuff

[nielsnuebel]

Otherwise I would like to create a pull request with a component that can do more.

• listing
• edit
• router
• history
• multilang
• sortable group
• ordering
• params
• alias check with catid
• nextOrder
• reOrderCondition
• menuitem with modal
• addFieldPath
• filter_item.xml etc.

@roland-d

[roland-d]

Hello @nielsnuebel A late reply as I have not had time before. Now I am looking at how to move forward with this. Although I think it is good to have examples of how to do things the correct way I wonder if the boilerplate is the correct place for it.

Where it would be useful is to have a practical boilerplate that sets up the basics and another boilerplate with all the code examples in it. With the basic boilerplate you wouldn't have to remove so much when you want to start your project.

I am going to check how we could set this up and get back to you.

[MarkRS-UK]

Did you get anywhere with this?

Also, is this directory structure correct? Whilst it does work (eg JCE), is it the best practice? "Built in" components (eg articles, but many, if not all, of them) do not have this structure.

[roland-d]

Hello,

Unfortunately I did not get anywhere to be honest :/ Recently I have been updating the J4 boilerplate as it is in a bad state at the moment. This should really be cleaned up first before doing anything else.

Articles is a really bad example of a built-in component as it definitely does not follow the structure it should. That is also because core tables have their own folder in libraries/src/Table. A custom extension will never have it's tables there. An extension like com_banners or com_contact is more representative of a custom extension.

[MarkRS-UK]

Hi @roland-d,
Yeah, I can understand it. Life really gets in the way, particularly of documentation type stuff.
I'm making my first foray into J4, upgrading my (in-house) component, and now I've started writing notes (a good idea, who knew!) and will publish them in the J docs space, inviting comments and corrections, of course :)
I use "articles" as an example because it's so feature packed, but you're right, it's so built in to the core that it can be an unhelpful example to build on.