I'm a big fan of NOT using tables in RST because they cause many problems when the docs are alive and continuously updated.

However, here we're using the compact RST table syntax, which doesn't add dashes in all rows and columns, so maintenance should be nice (I've suffered myself some conflicts when merging things, but it's easy to solve them because of this compact table syntax).

The problem I see(but only in this case, in others it would be nice to replace a table by several subsections) is that now we can quickly overview all available services in a small table ... but if we turn this into subsections, the information is now spread in a very very long document, because each section needs lots of space.

An additional issue is that these subsections wouldn't appear in the Table of Contents of the page, so you can't easily navigate through them.

So, it's tricky (RST tables always are) but I'd say there are more reasons to keep this doc "as is" instead of changing it.

Thank you for your feedback Javier, much appreciated.

I came to this proposal based on#15193 which was a lot of work just for this one new bridge and the diff is .... 👎

We can also think about using Option 1 or option 2 on a dedicated page, I know we want to go away from many page more to "complete" pages, but there is no silver bullet IMHO

The diff can be fixed by ignoring whitespace:https://github.com/symfony/symfony-docs/pull/15193/files?w=1

I agree with@javiereguiluz, tables just make sense here. The line wrapping is a bit suboptimal, but maybe we can remove a column?

The diff can be fixed by ignoring whitespace:https://github.com/symfony/symfony-docs/pull/15193/files?w=1

Sure, nonetheless I as a contributor needed to touch and move a lot of whitespaces to get a valid table just to add one line.

The line wrapping is a bit suboptimal, but maybe we can remove a column?

I think we will end up all the time with moving spaces around, but OK, lets close then