CMS for CLI

[shy prawn]

Currently the work around is going to create a blocks extension and create the apps CMS within blocks.

Could we be able to add a data component from the backend dashboard for CLI apps?
This would give a smoother process overall IMO.

Thought this would be a good time to request this before Blocks centralised collections feature is developed just incase that effects anything.

Q: Is this something that has been thought about in the past? If so, I’m intrigued what stopped the development of it 🙂

Thanks

[spice prawn]

Indeed, It would be great if we could add collection as an extension or even create a collection from CLI!

But better is the enemy of good so I would be happy if the collection panel from the block editor is enabled when opening in CLI mode, this would already provide a lot of value to us with minimal effort from Wix 🙂

[prisma star]

Hi,

CLI + CMS is being worked on

Current ETA is something like a few months.

Not much more I can add at the moment but I would be happy to see it, would really be a great addition 🤞🤞

[shy prawn]

@prisma star This is great! Would this be something that is accessible in the backend dashboard? 😁

[spice prawn]

Could you request hat we can have a workaround solution in the meantime? A few months is quite long while we are trying to build apps, hacking our way around a bad UI choice. Enabling the button to the CMS in the editor seems quite easy compare to the whole CLI integration

[shy prawn]

@prisma star out of curiosity, will CLI CMS have the requested features that blocks has? E.g a hidden collection? Restrictions such as end user not being able to add content via CMS directly? Centralised collections? Ect ect

I think this would be a good opportunity for these features to be implemented if not already to have a strong release covering requested features

[prisma star]

@shy prawn it will not be adding new features on launch, but it is on their roadmap overall (without any specific ETA).

[shy prawn]

@prisma star May i ask why these features have not been taken into consideration for the launch? While the teams are working on the feature it would make sense for the features to be implemented then. If Blocks has these features as planned then this is something that people would want/expect.

Currently, we are using Blocks for the CMS for CLI apps because CLI does not have the CMS feature so when blocks releases these features then we will be back to square one with using blocks for the CMS again which then seems pointless for the CLI CMS feature.

I think the team should look at what users want overall with features included rather than 'lets just get the CMS feature out there and catch up at a later date' ( sorry this could come accross as rude but its what i am hearing at the moment )

[prisma star]

@shy prawn Adding CMS to the CLI is under the CLI team, and adding new features to the CMS is the CMS team.
Each have their own roadmap and priorities.

For the CLI team not having CMS at all was a huge gap and they plan to solve it by adding support to the CMS. However they will not add features to the CMS itself as their focus is on improving the CLI.

I imagine that if the CMS team adds such features, it will not be added only to Blocks but also to CLI.

[shy prawn]

Got it so it sounds like blocks is awaiting on the CMS team to implement these features and once implemented and SDK updated then we will be able to use these features near enough straight away? It also sounds like if this is the case then CLI may get these features before Blocks right?

[prisma star]

I don't know what the rollout plan would look like or even exactly how these features would look like. In the roadmap means they haven't fully planned them let alone started working on them.

[prisma star]

@shy prawn @spice prawn 👀

https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/data-collections/about-data-collections-extensions

[shy prawn]

@prisma star OH MY! This is brilliant! This seems like a great way forward as when features are released ( such as hidden collections ) then there won’t be much to do to implement this into a CLI collection which means that regarding CMS, CLI will catch up quite easy 🙂

Thanks Uri!

[spice prawn]

I'm giving a try to this extension

@prisma star I would like to request the ability to set a default value when defining a field. For instance when we have a boolean the default value (empty) is false. I would like to initialize object with default value TRUE

[prisma star]

I made an internal feature request for that @spice prawn

[spice prawn]

@prisma star I’d like to submit a feature request for this extension. It would be extremely useful if we could host the schema directly within our CLI app, so everything lives in a single place.

Currently, I have to update my code and then go to the extension page separately just to keep the schema aligned with the code. This extra step is cumbersome and error-prone.

Ideally, the data schema could live in a file inside the app and be published alongside it.
A major benefit of this approach is that an AI agent could automatically update the schema as the app evolves and new requirements are introduced.

[prisma star]

@spice prawn made the feature request 🙂

[prisma star]

https://support.wix.com/en/article/developer-request-adding-default-values-for-app-collections