09:48 <PaulFertser> borneoa_: hey :) I think the openocd website/blog will be updated in manual mode by me for now. The build machine can't run Pelican yet :/ If you think there's anything newsworthy, I can add a new post at any time.

10:54 <borneoa_> PaulFertser: could be fine. We don't have many news to publish, nor frequently. Anyway thanks for updating the site so quickly after the problem. I had a look at it and looks good.

12:11 <zapb__> PaulFertser, can you make a Git repo for the page?

12:12 <PaulFertser> zapb__: I already have made it, but it's local for now. What would be the plan you suggest?

12:12 <PaulFertser> zapb__: btw, are you probably into CSS? I have few minor things that annoy me but I have no idea how to properly fix them.

12:12 <zapb__> PaulFertser, I have some experience in CSS, maybe it's enough

12:13 <PaulFertser> zapb__: current way is that I run Pelican locally and then rsync it to htdocs on sf.net via ssh.

12:13 <PaulFertser> My plan was to make the build machine run Pelican but the OS there is too old.

12:13 <PaulFertser> And we need to upgrade anyway but that needs some timeslot allocated from ntfreak.

12:14 <zapb__> PaulFertser, would be nice to have a Git repo in Gerrit or somewhere else so that we don't have a single point of failure (your local Git) and people can write blog posts on their local machine

12:16 <PaulFertser> zapb__: so first thing about the current site: when I do not enable JS the "Open On-Chip Debugger" in bold font that's used on my Debian Chromium by default is wider than 800px (from class "body") and somehow chromium compresses the text so that Debug is put on top of "Open On-Chip". It should either overflow to the right or th block should get higher.

12:17 <PaulFertser> zapb__: of course it would be, and that was my plan. Currently I back up the whole git to sf.net server too (on a level higher than htdocs). I planned to add this repo to be hosted on Gerrit instance but since it can't be processed there yet probably it doesn't make much sense?

12:17 <zapb__> PaulFertser, the theme does not work properly for mobile at all

12:18 <PaulFertser> Your outstanding research should get announced on openocd.org too I think.

12:19 <PaulFertser> zapb__: I kinda already used to Pelican so would prefer to keep it as a system but changing a theme to something else entirely seems to be the next logical step if we care about how the website looks... I'm surprised Pelican offers such a buggy theme with plenty of hardcoded measurements by default :/

12:20 <zapb__> PaulFertser, when you open the page on a mobile device then the entire page is scaled down instead of moving the elements around

12:20 <zapb__> I never used Pelican but a "mobile-ready" theme would be very nice

12:21 <PaulFertser> zapb__: btw, another thing related to CSS: SF.net caches them for 24 hours so we can't see the updates immediately. But the caching works only if you request a compressed version, so it's confusing, you get old CSS in modern web-browsers but new CSS in wget/curl/w3m.

12:21 <zapb__> :D

12:23 <PaulFertser> zapb__: Pelican was my almost random choice, I just noticed that it's often mentioned as a Python static generator, plus people apparently were happy with how it imports wordpress XML, so I gave it a try (Debian stable ships version 4.x) and it worked nicely enough, and the docs were ok so.

12:25 <zapb__> PaulFertser, their own page has this "broken" theme too... :-/

12:25 <zapb__> But maybe a different theme does the job

12:29 <PaulFertser> zapb__: I think you can "git clone http://paulfertser.info/openocdblog" to try how it goes locally. For me it's just "apt install pelican; pelican contents/" and pointing a web browser to output/index.html

12:29 <zapb__> PaulFertser, okay thanks, Maybe I find some time to test different themes

12:30 <PaulFertser> zapb__: thank you