My editors sometimes have to work with tabular data.
This can be needed in a textarea
-field, or an editor
-field (block?) or could even be in a dedicated field ( or even third party field via plugin - which doesn’t exist afaik).
I know in a textarea
-field you can use markdown tables, but these aren’t really an option for editors they can quickly become unreadable, you can’t do colspan or rowspan, etc …
If prosemirror is used under the hood of the writer field it should also be possible to add this functionality there.
We’ve also worked with a couple of clients that require to works with tables. So having a feature like this would be a great addition in my opinion. Good UI is a big challenge though
Tables are in my opinion not a core feature for a textarea field. You know it also from many other CMS, tables make very often problems. There are many ways to implement this differently:
With this ways, you can easy implement classes or other features.
While I kindof agree tables “often make problems”, I don’t agree they don’t have a place in core.
Tabular data is often useful, and requested by my editors.
I also fully agree with you on all points! Where I find the table field really very useful and it has so far satisfied everyone. Maybe it would make sense to integrate a similar field as a standard in the core?
I personally find the editor field absolutely sufficient. The more it becomes, the more confusing. But that is of course only my opinion.
Isn’t this already part of the core, in form of the table block? https://getkirby.com/docs/reference/panel/blocks/table
Yep, but not really flexible cause you can not let editors change the column count