A short, useful read for the Malachain community.
Frameworks come and go, but every page still ends up as HTML in the browser. Using the right element for the job, such as a real button for actions, headings in a logical order and lists for lists, gives the browser meaning it can use. Screen readers, search engines and reader modes all rely on that structure to understand what is on the page.
Semantic markup also saves work. A native button already responds to the keyboard, shows focus and announces itself correctly, while a clickable div needs extra code to imitate all of that. Before reaching for a custom component, check whether a standard element already does the job. Validating a page now and then catches unclosed tags and duplicated identifiers early.
If you try any of these ideas, start small and adjust them to your own situation. What works for one person will not suit everyone, and it is fine to keep only the parts that help. Writing down what you changed, and what happened, makes it much easier to see after a few weeks whether the effort was worthwhile.
The most useful step is usually the first one. Pick a single suggestion, try it for a couple of weeks, and then decide whether it is worth keeping. Small, steady improvements last longer than ambitious plans that are hard to maintain once everyday life gets busy again.
It also helps to talk the subject through with friends or colleagues who have tried something similar. Their experience points out the details that guides leave out: how long things really take, which costs were unexpected, and which shortcuts turned out to be a mistake.