nusserstudios / tailbliss Goto Github PK

View Code? Open in Web Editor NEW

286.0 6.0 131.0 62.33 MB

TailBliss is a Hugo Starter theme built on TailwindCSS 3, and Alpine.JS.

Home Page: https://tailbliss.netlify.app/

License: Apache License 2.0

CSS 63.56% JavaScript 3.55% HTML 32.89%

hacktoberfest alpinejs hugo hugo-theme tailwindcss-v3 tailwindcss hugo-blog-theme hugo-site image-processing

tailbliss's Introduction

TailBliss

TailBliss is an opinionated Hugo Starter with Tailwind CSS 3.2 and Alpine.js with light/dark modes.

View Demo · Report Bug · Request Feature · Ask Question

Install to VS Code with:
git clone [email protected]:nusserstudios/tailbliss your-name

Install with NPM

npm install

Install with Yarn

yarn

To start developing:

Develop with NPM

npm run start

Develop with Yarn

yarn start

To generate the site HTML:

Build with NPM

npm run build

Build with Yarn

yarn build

npm run start will run two commands parallel:
npx tailwindcss -i ./assets/css/main.css -o ./assets/css/style.css --watch

Has paginated Categories and Tags. Markdown files will automatically convert images put into /assets folder to .webp images.

Image shortcodes for webp as well.

Form

To use the form, visit FormSubmit.Co. Locate the contact form in "content/contact.md", and update the form action with the email address you want on this line: action="https://formsubmit.co/[email protected]" method="POST"

Credits

4044ever - Original Theme https://github.com/4044ever/Hugo-Tailwind-3.0.git

Jan Heise - Alpine.js Navbar https://github.com/jan-heise/responsive-navbar-with-dropdown

Made for Hacktoberfest, with ❤️ by NusserStudios.

tailbliss's People

Contributors

Stargazers

Watchers

Forkers

matahariramadhan vgangireddyin anishthanaseelan muksimdev ngeorger rexrowan inkan-tech progressicu louayshaat butlerc9 jakub3628800 sk-rama steven-ylee andrexandrex larry-lime ishtiakmokut dominicfung kyamitai emonmeena bulentevren steve-ross vinistoisr sinsinology andresf91 al4669 dismessy rentalges williamtaack hdralx moneyj0 zetogk dekker500 potatoqualitee mindtooth debrajmidya aloknathyadav2010 joshpinto6 fayazmiraz obicho ags4659 haubourg abeluis protocol-streams aionic anoduck invisibledevops elasticourse openadaptai ronibd0 antonychurch esokhransky mitchellurgero frankslin crazycth equilaterus pkbullock gabrieleciech joaoopereira pakeypay zettascalelabs polarisdhruv freedomlang tobyt99 prathamdupare samirparhi-dev priyankt68 okabrionz tellomnax furrykaraoke szymon-rd kamyar68 quentinglorieux alvyynm captainpacket bitapp-srl srigurubyo historyblogs sjbat kazox61 pascalwhoop-sv zalfypanini muhacus evenlangas hhsstudystuff ryan-pugh tzion0 liamsgreen galexrt tbe mggger 3nock sj1607 deining shzyxg weingartens whalito londi gauravjoshi1 alimohammad12314 ahmadilyas77

tailbliss's Issues

I tried it on windows with npm 6.14.8 and got below errors

`Start building sites …
hugo v0.121.1-00b46fed8e47f7bb0a85d7cfc2d9f1356379b740+extended windows/amd64 BuildDate=2023-12-08T08:47:45Z VendorInfo=gohugoio

Total in 5237 ms
Error: error building site: POSTCSS: failed to transform "css/style.css" (text/css): (node:7480) ExperimentalWarning: The ESM module loader is experimental.
internal/process/esm_loader.js:90
internalBinding('errors').triggerUncaughtException(
^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:730:11)
at Loader.resolve (internal/modules/esm/loader.js:100:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:246:28)
at ModuleWrap. (internal/modules/esm/module_job.js:47:40)
at link (internal/modules/esm/module_job.js:46:36) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: hugo --minify
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\wnadi\AppData\Roaming\npm-cache_logs\2023-12-30T14_19_53_576Z-debug.log
PS A:\wnadi\Documents\Local-Study\VScode-bucket\idealcloudconsulting-8\site\themes\tailbliss> `

