Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • asciidoc.org asciidoc.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Working Groups
  • AsciiDoc WG
  • asciidoc.orgasciidoc.org
  • Issues
  • #12
Closed
Open
Issue created Apr 05, 2022 by Dan Allen@mojavelinuxMaintainer

Pull custom fonts from npm package / node_modules

The custom fonts should be pulled from an npm package (i.e., the node_modules folder) when the site is built instead of being hosted in the source tree for this site. If the fonts are going to be subsetted as an optimization, that process should be done as part of the build. The current situation of storing subsetted fonts directly in the source tree for this site is not maintainable and makes the built hard to understand.

Furthermore, no font files should be loaded from Google Fonts. That violates our privacy requirements (since Google Fonts adds unwanted tracking). It's unnecessary anyway since the site's build already provides an opportunity to retrieve and publish these files as part of the site.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent