Earlier quoted context omitted.
You said it yourself. The tech you're suggesting didn't meet their requirements. Once it does, they will use it. A marketing site SHOULD be optimized for the editor. This is a failure of the dev, not the marketing person.
my confusion is why it's their requirements that need to get met, not say, the readers' requirements.
The Static Site Paradox
261–270 of 370 posts
Re: The Static Site Paradox
#262Imho, the big lie regarding static sites is that it's showcasing only part of the solution it fixes. In the end it does not reduce complexity, it pushes it away from your immediate attention span(it's serverless), either to building tools, browser and configuration files.
You still need to build it, pick a layout, maybe some plugins. That requires not only the time to do it but also infrastructure behind, to push changes. If you consider that, from the start till the end, there is the same amount of complexity around it. You still need to persist data, md files look more appealing, but in the end is a disk data store, and if you need to collaborate, edit, etc, you end up realizing why why databases were invented.
To conclude, I really like static sites for the reasons I didn't include here.
Re: The Static Site Paradox
#263There is a complicating factor for a Web developer's personal Web site: resumé-driven-development (RDD). For those professionals who try to use personal side projects for RDD, so that they don't have to sabotage as many employers' projects as they would otherwise. Which leads me to this morning, for example... For an indie Web site I'm about to launch -- and for which I'm using a popular modern Web framework, mainly…
Have you tried? Also, you don't need to put everything you have ever done on your resume if you don't think it will help.
Re: The Static Site Paradox
#264Earlier quoted context omitted.
I think that was true during the age of the blog, but far less so now. Comments and discussion of a post are to be found on third-party communities like Reddit, HN, or even Facebook. How many of us scan the list of comments under, say, a Substack post vs. will scroll through a page or two of HN comments for the same post? IMO it's a foregone conclusion that a discussion on HN will be higher quality for a tech-related…
The more people join a social media site the worse the conversation gets. This is already happening to HN as tech people flee Reddit. Most of the new comments on any given post are people that didn't read the linked content and complain about stuff addressed in the second paragraph. This is an evolutionary process where the commenters that get the most engagement are those that are first to respond or react. First-mo…
Re: The Static Site Paradox
#265Re: The Static Site Paradox
#266Earlier quoted context omitted.
You said it yourself. The tech you're suggesting didn't meet their requirements. Once it does, they will use it. A marketing site SHOULD be optimized for the editor. This is a failure of the dev, not the marketing person.
my confusion is why it's their requirements that need to get met, not say, the readers' requirements.
Re: The Static Site Paradox
#267The killer app of WordPress is comments. No SSG, almost by definition, allows comments; WordPress blogs almost always come with them built in. If you want something like Hugo to really take off in the blogging sphere, all you need to do is create some good looking themes with comments . Figure that out at scale - maybe by using per-blog sharded SQLite, which you can host as a third party for pennies on the dollar - a…
Another "interactive" part: contact forms. Not every business site wants comments, but they'll probably want a contact form. Putting an email address out is an alternative, but handling the input pipeline is better. On a static site that requires finding a service they trust to handle the submission and correctly plug it in their site. It becomes another moving part, potentially another bill that needs to be paid sep…
Re: The Static Site Paradox
#268There is a complicating factor for a Web developer's personal Web site: resumé-driven-development (RDD). For those professionals who try to use personal side projects for RDD, so that they don't have to sabotage as many employers' projects as they would otherwise. Which leads me to this morning, for example... For an indie Web site I'm about to launch -- and for which I'm using a popular modern Web framework, mainly…
Re: The Static Site Paradox
#269I have whole rants about this, based on bitter experience trying to convince marketing people to stop using WP and just use a static site. It comes down to ease of editing. A WP site optimises for the editor. Not the hosting, not the tech folk, not the accountants, and definitely not the reader. The people who edit the site get to say how it's implemented. If you give them the choice (as I have) between a site that r…
Re: The Static Site Paradox
#270The killer app of WordPress is comments. No SSG, almost by definition, allows comments; WordPress blogs almost always come with them built in. If you want something like Hugo to really take off in the blogging sphere, all you need to do is create some good looking themes with comments . Figure that out at scale - maybe by using per-blog sharded SQLite, which you can host as a third party for pennies on the dollar - a…
So Hacker News and "real programmers" continually underestimate the foundational concept of a CMS. They consider it to be unsexy tech and therefore all problems around it must be solved and boring problems, and therefore they aren't actually aware of what any of those problems are. The WordPress ecosystem is of course the polar opposite of this, it's populated by billions of dollars worth of businesses that understan…
Liferay, Sitecore, Dynamics, SharePoint, AEM, SAP, SharePoint, Optimizely, Contentful, Sanity,....