pacollins/hugo-future-imperfect-slim

Multilingual Blogging Theme for Hugo | Check the Wiki for Documentation

hugo-future-imperfect-slim's Issues

BUG: Spanish word in Portuguese locale for site footer

Bug Report

Describe the bug

In Spanish word "impulsado" has been introduced into the Portuguese locale file in #51.

hugo-future-imperfect-slim/i18n/br.toml

Line 50 in 80ca0db

other = "Tema: <a href='https://themes.gohugo.io/hugo-future-imperfect-slim/' target='_blank' rel='noopener'>Hugo Future Imperfect</a><br>Adaptado de <a href='https://html5up.net/future-imperfect' target='_blank' rel='noopener'>HTML5 UP</a> | Impulsado por <a href='https://gohugo.io/' title='{{ .Site.Hugo.Version }}' target='_blank' rel='noopener'>Hugo</a>"

However, this is not a Portuguese word. You may see, for example, Liguee, Wiktionary, Collins Dictionary, etc.

Expected behavior

A Portuguese translation for "powered by".

Screenshots

NIL

Environment

• Hugo Version: [e.g. 0.46]
• Browser and Version: [e.g. Chrome 74.0.3729.108]
• Platform: [e.g. Desktop/Mobile]
• Link to Project:

Additional context

BUG: Theme not responsive

Bug Report

Describe the bug

Especially on smaller mobile screens you first have to zoom out before you can see the full webpage. I removed all of my custom css and its still too big.

Also when changing the font-size, the text-boxes stay the same size relative to the text.

To Reproduce

Steps to reproduce the behavior:

1. Open Site with theme on mobile

Expected behavior

Correct site size

##Screenshots

Environment

• Hugo Version: v0.55.6
• Browser and Version: Chrome 75.0.3770.80
• Platform: Desktop/Mobile
• Link to Project: Private

FEATURE: Remove About from the Sidebar

Feature Request

Remove "about" from the sidebar
Changing categories to false under [params.sidebar] removes it from the landing page, however the same is not true for about.

Is your feature request related to a problem?

No

Solution

A parameter that toggles sidebar "About" similar to categories.

Alternatives

Additional Context

BUG: main.scss not used

Bug Report

Describe the bug

In #53, it's suggested to change

hugo-future-imperfect-slim/static/css/main.scss

Line 896 in d80bfe5

grid-template-rows: 22em auto auto 1fr;

However, searhcing "main.scss" gives no results.

Expected behavior

SCSS rules in static/css/main.scss compiled and loaded into the web browser's developper tools.

Suggestion

Use Hugo's ToCSS and remove static/css/main.min.css.

Screenshots

Environment

• Hugo Version: [e.g. 0.46]
• Browser and Version: [e.g. Chrome 74.0.3729.108]
• Platform: [e.g. Desktop/Mobile]
• Link to Project:

Additional context

How to setup SCSS with Hugo? on Stack Overflow.

FEATURE: Add authors page

Feature Request

Is your feature request related to a problem? Please describe.
One important thing missing from this blog is the author section.

Describe the solution you'd like
We are a team of Python developers and we would like to have designated author section for each of our authors.

Additional context
Is it possible to add the authors page functionality to this amazing theme?

FEATURE: Hide Staticman POST URL in Go-HTML template

Feature Request

Is your feature request related to a problem?

Staticman spam is a known issue for years.

1. eduardoboucas/staticman#175
2. eduardoboucas/staticman#176 (comment)

Despite Staticman's release of v3, the problem is still happening: https://github.com/zinefer/zinefer.github.com/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3ASpam.

Solution

Move the form action URL from the Go-HTML template to JavaScript assets.

Alternatives

Use reCAPTCHA, but there's no guarantee for this: see https://gitlab.io/pcercueil/

Additional Context

1. eduardoboucas/staticman#306
2. Anti-spam tips: https://discourse.gohugo.io/t/disqus-alternatives/2948/42?u=vincenttam

BUG: Folder structure in README lists files that do not exist in the repo.

Bug Report

Describe the bug

There seems to be some file structure in the README.md file which is no longer in the repo.

I was looking for the itemized files listed in the tree, but it seems they do no longer exist in the repo.

|   └── itemized
|       ├── item1.fr.md
|       ├── item1.md
|       ├── item1.pl.md
|       ├── item2.fr.md
|       ├── item2.md
|       ├── item2.pl.md
|       ├── item3.fr.md
|       ├── item3.md
|       ├── item3.pl.md
|       ├── item4.fr.md
|       ├── item4.md
|       └── item4.pl.md

FEATURE: Add Tags page similar to Categories page...

Feature Request

Is your feature request related to a problem?

I'm wanting to add a tags page similar to the categories page already included, but can't figure out how to...

Solution

Please add a tags page that will list all tags used in posts, and link to them.

Type: Maintenance Is there any reason not to raise the version of Font Awesome?

Feature Request

I wanted to send a pull request to add the keybase and mastodon icons to social-icon.html.
But the icons I want to add are compatible only with Font Awesome v5.8 or higher.
Is there any reason not to use the higher version?
I tried v5.9.0 on examplePage, but the icons seem to be showing without problems.

FEATURE: Support custom Git service provider

Feature Request

Due to Staticman v3's native GitLab support introduced in eduardoboucas/staticman#219, it's better to edit this theme's Go-HTML template code to provide support for this. #6 hard codes the :service to github, but this is unnecessarily GitHub specific. Staticman's author says that the app's job is to get the HTML form data into the Git repo in eduardoboucas/staticman#264 (comment). Restricting the form action URL to github contradicts this idea.

hugo-future-imperfect-slim/layouts/post/staticman.html

Line 3 in e0eb982

<form class="post-new-comment" method="POST" action="https://dev.staticman.net/v3/entry/github/{{ .username }}/{{ .repo }}/{{ .branch }}/data/comments">

See also: mmistakes/minimal-mistakes#1845

FEATURE: Is it possible to put a logo in the navbar header?

Hello,
I am trying to put a logo in the navbar where the title text goes (just like github does). Is there any way to do this other than hacking in the code?

I tried setting the following, but it seems the text does not get interpreted as html:

    navbarTitle         = "<img src='/img/logos/blog-logo.png'>"

Thanks

BUG: Incorrect image paths

Bug Report

Describe the bug

I tried building a demo site for this theme on Framagit: https://vincenttam.frama.io/fish-demo/blog/creating-a-new-theme/ with

baseurl = "https://vincenttam.frama.io/fish-demo/"

in config.toml. However, the images aren't rendered. Rendered HTML shows

<article class="mini-post">
      <section>
        
<a href="/fish-demo/blog/hugoisforlovers/" class="image featured">
  <img src="/img/2014/04/pic01.jpg" alt="Pic 1">
</a>


      </section>
      <header>
        <h1><a href="/fish-demo/blog/hugoisforlovers/">Getting Started with Hugo</a></h1>
        <time class="published" datetime="">April 2, 2014</time>
      </header>
    </article>

The src of the <img> is incorrect in case of GitHub/GitLab project pages. I'm not an expert in web design/development. You're going to be more proficient than me to fix this.

hugo-future-imperfect-slim/layouts/post/featured.html

Lines 1 to 5 in e0eb982

	{{ if .Params.featured }}
	<a href="{{ .RelPermalink }}" class="image featured">
	<img src="/img/{{ if eq .Params.featuredpath "date" }}{{ .Page.Date.Format "2006/01" }}/{{ else }}{{ .Params.featuredpath }}{{ end }}{{ .Params.featured }}" alt="{{ .Params.featuredalt }}">
	</a>
	{{ end }}

Besides, I also get error on nav bar and page redirect after submitting Staticman comment. The images in the posts have incorrect URL's.

To Reproduce

1. Use this theme on a GitHub/GitLab project pages
2. See broken images

Expected behavior

Screenshots

Environment

• Hugo Version: 0.55.6
• Browser and Version: Firefox 67.0.4 (64-bit)
• Platform: Desktop
• Link to Project: https://framagit.org/VincentTam/fish-demo

BUG: Twitter card doesn't show the feature image

Bug Report

Describe the bug

Twitter card doesn't show the feature image

To Reproduce

1. write an article with the feature image declared like this
   featured = "2019-07-Expatriation-2-Arriving-in-London.jpg"
   featuredalt = "London from the 'London Eye'"
   featuredpath = "date"

[twitter]
image = "https://www.jubi.io/img/2019/07/2019-07-Expatriation-2-Arriving-in-London.jpg"
image_alt = "London from the 'London Eye'"

Expected behavior

When posting on Twitter, I would expect the TwitterCard to show the picture
Upon inspecting the source code, I expect to find a <meta name="twitter:image> or og:image tags (cf the specification)
Upon using Twitter card validator, the image should be found

Actual behavior

The image feature is found, and does show up on the blog entry thumbnail, and as the hero image on the blog post itself.

The Twittercard shows the generic image
The twitter:image tag is nowhere to be found in the source code, which makes the validator fail to find the image

• Hugo Version: : v0.55.6
• Browser and Version: : Chrome Beta 76.0.3809.87 (Official Build) beta (64-bit)
• Platform: : Linux (not platform dependant)
• Link to Project: : https://jubi.io/blog/2019-07-expatriation-2-arriving-in-london/

Additional context

The default partial code is here, and seems to support many ways of declaring the image. It also seems that the template calls this partial in /themes/hugo-future-imperfect-slim/layouts/partials/head.html
I suppose I am declaring the image wrong, but I don't know what is wrong.

FEATURE: Search

Feature Request

The framework of this exists in the theme, but it needs to be re-implemented. Previously it was a custom Google search. I would like to see some sort of internal static search.

BUG: featuredpath other than 'date' resolves path to img/img/desired/path

Bug Report

In post parameters, the 'featuredpath' must use 'date' otherwise the url base will resolve to 'img/img/XXX' where 'XXX' is the alternative provided path.

To Reproduce

Create a new post.
Set featuredpath: 'pictures/post941pics'
Compile/hugo.
See resulting html path be to /img/img/pictures/post941/theimage.png

Expected behavior

The resulting html path to be /pictures/post941/theimage.png

• where theimage.png is defined in 'featured'.

Environment

• Hugo Version: [e.g. 0.55.6]

BUG: Left sidebar overlapping

Bug Report

Describe the bug

See the animated screenshot below and the title above.

To Reproduce

Increase the size of the site icon.

Expected behavior

Recent posts section won't overlap with intro section no matter how large the icon is.

Screenshots

Environment

• Hugo Version: 0.56
• Browser and Version: Firefox 68.0.1
• Platform: Desktop
• Link to Project: https://vincenttam.frama.io/fish-demo/, https://framagit.org/vincenttam/fish-demo/

Additional context

BUG: Titles, Tags, or Categories with long words cause horizontal scrolling small-width devices.

Bug Report

Describe the bug

I'm not sure if this is actually a bug or working as intended. I also apologize in advance if I use the wrong terminology for some things. Web dev is not my area of expertise.

When I create posts that contain Titles, Tags, or Categories that contain long words, the page gets rendered wider than the viewport(?) on devices with a relatively small width such as a phone. By long words, I mean something like thisisalongwordwithnospaces. Adding spaces or hyphens allows the words to wrap on those boundaries and the view renders normally again.

To Reproduce

1. Create a new post that contains any or all of the following. The longer the word is, the more obvious the problem is.

• title = "My Post WithASuperLongWordIsLong"
• categories = ["MySuperLongWordIsLong"]
• tags = ["mysuperlongwordislong"]

2. Open the page on a phone or emulated iPhone 6/7/8 view in Chrome

Expected behavior

For Categories and Tags, I'd probably prefer the words get cut off (clipped?) rather than cause the whole page to be rendered too wide and need horizontal scrolling. I have no idea how to make this happen though. I tried playing around with overflow-related CSS things in Chrome dev tools without much luck.

I'm not exactly sure what I'd prefer to happen for Titles. Is there a way to force the browser to wrap long words even if they don't have natural breaks like a hyphen?

Environment

• Hugo Version: 0.57.0
• Browser and Version: Mobile Safari on iOS 12.4, Chrome 76.0.3809.100 emulating iPhone 6/7/8,
• Platform: Mobile
• Link to Project:

BUG: exampleSite does not load main.min.css.

Bug Report

Describe the bug

When I start Hugo server using exampleSite, the following error happend. And does not load main.min.css.

Failed to find a valid digest in the 'integrity' attribute for resource 'http://localhost:1313/css/main.min.1b31ef55024da14996b25283db21d8b249bf405d2c3c4da88ea3f262280698cf.css' with computed SHA-256 integrity 'xMSqFvcG6mqcJ35Dzx2mGMTSDUgMR5z4njbozDQf4rM='. The resource has been blocked.

To Reproduce

1. Create new site.
2. Download hugo-future-imperfect-slim to theme directory.
3. Execute the following command in root directory.

xcopy /s /e .\themes\hugo-future-imperfect-slim\exampleSite .

4. Execute the following command in root directory.

hugo server

Expected behavior

Load main.min.css.

Screenshots

Environment

• Hugo Version: [0.57.2]
• Browser and Version: [Vivaldi 2.7.1628.33, Google Chrome 76.0.3809.132]
• Platform: [Desktop]
• OS: [Windows 10 (1903)]

BUG: qutebrowser display problem

Bug Report

Describe the bug

A user reported this theme's resposive issue in #18, in which @pacollins has provided a link to https://www.pacollins.com/. I've used Firefox 67.0.4 (64-bit) to browse it. That works great! However, the display for qutebrowser is strange.

To Reproduce

Open https://www.pacollins.com/ with qutebrowser.

Expected behavior

Screenshots

Environment

• Hugo Version: ?
• Browser and Version: qutebrowser
• Platform: Desktop
• Link to Project: ?

$ qutebrowser --version
qutebrowser v1.1.1
Git commit: 
Backend: QtWebEngine (Chromium 56.0.2924.122)

CPython: 3.6.8
Qt: 5.9.5
PyQt: 5.10.1

sip: 4.19.7
colorama: 0.3.9
pypeg2: 2.15
jinja2: 2.10
pygments: 2.2.0
yaml: 3.13
cssutils: no
attr: 17.4.0
PyQt5.QtWebEngineWidgets: yes
PyQt5.QtWebKitWidgets: no
pdf.js: no
sqlite: 3.22.0
QtNetwork SSL: OpenSSL 1.1.1  11 Sep 2018

Style: QFusionStyle
Platform: Linux-4.15.0-54-generic-x86_64-with-Ubuntu-18.04-bionic, 64bit
Linux distribution: Ubuntu 18.04.2 LTS (ubuntu)
Frozen: False
Imported from /usr/lib/python3/dist-packages/qutebrowser
Qt library executable path: /usr/lib/x86_64-linux-gnu/qt5/libexec, data path: /usr/share/qt5

Paths:
cache: /home/vin100/.cache/qutebrowser
config: /home/vin100/.config/qutebrowser
data: /home/vin100/.local/share/qutebrowser
runtime: /run/user/1000/qutebrowser
system data: /usr/share/qutebrowser

Uptime: 0:00:00

Additional context

BUG: Staticman reCAPTCHA Error

Bug Report

Describe the bug

Staticman V2 was not working due to an issue with request limits. Was upgraded to v3 and now it has a reCAPTCHA error even when disabled.

To Reproduce

Steps to reproduce the behavior:

1. Submit a comment via Staticman

Expected behavior

Comment should successfully post
##Screenshots
If applicable, add screenshots to help explain your problem.

Environment

• Hugo Version: 0.50
• Browser and Version:
• Platform:
• **Link to Project: **

Additional context

See eduardoboucas/staticman#243

BUG: social icons/ footer not centered

The footer section that encompasses the social icons is not centered.

FEATURE: Optionally remove 'recent posts' from sidebar

Feature Request

Is your feature request related to a problem? Please describe.
It would be great if it was possible to disable the 'RECENT POSTS'-box in the sidebar.
Yet it's always displayed, even if params.sidebar.postAmount is set to 0.

Describe the solution you'd like
In my opinion it would be enough just setting the key params.sidebar.postAmount to false:

  [params.sidebar]
    # Sets the number of recent posts to show in the sidebar. The default value is 5.
    postAmount          = false

That way it would be enough to simply add an if in the corresponding html-template layouts/partials/site-sidebar.html:

{{ if .Site.Params.sidebar.postAmount }}
    <section id="recent-posts">
        <header>
            <h1>{{ i18n "recent_posts" }}</h1>
        </header>
        {{ range first (.Site.Params.sidebar.postAmount | default 5) (where .Site.Pages  "Type" "post") }}
        <article class="mini-post">
            <section>
                {{ .Render "featured" }}
            </section>
            <header>
                <h1><a href="{{ .RelPermalink }}">{{ .Title }}</a></h1>
                <time class="published" datetime="">{{ default (i18n "date_format") | .Date.Format }}</time>
            </header>
        </article>
        {{ end }}
        {{ if ge (len (where .Site.Pages "Type" "post")) (.Site.Params.sidebar.postAmount | default 5) }}
        <a href="{{ with .Site.Params.viewMorePostsLink }}{{ . | relLangURL }}{{ else }}{{ "post" | relLangURL }}{{ end }}" class="button">{{ i18n "see_more" }}</a>
        {{ end }}
    </section>
    {{ end }}

Describe alternatives you've considered
Actually none 🤣

Additional context
What do you think?

BUG: Incorrect Staticman v3 form URL

The code for Staticman integration confuses me.

1. Should {{ with ... }} ... {{ end }} enclose the entire HTML form?
2. What does /data represent in Staticman's v3 URL scheme in eduardoboucas/staticman#219? Even though I didn't tested the GitHub Apps functionality, which won't interest any evangelical free software users, AFAIK such theme remains valid. The /data part probably needs to be removed.

hugo-future-imperfect-slim/layouts/post/staticman.html

Lines 1 to 28 in e0eb982

	<h2>Say something</h2>
	{{ with .Site.Params.staticman }}
	<form class="post-new-comment" method="POST" action="https://dev.staticman.net/v3/entry/github/{{ .username }}/{{ .repo }}/{{ .branch }}/data/comments">
	{{ end }}
	<input type="hidden" name="options[redirect]" value="{{ .Site.BaseURL }}{{ .RelPermalink }}">
	<input type="hidden" name="options[entryId]" value="{{ .UniqueID }}">
	<input required name="fields[name]" type="text" placeholder="Your name (Required)">
	<input name="fields[website]" type="text" placeholder="Your website">
	<input required name="fields[email]" type="email" placeholder="Your email address (Required for Gravatar)">
	<textarea required name="fields[body]" placeholder="Your message. Feel free to use Markdown (Google 'Markdown Cheat Sheet')." rows="10"></textarea>
	{{ if .Site.Params.staticman.recaptcha.recaptcha }}
	<input type="hidden" name="options[reCaptcha][siteKey]" value="{{ .Site.Params.staticman.recaptcha.sitekey }}">
	<input type="hidden" name="options[reCaptcha][secret]" value="{{ .Site.Params.staticman.recaptcha.encryptedkey }}">
	<input type="hidden" id="g-recaptcha-response" name="g-recaptcha-response">
	{{ end }}
	<input type="submit" value="Submit">
	</form>
	{{ if .Site.Params.staticman.recaptcha.recaptcha }}
	<script>
	grecaptcha.ready(function() {
	grecaptcha.execute('{{ .Site.Params.staticman.recaptcha.sitekey }}', {action: 'homepage'})
	.then(function(token) {
	//console.log(token);
	document.getElementByID('g-recaptcha-response').value=token;
	});
	});
	</script>
	{{ end }}

BUG: Post reading time singular/plural issue

Bug Report

Describe the bug

When postreadingtime = 1, the displayed text would be "1 minutes", which is grammatically incorrect.

hugo-future-imperfect-slim/i18n/en.toml

Lines 3 to 4 in afbf3cc

	[postreadingtime]
	other = "minute read"

hugo-future-imperfect-slim/layouts/post/header.html

Line 19 in 779a353

<p>{{ .ReadingTime }} {{ i18n "postreadingtime" }}</p>

Edited: idem for

hugo-future-imperfect-slim/layouts/contact/list.html

Line 29 in a596634

<h4>{{ i18n "repliestext" }} {{ .Params.contactanswertime }} {{ i18n "hours" }}.</h4>

⚠️ Note that the word order in different languages can be different. Creating a PR for that.

To Reproduce

Go to any post whose postreadingtime is 1.

Expected behavior

Display "1 minute" and "N minutes" wherever N > 1.

Screenshots

N/A

Environment

• Hugo Version: all versions
• Browser and Version: all browsers
• Platform: all platforms
• Link to Project: any forks/projects using this theme

Additional context

1. Hugo's docs for translation strings

2. Introduction theme's example:

   [blog_readingTime]
   one = "{{ .Count }} Minute zum Lesen"
   other = "{{ .Count }} Minuten zum Lesen"

   Source: https://github.com/victoriadrake/hugo-theme-introduction/blob/8b1684b6c27c51bde5c4bb058e40e288089eb129/i18n/de.toml#L19-L21

BUG: Menu code doesn't follow Hugo docs

Code Change Request

Is your request related to a problem?

The current code base makes use of the identifier field to render Font Awesome icons.

hugo-future-imperfect-slim/exampleSite/config.toml

Lines 111 to 115 in f0ec5ac

	[[menu.main]]
	name = "Home"
	url = "/"
	identifier = "fas fa-home"
	weight = 1

Even though this works, this is not the intended role of this field. This field serves as a unique ID for the menu entry so that its children be associate themselves with it using their parent field.

[[menu.main]]
  name = "About"
  url = "page/about/"
  weight = 1

[[menu.main]]
  name = "Math Resources"
  url = "math-live-preview"
  weight = 2

[[menu.main]]
  parent="Math Resources"
  name = "Math Editor"
  url = "math-live-preview"
  weight = 1

[[menu.main]]
  parent="Math Resources"
  name = "Math.SE Comments"
  url = "page/math-se-comment-templates/"
  weight = 2

Source: site config for my blog

Solution

Use the pre field instead of identifier.

Additional Context

• Menu Entry Properties | Hugo
• Menus | Hugo

BUG: pagination button size on long titles

Bug Report

Describe the bug

The buttons to navigate to the next or previous article are designed for quite short titles. Longer titles get wrapped. In this case, the border is to small.

In my opinion, you can fix it by allowing the box to grow:
Currently, the css class button contains "height: 4.8125em;" . By switching to "min-height: 4.8125em;" the box can grow. I think, for usability, that's good solution.

A second way would be to cut the text. This could be done by adding these attributes to button:

overflow: hidden;
white-space: nowrap;
text-overflow: ellipsis;

From a designers point of view, this is probably preferable. Even better would be to cut the title and keep the ">".

Environment

• Hugo Version: v0.57.2
• Browser and Version: Firefox 68, Chrome 76
• Platform: Dektop

BUG: Social Share Buttons inside post not working

Bug Report

Describe the bug

The social share buttons are not working as expected. They don't have the url and the title of the post. It is just e.g. https://twitter.com/share?url=&text=&

To Reproduce

Steps to reproduce the behavior:
Setup a hugo site with this theme and look at the details of a post.

Expected behavior

The share link should contain the permalink and the title of the post.

Environment

• Hugo Version:
• Browser and Version: Firefox 66.04
• Platform: Desktop and Mobile
• **Link to Project: ** https://atomfrede.gitlab.io/ https://gitlab.com/atomfrede/atomfrede.gitlab.io

FEATURE: Remove references to third-party CDNs from site head

Feature Request

Is your feature request related to a problem?

😥 Our project has several references to external scripts.

hugo-future-imperfect-slim/layouts/partials/scripts.html

Lines 8 to 10 in d36f889

	<script src="https://code.jquery.com/jquery-3.3.1.min.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/skel/3.0.1/skel.min.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/fancybox/3.3.5/jquery.fancybox.min.js"></script>

⚠️ This practice is not recommended by @onedrawingperday in the updated Theme Submission Guidelines in gohugoio/hugoThemes#668.

🖊️ I avoid putting links here so that our project won't be linked there.

Solution

Download the minified scripts and store the local copies under assets/static.

Additional Context

The aforementioned issue in https://github.com/gohugoio/hugoThemes.

FEATURE: Switch from flags to language names

Bug Report

Problem description

I am from Austria. Although we speak German here our language and culture is different from Germany in a few aspects.

Our official locale as far as i know is de-AT, but when I use that for the translation it tries to load the flag flag-icon-de-at which does not exist.

Solution

A configuration possibility to configure the flag icon independently could solve the issue.

i.e.

flag: at

Workaround

I just use 'at' now as locale. Now the flag works, but I am not sure what else I broke in the process of doing so.

BUG: nav bar URL error

Bug Report

Describe the bug

Nav bar links duplicate project slug in GitHub/GitLab project pages.

On demo site: https://vincenttam.frama.io/fish-demo/, I got

https://vincenttam.frama.io/fish-demo/fish-demo/categories/

and so on.

Expected behavior

https://vincenttam.frama.io/fish-demo/categories/

Screenshots

Environment

• Hugo Version: 0.55
• Browser and Version: Firefox 67.xxx
• Platform: Desktop
• Link to Project: https://framagit.org/VincentTam/fish-demo

Tags

Feature Request

Is your feature request related to a problem?

I have some problem using tags,

when I add tags to a new post i see the tags in the site (for now I'm using the local server provided by Hugo), the problem occurs when I click on the tag.

Clicking on the tag cause the 404 error, the site goes to "localhost:1313/tags/mytag" but I haven't that page in my Hugo's generated pages.

What can I do to resolve?
Thanks for the Help
(Sorry for my bad English, i'm not so good in writing)

Solution

Alternatives

Additional Context

I'm using theme Vanilla, i have modify only the language adding the Italian

FEATURE: Populate Non-Translated Articles with Default Language; Add "Page Not Translated" Banner

I am reading through the hugo functions and noticed lang.Merge which allows you to populate any non-translated articles with the default language:

--en
|---1.md
|---2.md
|---3.md
--fr
|---1.md.fr
|---2.md.fr
|---3.md <==English article

Any thoughts on this? A site that loses content when you change languages is odd, but so is thinking everything is translated.

BUG: all titles have the same size

Bug Report

Describe the bug

All titles have the same size (

To Reproduce

Steps to reproduce the behavior:

1. publish a blog post
2. realise all titles have the same size.

Upon inspection, it seems that this rule is the culprit (line 950 of main.css):

.post>div h1, .post>div h2, .post>div h3, .post>div h4, .post>div h5, .post>div h6, .post>p h1, .post>p h2, .post>p h3, .post>p h4, .post>p h5, .post>p h6 {
    font-size: 1em;
}

Expected behavior

I would expect titles to look different to convey hierarchy.
Removing this rule works, as all titles are already formatted in a different way

Here is the same post by unticking the rule in the Dev tools :

Environment

• Hugo Version: 0.55.6
• Browser and Version: Version 75.0.3770.51 (Official Build) beta (64-bit)
• Platform: Desktop
• Theme version

commit d36f8892421fe4bf831e8d1cfb8b1dd40b04fae9 (HEAD -> master, origin/master, origin/HEAD)
Author: Patrick Collins <[email protected]>
Date:   Mon May 20 08:29:06 2019 -0400

    Bug fix (#9)
    
    Closes #9

BUG: What is the matter with add-on.js and add-on.css?

Hello,

I was looking for the source of the issues why my browser was complaining that add-on.css and add-on.js have a MIME type mismatch. I read that this occurs when the file does not exist. And indeed those two files do not exist. However the documentation still lists them and they are also referred to in partials/scripts.html and partials/head.html.

So what is the matter with those files. Are the references forgotten references and should be removed or am I missing something?

I get the errors on the hugo live server as well as on my production system.

BUG:

Bug Report

Describe the bug

Error parsing the template

To Reproduce

hugo_0.55.6\hugo.exe server
Error: "C:\Users.......\themes\hugo-future-imperfect-slim\layouts\partials\scripts.html:3:1": parse failed: template: partials/scripts.html:3: function "Site" not defined

Licensing issue

https://html5up.net/license

Your LICENSE file makes it appear as though the original theme from HTML5Up was licensed under Expat/X11 though it was not and all users of remixes of the actual license (linked above) must give credit as required by the licensor.

BUG: Incorrect german date format

Bug Report

Describe the bug

The date_format in i18n/de.toml defined as ´02-01-2006´. The common format in Germany is "02.01.2006", according to DIN 1355-1. Actually nowadays there's ISO 8601 - but this is not used in Germany. "02.01.2006" is the format you see in common software like Windows. This format is used by public authorities, too.

Environment

• Hugo Version: 0.57.2

PRIORITY: Hugo 0.57.0 Breaking Changes

⚠️ HUGO BREAKING CHANGE ⚠️

I was notified by gohugoio/hugoThemes/issues/682 that:

a great number of theme demos now display empty homepages and/or post lists that point to section lists (instead of individual posts).

This includes us. The changes are described in more detail here gohugoio/hugoThemes/issues/678

Suggestion: Implement better documentation

yes

yes

There is no such wiki

yes

Expected Behavior

Include better documentation, including these shortcodes that the theme supposedly includes, but are not listed anywhere.

Current Behavior

The current documentation is limited and does not list the shortcodes that supposedly ship with this theme.

Possible Solution

Actually using the provided Wiki would be a good method of implementing better documentation.

Steps to Reproduce or Template with Error (for bugs)

Context

I cannot make full and proper use of this theme if I don't know all the ins and outs of it.

BUG: Missing locales for 404 page

Bug Report

Describe the bug

hugo-future-imperfect-slim/layouts/404.html

Lines 56 to 59 in 58c2de9

	<h1>404</h1>
	<h2>Page Not Found</h2>
	<p>Sorry, but the page you were trying to view does not exist.</p>
	<a href="javascript:history.back()">Go Back</a>

Since our theme claims to be a "multilingual blogging theme for Hugo", we've to fix that.

Expected behavior

Translations for these strings.

BUG: staticman comments rendered even when config boolean is false

Bug Report

Describe the bug

In config.toml when disqusShortname = "" in the root and staticman = false in the [params.staticman] section (which are the defaults in the example site), the staticman comments markup is still rendered by layouts\post\comments.html.

To Reproduce

1. Create a new site based on the example site
2. Go to any blog post
3. Scroll to the bottom
4. See the "Say Something" and "Comments" markup

Expected behavior

The "Say Something" and "Comments" markup should not be rendered when staticman = false.

Environment

• Hugo Version: 0.57.0
• Browser and Version: Chrome 76.0.3809.100
• Platform: Desktop

FEATURE: Add a link to the demo site

Feature Request

Is your feature request related to a problem?

I've to leave this search and google this theme to reach https://themes.gohugo.io/hugo-future-imperfect-slim/, which contains a link to the demo site. This is quite inconvenient.

Solution

Please add a link to the demo site at the top like https://github.com/daattali/beautiful-jekyll/.

BUG: Author not rendering in email link in share-buttons.html

Bug Report

Describe the bug

When clicking on the 'email' share button, the link created puts the text '{ map[]}' in the subject line instead of the author name.

Fix

Modify 'layouts/partials/head.html' and change

{{ .Scratch.Set "Author" .Author }}

to

{{ .Scratch.Set "Author" .Params.Author }}

Sorry -- not very proficient with git or pull requests (yet), so offered the above fix.

To Reproduce

Create/open a post and click on the share email icon.

The link created will have the correct permalink, but the bogus author name.

Expected behavior

The author name properly appearing in the email link.

Screenshots

None

Environment

• Hugo Version: 0.58
• Browser and Version: Chrome 77.0.3865.90
• Platform: Desktop
• Link to Project: (in development)

Additional context

FEATURE: Create Wiki and Update Docs

Feature Request

Is your feature request related to a problem?

In an effort to increase theme usability, we should update documentation and flesh out the wiki for new users.

Tasks

• Update theme.toml
• Update README.md
• Confirm LICENSE.md
• Remove stale.yml
• Update PULL_REQUEST_TEMPLATE.md
• Update CONTRIBUTING.md
• Update CODE_OF_CONDUCT.md
• Update bug_report.md
• Update PULL_REQUEST_TEMPLATE.md
• Add additional templates as needed

BUG: categories not performance good

Bug Report

Describe the bug

categories be a blog page

To Reproduce

Steps to reproduce the behavior:
hugo server
localhost:1313/categories/
and didn't see the categories list

Expected behavior

a categories list

##Screenshots

Environment

• Hugo Version: [ 0.55.6]
• Browser and Version: [e.g. Chrome 74.0.3729.108]
• Platform: [ Desktop and Mobile]
• **Link to Project: **

Additional context

Add any other context about the problem here.

I also use tags for that ,and tags performance good.

How can I dd more items on menu

I would like to add more options on menu. Create a menu item on conifg.toml, create a folder in contet and the new menu should be ready.

  [[menu.main]]
    name              = "Categories"
    url               = "/categories/"
    identifier        = "fas fa-sitemap"
    weight            = 4

  [[menu.main]]
    name              = "Articles"
    url               = "/articles/"
    identifier        = "far fa-envelope"
    weight            = 5

  [[menu.main]]
    name              = "Contact"
    url               = "/contact/"
    identifier        = "far fa-envelope"
    weight            = 6

And this new item doesnt appear on menu bar:

FEATURE: Create warning box for features and breaking changes.

Feature Request

Is your feature request related to a problem?

Currently, users of the theme may not know of features being deprecated or changed drastically. It would be ideal to provide a way of communicating with them via their localhost.

Solution

We could create a modal that pops up when a user is on localhost where we can write messages to inform them. Possible solution is use window.location.hostname to check for localhost so that it is only displayed locally.

Alternatives

Additional Context

BUG: Incorrect Staticman redirect link for foreign languages

Bug Report

Describe the bug

After leaving a comment under a post in French, I received a 404 error. (screenshot below)

The wrong URL is

https://vincenttam.frama.io/fish-demo//fish-demo/fr/blog/creating-a-new-theme/

This is due to incorrect options[redirect].

hugo-future-imperfect-slim/layouts/post/staticman.html

Line 5 in d7988d4

<input type="hidden" name="options[redirect]" value="{{ .Site.BaseURL }}{{ .RelPermalink }}">

To Reproduce

1. Go to https://vincenttam.frama.io/fish-demo/fr/blog/creating-a-new-theme/.
2. Scroll down to the comment form.
3. Leave a comment.
4. Click on 'Submit'
5. See error.

Expected behavior

Redirection back to https://vincenttam.frama.io/fish-demo/fr/blog/creating-a-new-theme/.

Screenshots

Environment

• Hugo Version: [e.g. 0.55]
• Browser and Version: [e.g. Firefox]
• Platform: [e.g. Desktop]
• Link to Project: https://framagit.org/VincentTam/fish-demo

Additional context

Take the example in Hugo's doc about absLangURL as an example.

{{ .Site.baseURL }}        → "https://example.com/hugo/"
{{ "blog/" | absLangURL }} → "https://example.com/hugo/en/blog/"
{{ "blog/" | relLangURL }} → "/hugo/en/blog/"

From this, we can expect that {{ .Site.baseURL }} and {{ .RelPermalink }} don't work well together. Two moderators on Hugo forum advice users to find alternative solutions.

FEATURE: Add tags to this repo

Feature Request

Is your feature request related to a problem?

Show tags on the top of this repo, like https://github.com/onweru/hugo-swift-theme. This helps this theme is stand out by searching #staticman.

Country logo

I can see a country logo at the extreme top right of the main page? Any idea how to remove that or change that..

Also I am using disqus here -

Disqus comments not available by default when the website is previewed locally.
comments powered by Disqus

not sure why these issue?

Also, I added some pictures in .md which works fine in preview but when I load it onto website, it doesnt show there