Design Table Podcast

You’re stuck building your portfolio. Should you use Webflow? Framer? WordPress?

Maybe you rebuild everything from scratch and start over? There are so many opinions on design social media that it is impossible to know what to do.

In this episode of the Design Table Podcast, we discuss why designers obsess over portfolio tools and why that’s (mostly) a waste of time.

We talk about what actually matters when someone reviews your work, why presentation beats platform, and how small details like having a custom domain has more impact than the tools you use.

We also cover platform tradeoffs (in case it matters), cost considerations, and when it actually makes sense to switch.

This episode is about focusing on what actually gets you hired instead of getting stuck in tool discussions. It is a must-listen for any designer building or rebuilding their portfolio.

In this episode you’ll learn:
🔸 Why portfolio tools don’t matter as much as you think
🔸 What hiring managers actually care about
🔸 What custom domains tell your audience
🔸 When platform choice does matter
🔸 The hidden cost of switching tools
🔸 Why shipping your portfolio matters more than perfecting it

⏱ Chapters
00:00 The portfolio tool debate
03:00 Why designers overthink tools
07:00 What actually matters
12:00 Custom domains and perception
18:00 Platform tradeoffs
25:00 Just ship it

Subscribe to The Design Table Podcast
https://www.designtablepodcast.com/subscribe

More about Tyler and Nick
Tyler: https://www.designtablepodcast.com/hosts/tyler-white
Nick: https://www.designtablepodcast.com/hosts/nick-groeneveld

What is Design Table Podcast?

Get a seat at the table and build the design career you want. This podcast is for designers looking to break in, level up, and take control of their careers—whether you're freelancing, climbing the corporate ladder, or just trying to get noticed. Every two weeks, we dive into career fundamentals, design best practices, and the hottest topics in the design community.

Nick:

Another benefit of coding your own website is that you will have way less platform risk.

Tyler:

Yes. Your if something goes stale or just like a security risk, like, can mitigate all that.

Nick:

Yeah. Yeah. For yeah. That that's that's true. Like, I've I do also have websites in WordPress and Webflow.

Nick:

Some projects, you know, client projects I recommend is

Tyler:

And we're officially live.

Nick:

We're officially live. Exactly. I mean, this is just an experiment. With designers, we have portfolios. Right?

Nick:

And I'm curious, Tyler, what platform or coding languages or whatever do you use to build a portfolio website?

Tyler:

My answer is a bit embarrassing because I've been using the same setup for ten plus years now. I've just been updating the same platform. So I use WordPress. Oh, I use WordPress. I know.

Tyler:

I use WordPress, and I use the Divi WordPress add on for, like, the visual editor. Yeah. The the cat's out of the bag.

Nick:

Well, nothing wrong with that. I mean, that's why we're having this discussion because I think we, as designers, we are putting way too much focus on what tool we're using for our portfolio Mhmm. With all the uncertainties that come with it. And I think you can all already see it in how you answer the question and then my reply to it Yes. Which was a bit, you know, sarcastic on my side because I I don't mind.

Nick:

Mhmm. Yeah. So I really want to take away that question maybe for entry level designers because it it really doesn't matter. I think the the tool a versus tool b is a massive waste of your energy. That's my opening statement, at least.

Tyler:

Yeah. I I think I'd I'd I'd agree. I don't think the vehicle is is irrelevant. I think it's the the work that sits on top of whatever platform, whether it's, like, Webflow, WordPress, or if you're building it, you're hand coding yourself. I think the work that you're showcasing is is the thing you're showing.

Tyler:

So regardless of, like, the the the scaffolding behind it, it's the presentation layer that matters the most. So is your is your portfolio nicely designed? Are you using the right are you using the right format to kinda communicate the case studies? I think that in itself matters the most rather than what tool you're using.

Nick:

Yeah. I think so. You know, because sometimes you see people on design community or or just in public, you know, Twitter, LinkedIn, or Reddit, or anywhere where designers gather, they say, well, I'm I'm using Squarespace. Mhmm. You know?

Nick:

And then they are embarrassed by it, and they ask if they should use something else. Mhmm. Many designers then reply saying, well, you should use Framer or Webflow or or anything cool. But I really think in that case, like, if you already have a website, you can bring your message across even though it's Squarespace or or anything else that's not Yeah. Quote, unquote designer proof approved.

Nick:

I don't really think it it matters. Like, if you can do great work in Squarespace, you know, just keep your website in Squarespace. You know? Your clients don't care.

Tyler:

No. I think, like, for me, like, from my perspective, it's not the Squarespace, like, the tool they're using. It's more from what I've seen is, like, if you have a Squarespace URL, like, that's the thing that I Oh, yeah. Like like, what is the, like, the gap to purchase, like, a $10 URL and then just update a setting in Squarespace just to remove it. Like so maybe there is a stigma, but, like, just purchasing a URL, like, someone would have to it's kind of it high it masks that whole layer.

Tyler:

So it's like, I get your upset. I'm focusing on your work, and I'm not distracted by the Squarespace slash one two three four year old that you've been given. I'm focusing on the work. That's only the one, like, the the one nuance that I'd add there.

Nick:

Yeah. So having a custom domain. No tyler white dot webflow dot I o. Like, that's not professional.

Tyler:

No. Exactly. Sure. Sure.

Nick:

Yeah. Yeah. If if you if you can, I would always go for, you know, fullname.com if it's available?

Tyler:

Yeah. Well, if people are googling you, that's a good way to rank SEO yourself.

Nick:

Yeah. Yeah. I have my myfullname.com and .nl from Netherlands because I I used to there used to be someone with the same name as mine, full name, and he was, I think, a photographer. It was very annoying that he had a .nl, and and I only had a .com. Then at some point, I saw that the website wasn't up anymore.

Nick:

And turns out the domain was available, so I purchased it, and now it redirects to the the main one. So I'm collecting a still very small, but I'm still collecting a a list of domain names around my name that I'll point to my website. Just, you know, talking about authority just to build that. I would say that's only relevant if you are located in a a non English country like I am. Fair.

Tyler:

Yeah. I think, like, the SEO play is, like, really important because, like, oftentimes I don't know if it's during the hiring process, but oftentimes, I'll go there's I know their name, and then I'll just put product designer or designer, and then they'll show up. So if I don't know your URL offhand, it's just like name, portfolio like, to rank it's very easy to rank for, like, product designer and your your first and last name. Like Yeah. That's an easy win to your point.

Nick:

I think so. You know? But then the discussion around that often is like, well, does it even matter? Is it going it's it's going to get me hired versus not hired? Or I don't think it will make that much of an impact.

Nick:

Like, it's not going to be a knockout criteria, but still someone a knockout criteria is, like, you present yourself. Like, did you think about the details? Does everything look professional and clean and that kind of stuff? And then having your own custom domain and being easy to find together is a big contributor to that answering that question with a yes. Like, yes, this person has thought of everything.

Tyler:

Yeah. And, also, like, it just feels, like, unfinished. Like, I don't know. Like like, what is your perception? If you see, like, a no domain no official domain name associated to a portfolio, it just feels like it's it was, like, recently done or hacked together versus Yeah.

Tyler:

Something that's been, like, this person's, like, established and been doing work for for a while. I don't know if that's my perception. I'm curious if that's how you perceive it as well. I

Nick:

didn't think of it yet in a way of it's just been put together just now. Mhmm. But I have an well, if if you would consider that to be a negative review of it, I do have my own negative view of it, and that's that it's well, this person couldn't even get a custom domain. You know? Yeah.

Nick:

They're cutting corners more in that regard. So so yeah. So in, you know, short answer in different ways, I also think it's not a good thing to to do.

Tyler:

But, like and for the platform, it's I think what I think it matters. I just different platforms allow you to do different things. So, like, on the execution side, it's probably, like, if you're into animations or different kind of layouts, then you're the different platforms facilitate that a bit. I've I've encountered kind of some designers that have been mentoring that are that are using a template, whether it's Framer or some kind of free free resource that just like, it's very restrictive in terms of, like, how you can kind of play with the the aesthetic treatment to it. So you're really Yeah.

Tyler:

It's one column fixed width. You can't do some like, a two column layout for, like, image and text. It's really just, like, text, image, text, image. So, like, there is, like, better there has there's an investigation stage in terms of, like, what you wanna design and, like, the limitations of the platform that it offers. Yeah.

Tyler:

Like, in terms of, like, how you

Nick:

can kind of customize it. Yeah. I I think that's an important nuance. The whole reason that I wanted to bring this up was mostly that I think we are overthinking it. But then at the other end, the opposite is also true.

Nick:

Like, it's not like it doesn't matter at all. Like, there are reasons to pick one over the other. But I just think the whole discussion of which one is best, like, overall best is a waste of your time. So what you're saying is, like, if you have some sort of creative idea in mind or something that's

Tyler:

Yeah.

Nick:

Specific or important to the type of work that you want to do more of, that's only possible in one of the, let's say, top five common website builders, well well, then it makes sense to pick the one where that is possible. But I just don't think it's it's it makes sense to switch if you currently have a perfectly fine portfolio website even though it's built in Yoongla or WordPress or Squarespace or whatever.

Tyler:

Plus there's, like, a cost, like there's a cost associated to it. Like, if I like, if everyone kinda switched to Weffle, it was, a whatever, the $25 US monthly, like, bill that comes with, like, your, like, your your yes. Your portfolio is the is the vehicle to to get more work or to to get a job. But, like, is it worth that monthly or yearly subscription tag just to host your work that you're if you're if freelance is a bit different because you're engaging with, like if you're in house, it's the thing you use once every year or once every three years when you're kinda switching. So, like, cost is a thing to be aware of as well.

Nick:

I mean, that's that's interesting. I didn't consider that yet because I there's a little bit of homework for this episode. I did come up with a list of things to ask yourself while making a choice, but I didn't consider that cost because I am a freelancer. So for me, a good website means more money. I think what you're saying is very interesting.

Nick:

Like, for you, you just need to have it. Like, when you know you're going to change jobs or lose your job

Tyler:

Mhmm.

Nick:

Then it might make sense to spend a bit more. But, like like you, when you are steady in your job, like, everything's going well, yeah, it feels like you're losing money every month if you would pay your monthly fee for any, you know, the plug in or whatever.

Tyler:

Yeah. Exactly. Yeah. So I'm paying for the the domain. I'm paying for the hosting.

Tyler:

Yeah. It's it's

Nick:

like Yeah. It's not a lot, like right? It's, like, like, 50 or $60 a year guesstimate, something like that.

Tyler:

Yeah. If that well, my we're I use so I use GoDaddy to host my WordPress because I got a really good deal. I was gonna leave or switch, and they're just like, hey. We can sign you up for three years at a for, like, whatever, $20 a year. I'm like, I'll take it.

Tyler:

It worked. It it works. I don't need to switch the WordPress. I'll take the cheaper deal. I don't it's it's something that I park in my garage and I forget about, and I dust it off, like, to your point when I need it.

Nick:

Mhmm. Yeah. Yeah. You know, recently, we talked about having your portfolio up to date at any time. So with with that in mind, you know, perhaps look at it once a quarter.

Nick:

But still, there's not a lot of that's not that's not a lot of touch points. Like, you're not working on it often. May maybe, I think, for when you're super early stage, like, entry level designer, you have no portfolio and your question is not is a or b better, but your question is which one? Perhaps it's good to list them quickly, like the main players people can choose from and Mhmm. When it makes sense to choose them versus not to choose them.

Nick:

I think that would be very educational to do.

Tyler:

Sure. Let's let's do it. I think there's a nuance like, I mean, number one, you can hand code your website, which is, like, if you have that skill set, that was more that was more relevant for me early early on in my career because I was, like, doing coding as well. And that you were judged on. So, like, there I think the stigma comes back to if you're a design engineer.

Tyler:

So if you're a design engineer specifically and you're have everything hosted in Framer versus building yourself, I think that's where the distinction is. But Yeah. I digress. So, like like, one is, like, you can build it yourself. And there's a bunch of, like, Sigma to HTML plugins that you can kind of do that.

Tyler:

It'll generate that code for you. You host it on on your provider of choice, and you're good to go.

Nick:

That's true. That sidetrack question is very important, by the way. Like, the other way around works too. Like, if you want to position yourself as a Framer expert, you should build your website in Framer because it's just a showcase of what you can do and really go all out. So that's that's the question regardless of platform.

Nick:

Like, do you

Tyler:

want to do more with that platform later on?

Nick:

Yes or no? If yes, build your portfolio there. If no, well, continue with the following things. Yeah. So so hand coding your website, I mean, it's also cheaper, right, just to to highlight that option.

Nick:

Like, I have hand coded two of my websites, and I think I pay €35 a year. That's just hosting the domain and one email address. So that's very cheap. So it's 35 a year versus 25 a month if you would go for Webflow, for example.

Tyler:

Yep. I think and the benefit of like, in general, like, the process of designing your portfolio, whether you start in Figma or you kind of well, you generally start in Figma or whatever your tool of choice. It's you're still practicing that dev handoff, but you're, I mean, you're you're basically juggling the potato back to yourself. So you're designing, and then you're implementing with the constraints of the platform. So Mhmm.

Tyler:

That's a fun exercise also. And that's what you're showing. Regardless if you hand code it or you do use another platform as well.

Nick:

It'll make you a better designer because the cliche is that there's always a designer versus developer battle. You know? And then if you play both sides, you, as a designer in particular, you'll learn, like, how challenging it can be as you're when you're also a developer, when you receive, you know, unrealistic design. Short sighted way of calling it, like unrealistic design, but, you know, it's you'll learn how to deliver clean design, and that's helpful. Another benefit of, know, coding your own website is that you will have way less platform risk.

Tyler:

Yes. Yeah. You're if something goes stale or just like Yeah. Security risk, like, you can mitigate all that.

Nick:

Yeah. Yeah. For yeah. That that's that's true. Like, I've I do also have websites in WordPress and Webflow.

Nick:

Some projects, you know, client projects, I recommend is to do one of those two. And then after a few months, they make an announcement that something changes or something is not going to be supported anymore at some stage.

Tyler:

Well, that's very annoying if you have convinced your clients to make the move to that particular platform for that reason,

Nick:

and then that reason isn't relevant anymore anymore. It's very annoying. So that's platform risk that you're more or less eliminating. Like, all you have to deal with is your hosting provider. As long as they don't go bankrupt, you're safe.

Tyler:

I know. How annoying is that that, like, you're using whether it's because I've used a bunch of, like, translation plug ins in the past where it's like, okay. This one is it's a free one that I can use for my client, and it works with WordPress. But then, well, in addition to the, like, daily, your WordPress website has been updated emails that are annoying, you have, like Yeah. When you have to update to a certain version and then the plugin is deprecated, then you have to go back to the client to your point.

Tyler:

Well, we have to go for a paid version, and that's a cost that you have to kind of Yep. Knock at their doors. Hey. We have to play for a new plugin because this one doesn't work anymore. You have to explain what that means if the if the client isn't super tech savvy.

Tyler:

Yeah.

Nick:

True. I mean, that's just annoying. You don't want to waste your time doing that. So yeah. So that's that's hand coding.

Nick:

You know? Cheap, fast, useful for your skills, no platform risk, or very low. We would still have to make or announce your preference. You know? WordPress, I think it's they're so big.

Nick:

Like, so many websites use WordPress that we cannot ignore it. You know?

Tyler:

Yeah. I I I like WordPress well, I like the WordPress Divi combo just because I used, like, the Divi so the Divi plugin is just, something you could add on. It's like a

Nick:

It's page builder.

Tyler:

Now it. Yep. It's a page builder. Exactly. It's a and it's evolved now where it almost resembles Webflow in terms of its UI.

Tyler:

But I used to use it on a lot when I was in my agency days. We used to use that to kind of quickly build out a website. So in the case where the developers are busy, the designers would you would design and use WordPress and Divi to kind of build things out. Yeah. Because, like, the drag and drop like, it's easy to translate your design to to a Divi layout because it's pretty flexible.

