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

Create & Document Element Stylesheets #148

Closed
wesleyboar opened this issue Mar 3, 2021 · 0 comments · Fixed by #150 or #194
Closed

Create & Document Element Stylesheets #148

wesleyboar opened this issue Mar 3, 2021 · 0 comments · Fixed by #150 or #194
Assignees
Labels
documentation Improvements or additions to documentation priority ▲ High priority

Comments

@wesleyboar
Copy link
Member

Goal

Create and document element stylesheets.

Background

Element styles should be organized, so they are easier to find (once one knows the organization) and easier to add when no other styles exist yet for the element. Multiple stylesheets limit context overhead when styling, but one stylesheet limits overhead of mastering organization before being able to edit styles.

Requirements

  1. Use KSS Node (for consistency).*
  2. One master element stylesheet may must be created. If so, then:
    1. Existing element styles must be migrated.
    2. TACC custom element styles must not be migrated.
  3. Multiple element stylesheets may be created. If so, then: […]

* This is a very old syntax that allows creation of a style guide with many supporting languages, like Node via kss-node. This syntax should probably be replaced later by something newer and better.

Direction

After much rumination and trial, I strongly suggest that one HTML stylesheet be created, because any organization—even MDN's—is foreign to someone, so we should ease the overhead of learning the organization by offering one stylesheet in which to search for any direct HTML element styling.

@wesleyboar wesleyboar added documentation Improvements or additions to documentation priority ▲ High priority labels Mar 3, 2021
@wesleyboar wesleyboar self-assigned this Mar 3, 2021
wesleyboar added a commit that referenced this issue Mar 3, 2021
wesleyboar added a commit to TACC/Core-CMS-Resources that referenced this issue Mar 3, 2021
Use `html-elements` stylesheet, not individual element stylesheets.
Use `GH-25` instead of `HACK` to highlight undesired `#content-wrap`.
wesleyboar added a commit to TACC/Core-CMS-Resources that referenced this issue Mar 3, 2021
wesleyboar added a commit to TACC/Core-CMS-Resources that referenced this issue Mar 3, 2021
Use `html-elements` stylesheet, not individual element stylesheets.
Use `GH-25` instead of `HACK` to highlight undesired `#content-wrap`.
wesleyboar added a commit that referenced this issue Mar 3, 2021
- The changes are relevant, but independent.
- They do not need to be mreged nor tested together.
wesleyboar added a commit that referenced this issue Mar 10, 2021
…ment-stylesheets

Task/gh 148 create and document element stylesheets
@wesleyboar wesleyboar linked a pull request Apr 14, 2021 that will close this issue
wesleyboar added a commit to TACC/Core-CMS-Resources that referenced this issue Apr 14, 2021
@wesleyboar wesleyboar linked a pull request Apr 14, 2021 that will close this issue
wesleyboar added a commit that referenced this issue Jul 1, 2022
* feat(submod): texascale, load annual stylesheets

For: https://jira.tacc.utexas.edu/browse/FP-1439
Mirrors: #490

* feat(settings): explicitely load new get_url_match

For: https://jira.tacc.utexas.edu/browse/FP-1439

* feat(submod): texascale, merged its PR #148

For: https://jira.tacc.utexas.edu/browse/FP-1439
Gets: TACC/Core-CMS-Resources#148
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 priority ▲ High priority
Projects
None yet
1 participant