nextcloud/nextcloud.com

Avoid loading assets from Google

Open

#606 opened on Sep 28, 2017

View on GitHubContributor guide
 (1 comment) (2 reactions) (0 assignees)PHP (126 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (215 stars)
PR merge metrics
 (PR metrics pending)

Description

It’s a bit antithetical that we load fonts and jQuery from Google in some places, whereas we can really easily serve them ourselves. Is there any specific reason for that?

If not, here’s a PR to load the fonts from our own site: https://github.com/nextcloud/nextcloud.com/pull/605

And I saw some places where jQuery and other libs are loaded from googleapis, would be good to fix that too.

Contributor guide

Research direction
Search the codebase for references to Google Fonts, googleapis, or other Google hosted assets. Identify each instance and research the corresponding local file or self hosted alternative. Create a list of changes needed to replace external URLs with local assets.
Tech stack
phpjavascriptcss
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Basic HTML/CSS/JSGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90