Ask HN: What are the *dynamic* needs for a static site these days? Static sites are getting more popular by the day. What are the dynamic needs of a site that are holding you back from using a static site generator? Things like comments, search are covered by tools like disqus and algolia. I'd love to see some examples. |
1. A content suggestion tool where based off of the current content and past content you'd build an interest profile so you can populate suggestion widgets on the page, while also not recommending articles they have already read before.
2. A user option to hide read content. When they read content, the link will be hidden from the site so they don't waste time sorting through old content to get to new content. I was planning on pairing this with the option to hide a story that's not of interest for the same reasons. All these articles can be viewed again either by turning off this option(provided the developers integrate it) or by viewing a page with all the content that has been hidden(or however the site developers integrate the api to access hidden content).
3. A favorites/history tool for users on a site. What I had in mind is being able to allow users to favorite content and this will be saved and accessible by the site developers through API to integrate, such as the obvious favorite's page.
Had a few others but don't remember off the top of my head.
I had some interest but acquired no regular users. Email me if you'd like more info, I'll not promote it here.
Most of my sites are served from my solar-powered RPi2 with boring old Apache 2.2 and various site checkers plaster them with As for technical performance. Very little need for JS. You may of course not like my content, but for me for those sites the answer to your question is "none".
You should see the rant about AMP, trending on the HN front page, to see an example of why more JS is not more bettererorz UX... B^>
Declaratory and static for me, where possible.
Having time/date wrong on your device - particularly a phone, which a lot of people use instead of a watch - is sufficiently annoying that it usually gets fixed.
Edit: Great advice! Works like a charm! I've never really worked with dates in JS. Should have read the docs earlier ;-)