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

Logo is muddy/ does not scale nicely #60

Open
DeniseColbert opened this issue Jun 26, 2019 · 3 comments
Open

Logo is muddy/ does not scale nicely #60

DeniseColbert opened this issue Jun 26, 2019 · 3 comments
Assignees

Comments

@DeniseColbert
Copy link
Collaborator

image.png

(both at 400%)

From @AlOneill : I can see what the the issue with the muddiness is caused by: the CSS is using data png instead of data svg

@DeniseColbert DeniseColbert assigned AlOneill and ghost Jun 26, 2019
@ghost
Copy link

ghost commented Jun 26, 2019

To confirm, you want to use https://www.freeukgenealogy.org.uk/images/svg/min/freeukgen.svg instead of the encoded PNG?

@AlOneill
Copy link
Collaborator

@arswright The Grunticon stylesheet loader is present in the head, but on both Chrome and Firefox, we are getting the data png styles. So the first question is does the data svg stylesheet exist and is it in the place expected by Grunticon?

I would not suggest putting the data svg image in the data png file: the separate files are there because of varying levels of browser support. There should also be a fallback file that uses ordinary png images: does that exist and is it where Grunticon expects? It should be served if, amongst other things, Javascript is turned off — have not tested that.

@ghost
Copy link

ghost commented Jun 26, 2019

@AlOneill

So the first question is does the data svg stylesheet exist and is it in the place expected by Grunticon?

I'm not seeing any references to the SVG logo in any files associated with the repo (nor any database dumps).

grep -Rin 'freeukgen.svg' ./
Binary file ./.git/index matches

I would not suggest putting the data svg image in the data png file: the separate files are there because of varying levels of browser support. There should also be a fallback file that uses ordinary png images: does that exist and is it where Grunticon expects? It should be served if, amongst other things, Javascript is turned off — have not tested that.

Haven't had time to get grunt-grunticon running - encountering errors when attempting to install:

7733 warn [email protected] requires a peer of grunt@>=1 but none is installed. You must install peer dependencies yourself.
7734 warn [email protected] No repository field.
7735 verbose stack Error: [email protected] install: `node-gyp rebuild`
7735 verbose stack Exit status 1
7735 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
7735 verbose stack     at EventEmitter.emit (events.js:198:13)
7735 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
7735 verbose stack     at ChildProcess.emit (events.js:198:13)
7735 verbose stack     at maybeClose (internal/child_process.js:982:16)
7735 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
7736 verbose pkgid [email protected]
7737 verbose cwd /mnt/archives/projects/site-uk.org.freeukgenealogy/public
7738 verbose Linux 4.4.0-151-generic
7739 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "grunt-grunticon"
7740 verbose node v10.16.0
7741 verbose npm  v6.9.0
7742 error code ELIFECYCLE
7743 error errno 1
7744 error [email protected] install: `node-gyp rebuild`
7744 error Exit status 1
7745 error Failed at the [email protected] install script.
7745 error This is probably not a problem with npm. There is likely additional logging output above.
7746 verbose exit [ 1, true ]

(Ultimately a moot point if this task is not prioritized over migration to WordPress CMS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants