local website rendering hindered by a partial in minimo theme (windows)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- hugo
- Domain
- build-system
Research direction
Start with README.md and inspect themes/minimo/layouts/partials/head/analytics.html, then check whether layouts/partials/head/analytics.html already exists in this repository. Run the local rendering procedure on Windows and verify that the missing _internal/google_analytics_async.html error is gone without modifying the minimo submodule.
Written by the indexing model from the issue text.
Description
While reviewing #359 , @damianooldoni noticed an issue with a file in head/partials while following the procedure to render the website locally (see README.md).
I needed to replace
{{ template "_internal/google_analytics_async.html" . }}inthemes/minimo/layouts/partials/head/analytics.htmlwith{{ template "_internal/google_analytics.html" . }}to solve [...]ERROR html/template:_partials/head/analytics.html:1:13: no such template "_internal/google_analytics_async.html"
Note that (as is good practice for hugo), instead of manipulating the minimo theme directly (which is a git submodule, i.e. a different repo), we should create or modify the layouts/partials/head/analytics.html in this repo.
It might be an option to simply remove the analytics partial.
- Dominant language
- HTML
- Stars
- 24
- Forks
- 10
- Avg merge
- 2d 32m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from inbo/tutorials
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
proposal tutorial
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
invalid question
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
🌈 enhancement design
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100