i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
-
@frankdelporte @b0rk +1 for hugo, but I run it in a container with a fixed (and now ancient) version because they aren't as backwards-compatible as I'd sometimes like...
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk I feel the same way. I also want it to cost as little as possible and be easy for me to create content. Like content from my phone would be a win.
Currently I have an unmaintained netlify project running gatsby because at one point in time it was easy to add markdown files to a repo and have dependabot keep it updated.
-
@tedmielczarek what kinds of frameworks do you mean? i feel like I use a lot of "technologies" to build my sites, for example on my latest project I'm using S3, a Dockerfile, a managed deployment service, GitHub Actions, and probably more things.
definitely gauging what is worth it and what isn't can get complicated and sometimes I try a new thing and decide it isn't worth the complexity
@b0rk I'm primarily thinking about frameworks like React here, which seem to only work well for companies who can dedicate staff to wrangle the complexity.
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk fwiw this is exactly why I made https://github.com/kokkonisd/mrbones
I wanna make the site not fight the site generator
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk@social.jvns.ca my answer would be vanilla js (or maybe jquery at most), Iβm curious what is yours
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
You may want to chat with @coopcloud @autonomic and @kawaiipunk about the techstack you are using.
-
This me also.
Alternatively, we could sponsor you to write your version of these manuals:
-
@b0rk fwiw this is exactly why I made https://github.com/kokkonisd/mrbones
I wanna make the site not fight the site generator
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk have you outlined what technical choices you've made as a result of these constraints? It feels almost like hand-writing simple HTML/CSS/JS would make sense here
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk
@frankdelporte offers a good option. I also like #VitePress for customization of the CSS/HTML/JS and use it to run several similar sites myself. https://vitepress.dev/ -
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk same!
I actually had to write myself a README file in the directory where my blog lives so I remember how to write a new post, when I come to do it once a year or so...
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
I don't know that is necessarily dictates a different tech choice, but I think it dictates making sure it's documented / annotated sufficiently, including any and all stuff you use to automate the test/version control/build/deploy/patch/etc bits that sit around the sides of "it"...
Incomplete documentation and/or annotation is the #1 thing that bites me in the arse when I come back to something, personally speaking.
-
-
-
@b0rk 2 more thoughts that haven't been touched on, but maybe make sense to mention:
- Make sure your theme brings all its JS, CSS and fonts with itself. (Independence from CDN disappearance)
- Use native HTML focused CSS frameworks like simplecss, because it makes porting content much easier. -
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk I feel the same way about websites generally. Also about languages lately. Like, I feel like go has so much good about it but also I feel like it is a language I would have to be using full time to really write good go so I avoid using it.
-
@b0rk same!
I actually had to write myself a README file in the directory where my blog lives so I remember how to write a new post, when I come to do it once a year or so...
-
@b0rk After I had a personal site sink into unmaintainability, I created a framework that I hope can work for more than a decade without any changes or updates
The key was making every build step skippable. Itβs all enhancement from basic HTML. If my syntax-colorer breaks in 2029 the site still builds
-
-
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
@b0rk imnsho your requirements are absolutely sane and not weird at all
