hugo | The world ’ s fastest framework for building websites | Static Site Generator library

I managed to make it work again by removing RVM completely from my system using the commands in https://rvm.io/support/troubleshooting.

Your user .Rprofile file is loading itself recursively for some reason:

To use localization, you need to use the Hugo function time.Format (which has an alias dateFormat). It takes two parameters:

• desired format
• time.Time object, or timestamp

Example:

{{ time.Format "Jan. 2, 2006" .Date }}

or

{{ dateFormat "Jan. 2, 2006" .Date }}

Docs: https://gohugo.io/functions/dateformat/

The .Format method (e.g. {{.Date.Format "Jan. 2, 2006}}) will not apply the desired localization.

Looks like your yaml is malformed. Arrays should have a dash or hyphen for each item. Something like:

From hugo v0.91.0++ you can use resources.GetRemote

source : https://github.com/gohugoio/hugo/releases/tag/v0.91.0

example:

You should be able to get your products using the Shopify API. This endpoint could be the one for you. From Hugo, you can then retrieve the products by getJson function with dictating the Shopify authorization header X-Shopify-Access-Token. Like this:

See if this works....

Instead of using static_dir, try using static_files and have your handler like the example here. That example has (the sample below). See if you can modify it to suit your pattern

The original approach is explained in gohugoio/hugo PR 3815

Several attempts have been started to fix #98 -- all of them have failed for some reason.
It is a hard problem to solve, and I think the main reason for failure has been the bottom-up-approach, i.e. we have started with the hardest problem: Solving Sherlock's last case.

The reason I'm picking up this ball again now is this Twitter thread:

Using intersect and keywords in page params work reasonably well, but it is quadratic and will be slow to unusable for larger sites.

So, instead of solving the hardest problem, I have started on this PR by outlining an interface:

You have at least three options:

Use front matter to set the "type":

In content/get-started.md set type: mytype in front matter.

The layout will be located at (for example) layout/mytype/single.html.

Use front matter to set the "layout":

In content/get-started.md set layout: mylayout in front matter.

The layout will be located at (for example) layout/_default/mylayout.html

Or use a subdirectory, but make it the section index:

The file is located at content/get-started/_index.md

The layout will be located at (for example) layout/get-started/list.html

Notice that the template name has changed from "single" to "list", but you can still write your layout in exactly the same way.

I use "(for example)" because Hugo has an enormous list of directories/filenames it searches through to find its templates, and if an earlier matching template is found, the custom layout gets ignored.