Skip to content
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

Builds page formatting issue #1151

Open
pmknowles opened this issue Jan 16, 2023 · 6 comments
Open

Builds page formatting issue #1151

pmknowles opened this issue Jan 16, 2023 · 6 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@pmknowles
Copy link
Contributor

@
re PR: arendst/tasmota#

Please add the new feature to the appropriate article in Tasmota documentation](https://tasmota.github.io/docs/BUILDS/)

Something appears to have gone wrong with the table in the Builds page. The Displays and Remarks columns are not appearing (they appear in the 'edit' page) and the scroll bar is at the bottom of the table so it's impossible to work out the rows. If the table was split it might fix it but the left and right hand margins seem to be excessively wide which would be a better solution.

@pmknowles pmknowles added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Jan 16, 2023
@blakadder
Copy link
Contributor

it's a limitation of the used theme. scroll bar is the solution

@pmknowles
Copy link
Contributor Author

So will splitting the table at each heading point create a scroll bar for each section? I don't want to waste time editing if it doesn't work.

@blakadder
Copy link
Contributor

you will waste time editing in any case since the BUILDS table is picked up from arendst/Tasmota

@pmknowles
Copy link
Contributor Author

pmknowles commented Jan 16, 2023 via email

@barbudor
Copy link
Collaborator

barbudor commented Jan 16, 2023

Any way to format the columns to be smaller so it fits without the horizontal scroll bar ?

There are also possibilities for tabs if I'm correct. So it could be some tabs for each different CPU ?
Bad idea as each tab would be a separated table to manage too

Something auto-generated parsing the code ?

@blakadder
Copy link
Contributor

add custom css to Material for mkdocs to reformat this table or edit the original BUILDS.md to make it fit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants