DEV Community

Filippo Ferrando Damillano
Filippo Ferrando Damillano

Posted on

What technology would you use to create a portfolio?

Hi to all1, I'm struggling to choose a framework/thing to create my portfolio; i don't want a complicated thing, like many page or something, what i was thinking is much more a responsive, beautiful, single page site to describe me in some words.
Can you give me some advices? Thanks to All!

Top comments (54)

Collapse
 
jonrandy profile image
Jon Randy πŸŽ–οΈ • Edited

I would recommend not making one, an interesting and active GitHub account (warts and all) is a much better way for employers to get an idea of your capabilities

Collapse
 
twwli profile image
Olivier Guillard

An active GitHub account is not always a good indicator. In my case, the majority of the projects I've worked on over the past few years are confidential, hence absent from my public Github. Therefore, in my case, a portfolio is more than necessary.

Collapse
 
jonrandy profile image
Jon Randy πŸŽ–οΈ

What's in the portfolio if the majority of projects are confidential?

Thread Thread
 
twwli profile image
Olivier Guillard

Unfortunately, I cannot display them in my portfolio neither.

Collapse
 
zoreankit profile image
Ankit Zore

How do i start contributing to OSS most of the time it seems overwhelming don't know where to start. I have contributed in some issue fixes with PR but those projects are not much active(PR were not reviewed). I want to participate in contributing OSS do you have any advice?

Collapse
 
guithomas profile image
Guilherme Thomas

Look for "good first issues". It's the best way I know to start contributing to OSS.

Thread Thread
 
zoreankit profile image
Ankit Zore

Thankyou

Collapse
 
p_s_1fb5f6a94548da9bd1865 profile image
P S

Never hurts to have one!

Collapse
 
jonrandy profile image
Jon Randy πŸŽ–οΈ

Actually not true. A poorly constructed portfolio has been a key reason for me not hiring a good few developers

Collapse
 
twankrui profile image
Twan kruiswijk

Lately I've been going back to plain old HTML, CSS, and some JS. If I don't need to fetch any data, it's the fastest/most simple way to get something online.

However, my personal site is written in Remix.JS (for the blog and some other small shenanigans. NextJS is also a great option.

Collapse
 
p2510 profile image
YATACHI

i used nuxt . because ... , i think that it's simple . if i don't need to call api or add system "send me a message " , i choose html/css/js . excuse me for my level of langage , i speak french . bood luck

Collapse
 
skylersaville profile image
Skyler Saville

Love me some Nuxt

Collapse
 
rdfilippo profile image
Filippo Ferrando Damillano

Hey! i have some updates, i've just finished writing my portfolio (even if it is not quite finished).
At the end i've used AstroJS with the portfolio theme (i'm not great at UI design).
So the end result is like this:

filippo-ferrando.github.io/

Thanks to all for the suggestions!!!

Collapse
 
colthands profile image
Aleksey • Edited

I'd say some static site renderer will do the job, but just plain old html/css/js just works as fine as it can.

But those static site generators use so much useless boilerplate.

Eleventy 11ty is a really good solution, a SSG, but no react or vue, just like we used to have an express.js with pug, jade, or ejs templates back in the day when people used ember.js because angualar sucked, but on frontend.

Collapse
 
hnrq profile image
Henrique Ramos • Edited

I'd use Svelte, mainly because of its performance and the flip function, which helps animating things. For styling, probably I'd go w/ Sass. Also, if I wanted some complex animations, I'd use GSAP

Collapse
 
vlajd profile image
Vlajd • Edited

I'm currently working on my own portfolio page using Svelte (actually for the first time using it), and I think I'll never want to go back to plain HTML/CSS/ja ever again. I've never experienced sooo much convenience ever, especially when it comes to interactivity and responsiveness.

So I'd go for Svelte, main points are easy to use/learn and install and super lightweight.

Collapse
 
jwhenry3 profile image
Justin Henry

For starters, I'd suggest that each of your projects in Github (that you want to be seen by potential employers) should use github.io (github pages) to host your demo/documentation in a presentable way. This tells them that you care about how your projects are consumed and that you care about the developers consuming them.

I would reference those github pages on your portfolio site with maybe a screenshot of each project (would be even better if you can set up SEO for the project and have it give you that out of the box).

For the actual stack of the portfolio site, use whatever tools come natural to you, whether it's plain (html, css, js) or react/angular/solidjs/vue/svelte.
There is no wrong way to go about it, but if you use the tools you want to develop for within your portfolio site, it is more impressive since it is a showcase in itself that you are experienced with the tools.

Collapse
 
stk_79 profile image
Sarthak Pati

Nice Explanation πŸ’―

Collapse
 
crtl profile image
crtl • Edited

Plain old CSS/SCSS,JS and HTML maybe some PHP if required.
I never understood why anyone would use frameworks like React with SSG or SSR for their own portfolio site...

Collapse
 
rdfilippo profile image
Filippo Ferrando Damillano

Can you explain what SSG ans SSR are? i never seen this terms

Collapse
 
crtl profile image
crtl • Edited

SSG is Static Site Generation meaning the code is executed at buildtime to produce a static html file with the components (in case of react) already rendered.
SSR is Server Side Rendering which does the same but on the server side for each request (if not cached)

Collapse
 
codewithcaen profile image
CodeWithCaen • Edited

If you are a frontend developer I would suggest seeing building a portfolio as a fun challenge with some new technology as a way to learn. However if you just want to get something online quickly and without much effort, I'd suggest using some kind of static site generator. I built one that's free and open-source called HydePHP. You can create a great looking site that "just works" out of the box. You can even create all your content in Markdown. All the TailwindCSS styles are already there as it Hyde comes with a great starter kit and frontend template that's both responsive and has a dark theme. The site then gets compiled to static HTML which is easy cheap and fast to deploy.

You can learn more at hydephp.com/, and feel free to ping me if you have any questions!