On Cloudflare Pages only production branch works, but any other fails

Would you know what is happening here? On Cloudflare Pages only production branch works, but any other fails with this error.

error calling partial: "/opt/buildhome/repo/themes/tailbliss/layouts/partials/head.html:24:47"

<pre class="c_jh c_bu c_ik c_il c_nt c_nu c_de c_jv c_oz c_pa c_pb c_fo c_fp c_nv c_bw c_pc">

22:39:38.139 | Building sites … ERROR 2023/04/20 20:39:38 render of "page" failed: execute of template failed: template: _default/single.html:5:7: executing "_default/single.html" at <partial "head.html" ...>: error calling partial: "/opt/buildhome/repo/themes/tailbliss/layouts/partials/head.html:24:47": execute of template failed: template: partials/head.html:24:47: executing "partials/head.html" at <resources>: can't evaluate field PostProcess in type interface {}
-- | --
22:39:38.139 | ERROR 2023/04/20 20:39:38 render of "taxonomyTerm" failed: execute of template failed: template: _default/list.html:5:7: executing "_default/list.html" at <partial "head.html" ...>: error calling partial: "/opt/buildhome/repo/themes/tailbliss/layouts/partials/head.html:24:47": execute of template failed: template: partials/head.html:24:47: executing "partials/head.html" at <resources>: can't evaluate field PostProcess in type interface {}
22:39:38.139 | ERROR 2023/04/20 20:39:38 render of "home" failed: execute of template failed: template: index.html:5:7: executing "index.html" at <partial "head.html" ...>: error calling partial: "/opt/buildhome/repo/themes/tailbliss/layouts/partials/head.html:24:47": execute of template failed: template: partials/head.html:24:47: executing "partials/head.html" at <resources>: can't evaluate field PostProcess in type interface {}
22:39:38.164 | Total in 35 ms
22:39:38.164 | Error: Error building site: failed to render pages: render of "taxonomyTerm" failed: execute of template failed: template: _default/list.html:5:7: executing "_default/list.html" at <partial "head.html" ...>: error calling partial: "/opt/buildhome/repo/themes/tailbliss/layouts/partials/head.html:24:47": execute of template failed: template: partials/head.html:24:47: executing "partials/head.html" at <resources>: can't evaluate field PostProcess in type interface {}
22:39:38.172 | Failed: build command exited with code: 255
22:39:38.927 | Failed: error occurred while running build command

</pre>

new list arrangement

Hi, thank you for the beautiful theme. I have played around with it and hope to make some modifications. Here is the layout structure as I understand it (though there might be some mistakes):

I'm unsure about where the 'home-hero.html' layout is used. Additionally, I would like to add another kind of list layout ('list2.html'), where the posts will occupy the whole row, like this (in your nusserstudios website):

I've already created the layout myself, but I'm not sure how to implement it into this theme.
Could you kindly guide me on how to do so?
Thank you very much.

style.css line 3404

... has free roaming properties and is failing to build in dev when running 'npn run start' from a fresh repo.

Difficulty getting framework to properly render on development server from 0.0.0.0

I am developing my site on a remote server, so I need to be able to render the site on an address other than localhost. I have made the necessary changes to packages.json and added --bind 0.0.0.0 -b ./ --disableFastRender, yet still assets are referenced to localhost.

Is there a way to change this?

white menu on black theme

Could not resolve "alpinejs"

Hello!

Trying to get started with a new Hugo site here + tailbliss. When I run hugo server after setting up the submodule for the first time, I get the error:

 % hugo server
