-
Notifications
You must be signed in to change notification settings - Fork 833
Some fixes and features #523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
siddhpant
wants to merge
20
commits into
panr:master
Choose a base branch
from
siddhpant:upstream-master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The font version used is old. Let's use the latest version (6.2). Source: https://github.com/tonsky/FiraCode/releases/tag/6.2 Let's use WOFF2 versions as their sizes are smaller so website load can be faster. Signed-off-by: Siddh Raman Pant <[email protected]>
Seems to be erroneously added in c779a70, but that commit actually seems to "fix" the issue where a random "::" was in between when it was seemingly supposed to be one colon. But anyways, we don't need a colon as the context is clear by being in the bracket. Signed-off-by: Siddh Raman Pant <[email protected]>
…is set. In c779a70, we copied the rest of the stuff but not for the top conditional. Fix that up. Fixes: c779a70 ("Add configurable timestamping for posts (panr#494)") Signed-off-by: Siddh Raman Pant <[email protected]>
…horter. It is unnecessarily verbose. Signed-off-by: Siddh Raman Pant <[email protected]>
…instead of brackets. "<date> [Updated: <date>] :: ..." v/s "<date> :: Updated <date> :: ..." The latter seems to be more in line with the theme. Signed-off-by: Siddh Raman Pant <[email protected]>
…rent from post date. Signed-off-by: Siddh Raman Pant <[email protected]>
…letely. For example, an about page need not have a date since that isn't really a "blog post". To use this, add `hideDate: True` in the frontmatter. Signed-off-by: Siddh Raman Pant <[email protected]>
With this, one can set prefix for creation date from the config using "createdDatePrefix". In case it's not set, no prefix is set, which preserves the existing behaviour. Signed-off-by: Siddh Raman Pant <[email protected]>
So the logic is more clear. Signed-off-by: Siddh Raman Pant <[email protected]>
Signed-off-by: Siddh Raman Pant <[email protected]>
Allow using LaTeX by setting `latex: true` on the page. Signed-off-by: Siddh Raman Pant <[email protected]>
Adding custom parameters to the top level language configuration is deprecated. So after moving the parameters to languages.xx.params, Site.Title does not work as we define title under langauges. See https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120 Signed-off-by: Siddh Raman Pant <[email protected]>
Make it match the other titles + subtitle is meant to be showed. Signed-off-by: Siddh Raman Pant <[email protected]>
…able via partial. Let's allow overriding just the copyright section, as HTML in a string in the config file can get unwieldy very soon. It also allows linking to a custom credits page and license text. Signed-off-by: Siddh Raman Pant <[email protected]>
Copyrights belong to the author, not hugo. Signed-off-by: Siddh Raman Pant <[email protected]>
…ear. When content is from, say, 2020 for example, then the copyright line having "© 2025" is misleading. Let's allow making it "© 2020-2025" instead upon generation. Set CopyrightStartYear in site config to use this. Signed-off-by: Siddh Raman Pant <[email protected]>
It is the natural intuition for a user that crawlers like Google won't index pages linked by pages which are marked as noindex. But it turns out crawlers are snarky and will follow the links in a noindex page. We need to set nofollow too to stop that from happening. Signed-off-by: Siddh Raman Pant <[email protected]>
This improves SEO for the page. While at it, we add a new boolean config key "nsfw" which tells whether the website is nsfw or not. Signed-off-by: Siddh Raman Pant <[email protected]>
Signed-off-by: Siddh Raman Pant <[email protected]>
Signed-off-by: Siddh Raman Pant <[email protected]>
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started to use this theme but the development was stopped, so I made some changes in my fork to add some features and do some fixes.
Now that you are back, I would like to merge those changes. I pulled new master and redid my changes (and some new fixes) since the current master of the fork is based on the old one.
Please take a look at all the commits.