🇯🇴Jordan @Rajab Natshah

Thanks for reporting!
Following up on the proposed fixes.

Thank you for this fix.
Hoping for a tag release

Facing the same issue.
Patch #6 is working
Thank you :)

rajab natshah → created an issue.

✅ Released vartheme_claro-4.0.12 →

✅ Released vartheme_claro-3.0.19 →

rajab natshah → created an issue.

Yes, the upgrade path and support will continue for 9.2.x and 10.1.x.
Doing 10.1.x first, and then 9.2.x will follow.

Thanks, Lucian, for asking.

The upgrade path will be:

• Varbase 10.0.x to 10.1.x
• Varbase 9.1.x to 9.2.x

Having a work in progress on that
📌 Start a 10.1.x branch for Varbase to support UI Pattern ~2.0, Storybook, Active

Have a look at the progress work

composer create-project vardot/varbase-project:10.1.x-dev PROJECT_DIR_NAME --stability dev --no-interaction

Use ddev start

✅ Released varbase_media-10.0.11 →

✅ Released varbase_media-9.1.17 →

✅ Released varbase_dashboards-1.0.8 →

It would be so nice to have.
Thanks, Martin, for starting this issue!

I'm with this idea for a Config Action to place an inline block in the selected section's region.
Maybe add a new section at the start or the end of the dashboard with pre-selected blocks
A bit like what the Section Library → is doing.

Thinking of

addDashboardSection:
  order: last
   ...

addDashboardBlock
  region: first
  ...

Exmaple:
We had a case which needed the following blocks in the Drupal CMS starter recipe.
Which could be in a new optional recipe. or add them directly to the Welcome Dashboard

Publishing content
Shows a list of publishing-managed content on the site.

My drafts Block
Shows a list of all draft content for the currently logged-in user.

Scheduled Block
Shows a list of all content scheduled for future publication on the site.

The Dashboard entity type is a config entity, not a data entity type.

What do you think? Should this config action be in Drupal Core with the Layout Builder?
We managed that with Content data entities ✨ Add a Normalizer and Denormalizer to support Layout Builder RTBC
What could be the best method to manage this with config entities?

I'm with this change.

Facing the same issue After Drupal CMS 1.1.0 was released
🐛 No icon for the Dashboard link in the Navigation menu Active
Hoping for a release.

Noted;
Ok then, Following up with the other issue.
Got it, no patching directly in Drupal CMS. The focus shifts to fixing and testing within the used module

I like the Base Recipe too!
A new Dev Tools recipe sounds like a great idea.
Also it could fit into the Advanced Tools for Content Publishing Workflow Recipe

Both human and AI reviewers(Agents) will need to move through the editorial workflow.
Reviewing what changed from the last step by AI or humans.

Slack conversion with Jamie
Drupal AI is moving fast and it will fit into having 3 or 4 new steps/statutes in the publishing workflow ( could be a new optional AI or workflow recipe)
Following with:

• Some Thoughts About How AI Could Reshape CMS Platforms
• How AI could reshape CMS platforms

What do you think?

It's nice to have this Dev Tools recipe.
I would add installing config_update_ui, and devel in it. Maybe other like diff

Still in needs work in
🐛 Dashboard icon missing from Navigation Active

rajab natshah → created an issue.

Moving this issue as a suggestion to Drupal CMS Development
After reading Some Thoughts About How AI Could Reshape CMS Platforms
And How AI could reshape CMS platforms

Nice, Thanks, Alex
✅ Released autocomplete_deluxe-2.0.9 →

You are right Alex.
thanks for following up.
Please, create new MR I will merge it for you, and follow with a quick fix release

✅ Released autocomplete_deluxe-2.1.2 →

✅ Released autocomplete_deluxe-2.1.2 →

Facing the following follow up issue 🐛 Version 2.1.1 breaks parts of the site when CSS aggregation is enabled Active

✅ Released varbase_privacy-1.0.0 →

rajab natshah → created an issue.

rajab natshah → created an issue.

Moving the optional config logic to 📌 Initialize the Varbase Privacy recipe Active

rajab natshah → created an issue.

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →

✅ Released varbase-9.1.9 →