Community forum for knowledge and support

Updated 2 months ago

Building a Portfolio of Fictitious Company Websites with Relume

At a glance

The community member is creating websites for fictitious companies to build a portfolio, and wants to know if they can have each site in a separate folder under /portfolio/site-name while maintaining unique class names and styles that don't interfere with their core website. The comments suggest that building each site as a separate Webflow project would be a more reliable approach, as it would allow for read-only links to be shared and make it easier to track and maintain changes across the different sites. The comments also indicate that using a Webflow.io project link would not be seen negatively by potential employers.

I'm making some websites for fictitious companies I made up, coz I feel that not having a portfolio is killing my sales potential.

What I want to do is have these sites as a folder under /portfolio/site-name.. But I know there's the global styles and the style guide for each site made with Relume.

Is there a way to do this in Relume where I can have a complete site under a folder and it would have its own unique class names etc. so it doesn't interfere with my core website styles?

M
A
4 comments

@Alex Quintana really doubt that this would work reliably. Would argue that while having a portfolio certainly is important - ensuring whatever work you do have in your portfolio is error-free. Especially when it comes to showing off your webflow skiils.

I would highly recommend that you just build each site in their own webflow project. This also will help to reveal a read-only link for each build which I feel would be a really great idea as somebody who would be looking to hire - I would want to look under the hood as quickly into the hiring process as possible and if its a link on a portfolio - even better.

That's just my two cents.

Biggest risk I see is that you accidentally make a change to a class that is being shared across these sites and it would be relatively hard to track what may or may not have broken because of said change. You'd constantly have to be QAing your projects as you build.

as somebody hiring, I would not look down upon a webflow.io project link either

as somebody hiring, I would not look down upon a webflow.io project link either

That's a good idea. I doubt that any prospective clients would care that it's a webflow.io link

Add a reply
Sign up and join the conversation on Slack