fix: handle relative non-root baseURL

[kusyka911]

What problem does this PR solve?

This PR solve issue with deploying site using relative non-root base URL.
Instruction to reproduce:

1. build website with relative non-root base url
   with config.toml

baseURL = '/kusyka/'

or with CLI options

hugo -b /kusyka/

3. Create deployment using local instillation of nginx (or you may use docker instead)
   Example nginx configuration /etc/nginx/nginx.conf:
   In this example we have default website in /usr/share/nginx/html/ and hugo website in /usr/share/nginx/kusyka/

http {
    include       mime.types;
    default_type  application/octet-stream;
    sendfile        on;
    keepalive_timeout  65;
    server {
            listen       80;
            server_name  localhost;

            location / {
                root   /usr/share/nginx/html;
                index  index.html index.htm;
            }
    
            location /kusyka {
                root /usr/share/nginx/;
                index  index.html index.htm;
                error_page  404 /kusyka/404.html;
            }
}

4. try to visit website (better using another device) by remote IP (check firewall configuration if needed)
5. Pay attention to the result

Solution

• fonts not loaded
  • head.html
    place built css file to root of the website and rename to style.css
  • _font.scss
    use root relative URL for fonts
• icons not loaded
  • regenerated icons with realfavicongenerator
  • move all icons to assets directory and load them as a resource in head.html using .RelPermalink
  • favicon.ico placed to site root after build (some browser may request it on root by default)
• make template for site.webmanifest and browserconfig.xml to fill them with all needed options
  • added more icons for windows tiles
  • added ability to customize some options using params.webmanifest and params.browserconfig

Is this PR adding a new feature?

no

Is this PR related to any issue or discussion?

no

PR Checklist

• I have verified that the code works as described/as intended.
• This change adds a social icon which has a permissive license to use it.
• This change does not include any external library/resources.
• This change does not include any unrelated scripts (e.g. bash and python scripts).
• I have enabled maintainer edits for this PR.

[netlify]

✅ Deploy Preview for hugo-blog-awesome ready!

Name	Link
🔨 Latest commit	8fe0007
🔍 Latest deploy log	https://app.netlify.com/sites/hugo-blog-awesome/deploys/64543911b049a90008beb23d
😎 Deploy Preview	https://deploy-preview-25--hugo-blog-awesome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[hugo-sid]

@kusyka911, this looks pretty exciting.

You are correct: this theme is not yet ready for non-root baseURL (or sub-folder baseURL). It is currently ready for root domain or sub-domain based URLs.

Looking forward to review this.

Thanks for your interest in contributing to this theme.

[kusyka911]

@hugo-sid I think there is possibility to make hugo template for site.webmanifest. I'll try to implement this solution.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so that we can review the pull request.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will soon review the pull request.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[kusyka911]

@hugo-sid updated, please review this. I think I covered all possible scenarios. At least for me everything works good.

[hugo-sid]

Thanks for the hard work @kusyka911.

I think I covered all possible scenarios. At least for me everything works good.

That's great.

If you feel, this PR is ready for review, could you please mark the PR as ready for review? Currently it's a draft PR.

[hugo-sid]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

You may ignore this warning, since you are addressing a single issue in this PR.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[kusyka911]

If you feel, this PR is ready for review, could you please mark the PR as ready for review? Currently it's a draft PR.

Done, also added docs.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[github-actions]

This PR exceeds the recommended size of 200 lines. Kindly ensure that you are NOT addressing multiple issues in one PR. We recommend you to create atomic PRs which focus on a single change.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[hugo-sid]

Thanks @kusyka911, for this new feature. I think this PR will fix #36.

Thanks for your willingness to improve this theme.

I appreciate your contribution.