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

We should not assume all images come from /images #14

Open
saper opened this issue Jan 13, 2020 · 0 comments
Open

We should not assume all images come from /images #14

saper opened this issue Jan 13, 2020 · 0 comments

Comments

@saper
Copy link

@saper saper commented Jan 13, 2020

It seems that it is not possible to use Hugo's image processing or page resources features because this theme seems to hardcode .../images/... path in few places:

  • {{ if .Params.img }}
    <img width="100%" src="{{ .Site.BaseURL }}images/{{ .Params.img }}" alt="{{ .Title }}">
    {{ else }}
    <img width="100%" src="{{ .Site.BaseURL }}images/{{ .Site.Params.defaultImage }}" alt="{{ .Site.Title }}">
    {{ end }}

  • {{ if .Params.img }}
    <img width="600" src="{{ .Site.BaseURL}}images/{{ .Params.img }}" alt="{{ .Params.title }}">
    {{ else }}
    <img width="600" src="{{ .Site.BaseURL }}images/{{ .Site.Params.defaultImage }}" alt="webjeda">
    {{ end }}

@saper saper changed the title We should not assume all images come from /static/images We should not assume all images come from /images Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.