Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
purescript-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 140
    • Issues 140
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • purescript-gargantext
  • Issues
  • #626

Closed
Open
Opened Jan 26, 2024 by Fabien Maniere@fmaniere
  • Report abuse
  • New issue
Report abuse New issue

[Fonts & CSS] Internalise external calls (initiated by alternative themes)

We have to internalise all external assets on Gargantext. The objective is to make Gargantext usable on a "bunker" environment, where there is no internet connection.

Here is a list of identified files to internalise:

  • on switching to different themes (themeswitcher select box), some google fonts (prefixed calls with "https://fonts.gstatic.com")
  • then these external font files make also external calls to css file, like "https://fonts.googleapis.com/css?family=Oswald:200,300,400,700"

If I identify other external resources, I'll add to this issue.

Edited Jan 26, 2024 by Fabien Maniere
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
To Do
Assign labels
  • View project labels
Reference: gargantext/purescript-gargantext#626