Edit: So my issue was that I missed the fact that Canvas introduces the concept of Pages, which are separate from the Basic Page content type. The answer is to install the module as normal, go into the Pages item in the sidebar, and then add a new page from there.

I will say that now that it's up and running I'm crazy impressed and excited to work with Canvas as it evolves. Original post below:

---------------------------

I feel like a dummy, but I install Canvas through Composer and enable it, and... crickets? No warnings or errors, but no obvious way to use it with a content type.

Okay, guess I need to read the docs. Nothing on the project page about installation, which would make one assume there aren't any special steps, but let's dig into the README.md and see.

Okay, it talks about the project in the future tense, that's weird, since I thought it just had a stable release? Oh, the readme hasn't been updated in three months. Okay. It shunts you to the CONTRIBUTING.md for installation instructions? Okay.

Great, CONTRIBUTING.md has instructions specifically for 'Joining the development process'. I guess those are the installation instructions? They are DDEV specific, fine, but will I be able to install this on production? Maybe these aren't the installation instructions for general users? Follow the instructions, get to the step: ddev add-on get drupal-canvas/ddev-drupal-canvas-dev returns a 404 error. The manual link to the add-on leads to a github 404 as well. Huh.

Every video I found already starts with it installed. The dedicated Canvas documentation site doesn't even mention installation. I feel like I must be missing something so obvious, it's making me crazy.

Dumb client deleted a views and a taxonomy with terms and now wants it back. I have a backup in dev but can't just override the db as everything else is where it should be. Content sync module are mostly broken in d11. Looking at default content or the new content export in 11.3 want other ideas?. Need to this today .

Update: exported terms as CSV including UUID and id, existed vocabulary as a configuration item, imported vocabulary and then used feeds to create terms maintaining uuids and everything worked!... Took me about 2hrs.

I am upgrading my D7 to D10 through the D10 UI, In the "web/upgrade/review" page, the core statistics module in the "Modules that will not be upgraded" list, I am confusing now if the D7 statistics data can be migrate to D10 ? Thanks

Edit: I managed to pass the argument to the entity_reference_1 display using the views_pre_view hook.

Hello,

in my Drupal 10.5.6 project I’ve created a view with two displays: a block (block_1) and an entity reference display (entity_reference_1).
In a custom hook I enabled the EntityReference filter so that block_1 can use entity_reference_1 as the reference display.

Both displays also have contextual filters.

My issue is that I don’t know how to pass the contextual filter argument (the one passed to block_1) to entity_reference_1.
In the filter settings there is an option:

View arguments – Provide a comma-separated list of arguments to pass to the view. This field supports tokens.

I’ve tried using:

• {{ raw_arguments.0 }}
• {{ arguments.0 }}
• %1
• !1

…but none of these work. If I hardcode a valid node ID (e.g., 2600), it works. But I’m unable to dynamically pass the value coming from the contextual filter of block_1.

Not sure if it matters, but I’m rendering the view via Twig Tweak in my Twig template like this:

{{ drupal_view('view_machine_name', 'block_1', argument) }} 

Has anyone successfully passed contextual filter arguments into an EntityReference filter? Any tips or examples would be greatly appreciated.

Example: DevPanel — the entire dashboard (multi-env workflows, CI/CD, Kubernetes automation, cloud IDE, etc.) is free if you deploy it inside your AWS/Azure/DO account.

No per-user fees, no “team tier,” no SaaS billing.
You just run it like any other self-hosted tool.

Pros I see:

• No vendor lock-in
• No per-seat tax
• Your data stays in your cloud
• Costs are just your infra usage
• Easy to scale with your existing IAM/security

Cons?

• You manage the deployment
• No SaaS “push-button” convenience
• Some orgs prefer vendors to host everything

Would your team use a DevOps platform that’s free under a BYOC model?

I've been having a heck of a time wrangling certain complex views in Drupal 10 and it's driving me up the wall. I'm a solo dev, so have been really banging my head off the wall on this. I don't really expect anyone to be able to solve this for me, but I just wanted to ask if there's anywhere that actually walks through more than basic Views problems? I've looked on YouTube and often found really simple examples, but nothing that unravels multi-layer complexity.

My use case is

- Content type called Resources

- A field within that page to reference a taxonomy called Contributors

- Contributors points to a Content type called Profiles, or a taxonomy page of Resources should they not have a full Profile

- I want to show a block with photo, name, title and link to the relevant profile/taxonomy page. I'm using Fields to pull this together, then outputting custom HTML

- I can get all the relevant Contributors to show up, but some show up in triplicate.

The issue seems to be something to do with Relationships in the View, but I for the life of me can't figure it out. I feel like I need to better understand just what Relationships and Contextual Filters are actually doing and why they would be showing multiple results. But I don't even know where to look to fill this knowledge gap. I've tried various AI chatbot solutions and they often muddle the issue way more than anything.

Edit: It looks like my solution was turning on Aggregation, then choosing Group by Entity ID in my Fields and it got rid of the duplicates.

It's going to be content and demo heavy, including

• Standard Canvas usage for your editors
• Comparisons with other Drupal page builders
• Tips and tricks for development
• Common Canvas “gotchas” and how we work around them
• Using Canvas patterns effectively
• Walkthroughs of Dripyard components and how they work inside Canvas
• The current limitations of Canvas and how to navigate them
• Q & A

Register at https://dripyard.com/blog/dripyard-webinar-drupal-canvas

I have a client who is frustrated with their current Strapi + React setup. It seems no one explained to them that a headless approach requires more ongoing maintenance compared to a traditional CMS. Most of their content lives in Strapi and is essentially “static,” with only two pages pulling data from an external API.

They’re unhappy with their existing vendor because everything takes an unreasonable amount of time— for example, they were quoted 200+ hours just to update Strapi, which is absurd. They’re fed up and want to move in a different direction.

They want the frontend look and feel to stay the same, so I can reuse some of the existing styling. However, I’m unsure whether I should try to reuse some of the React components with minimal modifications and integrate them into Twig/Paragraphs, or simply reuse the CSS and replicate the HTML markup.

I’m an experienced Drupal themer and I know how powerful Drupal is as a CMS, so I’ve never been a fan of fully headless builds for brochure-type sites like this one.

So I see three options:

1. Reuse the CSS and some JavaScript and rebuild everything using Drupal/Twig.
2. Integrate the existing React components on top of Drupal Paragraphs.
3. Create a fully headless Drupal implementation.

My plan is to go with option #1. It may take more time upfront, but in the long run it’s the most maintainable solution.

I look forward to suggestions and hints about the following steps.