Sure, 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 h…
This is the exact thing I experienced and have been dealing with the past couple days. I wanted to create a small collection of pages as my website, intending to keep everything as small and simple as possible since it was (mostly) just to display some basic info and "posts". Well as soon as I wanted that menu for pages it was a whole new can of worms. Sure, I could just copy/paste/replace content as it changes. But…
My stack is HTML+CSS
91–100 of 194 posts
Re: My stack is HTML+CSS
#92Has anyone tried to create something other than a simple blog, like an actual web product with with users, using only the HTML+CSS stack?
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.
Re: My stack is HTML+CSS
#93e.g. (with hypothetical and tags)
template.html
My Fancy Blog
index.html
Hello world
Maybe this would compromise browser performance or add some kind of vulnerability, but authoring DRY HTML directly is my fantasyRe: My stack is HTML+CSS
#94Earlier quoted context omitted.
My article covers that: > So... if I don’t use any templating system, how do I update my header, footer or nav? Well, simply by using the ”Replace in files” feature of any good text editor. They don’t need frequent updates anyway. The benefits of using a templating system is not worth the cost of introducing the tooling it requires.
>The benefits of using a templating system is not worth the cost of introducing the tooling it requires. Other people use static site generation, you use search and replace in your editor - not much of difference. Your approach is slower in long term, but with your on average 1 article per year it will take some time until you reach the threshold.
Far too often I see people spend days to save 2 seconds (and then proceed to not realize the savings over a long enough timespan)
Re: My stack is HTML+CSS
#95> 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.
For a fair comparison, you'd use a premade pure HTML+CSS template or write a Hugo template from scratch.
Re: My stack is HTML+CSS
#96Sure, 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 h…
Re: My stack is HTML+CSS
#97This 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.
Re: My stack is HTML+CSS
#98Earlier quoted context omitted.
This is the exact thing I experienced and have been dealing with the past couple days. I wanted to create a small collection of pages as my website, intending to keep everything as small and simple as possible since it was (mostly) just to display some basic info and "posts". Well as soon as I wanted that menu for pages it was a whole new can of worms. Sure, I could just copy/paste/replace content as it changes. But…
HTML, CSS and SSI includes would be an easier option. If you don't want to deal with Node.
Re: My stack is HTML+CSS
#99Sure, 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 h…
My article covers that: > So... if I don’t use any templating system, how do I update my header, footer or nav? Well, simply by using the ”Replace in files” feature of any good text editor. They don’t need frequent updates anyway. The benefits of using a templating system is not worth the cost of introducing the tooling it requires.
Re: My stack is HTML+CSS
#100What 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.