Starting probably in a month or two, I will open a category of blog posts of my site studies. I know there is such thing as case studies, but that term is more appropriate if I document something about a project that I’m responsible for. These site studies are kind of like website reviews that many hobbyist web designers used to do back in the days. 1 The only difference is that I provide a solution to what I feel (as a designer or dev) that could have been done to make the site better, etc. Website reviews were strictly critiquing and back then, sometimes it’s just straight up bashing and only praising the aesthetics rather than the functionality and user-friendliness. People didn’t know any better back then.
The reason why I’m opening this category mainly because of personal documentation of what I’ve done as a dev that’s non-work related. I feel that it would be a good presentation for a resume or a portfolio when I apply for a future web dev job. These may also be good as examples for job interviews too. But also, this would also be my personal notes on what solutions I can do if I ever run into the same situations again. I don’t know if I’m making any sense.
The (tentative) format
Maybe this would be a lot easier if I make a custom post type, but because I probably wouldn’t be having these types of posts on a regular basis, I’ll stick to the manual way of posting. After all, I still don’t get Gutenberg. 2
The following below is my proposed format for these site studies:
- Site or service being reviewed
- Issue to review
- Issue details (actions, interactions with tech support, how long has this issue been going on, etc.)
- Solution to the issue
- Conclusion and/or final remarks to the site study
I will probably start writing my first site study probably in two weeks. But as of now, this is another quick post as a side note for me. If I don’t write any “asides”-like posts like this one, I’ll eventually forget it. So, here’s a quick post.
More info about this much later.