15 ms·
My stack is HTML+CSS
- deleted 6y ago[deleted]
- nicbou 6y agoWell yes, but your website has a dozen pages, wasn't updated in 6 years, and is as interactive as a sheet of paper. Do consider that some people tackle slightly harder problems.
- ironmagma 6y agoVery much like saying, “my vehicle will outlive yours. No, it doesn’t have wheels or axles, because my vehicle is the human legs.”
- netizen-9748 6y agoMore like saying '...because my car is the public bus system' Github pages is still software, running on a server
- ironmagma 6y agoGithub pages is more akin to the roads; if Github, a particular road, were to go away tomorrow, your site could just use a different road.
- type0 6y ago"The World Reveals Itself To Those Who Travel on Foot" - Werner Herzog
- v3ss0n 6y agoTry that in a big , enterprise project and come back and say.
- nikivi 6y agoThe only issue I see with going pure HTML + CSS is that you lose those smooth client site transitions that tools like next.js/gatsby give you. Is there a library that can give you HTML + CSS low kb site but those client site fast interactions (no page reloads)?
- projektfu 6y agoCombine your static site with intercooler.js or Htmx.
- netzone 6y agoI'd say probably Turbolinks is your best bet there. You basically drop it in, and then it prefetches all the links on your page, and when you click them, it replaces the DOM. It works quite well actually, Rails has been using it out of the box for years and years.
- nikivi 6y agoHow come GitHub isn't using Turbolinks then? Because each link transition will reload the page.
- canadianwriter 6y agoMy site too, it has made life SO much easier: https://kolemcrae.com/notebook/whynocms.html https://kolemcrae.com/notebook/whynocms.html
- deleted 6y ago[deleted]
- projektfu 6y agoThe main issues are the ergonomics of authoring and maintaining consistency around a site. A minimal static site generator would keep internal links and boilerplate consistent. Connecting that with markdown, Org mode, or reStructured Text would help with the ergonomics. But then you lose the goal of having no necesary tools. Anyhow, if there's one general purpose tool that predates the web and will probably be around when it's replaced by some other content publishing standard, it's Emacs. You could do a lot with a minimal SSG in Emacs and Org Mode, and it would be forward compatible with whatever is in the future, as well as backward compatible to whatever you like.
- cxr 6y ago> A minimal static site generator would keep internal links and boilerplate consistent. Maybe not. There's an argument to be made that says you should treat a blog as a series of pages, each modeling something corresponding to what you might call a "publication event" in the real world, e.g. printing a magazine or passing around a physical memo. The consistency angle is probably overvalued (not worth its cost). When a newspaper or magazine changes its masthead, old issues don't get updated. You might say that this reflects a limitation of the physical medium and that you would if you could (as is the case with digital editions), but what does it get you, really? Your links to external sources are already going to lead to wildly different forms of presentation outside your control. If an internal link leads to a page published in 2014, and it still matches the way it looked in 2014, is that a problem? (And if so, e.g. due to changes in fashion/trends that have led to it being intolerable, it's worth asking, "what makes it so?", "was it ever really tolerable, even in 2014?", and "is the material I'm publishing right now guilty of the same thing—its presentation only squeaking over the threshold of acceptability because of something else that's currently en vogue but soon won't be?")
- rimliu 6y agoYes, I remember seeing this idea. Some blog was making new design for each of the post. I really liked that, but I did not see it getting popular ever back in the days when FB was not yet a thing and websites used uniques designs instead of the cookie-cutter so popular today.
- netizen-9748 6y agoThis post appears to assume that github pages will never have any vulnerabilities ever and will always be available.
- greatgirl 6y agoSure, but all the problems come from the server side. You could suffer data corruption, power outage, domain name theft, whatever. I agree css and html is great but the author made this post specifically to feel superior about his theoretically perfect website, and i figure it's my job to inform him it's not theoretically perfect.
- protonimitate 6y agoI swear this same exact post gets re-dressed and upvoted weekly. Is there anything worth discussing here? The entire thesis of the post is "my blog is maintenance free". Ok, and? Is blog maintenance really a noteworthy topic? How many times can blogs rephrase "use the right tool for the job"?
- kodt 6y agoGotta get people to read your blog somehow.
- JxLS-cpgbe0 6y ago"My personal website with 4 pages doesn't need a CMS!"
- cxr 6y agoThis comment presents a caricatured perspective of those it opposes by using a made-up quote (it doesn't seem to have actually been said by anyone anywhere), and it doesn't really do anything for the discussion that wasn't already covered by the parent comment it's attached to. Please, folks, don't encourage people to post low-effort noise by upvoting comments like this. https://news.ycombinator.com/item?id=13602947 https://news.ycombinator.com/item?id=13602947
- chubot 6y agoI agree it could have been phrased more nicely, but it actually pointed out something valid, which I didn't catch at first. The author hasn't written any posts in 5 years, and has ~15 total since 2010: https://blog.steren.fr/ https://blog.steren.fr/ As someone who blogs regularly, I'm more interested in the toolchain of people who HAVE done significant writing. I read blogs for at least a decade before I wrote one, and it's harder than it seems, and coercing a good result out of tools isn't easy. In fact I just wrote a few of my own tools to fix the image problem, e.g. http://www.oilshell.org/blog/2021/01/blog-roadmap.html#unix-y-web-services-i-wrote http://www.oilshell.org/blog/2021/01/blog-roadmap.html#unix-... Basically, the author's strategy is not likely to last (though it's not impossible). My blog started out very minimal, but as you write, you bump into the need for more automation and tools. My site looks very simple and minimal, but there is a surprising amount underneath. Funny comic: https://rakhim.org/honestly-undefined/19/ https://rakhim.org/honestly-undefined/19/ When I was writing those tools I often wondered if we should just go back to Spolsky's CityDesk. It was a Windows GUI that would FTP HTML and images to a static server! I remember trying it briefly in the early 2000's. Although his blog also rotted due to CityDesk rotting! It's a hard problem. https://www.joelonsoftware.com/2016/12/09/rip-citydesk/ https://www.joelonsoftware.com/2016/12/09/rip-citydesk/
- city41 6y agoMy output is HTML and CSS, but my stack is React with Next.JS. I just tell Next to not emit JS at build time. This is the best of both worlds. You get an excellent dev experience with TypeScript, fast refresh, the world of React components (granted many don't work when reduced to being static HTML), and I can also opt back into React on a page by page basis if I have the need. With Next's static site generation and export, the output is just HTML and CSS (and optionally JavaScript), no need for a server. If anyone is curious, my personal site was done this way: https://mattgreer.dev https://mattgreer.dev
- freedomben 6y agoBeautiful site! Do you write your articles in markdown or something like that and render them into pages at build time? Is your source available by chance? I've been wanting to do this exact thing but while the Next.js docs are great, what would really help is to just see an example site that does exactly what I want to do. All the good examples are either too trivial to be useful or to complex to be useful.
- city41 6y agoThanks! I am using MDX for the articles. I don't really like it though. MDX is fiddly and causes some headaches here and there. I am exploring other options. The MDX files are here: https://github.com/city41/mattgreer.dev/tree/main/pages/articles https://github.com/city41/mattgreer.dev/tree/main/pages/arti... And I just now wrote a new post about how I did the static HTML: https://mattgreer.dev/articles/how-i-built-this-static-site-with-nextjs/ https://mattgreer.dev/articles/how-i-built-this-static-site-...
- freedomben 6y agoWow, thank you so much! That's a great post, very helpful :-)
- anderspitman 6y agoI too, enjoy Dependabot reminding me my blog exists.
- duxup 6y agoI appreciate folks who do this, and they're not wrong that it works for them and their use cases. But all the other complexity that comes along with the web and web development don't exist just because of those use cases. Nothing wrong here, although the litany of "look i'm just using html and css" gets to be a bit much sometimes and it sort of irks me to see yet another and another posted on HN and up voted with nothing new to say about it.
- dceddia 6y agoWhile I really like the idea of serving raw HTML and CSS, I think that on the authoring side, a static site generator that ingests Markdown and generates HTML is a more practical way to go. I think writing raw HTML can work fine for small pages, and arguably it can be better than Markdown for pages with a lot of design elements, like landing pages. But for the typical blog post, or especially if the blog post has code snippets that you want to have syntax-highlighted, a static site generator is way easier to work with. With the pace of change, I do worry a bit about the longevity of some of today's static site generators, but the Markdown itself is pretty darn portable.
- Tomte 6y agoThere are lots of different MD flavours, though. And even with Pandoc extensions you cannot really have an image inside <figure> with <figcaption> and alt text and title text.
- esperent 6y agoEasy enough to do that with a static site generator like Hugo/Jekyll though.
- dceddia 6y agoYep there are definitely some differences, especially once you start to go off the beaten path by including HTML in the Markdown, or using whatever flavor of template language the SSG provides. I've got some older posts that use Jekyll's {% highlight %} directive, and I know that won't work if/when I change SSGs, but to me that's a small price to pay for not having to author those in raw HTML! :)
- TheRealPomax 6y agoMost near-trivial to rewrite to each other's format though, which means you can get any static generator to ingest your favourite flavour with only a one-time step possibly (but almost certainly not) required to teach it how to ingest a format that isn't a perfect match for what it expects.
- newsbinator 6y agoAfter having written Pug and component-scoped CSS the last few years, it's surprisingly hard for me to go back to raw HTML and raw CSS.
- deleted 6y ago[deleted]
- Rauchg 6y agoThis is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla `<img>` will ship the same image to every device, regardless of viewport size. Vanilla `<img>` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently proud of. Frontend performance is basically an iceberg[1]. We tend to look at the top and that's where the fashionable "silver bullet" currently is (whether Rust+wasm or HTML+CSS or a JS framework). Then we find deeper in the iceberg that even a `box-shadow` property[2] can ruin our day, and let alone images, YouTube and Twitter embeds, and all the things that make the web more interesting and powerful than a black page with white text. Oh and it gets even more fun! A Lighthouse score in itself is an over-simplification. There's more to a great experience than the initial impression the site makes, like what happens to FPS when you scroll or click around[2] [1] https://rauchg.com/2020/next-for-vercel#realistic https://rauchg.com/2020/next-for-vercel#realistic [2] https://ishadeed.com/article/new-facebook-css#using-an-image-for-the-shadow https://ishadeed.com/article/new-facebook-css#using-an-image...
- deleted 6y ago[deleted]
- dceddia 6y agoOh boy, YouTube embeds! I went through checking the Lighthouse score on a few of my pages a while back, and the ones that had videos were performing pretty badly. It turned out that embedded YouTube videos were pulling down something like 1mb of JS, just to show the thumbnail, before the user even clicked Play. I ended up making a static thumbnail with a hover-over "play" icon that would replace itself with the real embed when it was clicked. Got the Lighthouse score up and saved all those unnecessary downloads. But it was pretty amazing to me that while one arm of Google is pushing for web performance, another is building this YouTube player that auto-downloads a megabyte of JS just to show a thumbnail.
- leerob 6y agoTwitter embeds are equally bad. Ended up remaking them to output static HTML + CSS to improve perf (https://leerob.io/tweets https://leerob.io/tweets).
- Tomte 6y agoMy Wordpress blog has a system font stack (that's vanilla Wordpress with the current theme Twenty Twenty One), and a Lighthouse score of 100 Performance, 100 Accessibility, 100 Best Practices, and 98 SEO. The only plugin that's relevant for that is WP Super Cache. I don't know what the author did with his Wordpress, but even the awful Twenty Twenty theme with the broken fonts wouldn't give you a 19 score in Performance.
- webscout 6y agoGreat, now show me the money.
- greggturkington 6y agoWriting HTML and CSS by hand?! Those are just the output. OOTB Wordpress didn't have a perfect Lighthouse score, so it's worthless? > I didn’t need 99% of its features anyway Oh, then it was already a terrible fit. So why are you advising people on how to replace Wordpress?
- ehutch79 6y agoFor a blog page, especially something as simple as what's linked to, coding html and css by hand is very simple. It's a blog, not a full blown app.
- greggturkington 6y agoYep, if you wanted you could re-write the same HTML and CSS by hand for every page instead of using templates. Is this a revelation?
- tannhaeuser 6y ago> How could you possibly consider writing HTML and CSS by hand? Those are just the output. You know, HTML is rooted in SGML and digital humanism. The entire point of it is that you use it as a simple means for self-publishing of digital text (and HTML 5 "standards" portray it in that role, in case you've never had a look). Granted, that isn't quite apparent when looking at the trainwreck that is HTML/CSS/JS. The solution (with SGML at least) is that you use your own custom markup vocabulary, including custom Wiki syntax for markdown and other short form syntax, and then convert that into result markup for delivery. The idea being that nothing can be as lasting for your specific purpose than your own text format. But the self-proclaimed web heads didn't get it. They made CSS so absurdly powerful and "meta" to cater for the historic shortcomings of HTML, which is just a format for casual academic publishing locked in 1991. Not considering that you can, in fact, define your own elements and meta rules. Or at least, I don't have another explanation for the fact that everything around HTML has to change ad absurdum while HTML has to stay the same while it quite obviously isn't a good fit for the vast majority of content on the web. And that for some reason you absolutely have to send the same HTML to your mobile that you send to your desktop, and that CSS absolutely has to be the place to shift, re-layout and hide content for these different purposes.
- wishinghand 6y agoI've found for little blog sites like what the author talks about, templating is still really handy. https://sergey.cool https://sergey.cool is a very slim one that supports Markdown. There's no way I'm going to type up all a blog post and add in `<p>` tags as I go.
- ehutch79 6y agoI'm very glad the author actually said this: ``` You don’t need Wordpress, or Hugo to put a blog online, or Angular, React or Next.js to put a web page online. Raw HTML and CSS do the job. That being said, you’ll need to pick up some tooling or framework if you want to build a web app or add more interactivity or customization to your web pages. ``` So often people forget not everything sitting on the web has the same needs. saying 'you don't need a framework' ignores that, maybe i do infact need one, because otherwise i'd have to write it myself.
- cookingoils 6y agoA much better post on the same topic: http://john.ankarstrom.se/html/ http://john.ankarstrom.se/html/
- scook 6y agoThose poor Lighthouse scores are what you get when you put no work into refining your site's performance. This is especially true for an out-of-the-box Wordpress implementation. I have a React project with 100s across the board, but I wouldn't necessarily recommend a React implementation if high performance is key. This doesn't even touch upon the topic of good developer performance, which is just as important as a set of Lighthouse scores. It's far easier to jump into an app with established build tools and documentation than it is to wade through a block of static HTML. Though if you're the only one working in your zen garden, have at it.
- stimpson_j_cat 6y agoThe site still fails Lighthouse, including the test for "Includes front-end JavaScript libraries with known security vulnerabilities." But wait, I thought it was just HTML and CSS!
- Veen 6y ago> The site still fails Lighthouse No it doesn't. Are you sure something on your system isn't injecting JavaScript (browser extension?)
- davidwparker 6y agoI use Rails. I use Svelte. I do SSR and CSR. I have dynamic content (not a static blog). My light house scores are ~95, 100, 100, 100. It can be done, you just have to be smart about how you do things.
- henlo 6y agoPlain HTML+CSS is really good nowadays. You can for example lazy load images with `loading="lazy"` attribute. You don't need JS anymore just to lazy load images. You can use plain CSS for simple interaction like opening and closing menu, toggling pricing plan, etc. If you're curious with what you can build with plain HTML+CSS, check out my side project[0]. It's a collection of free landing page templates in plain HTML+CSS (no JS). No frameworks, no preprocessors. [0] Uisual: https://uisual.com https://uisual.com
- TheRealPomax 6y agoNot needing to write markup at the time of content generation even better than writing HTML, though. Use any of a million static site generators and get the benefit of writing what you want to write in the most efficient format for that, without needing to program the typesetting markup while you're writing. HTML is in no way the best tool for write content. But it is the best tool to serve content in a browser.
- m___ 6y agoThe browser is the bitch. Out of control, bloated, willingly so, in interaction with layers of scripting on both sides. The server and client are bait. There should be a serious effort to tackle the world of academics and their use of analog tools for digital publishing. Nothing is better mined and searched(for any entity not meta-rapers that "employ" slave coders as battery-chickens) as text. There should be a tendency to reductionist auto-censuring or have coders but one ambition? Being scooped up by corporations for scraps so they can piggy back on their wild efforts for cents on the dollar?
- deleted 6y ago[deleted]
- TheRealPomax 6y agoAre you okay over there? It sounds like you got a little lost.
- 6y ago
- unabst 6y agoI feel like there should be some better way to recognize and promote solutions that are future proof. Like transpilers and site generators that only produce vanilla code for deployment. Because it wouldn't matter how dated the tool is. Sticking to vanilla only is not the only option. But I guess there could still be vulnerabilities in HTML that may need to be addressed? Like cross domain or cookie security... But then again, same for a vanilla stack. It definitely seems like maximum future-proofness should be more of a thing.
- m___ 6y agoThe thing, auto-censureship should fit in, as well as the code a-n-d hardware life-lines, including how to reproduce the workflow outside of corporate claws.
- antihero 6y agoAh, it's the regular: Wow, amazing, if you do not need to do very much, you can do it with very little! Post
- ARandomerDude 6y agoI've been using the same Middleman + Slim setup as a static site generator for 7 years now. Still outputs HTML+CSS for speed but with some nice writing features. Version everything in your Gemfile, use rbenv, and and you're set.
- miguelmota 6y agoHas anyone tried to create something other than a simple blog, like an actual web product with with users, using only the HTML+CSS stack?
- stimpson_j_cat 6y agoYes. In the nineties.
- ratww 6y agoI worked in a project from 2010 to 2014 which was just HTML and CSS. It was a University portal for teachers, students and admin staff that handled almost everything in the campus: grades, attendance, class schedule, downloads, renting books in the library, making room reservations, lunch vouchers for staff, a helpdesk system for students and staff, getting a free email account, etc. The goal was to be simple enough for non-technical students and older teachers. Most things were one click away from the home page, which was just a bunch of colorful icons. You clicked one icon and could see schedule, grades and attendance. The teacher could edit grades and attendance of the whole class in a single screen. There were no special requirements to drop JS. We just removed JS at some point and never added anything again. Frankly it worked pretty well. The design was made by a professional rather than using off-the-shelf stuff. What killed it was a migration to Bootstrap around 2015 after I left. For no reason. The layout ended up looking outdated compared to what we had, and the animations and javascript dropdowns were too heavy for the University's ageing computer fleet. The extra whitespace from default tables made everything too big to fit in a screen. Kind of a pity. But by this point everyone was moving to phones anyway, so the university spent a couple million in an iOS/Android app.
- deckard1 6y agoThat's impossible. You're going to need a backend, which at that point it stops being HTML+CSS and becomes LAMP or something. The only thing I can think of that can be done in pure HTML+CSS that would drive any sort of revenue and could be considered a business is an affiliate marketing site. I suppose you could also run a survey site and collect feedback via mailto link, but that's really old school.
- pgcj_poster 6y ago<title>My stack will outlive yours</title> <meta name="description" content="My stack will outlive yours"> <meta name="twitter:title" content="My stack will outlive yours"> <meta property="og:title" content="My stack will outlive yours"> "name": "My stack will outlive yours", <h2>My stack will outlive yours</h2>
- steren 6y agoSo what? Don't Repeat Yourself? I'm OK repeating myself if that can avoid me taking a dependency on fragile tooling
- m___ 6y agoMy approach of theoretics goes in that direction, more or less accentuated on different goal settings. Your approach must work for you as for sheer efficiency. You will spend more time on relevant issues, if so desired, of producing meaningful content. Now include hardware into the same philosophy, the long term into shelf live, a single programming language worked on by dedicated knowledgeable individuals ideally. You are on our side of things. A page (web/print) should be written, locally, off-line, in the same editor of always, in open-source code, preferably the blob of compiled code at it's nucleus, if there is any neeeded also. Content should have a seven hundred year lifeline, readable, view-able in minimal software allowances. Then it cannot be said too often, hardware-software is in-extricable. For all those that think phishing in the public domain for the soul of the crowds, well, that is fine, but nothing the matter. And be prepared for a frustrated life-time of scratching your itches. Theodore Kackzinski, people who vouch for the "hundred year", robust hardware, for the fashion of the ages, they seem to be on the right side of history. That same observation de-obfuscates the evidenced in what is going on in AI, and statistics, mining data. ...when the data are repeats, high-level, junk, outright meaningless, no amount of AI or tweaking using computer power will assert anything but junk outcomes. People scale badly, that makes for the most efficient workflow to be a-synchronous, for nuggets of which as an individual we have as a rule none, and few individuals very little, that sort of data merits a long life-line, that data need to be tailored for the above allowances as you point rightfully out. You might be fake, or limited in your ambitions, but from what I read, I must concede you make sense before any back-ground check is at order.
- ivanhoe 6y agoSure, it's super easy when your page doesn't have even a header and/or a footer. Try having a top-menu in your design, or some banners/ads, and then you need to change ALL the pages to change a single url. This is how we used to do things long time ago, and it sucked BIG TIME, and that's why people invented server-side includes and cgi and mod_php and all of that... it saves time, and your time costs much more than hardware...
- 411111111111111 6y agoTo be fair, static site generators are a thing and are very much underused in cooperations. He could have the same scores/performance and still get the full advantages you mentioned. But yes, handcrafting html is pointless at some point, especially if you have to update the contents every so often
- lazyjeff 6y agoA static site generator requires a toolchain, being platform-aware, updating dependencies, etc. Sometimes I think of these things as labor for a new employee (if you need to onboard a new maintainer) on a new system (if you need to switch hosts or upgrade the disk/OS). It's probably about 2-4 hours for an experienced developer to figure out how to setup and maintain a static site generator assuming no unexpected problems, then get familiar with the syntax and structure, so hopefully the labor savings from using a static site generator is worth that.
- forgotmypw17 6y agoA static site generator requires the cat command. I don't see how you can call yourself "lazyjeff" when you've just written this, tbh.
- egypturnash 6y ago"I looked at static site generators like Jekyll, Hugo, 11ty, but all of these require tooling installed, have a build step and will ultimately need some updates or be abandoned by their maintainer." - from the article
- dctoedt 6y ago> "When I publish a new page, I need to link to it manually from the index page. I’m OK with that. It’s done in one line. It also allows me to have more control over when I want the page to be “published”." I've sometimes wondered whether pg's essays are done with just HTML and CSS — it kinda looks that way, [0] but I'm not expert enough to be able to tell. [0] http://www.paulgraham.com/articles.html http://www.paulgraham.com/articles.html
- chubot 6y agoI use Markdown and HTML, CSS, and Python (just stdlib, no packages) to generate static files. I think that will last just about the same length of time. http://www.oilshell.org/blog/ http://www.oilshell.org/blog/ Markdown is a significant win, and CommonMark made it a lot better. CommonMark is a Useful, High-Quality Project http://www.oilshell.org/blog/2018/02/14.html http://www.oilshell.org/blog/2018/02/14.html Admittedly I need a Makefile, and Make is pretty impoverished for this use, and I want to replace it with something else. Shell isn't quite good enough because I don't want to rebuild the entire site on every edit, and I don't want to remember which files to rebuild. http://www.oilshell.org/site.html http://www.oilshell.org/site.html
- kkoncevicius 6y agoI use something very similar on my website, except with a few twists - MultiMarkdown (instead of Markdown) for HTML, Perl for piping MultiMarkdown produced HTMLs through some regex changes, and redo instead of Make for rebuilds. If you are looking for Make replacement - I cannot sing enough praises for redo: https://github.com/apenwarr/redo https://github.com/apenwarr/redo
- chubot 6y agoI've seen redo (and talked with apenwarr about it) although I think my brain is still stuck on static/declared dependencies. That doesn't apply to every problem but it definitely applies to a blog. Is your build parallel? That's one of my main requirements. I'd be interested in seeing the redo files if they're public.
- kkoncevicius 6y agoI made the files public temporarily: https://github.com/karoliskoncevicius/website https://github.com/karoliskoncevicius/website My website is probably a lot simpler than yours. All the "do" files are at the root level. But I have to state that there is no "redo" syntax really. You just take the scripts that do things and save them to files with a "do" extension.
- tomaszs 6y agoAfter fighting with React hooks, SCSS, BEM, Node.js and styled components it must be a relief to use pure, normal, simple and elegant CSS and HTML.
- yagizdegirmenci 6y ago> You don’t need Wordpress, or Hugo to put a blog online It took me about 25-30 minutes to publish my website with Hugo, from scratch. I can't even estimate how long will it take if i try to build something like the current one. > Angular, React or Next.js to put a web page online. Raw HTML and CSS do the job. If you see someone who uses Angular for a blog, go straight to the DEA and report him/her.
- Evidlo 6y agoYes, but you probably used a provided Hugo theme. For a fair comparison, you'd use a premade pure HTML+CSS template or write a Hugo template from scratch.
- dmje 6y agoThis. But also, the point here IMO isn't just about performance but about tooling choices. There's so much tendency in the dev community (and has been since 1996 when I started doing web stuff) to jump on the latest thing without thinking about context or applicability. Perl then CFM then asp then Flash then js then...it goes on. Thing is, you don't need some jamstack hellhole of complexity if you're serving simple content pages. Need a common header, just do a find replace as he says or write a php include. It's always been the same: choosing overcomplex solutions may be fun and groovy - and good to learn and interesting - and this may be enough of a reason to do it, but it's always worth asking what you're trying to achieve and whether the toolset fits. So often that doesn't happen, and almost always the simplest solution is the very best one.
- xkcd1963 6y ago"will never have any security vulnerability" that is a good joke considering that css keyloggers have been around since a while
- jaywalk 6y ago> Sometimes, for drafting long blog articles, I’m working in Google Docs, and when I’m happy, export the content to clean HTML using an add-on. Oh, but as he said earlier in the post, relying on a static site generator that you can install and run locally is unacceptable. That makes sense.
- nashashmi 6y agoGreat for information but no so much for application. Once you get into forms and submissions you can’t do no-js anymore.
- Evidlo 6y agoWhy can't HTML some kind of templating system, or even simple includes? Then I wouldn't need to use a static generator and could just author HTML directly. e.g. (with hypothetical <extends> and <block> tags) template.html <!doctype html> <html> <h1>My Fancy Blog</h1> <block main/> </html> index.html <extends "template.html"> <block main> <body> Hello world </body> </block> Maybe this would compromise browser performance or add some kind of vulnerability, but authoring DRY HTML directly is my fantasy
- crazypython 6y agoIt's called XSLT
- err4nt 6y agoLook into custom elements and web components, HTML already has amazing stuff built in, supported in every browser, and maybe even being used on some of your favourite sites!
- progval 6y ago> Why can't HTML some kind of templating system, or even simple includes? XHTML does, it's XSLT. For example: <?xml version='1.0' encoding='ASCII'?> <?xml-stylesheet type="text/xsl" href="stylesheet.xsl"?> <root> <title>Page Title</title> <block name="main"> <article xmlns="http://www.w3.org/1999/xhtml"> <p>Hello world</p> </article> </block> </root> With this in stylesheet.xsl: <?xml version="1.0" encoding="ASCII"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/root"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <head> <title><xsl:value-of select="title" /></title> </head> <body> <h1>My Fancy Blog</h1> <xsl:copy-of select="block[@name='main']/xhtml:article" /> </body> </html> </xsl:template> </xsl:stylesheet> And it's supported by all major browsers. Probably even IE6.
- 6y ago
- krsdcbl 6y agoSorry to be so negative on this one but I'm kinda triggered by these "look its that easy" kinda blog posts that fail to adress the common task at hand entirely. This works for your personal blog with a super minimalistic design. This is completely unfeasible for client projects, or at least it will break your neck in the long run. And chances are your abysmal lighthouse score on WP had more to do with a bloated, mashed together WP setup than with the technology itself.
- naberhausj 6y agoI agree wholeheartedly with this sentiment and have elected for the same thing on my website. The only difference is that I wrote a simple template based static site generator (https://github.com/JosephNaberhaus/naberhausj.com/tree/master/builder https://github.com/JosephNaberhaus/naberhausj.com/tree/maste...) to keep my HTML sources in accordance with DRY. What I don't understand is how the linked page is downloading 1 MB of resources which unpack to nearly 2 MB. This page shouldn't need more than 100 KB.
- Santosh83 6y agoIt's the image of the Wordpress source and poor Lighthouse score. It's a poorly optimised PNG and a single file at 1 Mb instead of multiple sources for multiple screen resolutions. Of course, it does go with the thrust for simplicity in the article...
- Wowfunhappy 6y agoThe one thing I really feel like I'm missing out on, in my own no-build-system Github Pages site, is an RSS feed. A couple of people have emailed me asking if there's a way to be notified if I make a new post, but I don't see how I can do it without bringing in an external service.
- pedro1976 6y agoHave you tried https://github.com/damoeb/rss-proxy https://github.com/damoeb/rss-proxy ?
- Wowfunhappy 6y agoThis is the sort of the thing I may eventually go with. (And I hadn't seen this one, so thank you!) But it feels more than a little like I'm essentially adopting a build system, since I have to run this manually each update. The idea was I wanted a stack which I could not touch for 10+ years, and nothing would go out of date and stop working. I don't think I have that safety for anything involving NPM...
- progval 6y agoWhat about your commits' RSS feed; assuming most of your commits are only to add a page?
- deleted 6y ago[deleted]
- commandlinefan 6y agoWell, that's fine if you're running a completely static blog. I keep my stack as slim as possible, but I still need CGI and a DB to maintain a comments section. I also have just a bit of server-side scaffolding to ensure that there's a standard look and feel to the site.
- forgotmypw17 6y agoI agree 100%. Any Browser.
- dubcanada 6y agoYa well my stack is just HTML, who even needs CSS. It has everything yours has with the benefit is having a single file. Why just HTML you ask? Well all the reasons that they provided plus the fact it's only HTML files. This whole stack argument is silly, just let people use what ever they want to use. If someone wants to use a giant complex webpack setup, that's perfectly fine. Sure there is obvious downfalls and longer term maintenance can be a hassle, but it's what they enjoy. If you want to use just HTML and CSS, go for it, but why are we bragging?
- maloshackeros 6y agoAs a Fortran programmer I approve of this post.
- kome 6y agomy homepage, pure html+css https://mrtno.com/ https://mrtno.com/ (not optimized for smartphones) p.s.: hire me pls.
- anderspitman 6y agoI've found a nice middleground to be writing a custom static site generator for each site. They can be quite small (here's one[0] in ~50 lines). Usually it just loops through a directory and turns Markdown files into HTML (with header injected), and syntax highlighting. Also, if you're really committed, you might be surprised how app-like you can make HTML+CSS, using things like checkbox and :target hacks[1]. The UI demoed in the video on this site[2] has no JS. These techniques pretty much require a generator, and there are obviously tradeoffs. [0]: https://github.com/boringproxy/boringproxy.io/blob/master/ssg.js https://github.com/boringproxy/boringproxy.io/blob/master/ss... [1]: https://www.mattzeunert.com/2017/10/30/javascript-free-todo-app.html https://www.mattzeunert.com/2017/10/30/javascript-free-todo-... [2]: https://boringproxy.io/ https://boringproxy.io/
- apolymath 6y agoI built a CMS that focuses on HTML + CSS code writing and uses mustache to enable multilingual content. Check it: https://saber.datasilk.io https://saber.datasilk.io
- taivare 6y agoI want to build a simple blog with HTML + CSS, but I also need to have reader comments any suggestions?
- mastermojo 6y agoI am pro github pages. Used it for 5 years, no complaints. [1] However, I've chosen to also use Jekyll. Github pages explicitly supports/couples with Jekyll [2], so I view the combination as a single dependency as opposed to an extra. For deployment, I push to a git branch and github builds and updates my site in the 10-60 second time frame. [1] http://www.growthalytics.com/programming/2015/07/19/setting-up-your-own-blog/ http://www.growthalytics.com/programming/2015/07/19/setting-... [2] https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll https://docs.github.com/en/free-pro-team@latest/github/worki...
- nsilvestri 6y agoThis is almost my stack, but I added PHP for rendering Markdown files (via Parsedown) and use include statements for common components like headers. I use an Apache server on a 512mb VPS and deploy by ssh and a git pull. The only downside I have notice is that I can't easily put JS demos _within_ my rendered markdown, but I can work around it by stitching together multiple markdown files. Not pretty, but it works.
- notjustanymike 6y agoYeah and I walk to the grocery store on good old fashioned feet, but you can bet your ass I'll use an airplane if I need to get to California.
- ghostbrainalpha 6y agoI'm also a huge fan of keeping things simple. But there is a reason we are having this conversation here, and not in the comments section of his blog. Comments are something I consider pretty vital to even a basic blog now. And so he's kind of missed the mark for me.
- chrismorgan 6y agoComments used to be almost table stakes, but in the last decade or so, things have shifted so that I estimate that only somewhere around 5–20% of the blogs I encounter have them.
- gunnarmorling 6y agoWhat this approach doesn't really consider is that the same contents may appear multiple times on a site: - actual post - teaser on the front page - RSS feed - search index - title in multiple "tag" pages - title in sitemap - title in a paged list etc. pp. Sure, you can maintain all that manually, but it's so much easier using an SSG like Hugo.
- TurkishPoptart 6y agoOne thing I'd like to learn/better understand is this part: <script type="application/ld+json"> { "@context": "http://schema.org http://schema.org", "@type": "Article", "author": "Steren Giannini", "name": "My stack will outlive yours", "image": "https://blog.steren.fr/2020/my-stack-will-outlive-yours/lighthouse-score-improve.png https://blog.steren.fr/2020/my-stack-will-outlive-yours/ligh..." } </script> is this something created programmatically? I'd like to create a blog but I don't want to have to type all all the necessary schema.org tags myself. Any ideas here? edit: God, I can't even get this text to format properly. I'm such an idiot.
- dual88 6y agoI don't understand his point. HTML/CSS are fine if you know them but a lot of people have better things to do than learn those, so they use wordpress/medium/whatever instead of mocking about in html/css. Also, his blog is only text and has no functionality, so yeah, sure use html/css, but most apps like youtube/twitter have a lot of functionalities and they need js. "And because my sources are in git, pushed to GitHub,GitHub Pages is my host."-right, and if github is hacked so are you. So much for not worrying about security.