8 ms·

KDE.org migrated to Hugo

191 points by ognarb 6y ago

delgaudm 6y ago
Somewhat OT, but is the repeated use of "internalization" in the article instead of "internationalization" a common shortening of the term? I've seen i18n before, but it isn't really in my wheelhouse to know.
- timw4mail 6y ago
  More likely just a typo due to a similar looking shorter word.
- marcosdumay 6y ago
  Looks like an autocorrector failure. Internalization is an existing word with a completely different meaning and similar grammatical function... The kind of replacement autocorrectors do.
- ognarb 6y ago
  It's not a common shortening. I'm not a native English speaker and I made an error. I corrected it, thank you.
  - delgaudm 6y ago
    Ah, thank you. I've been learning about internationalization recently and wanted to make sure I understood the lingo. Much appreciated.
dhruvkar 6y ago
What are your thoughts on expanding hugo using Python? I have similar python scripts as the OP, that handle generation and pre-processing of markdown files which then get used by Hugo. It feels hacky and something extra to ship. Is there a way to extend Hugo or build add-ons to include custom functionality?
- ognarb 6y ago
  AFAIK there is no way to extends the Hugo with custom functionalities, like generating pages at run time. The only thing that is allowed is to add hooks when generating links, images and heading. I used it to generated link to the API documentation directly from the Doxygen tags files: https://invent.kde.org/documentation/develop-kde-org/-/blob/developement/layouts/docs/_markup/render-link.html https://invent.kde.org/documentation/develop-kde-org/-/blob/.... This is quite verbose but in the end it allows me to do things like this: `[Action](docs:kirigami2;Action)`. This is visible on develop.kde.org, the other big Hugo project in KDE.
