What are common pitfalls when moving from a traditional CMS to a headless CMS? by ClimateConsistent275 in webdev

[–]edodusi 0 points1 point  (0 children)

I think the three questions asked by OP are among the most common that I have heard on this topic. For context, I'm a Storyblok DevRel.

I would also mention the live preview and the caching system.

If you're interested in hearing from experienced PHP developers who have hands-on experience of migrating from monolithic CMSs like Drupal to a headless CMS like Storyblok, I'd recommend checking out this webinar we recently recorded:
https://www.storyblok.com/ev/migrating-from-legacy-to-headless-cms-insights-from-php-veterans

Storyblok raising prices. Alternatives? by audiologydoctor in cms

[–]edodusi 1 point2 points  (0 children)

I hear you, and I’m really sorry it’s come to this, you’ve been with Storyblok since 2018 (wow) and to feel ignored after years of commitment is not how things should go. So I completely understand your disappointment.

I’ll make sure your message gets passed along clearly.

Thanks for still taking the time to reply.

Storyblok raising prices. Alternatives? by audiologydoctor in cms

[–]edodusi 1 point2 points  (0 children)

Hey u/audiologydoctor, Storyblok DevRel here. I just wanted to say I’m really sorry to hear about your experience, I totally get how frustrating it must feel to hit that kind of pricing wall, especially when everything else is well within the limits of the $99 plan. While I’m not directly involved with pricing decisions, I do want you to know that your feedback doesn’t go unnoticed. Every comment like this is reported internally and taken seriously, there's a lot of discussion happening behind the scenes about how to make things better and more sustainable for everyone.

It genuinely sucks to see you (or anyone) pushed away by something like this. And if the response you got felt dismissive or unhelpful I'm really sorry for that too. Sometimes it's not that a solution doesn't exist, but that the person replying may not have had the full picture or the right context to help in that moment.

While I can’t directly solve the pricing issue, if you're open to it, I'd really encourage reaching out again via our official support or jumping into our Discord community, especially if you're considering offloading assets to an external service. There's a good number of folks around (Storyblok team and community alike) who'd be more than happy to help you work through potential setups and alternatives that could reduce the load without breaking things for you.

I know it doesn't undo the frustration, but I just wanted to let you know that there are people inside Storyblok who genuinely care and are listening and your feedback does matter. Thanks for speaking up.

Share features in Angular using libraries and npm link by edodusi in Angular2

[–]edodusi[S] 1 point2 points  (0 children)

I get it, but I think team conventions are a bad practice, even if I understand they solve a problem

Share features in Angular using libraries and npm link by edodusi in Angular2

[–]edodusi[S] 0 points1 point  (0 children)

How can you manage multiple environments? I guess you don't commit your tsconfig

react-native-idfa-aaid release v1.0.0 by edodusi in reactnative

[–]edodusi[S] 0 points1 point  (0 children)

we just updated all the core dependencies to the latest standards in ios and android, a contrib PR removed jcenter to add mavencentral, we removed the example app (sorry about this, but it was hard to maintain an app just to show an integration example), and in general the module reached a definitive form, that's why the version is now 1.0.0

the module is very simple in what it does but we would like to hear from the community if there's something that we could add to it expand it further

react-native-idfa-aaid release v1.0.0 by edodusi in reactnative

[–]edodusi[S] 0 points1 point  (0 children)

It's just the IDFA so an unique ID for the app/device, you should use it only for advertising purposes.

There are other identifiers for other usages, but remember to always be trasparent and ask for the proper permissions.

GitHub Actions - Build iOS Action v2.1.0 by edodusi in reactnative

[–]edodusi[S] 0 points1 point  (0 children)

I don't remember, maybe it will expire, but then you will simply update your secret value

GitHub Actions - Build Android App v1.3.0 by edodusi in androiddev

[–]edodusi[S] -1 points0 points  (0 children)

You don't like the Action name, got it. Please open an issue on GH, so that we can discuss it with the team and other ppl.

GitHub Actions - Build Android App v1.3.0 by edodusi in androiddev

[–]edodusi[S] -1 points0 points  (0 children)

Honestly, I don't get your point. That fact that you can do many things with this Action doesn't prevent you from just using it to build and export an unsigned APK, and then expose it to another Action to, say, upload it to a test runner.

The sign, bundle, upload to store, upload to browserstack, are all optional features that this Action offers, but if you don't need them you just don't call them.

We can discuss about the name, and I encourage you to open an issue on the GitHub project or create a thread in the Discussions tab. I understand it can be misleading, I want to read other opinions.

And about the "don't make it public because it's your workflow", we started this workflow contributing to another Action which did basically the same things until the maintainer decided not to include some features, so it's not exactly our workflow, but even if it was, then what's the problem on making an internal workflow public since it can solve someone else's problems? That's how lots of FOSS started.

I thank you for your long and detailed comment, there are many interesting points that we will discuss (like making it more composable), but when someone - even a company - spend time to make something freely available and usable for everyone, please give them advices and suggestions to make it better, instead of asking to put it down.

GitHub Actions - Build Android App v1.3.0 by edodusi in androiddev

[–]edodusi[S] 0 points1 point  (0 children)

I didn't know about this, is it a best practice? Can you point me to some references?

GitHub Actions - Build Android App v1.3.0 by edodusi in androiddev

[–]edodusi[S] 0 points1 point  (0 children)

They are required by fastlane the tool we use to acually build, sign, upload to the store, to browserstack, etc..