Replies: 4 comments 3 replies
-
|
Dear James, My thoughts on your questions:
Hope this helps. Antoine |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed reply! I actually think we have similar thoughts on this. I personally remove attribution when I use various themes too. However, I always post this information somewhere else as a way of thanking the original author. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't gotten anywhere with this yet, but I'm trying to rework the footer partial to implement an optional long version of the footer attribution for both Hugo and Congo (and then create an additional configuration parameter, to not only enable footer attribution, but to also choose between a short and long variant (short being the existing implementation). My desired long variant is like this: Powered by Hugo (0.101.0 extended) & Congo (2.3.0). Site last updated: Sat 25 Jun 2022 16.51:32 UTC (1656129060). I'd like to have the version info separately link to each project's changelogs so I can quickly get to them without having to go search for them (you will see 4 separate links in the above example). I'm trying to use In the event that the theme is (e.g., via Hugo Modules) is using a specific commit on the dev branch, then maybe the version info could be that specific, but it's not crucial. Moreover, either on the same line as the attribution, or a separate line below it, I will try to implement an optional "Site last built" timestamp, both with the UTC time, formatted per the site's configuration, as well as an optional UNIX timestamp.
Well, the only issue with that, for me, is that I try to eliminate all comments in production, so it would no longer be present, so the footer seems better for me personally. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for having the version numbers (maybe even behind a Personally:
Thinking about it more, for any other theme I would probably remove the attribution. I think I have left it in @jpanther because I really like this project, and admire your dedication, brilliance, and your support to the community, and want to help you in whatever small ways I can. |
Beta Was this translation helpful? Give feedback.
-
|
I like to have the attribution to your theme on the bottom of my website. It allowed me to create an amazing website very easily, and it makes it clear to an observant visitor they can easily do the same thing. If someone wants to remove it, they could modify the footer partial, right? I don't mind the mention of Hugo, but it might take some of the attention (about half) from Congo. I think the Congo attribution is more relevant, and the very first sentence of the GitHub README has the link to Hugo in it. I do think it would be better if the link led to a landing page in the docs that has similar content as the current README. I think it's better branding. I also use the link to go to the docs of the theme regularly, and GitHub makes that into a journey twice as many clicks long. |
Beta Was this translation helpful? Give feedback.
-
|
How about an option to pay/donate to remove attribution? I’ve done this with other themes. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion, however I have no intention to monetise the theme. Some people choose to sponsor me on GitHub as a way of saying thanks, and that's enough incentive to keep me working on new open source contributions. |
Beta Was this translation helpful? Give feedback.
-
One of the things that has started to become an issue is how Hugo and Congo are attributed in various places throughout the theme. As the theme author, I feel like there should be some attribution somewhere, but recognise that some people do not want this information so visible on every single page.
Like many themes, Hugo and Congo have always been attributed in the footer of the rendered page, and for some time this has been customisable using an i18n string that equates to "Powered by Hugo and Congo" with links to their respective pages. Prior to version 2.2, Hugo was also attributed in the HTML generator tag in the page
<head>.In version 2.2 this behaviour was adjusted to remove the generator tag from the HTML and this is now handled by the default Hugo logic. However, the question now remains how to best handle the attribution in the footer. Some people prefer to remove this altogether, while others want more customisation.
Since the very beginning, there has been an undocumented
attributionparameter that allows the text to be removed, however it is a blunt instrument in that the CSS doesn't layout the page taking this into account, and it is better customised using the i18n string. As more people dig into the code and discover this 'feature', it's becoming something that people want to be able to have finer control over. I have received many requests to tweak this behaviour but as everyone has a different requirement, it's increasingly difficult to find a clear way forward. My current intention is to remove this parameter altogether, however I would like to replace it with something more useful.Before making any further changes on this, I wanted to ask the community what your thoughts are on this topic in the hopes of coming to some sort of consensus on the best way to handle this.
The types of questions I'm trying to answer are:
disableHugoGeneratorInjectparameter?attributionparameter, or some other way?Related: #179, #191
Beta Was this translation helpful? Give feedback.
All reactions