Tyler:

Yeah. And then you just do a bit of CSS in the background for, like, the little design touches. But it's a heavy it's a heavy platform to use. So it comes with a lot of bloat for sure.

Nick:

K. So when you say heavy heavy in a sense of website performance, like loading times and that kind of stuff.

Tyler:

Yeah. Like, if you were to compare it to, like, hand coding a thing, like Mhmm. It's leaves in bed. Like, it's probably, like, 20 x the size Yeah. For something that's essentially just a a presentation website.

Tyler:

Yeah. There's no functionality. It's just, like, page, like, homepage work my work about me, a contact form. Yeah. It's it's it's it's excessive.

Tyler:

Like, if you look at it practically, like, WordPress is it's a bit excessive for what for the job that it needs to perform.

Nick:

That's true. Yeah. Yeah. Yeah. I I migrated one of my websites from WordPress to hand coded.

Nick:

Mhmm. And while doing so, I added a bunch of extra features. So the website became bigger, but the website on WordPress in total was over 400 megabytes, like, everything put together. And then after the migration, it was 12, you know, same website. There you go.

Tyler:

There you go.

Nick:

So that's that's, you know, that that makes difference. So I I think, like, 40% of the web runs on WordPress. So if you let's say you're a freelancer and you want to focus on web design or landing pages for local entrepreneurs or small to medium sized businesses, learning WordPress makes a lot of sense because it's just so easy to use, so cheap to use. And that type of client usually doesn't really care about fancy, you know, framer specific animations. They just want the website so that people can call them and buy something at their store, you know, and then just move on.

Nick:

Like, they don't really care. So with that in mind, WordPress makes a lot of sense. It's just the biggest player. Although Yeah. We designers don't really like it anymore.

Tyler:

Yeah. Exactly. And plus it's, like, it's easy to use. Like, the plugins, you can add any plugin you want, like, within within Reason. Mhmm.

Tyler:

And then you can, like you can unlock SEO. You can do translate this. It's a it's a well kind of it's 40% of the web to your point. Like, you can quickly get something done. Yeah.

Tyler:

And it has all the plugins you can just to do whatever you need to get done.

Nick:

I I think that's also the downside of WordPress because there are so many different plugins to use. And then for each thing you want to achieve, you have so many plugins just to choose from for one thing that you want to do. With the platform risk of, you know, someone hacked together their own plugin, and then you use it, you depend on it,

Tyler:

and then at some point,

Nick:

they just stop updating it. And then WordPress has an update, and your plug in breaks. And because of that, your whole website breaks. Yeah. So it's that well, that's just annoying if that happens.

Nick:

Yeah. And that's a risk you're running, plus and the bloatiness, if that's even a worse, that can get very bloated like we just said. Mhmm. And many plugins are premium premium in a way of it being paid. So I moved yet another website from WordPress to Webflow.

Nick:

You know, WordPress is quote, unquote free, and Webflow is $25 a month plus your workspace costs. But I actually went down in total costs because of all the the paid plugins that I could cancel from WordPress. So still an expensive website, but, yeah, there's a lot of hidden costs potentially if you want to do more in WordPress.

Tyler:

Yes. Definitely. Shoot. Yes. On so on Webflow yeah.

Tyler:

Webflow is an option. I mean, there's a there's a bunch of, like, Figma to to Webflow plugins where you can translate your design quite easily. It resembles a Figma or a design tool, so it's it's it's the trend like, the I mean, there's still the the learning curve, but it's probably less steep for going from like, if you wanna hand code something or you wanna use work WordPress, it's it's a familiar tool to a designer if you if you look at, like, the the UI treatment, like, how you and how you build things.

Nick:

Yeah. That's true. I think Framer has it even more. Like, Framer really is is like your your base basically, your on the web. Just turning that into a verb, like.

Nick:

Well and it like, the difference is very subtle, but I think, like, Webflow, you're visually developing, and frame is the other way around. Like, you're designing in code, basically. So if you are a d if you if if that makes sense, like, really took me a long time to to wrap my head around it. If you have a little bit of maybe if you have a technical background or if you just enjoy code, Webflow will be easier for you to learn compared to

