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

Review use of inline table styles in complex doc tables #297

Open
jobara opened this issue Aug 1, 2024 · 1 comment
Open

Review use of inline table styles in complex doc tables #297

jobara opened this issue Aug 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@jobara
Copy link
Member

jobara commented Aug 1, 2024

#103 reintroduced some inline CSS styling that had previous been in use in the previous incarnation of our documentation on the Confluence wiki platform. Given we had had to manage without this for a while, the information that it conveyed (that particular sets of options were exclusive and not to be used simultaneously) had been encoded by other means (particular reference symbols such as daggers and double daggers). However, we should review the use of this styling and whether it is worth hoisting up into the shared infusion-docs.css area

Additional context or notes

Originally filed as FLUID-6063 by @amb26 on November 11, 2016.

@jobara jobara added the bug Something isn't working label Aug 1, 2024
@jobara
Copy link
Member Author

jobara commented Aug 1, 2024

Comment Migrated from FLUID-6063 originally posted by @sbates-idrc on November 18, 2016

An alternative to the use of styling and symbols such as daggers and double daggers for variant values would be to repeat each variation in full, such as in the jQuery docs: http://api.jquery.com/attr/#attr2
I think this might be a little easier to read but there is going to be some overhead in maintenance due to the duplication of information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant