#Doing some enhancement on my personal website. ...
winged yarrow
jagged frost
I have a general comment. Consider what information you’re presenting to the end user and what of it is actually valuable to them.
I see this trend of people just listing all their languages and frameworks and tools they know, but is that actually valuable information to place on that page for the audience you built this portfolio for? Reason being is that knowing react or cypress or whatever else you listed is no longer a differentiator. These skillsets aren’t that unique, despite demand being high. So enumerating all of them on portfolio just feels like filler.
Instead choose a few skills or projects that actually are unique to you and focus on them. Show your audience why you’re awesome with readily available examples instead of just telling them you’re awesome because you know x and y and hoping they trust you.
My only advice is to condense it all down and really think about your audience. For example if you’re building this to land work, then your contact form needs to be far more prominent and not at the bottom of the page.
In terms of actual ui, I think it looks great. Color and font choice is 👍
hollow flint
Thanks for the suggestions.
The target audience is (future) potential employers, both technical and non-technical. The goal of the website is to illustrate my hard skills and the fact that "I can make a beautiful website". Though it is also one of my hobby projects, just for fun type of thing. So it's not a portfolio web site so to speak, although I wish I can make one, more on that later. It's more like an online resume website.
Show your audience why you’re awesome with readily available examples
This is not something that can be done easily in a place where NDA is highly regarded and side projects are strictly forbidden when you have a full-time job (or at least I'm not supposed to share with the world). I do hope I can have a portfolio section, but I'm not sure whether filling it up with school projects that are not up to my current standard is a good idea. If not, then perhaps it's better to leave it empty.
I used to briefly talk about each project I've worked on in my full-time job. And the next day, my manager asked me to come to his partition and give me a verbal warning/reminder of not to do so.
I see this trend of people just listing all their languages and frameworks and tools they know
Agree. In fact, I've already removed some that are low-value (e.g. ASP) or are implicitly expected me to know about (e.g. HTML, JS, CSS Modules, etc.). My initial thought of listing those techs this way is to illustrate that FE is not the only stream I've touched. I'm more or less also familiar with other streams, although FE is indeed my main stream.
And yes, the contact form is seldom used. I can't even remember when is the last time I receive a meaningful message. If some recruiters want to contact me, they usually do it through LinkedIn, email, WhatsApp, or on call.
jagged frost
Woah that’s pretty wild about the side projects being forbidden
Good luck iterating on the site/portfolio 🚀
It does look quite pleasant to the eye
hollow flint
Thanks.
Yeah, I'm not sure. I guess it's more about the culture where I live. I do see many people have side projects in the web dev community, more commonly in western countries. Here, the company usually forbids that explicitly in the contract.
grave surge
Why are you listing udemy courses that you have completed? Seems like a bit of a vanity metric given your experience and education (which is great)
hollow flint
Why are you listing udemy courses that you have completed? Seems like a bit of a...
Yeah it's more like a show off. I consider those to be low value contents TBH. but since I was given a free Udemy subscription as one of perks in my previous job, and I did make use of it by learning something new, I wonder why not showing off of me not being just another FE dev who knows nothing except FE
latent junco
Hi, I love it. I have downloaded the script from your github but when I run it (npm run dev) I am getting this warning, not sure what it means ...
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.
Warning: Only createServerContext is supported in Server Components.```I get that, makes sense 🙂
hollow flint
Hi, I love it. I have downloaded the script from your github but when I run it (...
Noticed, but I don't have time to investigate in detail. I tend to believe it is a bug/incompatibility of /app dir.