Problem/Motivation

We don't provide clear guidance one when to use Libricons and what they mean. This may lead to them being used inconsistency in core and contrib.

Proposed resolution

Document the standards on https://drupal.org/ui-standards

Remaining tasks

1. Agree on the standard in this issue.
2. Update https://drupal.org/ui-standards with this new standard.

User interface changes

None.

API changes

None.

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Title: Document Libricon semantics with examples » [policy] Document Libricon (icon font) semantics with examples
Issue tags: +Coding standards

Um... What's a Libricon? Google and Wikipedia are not helpful. Oh, I see the parent issue. It's a font.

Where do you think this documentation should go? And is this a coding standard? I think it is; tagging/titling appropriately.

lewisnyman’s picture

lewisnyman
he/him
commented

Oops, It's a UI standard? That doesn't fall under documentation right?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

I guess it's a UI standard -- are you asking me? I don't really know what this issue is about, actually, but it looks like a UI standard. Some thoughts on tags, etc.:
- If it's just for the Seven theme, you could change the component to that; if it's for more themes, then "documentation" or "other" or "theme system"?
- If it's a UI standard, it probably needs the "usability" tag.

draganeror’s picture

draganeror
Primary language Serbian
Location Novi Sad
commented
Issue summary: View changes

Turned "Libricons" string into link in description above (for anyone who is curious).

Bojhan’s picture

Bojhan commented

This should be documented in https://drupal.org/ui-standards

lewisnyman’s picture

lewisnyman
he/him
commented
Issue tags: +frontend, +Usability
jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Issue summary: View changes

Updated issue summary with steps to be taken on this issue. (the next step would be to write up the section to be added to https://drupal.org/ui-standards as a comment here).

corbacho’s picture

corbacho commented

We are thinking to add a new SVG icon to Drupal core #2427213: Replace feed.png with feed.svg, following the Libricon structure. See the comment I'm linking

This will mean that not all the misc/icons/xxxxx (hex color) are designed by ry5n in his Libricon project.
(Personally I wouldn't like to add this restriction to SVG icons)

This would be important for documentation purposes.

corbacho’s picture

corbacho commented

Actually,
I think when this thread was open .. looks like libricons were going to be used in a "semantic way", with CSS classes.

Semantic Definition:

.druplicon-new:before { content: "\e000"; /* Copy this from the generated CSS */ }

So you can use .druplicon-new class somewhere in your code.

But that's not the case anymore. Icons are being used directly

.toolbar .toolbar-icon.toolbar-handle:before {
  background-image: url(../../../misc/icons/5181c6/chevron-disc-down.svg);
}

So, maybe we should remove the word "semantics" from the issue title ?

This change record is a bit related to the issue too: https://www.drupal.org/node/2384159

lewisnyman’s picture

lewisnyman
he/him
commented
Title: [policy] Document Libricon (icon font) semantics with examples » [policy] Document Libricon semantics, including examples

I think that the semantics should still be clear, even if the usage is different. We can open a new issue to create a set of reusable icon classes.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Postponed (maintainer needs more info)

There has been no activity here for 10 years.

Is this still needed? If confirmation that this is still needed isn't supplied this may be closed after three months.

Thanks!

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

I think this can be removed. I don't believe we use those fonts anymore?

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.