Skip Navigation

tumulus_scrolls
tumulus_scrolls @ tumulus_scrolls @lemmy.fmhy.ml
Posts
0
Comments
4
Joined
2 yr. ago

Helping those who come after me maintain a website.

Jump

  • There's a case to be made, realistically speaking, that using a well-known framework or even a CMS like Wordpress means less complexity specific to your website to understand for the next person. FTP cough SFTP or Markdown/HTML is definitely not beyond non-technical people to understand and use, but sadly there could be some resistance nowadays I imagine.

    I would look into static website generators. Sadly I'm not sure what is most reliable nowadays, but I would prioritize easy of use and installation, as speed is probably meaningless on your scale. Here's a random article.

    • wayland was a mistake

    Jump

  • There is !linuxmemes@lemmy.world and !linuxmemes@lemmy.fmhy.ml.

    I mean... "who needs features in 2022" is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.

    • Open Source Lightweight Markup Language for Project Management

    Jump

  • Feedback: to see an example one has to click through to another file in the repo.

    Is it a subset of Markdown or YAML? It is a type of decision that it would be good to be upfront with to the users. It also gives you a framework for further thinking and development, and some out of the box parsability.

    • Keeping and running frequently used commands

    Jump

  • Obvious things I don't see mentioned:

    • Bash scripts kept in the home directory or another place that's logical for them specifically.
    • history | grep whatever (or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE and HISTFILESIZE environment variables in your system.