New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table formatting in the schedules section #425
Comments
I've investigated this and I think the tables are simply too large. I investigated by injecting/removing various css classes on the rendered page, as well as recreating the issue by writing a new table incrementally. After a certain size / number of columns, it simply breaks out of the container. Given that there many more columns than rows, it may be more appropriate to simply transpose the tables; this may support readability anyway. This would mean going from this (truncated):
to this (also truncated):
The header row can be labelled appropriately. I've used array notation but we can be explicit and say e.g. On top of this, I would also like to move away from hardcoding tables for worked examples in rst and markdown. We can do this by using the I propose creating a subfolder of @dan-odsc @kindly @Bjwebb @greggish are there any concerns with this approach? If not, I can start on this soon. |
I've had some additional time to think about this and have the following thoughts:
Keen to hear from others if they've got thoughts. |
Thanks for this @mrshll1001, @greggish Just bringing this to your attention. Dan |
I'd like to hear what folks in the dev community think. Should we post in the forum? Not sure if this thread is the right one for it, or a new one. cc @Cskyleryoung @devinbalkind |
For wide tables, can we adopt a horizontal scroll? https://knowyourtoolset.com/2018/02/controlling-the-width-of-a-table-with-read-the-docs/ I agree about the points related to JSON. We should use it more seeing as we're a JSON standard now. |
Table formatting in schedules section needs to be looked at.
Been through all of the docs and this is the only instance. The other one we found and fixed was in the Logical model section but this has been sorted.
The text was updated successfully, but these errors were encountered: