Portfolio with a blog
A portfolio blog website is a single site where your work and your writing live together, so a reader who finishes a case study lands on your next post instead of a dead end. In Folio the blog is not a bolted-on second app: the blog index, every post page, and the tag and category archives render through the same theme as your portfolio, so changing your design never leaves the writing looking like a different website. Publishing is free at portfolio.wrxstack.com/yourname, and mapping a domain you own is a Pro feature at Rs 599 or $9 a month.
Put the work and the writing on the same site.
Start with no card. Free publishes at portfolio.wrxstack.com/yourname with a Made with Folio credit, 10 core designs, and 10 AI drafts a month; your own domain and the full gallery of 60 sit on Pro. The resume PDF and DOCX come out unwatermarked either way.
What you get
Most builders sell you a website and then sell you a blog module to nail onto it. Folio ships one profile that renders both surfaces.
One theme
The blog index, every post, and each tag and category archive are drawn by the theme you already picked, using the same navigation and footer as your case studies. Switch designs and the writing switches with it in the same pass.
Post SEO
A native, deterministic checker reads the draft in-process with no external model and no network call. It checks title length, meta description, slug, keyphrase placement, word count, readability, excerpt, links, and image alt text, then hands back a letter grade from A to F and the exact line to fix.
Internal links
Folio reads your other published posts and proposes internal links that actually fit the draft in front of you. That is the part of blog SEO nearly everyone skips, and it is the part that compounds.
Structure
A post carries a category, tags, an excerpt, a cover image with alt text, an author line, and a canonical URL if it ran somewhere else first. Feature the ones that matter, queue the rest with a publish date.
Distribution
Your posts and case studies go out together in one RSS feed, readers subscribe from the site itself, and the contact form drops into an inbox that belongs to you rather than to a platform.
Structured data
Folio emits the JSON-LD for the post, the blog index, and the breadcrumb trail on every render, so a crawler reads a dated article with an author instead of guessing at a page of text.
Build your blog portfolio
Start with the work. The writing has more to say once there is something for it to point at.
01
Paste a resume or a few lines about yourself and Folio structures a first draft of the site, projects and all. You edit every word before anything is public.
02
Free gives you 10 core designs; all 60 are on Pro. Whichever you pick governs the portfolio, the case studies, and the blog together, so there is no second theme to keep in sync.
03
Compose in the editor, set a category and tags, add a cover image with alt text, and name a focus keyphrase so the checker can grade where it lands.
04
Under 300 words fails outright. Under 600 warns. The checker also tells you when your slug is noisy, your meta description is the wrong length, or the keyphrase never reaches a heading.
05
Set it live now or give it a future date and walk away. The post joins the index, its archives, the sitemap, and the RSS feed on its own.
Blog portfolio ideas
The blog exists to prove judgment. A case study shows what you shipped; a post shows how you decided. Six shapes that work, in rough order of how easy they are to start.
Teardown
Take one call from a project, lay out the option you rejected, and say what changed your mind. This is the single most convincing post most people can write, and it takes an afternoon.
Process
The messy middle of one project: the discarded direction, the constraint that reshaped it, the thing the client asked for that you talked them out of. Link it from that case study.
Teaching
Whatever colleagues keep pinging you to explain is a post with a built-in audience. Teaching is the fastest way to read as senior without saying the word senior.
Field notes
A short, dated log of what you tried, what broke, and what you would do differently. Low effort per post, and it proves you are still moving.
Tools
The stack, the plugins, the shortcuts, and the reasoning behind each. These posts get bookmarked and shared, which is how a portfolio gets read by people who did not come looking for you.
Results
Pick one measurable outcome you own and walk through how it moved. Keep it honest about what you cannot attribute to yourself. That caveat is what makes the rest credible.
How it compares
The general builders all let you add a blog. The question is whether it is the same thing as your portfolio, or a second thing you now have to maintain.
| Capability | Folio | Wix | Squarespace | Webflow | Medium |
|---|---|---|---|---|---|
| Blog and portfolio share one theme | One theme renders both | Blog is an app you add | A separate collection to style | A CMS collection you design yourself | Blog only, no portfolio |
| Per-post SEO grade | Deterministic checker, A to F | SEO fields, no grade | SEO fields, no grade | SEO fields, no grade | Little control |
| Internal-link suggestions | Reads your published posts | Not offered | Not offered | Not offered | Not offered |
| Resume and ATS score in the same account | Built in, PDF and DOCX free | Not offered | Not offered | Not offered | Not offered |
| Your own domain | Pro, Rs 599 or $9 a month | A paid plan is required | A paid plan is required | A paid plan is required | Posts sit under Medium |
Cells describe the published shape of each vendor's free and paid tiers, which any of them can change, so read their pricing page before you commit. Folio is held to the same rule here: Free has zero custom domains and 10 of the 60 designs, and it shows a Made with Folio credit. Only the blog, the portfolio, the resume, and its exports are unconditional.
The numbers, including the awkward ones
Every figure below is a product fact you can check on the pricing page.
1
profile behind both surfaces
the blog cannot desync from the work
10
core designs on Free
the other 50 are on Pro
0
custom domains on Free
you publish on a Folio address
$0
to publish and to export
no watermark on the resume file
Portfolio blog design
The tell of a bolted-on blog is small and it is fatal. The type on the post page is a size the rest of the site never uses. The nav loses an item. The footer changes. A reader does not articulate any of this, they just feel the seam and click away, and the piece of writing you spent a Sunday on stops doing the job you wrote it to do.
That failure is structural, not aesthetic. It happens because the blog and the site were built by two different systems that happen to sit on one domain. Folio does not have that seam to fix, because there is nothing to keep in sync: the post pages come out of the same theme, the same navigation, and the same profile as your projects. Pick a new design at midnight and by the time the page reloads, every archive, every tag, and every post you have ever published is already wearing it.
So the design question stops being about the blog at all. Choose the site you want to be read on, write things worth linking to, and let the case studies and the posts point at each other. That is the whole trick, and one product is the only way to get it without maintenance.
FAQ
Nothing to start. Writing, publishing, the SEO checker, the RSS feed, the newsletter signup, and the resume exports all sit on Free, with no card taken at signup. The edges are real and worth knowing before you invest a weekend: Free publishes at portfolio.wrxstack.com/yourname rather than an address you own, a small Made with Folio credit appears on the site, AI drafting stops at 10 generations a month, and you choose from 10 designs instead of all 60. Pro lifts those at Rs 599 or $9 a month.
Yes, and on Folio you have to. The Free plan includes zero custom domains, so your posts go live under a Folio address with your handle on it, which is enough to be indexed, shared, and put on a resume. Buying and mapping your own name is a Pro feature: point two DNS records at Folio and the certificate is issued for you. Nothing you wrote is stranded when you move, because the posts and their slugs come with you.
Write the things a case study cannot hold. The decision you almost got wrong, the direction you threw away, the constraint that reshaped a project, the question colleagues keep asking you, the number you moved and the part of it you cannot honestly claim. A portfolio proves you shipped. A blog next to it proves you think, which is the thing a hiring manager is actually trying to work out from the other side of the screen.
Folio applies a hard floor and a soft one. Under 300 words the checker fails the draft outright, because there is not enough on the page for a search engine to rank. Between 300 and 600 it warns you. Past 600 it passes, and it stops nagging you about length so it can nag you about the slug instead. Depth beats padding: a 700-word post that answers one question completely will outlive a 2,000-word post that circles it.
It depends on what the blog is for. If you want an audience and nothing else, a dedicated writing platform is fine, and your work will live under its brand. If the blog exists to make people trust the work and hire you, it belongs on the same site as the work, sharing a nav and a design, so the reader can cross from an essay to a project in one click. That is a different requirement, and it is the one Folio was built for.
It can give you a first draft, and Free covers 10 of those a month. Be clear about the split under the hood: the generative draft calls an external model, while every piece of analysis is native and deterministic and never leaves the server. The SEO grade, the keyphrase checks, the readability score, and the internal-link suggestions are rules, not a model, so the same draft always scores the same. Whatever comes back, it is a starting point. Rewrite it in your voice before you publish it under your name.
Keep going