DEV Community

loading...

Discussion on: Goodbye portfolio site

Collapse
mjericsson profile image
Matt Ericsson

I'm definitely in the same boat when it comes to using WordPress. So many clients like the idea of having control of their content, but in reality they'd rather go to someone else for changes (in my experience). That's why I always recommend designing and building over using a platform. There are pros and cons to both, but I can't imagine using WordPress in my workflow.

To answer your question, yes. I believe a portfolio site is important if you're in this industry. It's a great way to showcase your work if you're looking for work and/or have quality work to show--whether that be design and/or function.

To me, a blog is nice if the content is relevant and how often it's updated. I can't tell you how many times I've been to a blog site and there not be posts for months or even years at a time. From what I can see on your site, you're doing great with staying active with posting. Great job!

Collapse
maxaboxi profile image
Arto Tukki Author

The thing about portfolio site is that while every one recommends having one I personally haven't had the opportunity to show it as I said. And when it comes to building a portfolio of projects I don't have that many quality products to show outside of work. To be honest I'd say I have exactly one bigger project that is worth mentioning.

The other projects that I have built are a lot simpler just because I lack the time (and especially ideas) to do these big and great projects. And when I am building something I need to be enthusiastic about it and it has to have some real value or use case.

Outside of blogging, I wouldn't use WordPress. If I'd want to show my talents with the site, WordPress really wouldn't be my first (or even second) choice. But since that is not the case WordPress is just fine.

Thanks! I try to blog at least three times a month. So far it's been rather easy because I do enjoy writing and usually I have something to tell about my programming endeavors. :)

Collapse
mjericsson profile image
Matt Ericsson

I hear ya! I think the blog route in your case makes total sense then. That's definitely something that I haven't done with my portfolio is go into detail on how a site was built, the features used, the why, etc. It's great that I can say I've done a project, but it doesn't give the viewer total vision. I guess where I find my space here on dev.to will help mold that aspect.

That's awesome! Best of luck down the road in writing and development growth.

Collapse
chillsunfire profile image
Sunfire

Even if you haven't had a need YET to show off your portfolio, it's good to have a record of the things you've done, so you can look back later and see how you've grown.

I use WordPress for my own site (uberdreamer.tech), but only because [s] I built a custom theme for it, and [b] most of the sites I build for clients I build on WP for their convenience. If I had my say, for security and retainability reasons, I would only build non-CMS sites. Most clients don't take advantage of WP once I've handed it over, and end up coming to me when there are issues...

The thing with the portfolio site that I've found is to pick a design and stick with it, so that the only updates you need to do are to add new projects. If you spend too much time constantly changing the design of the site, you'll never really have anything else to show off, and that's time you could be spending on something else (in your case, being consistent with your writing).

Thread Thread
maxaboxi profile image
Arto Tukki Author

I'd like to think that my blog can work as a way to show my progress. Of course, reading it takes way more time than just checking out a page where I'd show my projects.

Sticking with the design was kinda hard. I always felt there was room for improvement since my designing skills are almost non-existent. But the last iteration was good and I could have stuck with it a lot longer. I just couldn't get myself to update the pages because it felt so awkward to start "working" with Django again after such a long time. Maybe if I'd used Node (like I previously had) I might have not made the switch to WP.