#tinacms — Public Fediverse posts

I like what #tinacms has to offer in terms of a git-based #CMS, but I loathe #React and #NextJS . They support #hugo as far as I can tell, but their starter template doesn't work. Crashes during startup 😒

#decapcms seems like a reasonable alternative. Plenty of support for many #ssg tools like #11ty, but the editing experience in #decapcms is pretty boring. Doesn't really offer anything for me beyond what I could simply do with text files.

I want a decent editing experience, where I can both author blog posts, but also build my web-site using blocks/components. #Tinacms seems pretty ok all around, but looking at the starter sample, the code is crazy convoluted. There is more wrapper-code and boilerplate than there is actual HTML. Hard to know where to even start.

#cloudcannon has an excellent alternative. If this was free for individuals, I'd jump right on that. But I'm just running a little personal website that makes no revenue, so I don't want to fork out $50 a month for it.

Anyway, #sendhelp

. the integration is effectively zero effort. i didn't want to add extra npm build / run steps for my end users, otherwise #tinacms was also a frontend i had considered.

. fully local file editing is HUGE for me, probably the biggest reason i didn't use DecapCMS instead. i don't like adding the netlify OAuth dependency and all that entails, and i just wanted a workflow for my users to edit files locally and pass them into a pull request later. it's a bit weird that it's only supported in Chrome/ium, and i hope the file editing API has support for firefox-based browsers in the future.

. lack of custom components hurts a lot. i wanted the ability to have tweet and PDF.js embeds, but there isn't direct support for custom components yet. I ended up making a workaround by using partials that pick up the data from post attributes and embed them directly at the bottom (which is feasible for my specific requirements but probably generally a bad idea)

. no support for Hugo's page bundles is frustrating. i like to organise my assets alongside my posts, although maybe that's more sensible in a VSCode / obsidian workflow than a CMS workflow. had to reorganise my asset files to make it work, and i worry it won't scale well to ~1000 posts (which i don't need anyway). there is category-level asset organisation, but even that is really insufficient

. field customisation is a 10/10 from me. the configs expose all the options that i would've liked, it looks pretty, and there's even support for adding individual pages. custom slugs are great to have too. i would like to see some enum style arrangement for category fields if possible to avoid typos.

. i'm still unfamiliar with the nuances of Hugo, and the template language is quite intimidating to learn (no prior experience with JS components doesn't help). regardless, it was simple enough to hack together some patches onto the theme

. i might want some sort of folder organisation on my admin page in the future, though i don't know if that's already doable with some configuration 😅. the project is not at that scale yet though.

#sveltia #sveltiacms #decap #decapcms #hugo

. the integration is effectively zero effort. i didn't want to add extra npm build / run steps for my end users, otherwise #tinacms was also a frontend i had considered.

. fully local file editing is HUGE for me, probably the biggest reason i didn't use DecapCMS instead. i don't like adding the netlify OAuth dependency and all that entails, and i just wanted a workflow for my users to edit files locally and pass them into a pull request later. it's a bit weird that it's only supported in Chrome/ium, and i hope the file editing API has support for firefox-based browsers in the future.

. lack of custom components hurts a lot. i wanted the ability to have tweet and PDF.js embeds, but there isn't direct support for custom components yet. I ended up making a workaround by using partials that pick up the data from post attributes and embed them directly at the bottom (which is feasible for my specific requirements but probably generally a bad idea)

. no support for Hugo's page bundles is frustrating. i like to organise my assets alongside my posts, although maybe that's more sensible in a VSCode / obsidian workflow than a CMS workflow. had to reorganise my asset files to make it work, and i worry it won't scale well to ~1000 posts (which i don't need anyway). there is category-level asset organisation, but even that is really insufficient

. field customisation is a 10/10 from me. the configs expose all the options that i would've liked, it looks pretty, and there's even support for adding individual pages. custom slugs are great to have too. i would like to see some enum style arrangement for category fields if possible to avoid typos.

. i'm still unfamiliar with the nuances of Hugo, and the template language is quite intimidating to learn (no prior experience with JS components doesn't help). regardless, it was simple enough to hack together some patches onto the theme

. i might want some sort of folder organisation on my admin page in the future, though i don't know if that's already doable with some configuration 😅. the project is not at that scale yet though.

#sveltia #sveltiacms #decap #decapcms #hugo

Eeeh, took a few moths break from a #web-dev project that used #StaticCMS as a #Git-based #CMS for a #StaticSite and now I'm learning it is archived and development has stopped 😅

Any toughts on alternatives? #TinaCMS? #DecapCMS? Is Netlify funding the latter? Is Netlify evil?

is there a thing called developer adhd ?

I do know that i might be in the range BUT here me out :

everytime im diving into a project then as i work on it i get cought up in uuuuh but what about this intergration or that or that
for the last couple of years if have been building steady my #11ty website build with a cms in the backend using #decapcms

but now after a week of looking suddenly its uh but what about #tinacms / frontmatter...

its like no focus at all or am i just to curious ?

https://www.teotimepacreau.fr/blog/git-based-headless-cms/

@tinacms

#CMS #Git #Headless #Jamstack #HeadlessCMS #TinaCMS #DecapCMS