Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rewriting my website in plain HTML and CSS

vijayp.dev

Post reply on HN
Print view View original

181–190 of 218 posts

Re: Rewriting my website in plain HTML and CSS

#181

Post by QuantumGood »

HackerThemAll wrote: post #179

The website of one of the most influential IT person, who won the court battle against U.S. Government, allowing for widespread cryptography, professor Daniel J. Bernstein, is and always has been plain HTML mostly with no CSS. https://cr.yp.to/ It's served using his own HTTP server - publicfile, and the DNS domain is served using his own DNS server - djbdns. E-mail is handled using his own SMTP server - qmail. He inv…

These kinds of sites really benefit from "reader"-type plugins, pushing off readability across different interfaces onto the visitor.

Re: Rewriting my website in plain HTML and CSS

#182

Post by nbbaier »

benchly wrote: post #154
nbbaier wrote: post #115

Earlier quoted context omitted.

I love this site and concept and have been thinking about moving to this method for my own site

Same. This would work really well for my site, I think, although I worry slightly about latency as it scales and I add more and more photos. That is not so much a problem right now, but it might impose some latency later.

Yeah. I don't know if it scales to adding a blog either, which I have been thinking about doing.

Re: Rewriting my website in plain HTML and CSS

#184

Post by [deleted] »

culi wrote: post #178
spoonfeeder006 wrote: post #56

Earlier quoted context omitted.

Isn't using React with a static site generator framework basically the same thing but better?

Not remotely! Unless you meant Preact. React ships an entire rendering engine to the front-end. Most sites that use React won't load anything if javascript isn't enabled

[deleted]

Re: Rewriting my website in plain HTML and CSS

#185

Post by XCSme »

I also created something similar in PHP + Apache rewrites.

I already had a PHP website, and I wanted to add a simple blog system to it, but most suggestions were complex systems that required installation.

I created a .htaccess file and some PHP files to load and display markdown files from the /posts folder.

It doesn't require installation (just copy-paste the files and you have a blog), and no database (posts are simply the markdown files).

https://github.com/Cristy94/markdown-blog

Re: Rewriting my website in plain HTML and CSS

#186

Post by spoonfeeder006 »

realusername wrote: post #103
spoonfeeder006 wrote: post #56

Earlier quoted context omitted.

Isn't using React with a static site generator framework basically the same thing but better?

In theory yes, in practice good luck maintaining that if you are just a solo blogger. I doubt your blog would last a single month without some breaking change of some sort in one of the packages.

you mean npm packages? why would you need to update those anyhow?

Re: Rewriting my website in plain HTML and CSS

#187

Post by mixmastamyk »

mrweasel wrote: post #128
mixmastamyk wrote: post #48

Earlier quoted context omitted.

I recently learned the object tag can do what I wished for in the 90s... work as an include tag: Turn your back for twenty-five years, and be amazed at what they've come up with! ;-) Should reduce a lot of boilerplate that would get out of sync on my next project, without need for templating.

Couldn't you sort of do that using server side includes back en the 90s? Assuming that your web server supported it.

Yes, and a Makefile was an option as well. But an include tag was a no-brainer not long after html was invented. Especially after img, link, applet, frame, etc were implemented.

Re: Rewriting my website in plain HTML and CSS

#189

Post by lmm »

TeMPOraL wrote: post #165
lmm wrote: post #125

Earlier quoted context omitted.

I don't particularly care about "designed for". If you've got to serve something to make the browser display the static content you want it to, the least unpleasant way to do so is with JS.

Least unpleasant to the developer. Most unpleasant to the user. It breaks all kinds of useful browser features (which frontend devs then recreate from scratch in JS, poorly; that's probably the most widespread variant of Greenspun's tenth rule in practice).

> It breaks all kinds of useful browser features (which frontend devs then recreate from scratch in JS, poorly; that's probably the most widespread variant of Greenspun's tenth rule in practice).

Nah, it's the opposite. JS tends to perform better and be more usable for the same level of feature complexity (people who want more complex sites, for good reasons or bad, tend to use JS, but if you compare like with like), HN just likes to use them as a stick to reinforce their prejudices. (E.g. if you actually test with a screenreader, aria labels work better than "semantic" HTML tags)

Re: Rewriting my website in plain HTML and CSS

#190

Post by realusername »

spoonfeeder006 wrote: post #186
realusername wrote: post #103

Earlier quoted context omitted.

In theory yes, in practice good luck maintaining that if you are just a solo blogger. I doubt your blog would last a single month without some breaking change of some sort in one of the packages.

you mean npm packages? why would you need to update those anyhow?

Because at some point it will cease to work? It needs upgrades like any other project.

Every upgrade in the JS world is very painful.

Post reply on HN