DyslexicAtheist 6y ago
I used Hugo some years ago[1] and my memory of it was mostly negative in terms of usability. I revisited it again this year for another project and it drove me so mad that I ended up switching to Zola[2]. My issue with Hugo was that it just wasn't reliable with what was in the cache so I could never trust whether what I saw was actually the state of the site and causing me to push a broken state to the remote server. Hugo is great if it works but I found it a nightmare to deal with when it doesn't. There are countless options in Hugo (yes I understand it's powerful but I rather it just had half the option and they work as advertised), some of which at times are contradictory so searching for solutions took me ages. I have no affiliation with the zola project and am not even big on Rust. Zola just worked for me and seems a lot less "hacky" than hugo thanks to the Tera templating system. The Author of Zola writes on his github: > [hugo] personally drives me insane, to the point of writing my own template engine and static site generator. a sentiment that I share very much. [1] https://web.archive.org/web/20180714043311/https://iotdarwinaward.com/post/improve-your-privacy-in-age-of-mass-surveillance/ https://web.archive.org/web/20180714043311/https://iotdarwin... [2] https://github.com/getzola/zola https://github.com/getzola/zola [3] https://github.com/getzola/after-dark https://github.com/getzola/after-dark
- notsureaboutpg 6y ago
  >it just wasn't reliable with what was in the cache so I could never trust whether what I saw was actually the state of the site and causing me to push a broken state to the remote server Can you explain this a bit further? Why would what is/isn't in the cache cause issues? I must be missing something here. I have used Hugo before but not sure what this means exactly.
- lwhsiao 6y ago
  Similar story for me. Another point I find challenging with Hugo is that they very frequently release breaking changes. I want to upgrade because of features or speed, but there are only a few patches per version before there are also breaking changes. These happen so frequently it's hard to keep up. Zola is less powerful, but does the job and feels much more stable.
  - 6y ago
adoxyz 6y ago
Huge fan of Hugo here. My personal site (https://ado.xyz https://ado.xyz) runs on Hugo and I've deployed a number of others. For purely static sites, there is nothing better than Hugo imo. Next.js comes in at a close second, and is really handy when you need more than just a static site, but man I can't say enough good things about Hugo.
gitweb 6y ago
Hugo is amazing and I hope that it gets a huge amount of contributors to help improve it—but I wish they would take a couple development cycles to focus on basic functionality like SSL support in the server (for testing PWAs locally on your network), adding a tidy function (has a minify, why not tidy?), and building logic to use directories and files as titles automatically (as well as fixing the weird _index.md requirement) for nested directories.
- buovjaga 6y ago
  There is a draft PR for tidying: https://github.com/gohugoio/hugo/pull/7825 https://github.com/gohugoio/hugo/pull/7825
  - gitweb 6y ago
    Thank you for sharing that, I wasn't aware that it was being worked on finally. Looking forward to this one very much. Hopefully SSL support in the server will be next since it is the easiest to implement, then I hope the nested directories thing is resolved. That would make Hugo much more powerful.
AnonHP 6y ago
If the author is here, could you please link to kde.org in the post? I read this post and had to type it on the browser address bar to check it out. Also, has the entire kde.org website migrated to Hugo or is it only the Announcements section? The RSS feed linked in the post is for the announcements section alone. More clarity on this in this blog post would be good.
- ognarb 6y ago
  Thanks, I now added a direct link to kde.org in the blog post and I also added a link to the Capacity framework that was used previously. The entire kde.org website migrated to Hugo. Previously only a very small part was using it (< 10 pages) and this was quite helpful to test if everything worked before porting the rest of the website.
kalimatas 6y ago
> KDE.org now uses the Hugo. But in the footer there is "Powered by Jekyll with Type Theme". Hm...
- thrownaway954 6y ago
  The article site is powered by Jekyll. The actual KDE.org site is Hugo
- jmondi 6y ago
  The website of the blog post describing kde.org has the "Powered by Jekyll..." footer. The actual kde.org website that the blog post is talking about, does not.
- johannes1234321 6y ago
  See this comment: https://news.ycombinator.com/item?id=24945745 https://news.ycombinator.com/item?id=24945745
clircle 6y ago
I'm a blogdown user that doesn't know a lick about html or css. I love hugo!
yboris 6y ago
When deciding a few months ago to update my Video Hub App website from hand-edited static template I used I wanted to find a good approach. I needed i18n (internationalization) with unique per-language routes (as is described in this article). I tested Hugo but ended up going with Gatsby. I'm happy with the result - adding a new language now is just adding another .json file. public: https://videohubapp.com/en/ https://videohubapp.com/en/ GitHub: https://github.com/whyboris/video-hub-app-gatsby-website https://github.com/whyboris/video-hub-app-gatsby-website
gouggoug 6y ago
I've used Hugo for my very small, rarely updated, personal blog, and I really like it. Not sure how it works for larger scale websites. Now, I'm surprised Markdown is often chosen over Asciidoc. Especially for larger website like KDE.org; it seems you'd want to use a markup language that is more standardized than MD.
qwerty456127 6y ago
> A french, ukrainian, catalan, Dutch, and a few more languages are already available. Why is it only Dutch which is capitalized? I'm genuinely curious (my English is not perfect, perhaps there is a rule behind this I don't know).
- nerdponx 6y ago
  In American English, all of those should be capitalized. I assume this was just an editing error.
manofmanysmiles 6y ago
Definitely a bit off topic, so feel free to vote me into oblivion. Does anyone else get an almost visceral feeling of disgust most applications (or even words) that use K instead of C, or add a K just to fit the KDE motif? I really want to like KDE, but there is something stylistic about it that drives me up the wall. I'm asking not to insult anyone, but to see if anyone has an explanation of why I react this way. Maybe it will remain an unexplained idiosyncrasy.
- pkaye 6y ago
  Do you feel the same when Apple named everything with an "i" like iPod, iTunes, iPhone, iBook, iMac, etc?
  - manofmanysmiles 6y ago
    No, the K bothers me more. The G in GNU projects bothers me a bit.
    - cycomanic 6y ago
      I guess you're not German then ;). The k looks very normal to me, but that's because many of the words spelled with c in english are spelled with k in German. I suspect this is also where it comes from (KDE originated in Germany IIRC)
- jfax 6y ago
  I agree with this, including GNU software that starts with "g". Actually to bringing this kinda into topic, Hugo itself is named (albeit, subtly) by the fact that it uses Go. I'm reminded of Rob Pike's polite reminder: https://twitter.com/rob_pike/status/618357610287226880 https://twitter.com/rob_pike/status/618357610287226880
- sho_hn 6y ago
  Note this is mostly a historic concern. KDE largely stopped doggedly naming new projects K-something over a decade ago. Yes, there's examples to the contrary, and of course there are major projects sensibly sticking by their already-established brands, but plenty of core projects don't follow this scheme anymore (obviously Plasma, for one). It's largely a relic of a time before interoperability-enabling standardization via freedesktop.org specs, when "k = will work well with your desktop" had much more utility to users. The Gnome crowd did the more or less the same thing with g, and also stopped. As others mentioned, plenty of other tech orgs have pulled branding moves like this, be it iSomething or "My Foo", and arguably those provided less actual utility. I would argue this should affect the relative levels of irksomeness. :-)
nikodunk 6y ago
Funny, just spent this morning working on a Hugo project for the first time in a while, because I just discovered https://netlifycms.org https://netlifycms.org. I love Hugo and how fast it generates my business site (https://sunboxlabs.com https://sunboxlabs.com), but having just hired a first (non-technical) writer I had a classic dilemma: either teach them the Hugo command line/markdown or switch to something like Forestry/ButterCMS/Wordpress for a non-technical CMS. Then I found https://NetlifyCMS.org https://NetlifyCMS.org: You just add an /static/admin/ folder with two files in it and BOOM: non-technical users can create and edit posts with a Wordpress like dashboard (saves as Markdown to Git still). Strongly recommended.
- seanwilson 6y ago
  What's your workflow for letting your writer preview the generated styled pages?
  - nikodunk 6y ago
    Great question. We basically set every article as a draft, and because they can write in WYSIWIG writer now (no markdown) and the netlifycms admin dashboard allows them to see a fully-rendered preview that gets us 80% of the way. At that point (once we've checked the links and typos, etc) we flip the draft boolean to false and check the article looks as expected on production. Not perfect – we'd probably have a staging server if we were bigger – but we're still small :)
    - seanwilson 6y ago
      Thanks, I was just thinking about how this works vs something like WordPress where you can preview how the actual edited page will look before you publish. Netlify CMS lets you view the Markdown, but the non-tech editor would have to understand there's a build delay to the page going live and the final page might need reviewing. Nothing's perfect though, I just find most static site stories don't address the above so any thoughts are appreciated!
      - 6y ago
seanwilson 6y ago
Coincidentally, I just converted a small personal site from Hugo to Jekyll (a custom home page and a handful of blog posts). Took about 3 hours to make the full transition. Build times went from 10 seconds to 0.2s. I don't love the template language but once we've coded blog post pagination, head tags, image optimisation etc. it's rare you need much more. The speed up feels amazing when you're developing, I love that it's a single binary as you know it'll build without issues when you return to it in a few months, and it has enough built in (Sass, minifying, JavaScript bundler, image optimisation) that you just focus on site content rather than procrastinating with your build chain.
- shazow 6y ago
  > I just converted a small personal site from Hugo to Jekyll Did you mean "from Jekyll to Hugo" instead?
  - seanwilson 6y ago
    Yep! Doh.
louib 6y ago
> There is also now an RSS feed with all the latest announcements. Good to see RSS is still being added to websites in 2020!
- ognarb 6y ago
  KDE loves RSS, we have 2 RSS readers, a Qt library for parsing RSS feed and a Planet (planet.kde.org) with a lot of post each week. Planet build with Jekyll.
mraza007 6y ago
Why not use vuepress? I love its search Feature
rurban 6y ago
Which of the hundreds of kde.org websites exactly? The ones I inspected from https://invent.kde.org/websites https://invent.kde.org/websites had something else. Ah, found it. This one: https://invent.kde.org/websites/kde-org https://invent.kde.org/websites/kde-org
donaldihunter 6y ago
I use Hugo + org-mode for my blog. It’s native org rendering is very good and works well for posts with inline code using org-babel. I agree with what others have said that Hugo can be a pain to configure. My experience is that it’s dependent on the quality of the site template you start with.
arminiusreturns 6y ago
For those fighting with this and similar frameworks, you might consider simplifying with post-commit/recieve hooks, which is how I deploy some websites.
- tomcam 6y ago
  Can you explain a bit further please?
  - arminiusreturns 6y ago
    So, git hooks are basically executable scripts (of whatever language you have available, I use bash) placed in the .git/hooks dir, whcih are then executed at whichever event is designated (by the name of the script itself) For me, it's post-recieve. After initial setup, a push automatically triggers the post-recieve hook that does something like the following from my git dir: GIT_WORK_TREE=..../example.com git checkout -f and voila, pushes are insta-live, but commits can be pulled and worked on in the meantime. Learned from a few sources (shout out to Dreamhost for my original intro to this idea), but here are some relevant readings: https://www.ibm.com/developerworks/library/wa-git/ https://www.ibm.com/developerworks/library/wa-git/ https://opensource.com/life/16/8/how-construct-your-own-git-server-part-6 https://opensource.com/life/16/8/how-construct-your-own-git-...
    - tomcam 6y ago
      That was very helpful. Thank you.
syl_sau 6y ago
A few years ago, I made the switch from Jekyll to Hugo for various sites I've been developing. It was the best decision I ever made for that side web-dev career I'm entertaining. Jekyll, to me, is a DIY tool; it's clunky and obscure and you only make it happen with your pliers and your hammer -- you can achieve nice little projects quite fast, but once you go for a more elaborate structure your work starts falling apart. Hugo is more like a construction company with very-well organized architects. Its logic is relentless, yet it is an incredible powerful tool once you master it -- and honestly the video tutorials by Mike Dane and documentation at gohugo.io are really well-made and if you're switching to Hugo, you should dedicate one day to watch the courses and RTFM. The quality of the template from which you start might indeed be very determining of future success/frustration. Just don't rush it, you'll get there.
wink 6y ago
Whoever you are that feels responsible, please add a note to the repo which hugo version you've used (or are currently using for the official build) or this might bite you a few years (months?) down the line, it has happened for most people I know who have used hugo. We like it, but there breaking changes from time to time - especially if you only have a small team building the site, I was using a 4y old version until I did an upgrade in one go.

191 points by ognarb 6y ago

Somewhat OT, but is the repeated use of "internalization" in the article instead of "internationalization" a common shortening of the term? I've seen i18n before, but it isn't really in my wheelhouse to know.

timw4mail 6y ago
More likely just a typo due to a similar looking shorter word.
marcosdumay 6y ago
Looks like an autocorrector failure. Internalization is an existing word with a completely different meaning and similar grammatical function... The kind of replacement autocorrectors do.
ognarb 6y ago
It's not a common shortening. I'm not a native English speaker and I made an error. I corrected it, thank you.
- delgaudm 6y ago
  Ah, thank you. I've been learning about internationalization recently and wanted to make sure I understood the lingo. Much appreciated.

dhruvkar 6y ago

What are your thoughts on expanding hugo using Python? I have similar python scripts as the OP, that handle generation and pre-processing of markdown files which then get used by Hugo. It feels hacky and something extra to ship. Is there a way to extend Hugo or build add-ons to include custom functionality?

ognarb 6y ago
AFAIK there is no way to extends the Hugo with custom functionalities, like generating pages at run time. The only thing that is allowed is to add hooks when generating links, images and heading. I used it to generated link to the API documentation directly from the Doxygen tags files: https://invent.kde.org/documentation/develop-kde-org/-/blob/developement/layouts/docs/_markup/render-link.html https://invent.kde.org/documentation/develop-kde-org/-/blob/.... This is quite verbose but in the end it allows me to do things like this: `[Action](docs:kirigami2;Action)`. This is visible on develop.kde.org, the other big Hugo project in KDE.

DyslexicAtheist 6y ago

I used Hugo some years ago[1] and my memory of it was mostly negative in terms of usability. I revisited it again this year for another project and it drove me so mad that I ended up switching to Zola[2]. My issue with Hugo was that it just wasn't reliable with what was in the cache so I could never trust whether what I saw was actually the state of the site and causing me to push a broken state to the remote server. Hugo is great if it works but I found it a nightmare to deal with when it doesn't. There are countless options in Hugo (yes I understand it's powerful but I rather it just had half the option and they work as advertised), some of which at times are contradictory so searching for solutions took me ages. I have no affiliation with the zola project and am not even big on Rust. Zola just worked for me and seems a lot less "hacky" than hugo thanks to the Tera templating system. The Author of Zola writes on his github: > [hugo] personally drives me insane, to the point of writing my own template engine and static site generator. a sentiment that I share very much. [1] https://web.archive.org/web/20180714043311/https://iotdarwinaward.com/post/improve-your-privacy-in-age-of-mass-surveillance/ https://web.archive.org/web/20180714043311/https://iotdarwin... [2] https://github.com/getzola/zola https://github.com/getzola/zola [3] https://github.com/getzola/after-dark https://github.com/getzola/after-dark

notsureaboutpg 6y ago
>it just wasn't reliable with what was in the cache so I could never trust whether what I saw was actually the state of the site and causing me to push a broken state to the remote server Can you explain this a bit further? Why would what is/isn't in the cache cause issues? I must be missing something here. I have used Hugo before but not sure what this means exactly.
lwhsiao 6y ago
Similar story for me. Another point I find challenging with Hugo is that they very frequently release breaking changes. I want to upgrade because of features or speed, but there are only a few patches per version before there are also breaking changes. These happen so frequently it's hard to keep up. Zola is less powerful, but does the job and feels much more stable.
- 6y ago

adoxyz 6y ago

Huge fan of Hugo here. My personal site (https://ado.xyz https://ado.xyz) runs on Hugo and I've deployed a number of others. For purely static sites, there is nothing better than Hugo imo. Next.js comes in at a close second, and is really handy when you need more than just a static site, but man I can't say enough good things about Hugo.

gitweb 6y ago

Hugo is amazing and I hope that it gets a huge amount of contributors to help improve it—but I wish they would take a couple development cycles to focus on basic functionality like SSL support in the server (for testing PWAs locally on your network), adding a tidy function (has a minify, why not tidy?), and building logic to use directories and files as titles automatically (as well as fixing the weird _index.md requirement) for nested directories.

buovjaga 6y ago
There is a draft PR for tidying: https://github.com/gohugoio/hugo/pull/7825 https://github.com/gohugoio/hugo/pull/7825
- gitweb 6y ago
  Thank you for sharing that, I wasn't aware that it was being worked on finally. Looking forward to this one very much. Hopefully SSL support in the server will be next since it is the easiest to implement, then I hope the nested directories thing is resolved. That would make Hugo much more powerful.

AnonHP 6y ago

If the author is here, could you please link to kde.org in the post? I read this post and had to type it on the browser address bar to check it out. Also, has the entire kde.org website migrated to Hugo or is it only the Announcements section? The RSS feed linked in the post is for the announcements section alone. More clarity on this in this blog post would be good.

ognarb 6y ago
Thanks, I now added a direct link to kde.org in the blog post and I also added a link to the Capacity framework that was used previously. The entire kde.org website migrated to Hugo. Previously only a very small part was using it (< 10 pages) and this was quite helpful to test if everything worked before porting the rest of the website.

kalimatas 6y ago

> KDE.org now uses the Hugo. But in the footer there is "Powered by Jekyll with Type Theme". Hm...

thrownaway954 6y ago
The article site is powered by Jekyll. The actual KDE.org site is Hugo
jmondi 6y ago
The website of the blog post describing kde.org has the "Powered by Jekyll..." footer. The actual kde.org website that the blog post is talking about, does not.
johannes1234321 6y ago
See this comment: https://news.ycombinator.com/item?id=24945745 https://news.ycombinator.com/item?id=24945745

clircle 6y ago

I'm a blogdown user that doesn't know a lick about html or css. I love hugo!

yboris 6y ago

When deciding a few months ago to update my Video Hub App website from hand-edited static template I used I wanted to find a good approach. I needed i18n (internationalization) with unique per-language routes (as is described in this article). I tested Hugo but ended up going with Gatsby. I'm happy with the result - adding a new language now is just adding another .json file. public: https://videohubapp.com/en/ https://videohubapp.com/en/ GitHub: https://github.com/whyboris/video-hub-app-gatsby-website https://github.com/whyboris/video-hub-app-gatsby-website

gouggoug 6y ago

I've used Hugo for my very small, rarely updated, personal blog, and I really like it. Not sure how it works for larger scale websites. Now, I'm surprised Markdown is often chosen over Asciidoc. Especially for larger website like KDE.org; it seems you'd want to use a markup language that is more standardized than MD.

qwerty456127 6y ago

> A french, ukrainian, catalan, Dutch, and a few more languages are already available. Why is it only Dutch which is capitalized? I'm genuinely curious (my English is not perfect, perhaps there is a rule behind this I don't know).

nerdponx 6y ago
In American English, all of those should be capitalized. I assume this was just an editing error.

manofmanysmiles 6y ago

Definitely a bit off topic, so feel free to vote me into oblivion. Does anyone else get an almost visceral feeling of disgust most applications (or even words) that use K instead of C, or add a K just to fit the KDE motif? I really want to like KDE, but there is something stylistic about it that drives me up the wall. I'm asking not to insult anyone, but to see if anyone has an explanation of why I react this way. Maybe it will remain an unexplained idiosyncrasy.

pkaye 6y ago
Do you feel the same when Apple named everything with an "i" like iPod, iTunes, iPhone, iBook, iMac, etc?
- manofmanysmiles 6y ago
  No, the K bothers me more. The G in GNU projects bothers me a bit.
  - cycomanic 6y ago
    I guess you're not German then ;). The k looks very normal to me, but that's because many of the words spelled with c in english are spelled with k in German. I suspect this is also where it comes from (KDE originated in Germany IIRC)
jfax 6y ago
I agree with this, including GNU software that starts with "g". Actually to bringing this kinda into topic, Hugo itself is named (albeit, subtly) by the fact that it uses Go. I'm reminded of Rob Pike's polite reminder: https://twitter.com/rob_pike/status/618357610287226880 https://twitter.com/rob_pike/status/618357610287226880
sho_hn 6y ago
Note this is mostly a historic concern. KDE largely stopped doggedly naming new projects K-something over a decade ago. Yes, there's examples to the contrary, and of course there are major projects sensibly sticking by their already-established brands, but plenty of core projects don't follow this scheme anymore (obviously Plasma, for one). It's largely a relic of a time before interoperability-enabling standardization via freedesktop.org specs, when "k = will work well with your desktop" had much more utility to users. The Gnome crowd did the more or less the same thing with g, and also stopped. As others mentioned, plenty of other tech orgs have pulled branding moves like this, be it iSomething or "My Foo", and arguably those provided less actual utility. I would argue this should affect the relative levels of irksomeness. :-)

nikodunk 6y ago

Funny, just spent this morning working on a Hugo project for the first time in a while, because I just discovered https://netlifycms.org https://netlifycms.org. I love Hugo and how fast it generates my business site (https://sunboxlabs.com https://sunboxlabs.com), but having just hired a first (non-technical) writer I had a classic dilemma: either teach them the Hugo command line/markdown or switch to something like Forestry/ButterCMS/Wordpress for a non-technical CMS. Then I found https://NetlifyCMS.org https://NetlifyCMS.org: You just add an /static/admin/ folder with two files in it and BOOM: non-technical users can create and edit posts with a Wordpress like dashboard (saves as Markdown to Git still). Strongly recommended.

seanwilson 6y ago
What's your workflow for letting your writer preview the generated styled pages?
- nikodunk 6y ago
  Great question. We basically set every article as a draft, and because they can write in WYSIWIG writer now (no markdown) and the netlifycms admin dashboard allows them to see a fully-rendered preview that gets us 80% of the way. At that point (once we've checked the links and typos, etc) we flip the draft boolean to false and check the article looks as expected on production. Not perfect – we'd probably have a staging server if we were bigger – but we're still small :)
  - seanwilson 6y ago
    Thanks, I was just thinking about how this works vs something like WordPress where you can preview how the actual edited page will look before you publish. Netlify CMS lets you view the Markdown, but the non-tech editor would have to understand there's a build delay to the page going live and the final page might need reviewing. Nothing's perfect though, I just find most static site stories don't address the above so any thoughts are appreciated!
    - 6y ago

seanwilson 6y ago

Coincidentally, I just converted a small personal site from Hugo to Jekyll (a custom home page and a handful of blog posts). Took about 3 hours to make the full transition. Build times went from 10 seconds to 0.2s. I don't love the template language but once we've coded blog post pagination, head tags, image optimisation etc. it's rare you need much more. The speed up feels amazing when you're developing, I love that it's a single binary as you know it'll build without issues when you return to it in a few months, and it has enough built in (Sass, minifying, JavaScript bundler, image optimisation) that you just focus on site content rather than procrastinating with your build chain.

shazow 6y ago
> I just converted a small personal site from Hugo to Jekyll Did you mean "from Jekyll to Hugo" instead?
- seanwilson 6y ago
  Yep! Doh.

louib 6y ago

> There is also now an RSS feed with all the latest announcements. Good to see RSS is still being added to websites in 2020!

ognarb 6y ago
KDE loves RSS, we have 2 RSS readers, a Qt library for parsing RSS feed and a Planet (planet.kde.org) with a lot of post each week. Planet build with Jekyll.

mraza007 6y ago

Why not use vuepress? I love its search Feature

rurban 6y ago

Which of the hundreds of kde.org websites exactly? The ones I inspected from https://invent.kde.org/websites https://invent.kde.org/websites had something else. Ah, found it. This one: https://invent.kde.org/websites/kde-org https://invent.kde.org/websites/kde-org

donaldihunter 6y ago

I use Hugo + org-mode for my blog. It’s native org rendering is very good and works well for posts with inline code using org-babel. I agree with what others have said that Hugo can be a pain to configure. My experience is that it’s dependent on the quality of the site template you start with.

arminiusreturns 6y ago

For those fighting with this and similar frameworks, you might consider simplifying with post-commit/recieve hooks, which is how I deploy some websites.

tomcam 6y ago
Can you explain a bit further please?
- arminiusreturns 6y ago
  So, git hooks are basically executable scripts (of whatever language you have available, I use bash) placed in the .git/hooks dir, whcih are then executed at whichever event is designated (by the name of the script itself) For me, it's post-recieve. After initial setup, a push automatically triggers the post-recieve hook that does something like the following from my git dir: GIT_WORK_TREE=..../example.com git checkout -f and voila, pushes are insta-live, but commits can be pulled and worked on in the meantime. Learned from a few sources (shout out to Dreamhost for my original intro to this idea), but here are some relevant readings: https://www.ibm.com/developerworks/library/wa-git/ https://www.ibm.com/developerworks/library/wa-git/ https://opensource.com/life/16/8/how-construct-your-own-git-server-part-6 https://opensource.com/life/16/8/how-construct-your-own-git-...
  - tomcam 6y ago
    That was very helpful. Thank you.

syl_sau 6y ago

A few years ago, I made the switch from Jekyll to Hugo for various sites I've been developing. It was the best decision I ever made for that side web-dev career I'm entertaining. Jekyll, to me, is a DIY tool; it's clunky and obscure and you only make it happen with your pliers and your hammer -- you can achieve nice little projects quite fast, but once you go for a more elaborate structure your work starts falling apart. Hugo is more like a construction company with very-well organized architects. Its logic is relentless, yet it is an incredible powerful tool once you master it -- and honestly the video tutorials by Mike Dane and documentation at gohugo.io are really well-made and if you're switching to Hugo, you should dedicate one day to watch the courses and RTFM. The quality of the template from which you start might indeed be very determining of future success/frustration. Just don't rush it, you'll get there.

wink 6y ago

Whoever you are that feels responsible, please add a note to the repo which hugo version you've used (or are currently using for the official build) or this might bite you a few years (months?) down the line, it has happened for most people I know who have used hugo. We like it, but there breaking changes from time to time - especially if you only have a small team building the site, I was using a 4y old version until I did an upgrade in one go.