#Strapi as a CMS for an Astro marketing/portfolio site? Or DecapCMS or TinaCMS...?

29 messages · Page 1 of 1 (latest)

still fulcrum
#

Hey, what are peoples views on using Strapi as the headless for a statically built personal site with things like portfolio items and blog posts? Is it overkill?

I often enjoy git-based CMSs due to the ease of use with GitHub and free hosting on Netlify, but I'm wondering if people have used it for this and found it a good choice? Main downside I currently see is having to pay for hosting - unless there is a free way to do so?

Currently my go-to has been NetlifyCMS, but now that's changing to Decap, I'm uncertain if it's stable to using in production for the time being? I've also considered TinaCMS.

Thanks for any advice/input! I just want something free/inexpensive for my clients that is nice and user-friendly.

still fulcrum
#

Also just checked out hygraph which has a pretty nice free plan

oak narwhal
still fulcrum
#

@oak narwhal Yeah true... would you say that's there business plan to trap people in with the free plan first... Free plan seemed pretty generous to me for a the scale of a portfolio or marketing site?

still fulcrum
#

As an ever ongoing process of Lucian looks for the bestest CMS ever, I am now look at Sanity's free plan and liking the look of that more than hygraph

oak narwhal
#

Yes, I like sanity’s free/pay as you go tier a lot. Hygraph free tier is fine as well, most won’t reach the limits of that plan.

#

But I’d like to invest my time learning something that can benefit a large range of clients, from small portfolio site to corporation.

#

That and I want to do as little devops as possible. That’s why I settled on sanity

still fulcrum
#

Very nice justifications and I agree with your motives - I am also leaning towards Sanity a lot - it looks pretty great with friendly scalability!

wraith blaze
#

Shameless plug to Keystatic ⚡️ - you might find it interesting: https://keystatic.thinkmill.com.au

Keystatic

Keystatic is a new tool from Thinkmill Labs that opens up your code-based content (written in Markdown, JSON or YAML) to contributors who aren't technical.

tawdry echo
#

👋 Hi there! Thinkmill founder here, we're making Keystatic. Absolutely not here to bash other CMS’s, and +1 for Sanity if you want to go down the “hosted API CMS” route

But we’re doing some pretty new stuff with Keystatic, and really working to make it the CMS for Astro sites.

You embed it inside your Astro site (it’s just a dependency you add, kind of like adding storybook to a project) and it gets deployed with your site as well. So there’s no additional infra or cost associated with it, and you can edit content locally or live (that part’s a lot like NetlifyCMS except you don’t have to host it separately)

For content it stores your choice of YAML / JSON / and Markdoc... and we’ve nearly got it working seamlessly with Astro Content Collections. So it really has no impact on your build process, how you query content, live reload, speed, branch preview deploys, etc, all the good stuff we love about Astro. Drafting, publishing etc is all GitHub workflows, you edit on branches then open a PR.

Anyway I don’t mean to make this into too much of a sales pitch, but if you’d like to learn more or give it a go let me or @wraith blaze know, we’re super keen for feedback from the Astro community!

(oh also it’s free and open source, and we’re not going to do a licence rug-pull at any point)

still fulcrum
#

Sounds very interesting thanks for your input both! I will definitely keep an eye on it - would you say it's not quite ready to be used in production for clients though seeing as it's still early days?

Thanks for brining it up though, it sounds like potentially an alternative to me for NeltifyCMS (now DecapCMS...). I really liked the simplicity of NetlifyCMS but I just found the editor experience a bit... meh. I want something really nice, clean and organised for clients to use

oak narwhal
#

Oh yeah, that looks really cool. I think I tried it a month ago and it worked at first but quickly afterwards failed to build for inscrutable reasons. I’ll give it another try.

vital folio
tawdry echo
# vital folio Hi. When are you going to make a language switch? And how do you make md files i...

We're planning to add a language switch soon (hopefully the next few weeks) but in the meantime, which will be a nice UX improvement, but in the meantime you should be able to get all the files in subfolders to be visible/editable by treating the language as part of the slug. See the path docs here: https://keystatic.com/docs/path-configuration#nested-slug-example

Granular control over where Keystatic stores content.

vital folio
#

I understand correctly that it is now impossible to regulate which folder a new file goes to?

#

oh, I get it. In the slug you need to specify the folder name/file name. That works now, thanks

tawdry echo
#

That's sort of correct — content authors will be able to put whatever they like in the ** part of the path, by entering it into the slug field.

So e.g if you want to create a new Hello World blog post in French, and you had the content structure

path: '/content/blog/{language}/{post-slug}

then ideally the content author will enter fr/hello-world as the slug in the Admin UI.

If they enter something unexpected like crazy/post/slug then ... you can't prevent that (yet)

#

Sounds like you got it working while I was typing the answer though 🙂

#

Our plan is to special case language folders, and put a language switcher in the UI, but in the meantime using folder/filename in the slug works

vital folio
#

You guys are awesome, I hope you get it all worked out with the language switching other improvements. I'll keep an eye out for updates👍

tawdry echo
#

Thanks 😄

vital folio
#

like this

tawdry echo
#

I've been wondering about how the UI should work actually... there might be a few places it should go.
First thought is in the list screen (probably up near the Search field) so you can filter the list to all / one language... some way of making it clear which slugs exist in one / several / all languages seems useful.
And then on the entry editing screen, probably some way of indicating which languages exist for the current slug (with an easy way to create missing languages)

#

That sort of assumes that you're planning to have the same entries in multiple languages (translated), it maybe should work differently if you're planning to have completely different entries for different languages in the same content collection (that seems like a less common use case though?)

vital folio