Tyler:

when you do not have a technical background or just an eye for for code because they in Webflow, they

Nick:

will ask you a lot about CSS properties Yep. And variables and all that kind of stuff. While in Frabre, it's more drag and drop and just clicking and selecting. So it does yeah. Visual people, Framer, technical people, Webflow is what I would say.

Tyler:

Yeah. I don't know what the risk there is. Like, the difference between, like, Webflow to your point, like, it's a bit technical because it's, like, it's it's spitting out code at semantic. So, like, you'll notice, like, as you're using the tools or the settings that it it's one to one to how you would kind of hand code things. So, like, you'd have the padding properties.

Tyler:

You have, like, the the flex box or or kind of table settings. Like, it's I feel like it spits out cleaner code. I don't know. I haven't I don't have a lot of experience using Framer. But, like, if you're designing and it spits out code, I'm just wondering what the quality of code it's spitting

Nick:

out Mhmm.

Tyler:

Yeah. What that looks like.

Nick:

I I can say something about it, but that's based on today's output or, let's say, the last three months. So maybe that will change in in the future, but what I know now is that out of the box, Webflow is a bit performance wise, a bit quicker than WordPress. That's what I noticed. Framer, I've seen a few horror stories on Framer in terms of SEO and how it's rendered, but they are working on it. Like, last time I used Framer, they has, you know, more SEO properties that you could play around with.

Nick:

So I think currently, Webflow is a little bit in the leads compared to those three big players in terms of code output. But I would stay, you know, relatively because compared to a hand coded website, even Webflow would be bloaty.

Tyler:

And there's a I think I don't know if you brought this up to my attention, but, like, the Google, like, SEO rules changed on, like, the the size of your website. Like, it there's a cutoff now. Like, if your website now exceeds, like, 10 megabytes

Nick:

Mhmm.

Tyler:

That's where it's gonna stop. So if it's scanning your website and then it reaches that kind of 10 megabyte limit

Nick:

Yeah.

Tyler:

It will not scan the rest. So there's a risk of, like, not having your website be SEO friendly because it can't be crawled to completion. Yeah. Was that Yeah. That true?

Tyler:

I I didn't bring it up to you, but I did read about it

Nick:

and the discussion around it and people being frustrated or scared or or insecure about it, which makes sense. Like, imagine you have your perfect website, and then it's just cut off, and then it means you're losing business. You know, that's not a fun place to be in. At the same time, I'm also thinking, like, if you have a page over 10 megabytes, that's massive already. That's an unoptimized page.

Nick:

So I think you should shouldn't be in that position.

Tyler:

And, like, that's, like, the consequence of, like, the overutilization of SVG images. So, like Mhmm. Now you can translate like, if you create a UI in Figma, you can now export that as an SVG. Yeah. But the output of that so let's say, for example, you have an image of, like, a UI and it contains, like it it's pretty complex, but, like, the the output of that export is is like a like a thousand lines just to kind of render that that image.

Tyler:

I think that's what's happening there. It's like the overuse of, like, SVG images. Mhmm. I mean, the benefit of using SVG images is that, like, the quality is, like, perfect on desktop, mobile. It's like it's solid, but, like

Nick:

On an airplane? Even? Yes. Yeah. Yeah.

Nick:

No. No. You're you're right. When I say airplane, I mean, like, stretched out on the side as a print because it's scalable. Not on the airplane Internet.

Nick:

Yes. So that's true. Like, what I know is just a quick tip. Like, if you are going to SVG export your dashboard Mhmm. It will also try and turn an image inside of the dashboard into code.

Nick:

So if you have your profile picture in the top right corner for a menu like a profile picture, that will make the SVG way bigger. Like, if it's just layers, you know, then that will really save you a lot of weight in the SVG output. So but ask yourself, like, does the image really need to be there to get my point across? If no, take it out. If yes, make sure you optimize the image before you click export.

Nick:

