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

Table? #1

Closed
azerupi opened this issue Aug 16, 2015 · 4 comments
Closed

Table? #1

azerupi opened this issue Aug 16, 2015 · 4 comments

Comments

@azerupi
Copy link

azerupi commented Aug 16, 2015

Since you have added quite a few editors I would suggest using a table to have a quick overview of all supported features per editor.

@contradictioned
Copy link
Owner

Yep, I had this also in mind.
But I'm not quite sure, about the columns (assuming one row per editor).

I think, I'll collect some more feedback, and make my mind up :)

@azerupi
Copy link
Author

azerupi commented Aug 16, 2015

If it is place you worry about you could rotate the header text: https://css-tricks.com/rotated-table-column-headers/ :)

@contradictioned
Copy link
Owner

The major concern is, I'm not sure how to handle, e.g. "build scripts", one editor/plugin ships support for rustc, the next for cargo. And I am not a fan of tables with footnotes, or much text in the table cells.

Thanks for the rotation ;)

@azerupi
Copy link
Author

azerupi commented Aug 16, 2015

Ah yes I get it. I would avoid text in table cells too. Use unicode symbols like arewewebyet. And what you could do, is have both a table and a more detailed overview for each editor below the table. You could then link the different cells to the corresponding paragraph in the more detailed overview.

Just throwing in some ideas ;)

contradictioned pushed a commit that referenced this issue Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants