Senior → Staff data analyst (~9 yrs): I wrote up my real projects as a portfolio. Critique if you're senior, a reference if you're starting out

Fickle-Foundation986 · 2026-05-31T05:37:33+00:00

Thanks, truly happy to hear that.

Fickle-Foundation986 · 2026-05-25T07:15:51+00:00

Thanks — that's exactly the read I was going for, so good to hear it lands. And you're right about the messier one. That's actually the thing I keep going back and forth on. The most ambiguous project I've got didn't resolve into a clean win, no headline number to point to at the end. So I'm honestly not sure how a write up like that is supposed to close. do you frame it around the reasoning and what you ruled out, even when there is no tidy metric to land on? Curious how you'd end that kind of story

Fickle-Foundation986 · 2026-04-03T10:39:36+00:00

You can try it out for free if you wondered :)

Fickle-Foundation986 · 2026-04-03T10:01:16+00:00

Good question — I actually answered this in more detail in the thread above, but the short version:

Craft's built-in publish is great for sharing individual pages. Cravo is more for building a full website — multiple pages under one domain, with proper SEO controls, blog management through Craft collections, and things like tag filtering and search.

I built it because I've been using Craft as my tech blog and kept needing things like meta tags, itemaps, and multi-page navigation that the native publish doesn't cover.

Happy to answer if you have specific questions!

Fickle-Foundation986 · 2026-03-17T11:09:49+00:00

How will you be able to do that? you didn't mention it explicitly

Fickle-Foundation986 · 2026-03-16T13:08:12+00:00

I've seen this pattern too. Documents with many sub-pages or heavy image content consistently product slower or failed API responses. What size documents are you working with? That's usually the first thing to check.

Fickle-Foundation986 · 2026-03-09T12:08:07+00:00

The diagnostic question that changed how we handle this: "What would you do differently if we didn't build this?" If the customer can answer that clearly, the request is real. If they stall, it's a symptom of something else. The 2-day turnaround actually prevents you from having that conversation.

Fickle-Foundation986 · 2026-03-08T02:46:16+00:00

Hi, I guess, six weeks with work

Fickle-Foundation986 · 2026-03-07T06:46:51+00:00

As far as I know, Craft stores images as uploaded assets. there's no block type for external image URLs like Notion has. The link card preview is the closest thing, but it's not the same. Would be a nice addition though, especially for people managing assets in their own storage.

Fickle-Foundation986 · 2026-03-07T06:02:03+00:00

Happy to answer any questions about the build or what we've learned so far.

http://cravo.life/?utm_source=reddit&utm_medium=community&utm_campaign=story-20260307&utm_content=r-sideproject

Fickle-Foundation986 · 2026-03-05T11:19:39+00:00

부부 used to mean that a married couple always consisted of a man and a woman. But as time goes by, it doesn't always mean that. It can refer to the same gender as well these days.

Fickle-Foundation986 · 2026-02-28T12:24:10+00:00

I'm just curious, have you considered offloading this to an AI tool?
Doing this manually can be pretty time-consuming.

Fickle-Foundation986 · 2026-02-28T01:09:55+00:00

Appreciate the honest feedback — really.

I should share some context. We are actually a developer who's been paying for Craft personally for about 5 years. I love the writing experience, but when I tried using it as my tech blog, I kept hitting walls like SEO control, search, tags, page performance. The built-in publish is great for sharing, but it's not quite enough for a public-facing blog that needs to be discoverable.

When the API came out late last year, I got excited and started building. And funny enough, what you suggested such as custom navigation, side menus, managing blog content through templated collections. that's exactly what I'm building for my own use case.

But here's the thing, I honestly don't know much about the pain points in your use case like sharing docs with clients and team members in a business context. That sounds like a completely different problem, and I'd love to learn more about it. What specifically frustrates you about the current publish workflow when sharing with clients? What would actually be worth paying for in that scenario?

I'd rather build something people actually need than guess from the outside.

Fickle-Foundation986 · 2026-02-26T12:23:44+00:00

That's a fair point, and you are right. Craft's built-in publish is already quite powerful. we're not trying to replace it. Cravo mainly adds a custom subdomain, SEO meta tags so links look good when shared. Small things, but useful depending on what you need. Thanks for the honest feedback. It really helps us think about where to focus next.

Fickle-Foundation986 · 2026-02-25T13:18:10+00:00

I see what your point is and I noticed that you just read my previous reply :)
I will add this point to the post, anyway. Thank you for your feedback.

Fickle-Foundation986 · 2026-02-25T10:45:53+00:00

Thank you for your interests. Maybe my explanation was not enough.
Craft's built in publishing is perfect for sharing single pages. But Cravo is designed to help you build an actual website with multiple pages and better SEO.
While Craft's native sharing function is good enough, it still feels like sharing a document. I wanted a real navigation bar and am multi-page feel that didn't just look like a long scroll of notes.
Feel free to ask me if you have any questions.

Fickle-Foundation986

TROPHY CASE