WARN 2023/01/20 10:22:14 Module "tailbliss" is not compatible with this Hugo version; run "hugo mod graph" for more information.
Start building sites …
hugo v0.110.0+extended darwin/arm64 BuildDate=unknown
Error: Error building site: JSBUILD: failed to transform "js/alpine.js" (text/javascript): "/Users/peterehrlich/projects/zpc-site/themes/tailbliss/assets/js/alpine.js:1:19": Could not resolve "alpinejs"
Built in 629 ms

I also hopped in the themes/tailbliss and ran the npm install / npm run build, but got the same errors.

I'm probably missing something a bit obvious here?

Thanks!

edit: npm install alpinejs seemed to fix this. Maybe it should be an explicit dependency somehow?

Move navigation into frontmatter.

markdown-it support

I have skimmed the about page to see how the typography and markdown parsing is done. At the end of the page there are some markdown-it plugins mentioned with a sample text to demonstrate how they work. It seems that only some of the examples work (might be only footnotes) and the rest is not.

Also the typographic replacements at the top of the page do not work.

I compared to the output of the markdown-it sample page at https://markdown-it.github.io/.

My questions are:

Is this a bug or missing feature? Or are markdown-it plugins generally not supported?
- If those plugins should be supported: Where to configure them? I'm not sure if this theme is using a specific markdown parser and how to change it accordingly.
- If those plugins aren't and won't be supported: The only possibility to extend the markdown functionality is to configure the hugo goldmark markup. Or am I missing something?

[BUG] baseURL Causing CSS Linking Errors

When baseURL is set, I found out that the CSS is not relatively linked, turns out by changing refPermalink with Permalink in layouts/partials/head.html will resolve the issue:

{{ $styles := resources.Get "/css/style.css" | postCSS }}
{{ if .Site.IsServer }}
<link rel="stylesheet" href="{{ $styles.Permalink }}" />
{{ else }}
{{ $styles := $styles | minify | fingerprint | resources.PostProcess }}
<link rel="stylesheet" href="{{ $styles.Permalink }}" integrity="{{ $styles.Data.Integrity }}" />
{{ end }}

How do you change colors?

I can't get my head around how to change colors.
I tried extending colors in tailwind.config.js with no luck.
Any help or link to the correct guide?
Thanks

Modular partials for sections.

Modularize homepage into reusable sections.

multilanguage support

of course, we can use a clone of the site with a different language, but I think the language support inside the theme is better

Dark text on dark background

On the demo I'm seeing dark text on dark background:

Failed to clone hugo-twcss-alpine

Is the hugo-twcss-alpine repo public?

git clone [email protected]:nusserstudios/hugo-twcss-alpine.git your-name
produces an error

Cloning into 'your-name'...
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

Same as
git clone https://github.com/nusserstudios/hugo-twcss-alpine
which produces

Cloning into 'hugo-twcss-alpine'...
remote: Repository not found.
fatal: repository 'https://github.com/nusserstudios/hugo-twcss-alpine/' not found

Am I missing something?

Can't build site nor launch server

I downloaded the repository to a folder to make a website using this theme. I installed the node modules using npm install at the root of the project then I made hugo server and I have this output :

It wasn't clear on the readme, but I saw I had to use npm run start to launch hugo server but I have this output :

My OS is Debian 11 Bullseye
I'm using Node version 14.21.2 as I had problems with POSTCSS using Node 10
My NPM is v6.14.17 maybe I should upgrade it but I didn't try.
Hugo version : hugo v0.110.0

Include non-theme content in build pipeline?

I found I had to add my non-theme html files to the build pipeline to get it working correctly:

# themes/tailbliss/tailwind.config.js
content: ['./layouts/**/*.html', './content/**/*.md', '../../layouts/**/*.html'],

as well as adding a blank tailwind.config.js in my root dir. This allowed me to switch from indigo to another color, and have the css file correctly rebuild with the watch command.

mysql issue

when i added a email processor to my project with the npm mysql package it throws a error when building.

Start building sites … 
hugo v0.108.0-a0d64a46e36dd2f503bfd5ba1a5807b900df231d+extended windows/amd64 BuildDate=2022-12-06T13:37:56Z VendorInfo=gohugoio
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "crypto"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "net"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "tls"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "url"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "crypto"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "stream"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "timers"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "fs"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "util"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "events"
ERROR 2022/12/13 13:45:40 js.Build failed: Could not resolve "buffer"
Error: Error building site: JSBUILD: failed to transform "js/email.js" (text/javascript): Could not resolve "buffer"
Total in 2392 ms```

Please ignore

Image processing

Hi Jeremy,

Thanks for such great responsive theme. I'm about to submit a PR of some minor issues I found as I developed with this theme.

I have some issues with image processing and paths. First, I noticed all images are pixelated and of lower quality in post content, featured image and even homepage p1,2,3.. etc images
Example

Take step 2 as example from the example. The original image in png format is 36kb
using imgc shortcode
{{< imgc src="gns3-platforms.png" alt="gns3-platforms" >}}
it produces webp version at 14.5kb but looks really bad.

native image code
![Stormtroopocat](/images/gns3-platforms.png "The Stormtroopocat")
uses the original png 36kb, best quality

native image code but using converted webp version using cloudconvert.com
![Stormtroopocat](/images/gns3-platforms.webp "The Stormtroopocat") optimized webp is sized 17kb, shows much higher quality than the imgc, and slightly lower quality than png but still acceptable

do you have any suggestions?

My second question is regarding paths, I'm using the release that has canonifyURLs: true, I have a hard time understanding how paths work with multiple image folders

take sample blog posts as an example,
authorimage: ../assets/images/global/author.webp WORKS
featured_image: /images/gns3.webp WORKS
both the featured image and authorimage are in assets folder, but they are referenced in two different ways
from post point of view at tailbliss/content/posts/x.md
how could tailbliss/assets/images be referenced this way? I would have expected something like ../../assets/images/gns3.webp

then on the other hand the native image tag would only look in tailbliss/static/ then reference the internal path
![Stormtroopocat](/images/gns3-platforms.png "The Stormtroopocat")
it also wouldn't support native image code for a file in the assets/images regardless

![Stormtroopocat](/assets/images/ova.jpg "The Stormtroopocat")
![Stormtroopocat](../assets/images/ova.jpg "The Stormtroopocat")
![Stormtroopocat](../../assets/images/ova.jpg "The Stormtroopocat")

Best,

Issues deploying on Netlify but everything works locally

I am getting these issues on Netlify:

3:55:19 PM: ERROR 2023/06/27 22:55:19 failed to render pages: render of home failed: /opt/build/repo/layouts/index.html:53:48: execute of template failed: template: index.html:53:48: executing main at <resources.Get>: error calling Get: dirs not supported resource types: &{0xc00136c990 0xc000d78640} 3:55:19 PM: Error: Error building site: JSBUILD: failed to transform js/alpine.js (text/javascript): /opt/build/repo/assets/js/alpine.js:1:19: Could not resolve jslibs/alpinejs/v3/alpinejs/dist/module.esm.js

But everything is ok locally.

Including the entire log here from Netlify.

Initializing - Passed

3:54:58 PM: build-image version: c11c0eb9939c949586b0f78302107908b668a11e (focal)
3:54:58 PM: buildbot version: 55489dea6ef0428412532c40d27c9bef94a7fd4a
3:54:58 PM: Fetching cached dependencies
3:54:58 PM: Failed to fetch cache, continuing with build
3:54:58 PM: Starting to prepare the repo for build
3:54:58 PM: No cached dependencies found. Cloning fresh repo
3:54:58 PM: git clone --filter=blob:none https://github.com/obicho/tailbliss-test
3:54:58 PM: Preparing Git Reference refs/heads/main
3:55:00 PM: Starting to install dependencies
3:55:00 PM: Python version set to 3.8
3:55:00 PM: Attempting Ruby version 2.7.2, read from environment
3:55:00 PM: Using Ruby version 2.7.2
3:55:01 PM: Started restoring cached go cache
3:55:01 PM: Finished restoring cached go cache
3:55:02 PM: go version go1.19.10 linux/amd64
3:55:03 PM: Using PHP version 8.0
3:55:03 PM: Installing Hugo 0.105.0
3:55:04 PM: hugo v0.105.0-0e3b42b4a9bdeb4d866210819fc6ddcf51582ffa+extended linux/amd64 BuildDate=2022-10-28T12:29:05Z VendorInfo=gohugoio
3:55:05 PM: Downloading and installing node v18.16.1...
3:55:05 PM: Downloading https://nodejs.org/dist/v18.16.1/node-v18.16.1-linux-x64.tar.xz...
3:55:05 PM: Computing checksum with sha256sum
3:55:05 PM: Checksums matched!
3:55:07 PM: Now using node v18.16.1 (npm v9.5.1)
3:55:07 PM: Enabling Node.js Corepack
3:55:07 PM: Started restoring cached build plugins
3:55:07 PM: Finished restoring cached build plugins
3:55:07 PM: Started restoring cached corepack dependencies
3:55:07 PM: Finished restoring cached corepack dependencies
3:55:07 PM: No npm workspaces detected
3:55:07 PM: Started restoring cached node modules
3:55:07 PM: Finished restoring cached node modules
3:55:08 PM: Installing npm packages using npm version 9.5.1
3:55:16 PM: added 145 packages, and audited 146 packages in 8s
3:55:16 PM: 31 packages are looking for funding
3:55:16 PM:   run `npm fund` for details
3:55:16 PM: found 0 vulnerabilities
3:55:16 PM: npm packages installed
3:55:16 PM: Install dependencies script success
3:55:16 PM: Starting build script
3:55:17 PM: Detected 0 framework(s)
3:55:17 PM: Section completed: initializing

Building - Failed

3:55:21 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
3:55:18 PM: Netlify Build                                                 
3:55:18 PM: ────────────────────────────────────────────────────────────────
3:55:18 PM: 
3:55:18 PM: ❯ Version
3:55:18 PM:   @netlify/build 29.12.1
3:55:18 PM: 
3:55:18 PM: ❯ Flags
3:55:18 PM:   baseRelDir: true
3:55:18 PM:   buildId: 649b68c0e81886008029f6f7
3:55:18 PM:   deployId: 649b68c0e81886008029f6f9
3:55:18 PM:   tracing:
3:55:18 PM:     enabled: 'false'
3:55:18 PM:     host: 10.65.159.57
3:55:18 PM:     parentSpanId: b08444aa644df82c
3:55:18 PM:     traceFlags: '01'
3:55:18 PM:     traceId: e7573e97bab37e1f0b3c87c7d830154b
3:55:18 PM: 
3:55:18 PM: ❯ Current directory
3:55:18 PM:   /opt/build/repo
3:55:18 PM: 
3:55:18 PM: ❯ Config file
3:55:18 PM:   /opt/build/repo/netlify.toml
3:55:18 PM: 
3:55:18 PM: ❯ Context
3:55:18 PM:   production
3:55:18 PM: 
3:55:18 PM: build.command from netlify.toml                               
3:55:18 PM: ────────────────────────────────────────────────────────────────
3:55:18 PM: 
3:55:18 PM: $ hugo --gc --minify
3:55:18 PM: Start building sites …
3:55:18 PM: hugo v0.105.0-0e3b42b4a9bdeb4d866210819fc6ddcf51582ffa+extended linux/amd64 BuildDate=2022-10-28T12:29:05Z VendorInfo=gohugoio
3:55:19 PM: ERROR 2023/06/27 22:55:19 failed to render pages: render of home failed: /opt/build/repo/layouts/index.html:53:48: execute of template failed: template: index.html:53:48: executing main at <resources.Get>: error calling Get: dirs not supported resource types: &{0xc00136c990 0xc000d78640}
3:55:19 PM: Error: Error building site: JSBUILD: failed to transform js/alpine.js (text/javascript): /opt/build/repo/assets/js/alpine.js:1:19: Could not resolve jslibs/alpinejs/v3/alpinejs/dist/module.esm.js
3:55:19 PM: Total in 1429 ms
3:55:19 PM: 
3:55:19 PM: build.command failed                                        
3:55:19 PM: ────────────────────────────────────────────────────────────────
3:55:19 PM: 
3:55:19 PM:   Error message
3:55:19 PM:   Command failed with exit code 255: hugo --gc --minify (https://ntl.fyi/exit-code-255)
3:55:19 PM: 
3:55:19 PM:   Error location
3:55:19 PM:   In build.command from netlify.toml:
3:55:19 PM:   hugo --gc --minify
3:55:19 PM: 
3:55:19 PM:   Resolved config
3:55:19 PM:   build:
3:55:19 PM:     command: hugo --gc --minify
3:55:19 PM:     commandOrigin: config
3:55:19 PM:     environment:
3:55:19 PM:       - HUGO_VERSION
3:55:19 PM:       - HUGO_ENV
3:55:19 PM:       - HUGO_ENABLEGITINFO
3:55:19 PM:     publish: /opt/build/repo/public
3:55:19 PM:     publishOrigin: config
3:55:19 PM:   redirects:
3:55:21 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
3:55:21 PM: Failing build: Failed to build site
3:55:21 PM: Finished processing build request in 23.762s

Can't access new HTML file created in the layouts folder

I created a new HTML static file info.html. I want it to be accessible at /info/
Here's the content of the file

{{ define "main" }}
<main>
    <header class="mb-4 bg-indigo-600">
        <span class="py-96">
            <h1 class="py-16 text-5xl font-black text-center text-white capitalize">
                Calculateur de 1 RM
            </h1>
        </span>
    </header>
    <div class="max-w-4xl mx-auto mt-8 mb-2">
        <div class="px-6">
            <label for="poids">Poids</label>
            <input name="poids" id="poids" type="number">
            <label for="repetitions"></label>
            <input name="repetitions" id="repetitions" type="number">
            <button id="calculer">Calculer</button>
        </div>
    </div>
    <!-- " {{.Content}}" pulls from the markdown content of the corresponding _index.md -->
    <div class="max-w-2xl px-6 pt-6 pb-16 mx-auto prose dark:prose-invert dark:text-white">
        {{.Content}}
    </div>
</main>
{{ end }}

But when I launch hugo server there's no new page generated

Layouts folder content :

I'm not using TailbLiss as a theme but it is the root of my hugo site.

If there is a way to make new HTML pages accessible right after the / let me know it would help me a lot, thanks.

module does not exist

i got this error when running hugo server with the tailbliss theme:

Error: command error: failed to load modules: module " github.com/gohugoio/hugo-mod-jslibs-dist/alpinejs/v3 " not found in "C:\\Users\\jesic\\work\\blog\\themes\\ github.com \\gohugoio\\hugo-mod-jslibs-dist\\alpinejs\\v3"; either add it as a Hugo Module or store it in "C:\\Users\\jesic\\work\\blog\\themes".: module does not exist

Steps to reproduce :

hugo new site blog
cd blog
git init
git submodule add [GitHub - nusserstudios/tailbliss: TailBliss is a Hugo Starter theme built on TailwindCSS 3, and Alpine.JS.](https://github.com/nusserstudios/tailbliss.git) themes/tailbliss
echo “theme = ‘tailbliss’” >> hugo.toml hugo server

Document how to utilize the contact me page

Super great theme! love it!

Could you possibly give a short sample of an easy way to utilize the contact me form with a given provider?

Documentation on images location

Can't figure out a proper images location.
We have:

images
assets/images
static/images
resources/_gen/images (ok, this one we can exclude)