So if it's a 32 by 32 profile picture, but you put in a full HD image and you just shrunk it, you know, the file will still be quite big. So make sure that you made the the file the the image file very small first and then put it in. So there's a bit of Thigma hygiene that you need to take into account there to just to save yourself there. And one thing before I forget about that 10 megabytes cut off is you really need first need to think about where your traffic is coming from just to determine if it's a problem or not. Like, if you are, like, SEO heavy, like, all your leads are inbound from people finding you online through Google or or ChatGPT or different means, then it's a problem.

Nick:

But if you let's say you're a design influencer, you have 100,000 followers and people find you through LinkedIn just because you're sharing an image of your work, then it doesn't really matter, you know, because they will find you through social. You know? So don't panic just yet. Take a step back. Answer those questions for you, and then decide if you should panic.

Nick:

Yeah. Full disclaimer, I am a Webflow certified partner. Know? So I'm deep in the Webflow camp, but I'm trying to be as transparent and objective here as possible. Like, I'm not a a fanboy even though I work primarily in Webflow.

Tyler:

Well, I mean, to your point, if you're certified, your website should be in kind. Right? And then speaking

Nick:

of, not it's not something you can just guess, like like, I mean, sure. It doesn't really mean too much, but still, they you will need to showcase three websites, and they will review it and decide if you're good enough to get the label. So I have at least three good websites, which isn't a lot still. But but yeah. But it's it it has it it holds some weight, a little bit of weight.

Tyler:

Well, a little SEO weight as well.

Nick:

Yeah. True. True. I should brag about it more on my website, which I currently do not do. Anyway, you you wanted to say something.

Nick:

Please please call.

Tyler:

I think one one that that's probably relatively newish. You can probably another vehicle is Figma Make. You can Mhmm. If you wanna stay within Figma, you can now create a website, slap on a URL, and then generate everything in Figma itself. So you don't never have to choose another platform or do that to kind of hand off.

Tyler:

It'll do it for you, which is which is nice.

Nick:

Is that is yeah. And so so because you have Figma design, that's the original Figma, then your Figma make, that's their generative tool. But then that's different from Figma sites. Right? It was Figma sites was also something.

Nick:

Right? So then you would go through all three steps. Right? Or am I mistaken there? So you you generate something in Make, and then you put it in Sites?

Tyler:

Or I was

Nick:

thinking connecting. I don't know. Well, social media gurus a few months ago told us everything else was done. So I imagine you can scratch everything we just said and just do Figma Sites.

Tyler:

I don't even know if Figma Sites is a thing anymore. I think it's now all no. Oh, Figma Sites. It's still in beta. Mhmm.

Nick:

Let well, let let's just pause a real quick moment here just to consider that. Like, when they announced Figma Sites, like, everyone was falling over each other saying on social media, like, they are going to overtake Webflow. WordPress is dead. Framer is dead. They're going to acquire blah blah blah blah.

Nick:

All sorts of nonsense. And then now it's a few months or maybe even a year later, and you have two seniors designers here talking, and then they're like, does it even exist? So don't don't take people too serious on the Internet. Like, they they they're all just in an echo chamber talking the same thing just to get a few clicks.

Tyler:

Exactly. Yeah. It's

Nick:

Do your do your own thing. Stay in WordPress. Stay in Squarespace. It doesn't matter.

Tyler:

It it honestly doesn't matter. Mhmm. It's really it's like like your plus, like, on the job, you don't get to choose what platform the your client works on. So Yeah. Sometimes you're holding to, like, their choice.

Tyler:

So pick one and then deal with the the constraints

Nick:

Yeah.

Tyler:

Accordingly. Yeah.

Nick:

Yeah. I mean, if we would summarize all of this, I think then we would say, like, if you have a website, stick to it. You know, if you can design what you have in mind on that platform. It's all fine. Nobody cares.

Nick:

Get your custom domain. That's important. And, yeah, depending on your clients or your goal, pick the the platform that fits, you know, based on what we just discussed. Right? But don't overthink it.

Nick:

Pick one, get started, and go live. That

Tyler:

was a great episode. So if you like this content and wanna hear more, please like and subscribe.

Nick:

Yeah. And if you want to see more, please go to designtablepodcast.com, Spotify, Apple Music, all the big players, and more.