Hacker Newsnew | past | comments | ask | show | jobs | submit | wolframkriesing's commentslogin

Static site generators – sounds boring. But most aren’t, because they try to do everything and end up big and complex. PicoSSG is intentionally boring. It processes .md and .njk files, copies everything else as-is. Around 300 lines of plain JavaScript. Think of it as cp + markdown + nunjucks. That’s it. Boring!


I agree, when I saw the <style scoped> I also thought this would have been the coolest. But I guess there have been considerations and discussions about it. I just don't know where.


what do you mean by this? there is hardly any JS on the site. Any suggestions on how to improve it?


Yeah I'm sorry I was so blunt - I fell for the temptation to make a smart remark rather than being constructive. I found difficulty navigating because the page edits my browser history and I found I couldn't see much of the content of the page unless I figured out where to click. My preference is that when the core of a page is about presenting information it should just be there, I don't want to play a guessing game. Having said that, I'm not everyone and I may not be the audience for the page.


Thanks, I appreciate it. I would love to make this useful for more, which is definitely easier with feedback. And lovely feedback is just more fun to incorporate.

I had no idea I had broken the back button, I has just been in my tunnel. Thanks for discovering.


Get rid of the silent back-button capture.

Remove the buttons that show more content. (1) You're scrolling down anyway, which already limits the amount of content people can see and (2) most of the buttons don't show much additional content anyway.


What is the silent back-button capture? I am not aware I built this in.


oh, I hadn't tried that ... its the automatic hash update. ok, that's what you mean. true that's annoying. didn't try that, thanks


sorry if its annoying. I had put it there to not overwhelm with info right from the start. Seems not to work for some.


Some data about ES1, ES2, ES3, ... up to the latest.


Some ideas:

Either restructure the content chronologically (it's a chronicle, right?) or tell a story that's convincing enough to justify jumping back and forth between dates.

Also, add more details. For a chronicle it is very thin.


good to know. thanks for the feedback. it all started out as one chart and I thought I need to add some more data.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: