Documentation site for Hugo theme Toha.
hugo-toha / guides Goto Github PK
View Code? Open in Web Editor NEWDocumentation Hugo theme Toha. https://github.com/hossainemruz/toha.
Home Page: https://toha-guides.netlify.app/
License: MIT License
Documentation Hugo theme Toha. https://github.com/hossainemruz/toha.
Home Page: https://toha-guides.netlify.app/
License: MIT License
Documentation site for Hugo theme Toha.
Currently, one can integrate custom HTTP headers to Hugo site by adding the below code portion to netlify.toml file
[[headers]] for = "/*" [headers.values] X-Frame-Options = "DENY" X-XSS-Protection = "1; mode=block" X-Content-Type-Options = "nosniff" Content-Security-Policy = "" Referrer-Policy = "strict-origin-when-cross-origin" Strict-Transport-Security = "max-age=2592000" Permissions-Policy = ''' accelerometer=(none), ambient-light-sensor=(none), autoplay=(none), camera=(none), encrypted-media=(none), fullscreen=(none), geolocation=(none), gyroscope=(none), magnetometer=(none), microphone=(none), midi=(none), payment=(none), picture-in-picture=(none), speaker=(none), usb=(none), vibrate=(none), vr=(none)'''
Currently, I have kept the content-security-policy section blank because it can be different for particular sites based on their src of javascript files, image files, and style files.
I'm assuming you use this repo for validating changes to the theme repo. I understand I'm opening a lot of PRs which can take a lot of time to validate and test. A tool i've found very useful for validating changes is percy.io which will automatically take screenshots of all of the pages and do a visual diff as a github check which highlights visual screenshot differences between branches. This creates views like this for each PR that you can then approve to check visual diffs across viewports and browsers
If you wanted to set something similar up for this repo, I did so doing the following
For my site, this does generate 48 screenshots (each of my posts and home page across firefox and chrome across 2 viewports) which would give me ~100prs worth of screenshots per month. Since your site has many more posts, it would probably be good to restrict the number of pages it actually tests to be a more reasonable amount via https://docs.percy.io/docs/sdk-configuration#snapshot.
I also setup https://dependabot.com/submodules/ to automatically create PRs updating my submodule. This combined with percy + i use vercel to auto deploy all PR branches (which you use netlify but it does the same thing). These things combined make for some really nice automation around PR validation and consuming new theme changes (like this alex-bezek/blog#47 ).
I just thought i would share to see if you were interested.
On the guide https://toha-guides.netlify.app/posts/update-v3-to-v4/#6-update-the-configyaml-file there is an instruction:
you can check the sample config.yaml
that should be renamed to
you can check the sample hugo.yaml (previously config.yaml)
I'm not 100% sure about the parenthesis though, waiting for comments.
There are probably more references like this on other posts as well
You do not mention tags in your docs but they are pretty easy to add.
<ul id="tags-single">
<li>Tags:</li>
{{ range .Params.tags }}
<li><a href="/tags/{{ . | urlize }}">{{ . }}</a> </li>
{{ end }}
</ul>
and add
taxonomies:
tag: tags
to config.yaml
I could update the docs but figured I would ask first.
Thanks for all the work btw!
I do not see it in the docs and
https://toha-guides.netlify.app/posts/configuration/sections/about-section/
and
https://toha-guides.netlify.app/posts/
do not work
Hi @hossainemruz,
When you read the shortcodes page. We can see the different alert blocks available on the page. But there are no code examples associated with each block on the post.
This is not practical, the visitor is forced to go to the git repository to see the code examples.
For each alert block, put the associated shortcode directly on the post.
Note that this development is valid for the entire rest of the page.
Re @hossainemruz,
Suppose I want to start translating the guide into French. How should I go about it ?
Today, the content/posts
directory doesn't have an en
or fr
directory to differentiate articles from one language to another.
Should I conclude that it would be necessary to create a complete clone of the original repository and replace the English content with French content ? This would not be practical as someone wanted to offer a German or Spanish translation for example, there would be as many repositories of the guide as there are language ๐ค๐คจ.
Last question : If someone updates the original doc, how can I detect this and report the change to another language ?
Do you have an opinion ? Thank you by advance for your feedback.
Mermaid not woring in https://toha-guides.netlify.app/posts/writing-posts/mermaid/
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.