Here is (part of) a table I use in some documentation:
+---------------+------------------------+---------------------------------------+
| TASK NAME | WHEN | DESCRIPTION |
+---------------+------------------------+---------------------------------------+
| db:seed | On every update | Data required for the application to |
| | | run; you should always be able to |
| | | safely execute this multiple times |
| | | for an update. |
| db:truncate | Manually (dangerous!) | TRUNCATE all tables but postal_codes |
| postal_codes | Once | Load the postal_codes table |
+---------------+------------------------+---------------------------------------+
The problem is this is very awkward to edit; if I change one thing, I need to (manually) re-align everything, which is a PITA
Are there easier ways to manage this? I don't care about the exact above layout as such, but would like to keep the wrapping of the 3rd column...
list-table
(recently I converted many tables to this, because ascii tables are hard to maintain and diff poorly)