In this series: I'll cover the reasons why I build my portfolio without using a CMS, show my progress of troubleshooting, working through the mess and what I learn in between. The portfolio is in the making.
The purpose of the series: to record my process, visualize my progress for a future improvement, keep myself accountable and connect with you who may have the same journey.
Feb 23, 2021
A short and sweet update for today.
Here are some questions I have for you:
When do you feel the need to explain your thought process while working through difficulties in each project?
- Do you think it's important to do so?
- Or the results of the work already explain themselves?
These questions came up during my content editing process. In my opinion, I just felt like it's worth mentioning what I went through. So, I ended up including some explanation that can look...a little bulky.
On the other hand, it could also depend on who the audience is, I think. If they're potential employers who are interested in how I solved problems technically, this can be a good presentation. But if they're potential clients, say local business owners who just want to visually see my past work and want a website, this may not matter much?
In the end, I want it to be presentable for both audience.
For now, I guess I'll just keep editing and getting it done. Then will see how I feel about it later on. I'll be happy to hear what you think as well.