I've removed the microcontent heading from the IS. Although I can see a use case for having testimonials and FAQs being reusable, it adds a lot of complexity to the content model, and for me does not add much value. In other words, I think it's possible but not that common that a site may want to reuse these but I don't think it meets the 80% threshold and therefore does not feel like MVP.
The features listed are specific to the SaaS template, but are we missing some features that site owners just expect to be present?
Not sure whether it has been made explicitly clear but we assume that Drupal CMS will provide this basic functionality for all of the templates that we develop. There are definitely things missing from Drupal CMS itself on this front but we should aim to add them there rather than in each template so they are consistent across sites that use it.
thejimbirch → credited pameeela → .
Thanks, yes I assumed that the fix would be in core :) Just didn't want this to get lost.
Re-rolled the branch and attaching a patch file to use for this. It's working for us, but I haven't looked into the test fails so still NW.
pameeela → made their first commit to this issue’s fork.
@phenaproxima So should we create a new issue for better error handling?
It makes perfect sense to me that this doesn't work, but this is going to be pretty common in a world of contrib recipes and site templates. So it's definitely worth capturing these cases and improving the experience.
In this case, the error itself is not very helpful. So improving the error message to provide specific information about what config is causing the problem, and what you can do to get around it, might be a good first step? That would be a recipe feature I assume?
Sitemap module just allows you to enable various menus or taxonomy vocabs to display on the sitemap page. So it shouldn't be affected by XB I think? If there are XB pages in the menu, they would appear in the sitemap.
Updated the IS to group the modules based on whether they are relevant to XB and made a few other updates.
pameeela → created an issue.
pameeela → created an issue.
@phenaproxima are you saying we should have Drupal CMS running on 11.2 beta by default?
@kunalgautam thank you for working on this, however, we are not currently seeking contribution of a specific recipe. @jose reyero is working on the underlying features required to support this.
Until we are ready to proceed with the actual recipe, I will mark this task as Postponed.
I've gotten the same result:
@penyaskito can you try again and see if you are still having this issue?
Created the MR, will ping Emma for approval :)
Huge support for this from me! Emma has been fantastic to work with on Drupal CMS and I think it will be great to formalise her involvement in core too. This also feels like a big step generally toward prioritising UX!
Using this patch on a project and it works quite well! Would be great to get it in before 11.2.
We are having the same issue trying to use this module with D11. Wonder if anyone else has had any luck?
@kunalgautam this is a feature suggestion, not something that we are actively planning to add at this time. If we do decide to go ahead with it, we will define the approach in the issue. I'm updating the status to 'Postponed' to reflect this as there is nothing to action right now.
Tested the patch and it works to hide the menu link. I'm not the best person to do a code review of this as it's outside of my expertise, but I am not sure about the empty pages. The top level page is reachable via the side navigation:
For now, the second level pages don't link but they may in future.
I see, wow, I was way off thinking thinking initially this was a simple fix! For our case, we were able to patch by just making the change I proposed because we won't have any users with access to only some of the tools.
I will try to find time to test this proper fix during the week.
Just hit this on a project yesterday, and I think it belongs in the navigation itself, not the top bar. And the user menu is a logical place. So +1 to #1!
Also was super confused by #7 because I could not find this menu, until I reread the comment, and yes, the user block isn't a proper menu until 11.2 :)
Ah, wait -- this probably doesn't work because it means the cron permission can't be used separately. So I guess the fix would be to add a new general permission?
pameeela → created an issue.
I think this is unblocked now.
hestenet → credited pameeela → .
Thanks @dww!
I'd love to do this, but there is no way we would be able to get it done before 11.2 anyway unfortunately.
I also could swear there was already an issue for this! But I can't find it.
We already have a process for taking over modules that are no longer maintained. A "guarantee" is not really feasible, since there is nothing commercial here, we are all just volunteers or sponsored by our companies at their discretion.
Certainly, we are vetting the modules included in Drupal CMS carefully, and it is highly unlikely that a module that is included would be totally abandoned. But if that did happen, the Drupal CMS team and the wider community would work toward a solution. I don't think this can be formalised, at least not for now.
Last child meta is closed, I hereby declare Drupal CMS 1.0 complete :)
Going to close this because there is some work being done on the larger AI strategy that will define what happens post v1. No need to update this issue I think.
OK cool, agree with removing it and the test for caching also sounds like a great idea :)
So I think this depends on 📌 Add documentation section for automatic updates Active and we can update the link (in AU) once we have something to link to.
Or should this be closed as a duplicate of 📌 Improve messaging to users to backup database Needs review ?
smustgrave → credited pameeela → .
We don't currently have any releases planned for 1.x, as we are now focusing on 2.x. So I think the main thing we should look at is testing existing functionality with 11.2 alpha/beta?
Wow what a pain. Agree on not hard coding it.
Do we really need a copyright meta tag? I have never once done this in 14 years of building websites.
@yautja_cetanu I'm triaging all of the existing meta issues as they were all pretty much delivered for 1.0 and I'm keen to close them out so we can start documenting what's happening for 2.0. Would you be able to update this issue to summarise the state of things in 1.0? And if needed, create a new meta for the ongoing work?
We got what we needed for 1.0 and Navigation is very close to stable now, so closing this one off.
This was successfully delivered for 1.0 so I'll close it off for now. We should separately scope out any future work needed for this track for 2.0.
Crediting @tonypaulbarker but feel free to credit anyone else who should be!
This was successfully delivered for 1.0 so I'll close it off for now. We should separately scope out any future work needed for this track for 2.0.
This was successfully delivered for 1.0 so I'll close it off for now. We should separately scope out any future work needed for this track for 2.0.
This was successfully delivered for 1.0 so I'll close it off for now. We should separately scope out any future work needed for this track for 2.0.
Closing this off since the planned 1.0 scope was delivered and we have a plan for the rest! But we should create new issues as needed.
Closing this off as the 1.0 scope was delivered.
Closing this off as the 1.0 scope was delivered.
Closing this off as the 1.0 scope was delivered.
Closing this off as the 1.0 scope was delivered.
Thanks @baddysonja!
Thanks everyone for your input! After reading all the comments, I think it probably doesn't make sense to introduce this to Drupal CMS at this point. For sure, SPP is great for existing sites and will be for those using the legacy node form for a long time to come. But since Drupal CMS is a starting point for new sites, and we are now working on 2.0 as the XB-ready version, I don't think it is the right fit.
We do have Views UI enabled by default for now.
Gin got a stable release for 1.0, I'd consider that a huge success :)
This didn't go ahead and will be pretty much entirely in the XB remit, so I'm going to close this off.
This didn't go ahead as described for 1.0, and the current work being done in this area doesn't really align with the original vision of just having a recipe. So I'm going to mark this closed, and will create new issues to capture the new work as it develops.
This was successfully delivered for 1.0 so I'll close it off for now. We should separately scope out any future work needed for this track for 2.0.
Don't want to mix this up with the 1.0 tracks, we'll have to figure out how to group these in the context of the new and ongoing work. Not sure what that is yet!
This was successfully delivered for 1.0! Plenty more to do but I think we should scope that out when we get to it.
This is completed as far as we planned for v1, with the Acquia trial live. Future work should be done in new issues.
I think we should close this off, since all of the existing tracks were aimed at 1.0. There is obviously work still ongoing but I think we should start fresh.
I'll work on that, but in the meantime I would not worry about updating this.
Closing this one since 1.0 is complete. Ongoing product marketing will be owned by Nick and Ryan from the DA.
Agreed, no objections raised on Slack either.
@drumm great question re: category, I was not even thinking, but of course the field is not on general projects.
I'll try to get consensus on this. I do think the module categories will be applicable, as in many cases recipes are providing an optimised setup for a single module or a few modules.
The separately, we can try to resolve the classification. I wouldn't block this on those tasks, but I think we should be able to decide at least on reusing the categories pretty quickly.
I agree with @quietone that this isn't actionable as a Drupal core issue, perhaps it would be most suited for https://www.drupal.org/project/promote_drupal → where the marketing is discussed?
smustgrave → credited pameeela → .
Considering that the Ludwig project page recommends using Automatic Updates instead, I'm marking this won't fix.
Please, consider the use of the Automatic Updates contrib module instead of Ludwig!
The Automatic Updates contrib module has a stabile release now. It is a long-term Drupal UI solution for package management. So, try it and find out if it works for you. If not... you can come back to Ludwig always. :)
I think that between Project Browser and Automatic Updates, this is largely solved?
Nice! Thanks for linking back to it.
Thanks @drumm, FWIW I definitely think there is value in having the listing page before that lands, as most recipes will be brand new for now. But I will try to move that forward as well.
pameeela → created an issue.
Ah, thanks for the heads up! I'll create an issue for adding the logo.
pameeela → created an issue.
Thanks!
pameeela → created an issue.
Thought about this some more and I think it might be better done as a warning in the status report? The dashboard feels quite prominent considering it really only affects sites with events. @penyaskito reminded me we can do this with ECA too, I forgot.
if after install the timezone is set to UTC, we add dashboard notice to verify that the timezone is set properly.
Not really sure how we would go about doing this in Drupal CMS? Definitely seems worth tracking the issue of timezone handling, but I think anything like this would need to be done in a contrib module (or core I guess but unlikely). Is there an existing contrib module that would make sense?
Separately is there a feature planned for notices/warnings on the dashboard? Right now it only supports blocks, right? I think this may come up as part of the onboarding research and user testing that the UX folks are currently doing.
@d34dman this is a cool feature but it's super technical, and not really suitable for our target audience. We are aiming for default features to be things that ~80% of sites would use. This module currently reports 8 sites using it, so I think we can gather from that statistic that it is not an 80% feature.
I can't seem to reproduce this -- can you attach a screenshot? This is what I get:
Thanks, I had no idea it used a separate logo.
Or change the easy email theme to use the front end logo by default and only use a custom logo if it is overridden.
This makes a lot of sense to me, it seems like setting a custom logo is an edge case. Moving over to the module queue though since it'll have to happen there.
The only hesitation I have with this is the workspaces stuff which will replace content moderation. I'm not 100% sure how Diff fits in with that? I'll see if I can find that out at DrupalCon.
And if we do add it we'll need to add Diff Plus → as well :)
kristen pol → credited pameeela → .
kristen pol → credited pameeela → .
kristen pol → credited pameeela → .
@garphy a decouple recipe would be awesome! But not something we will ship with Drupal CMS anytime soon. We don't want to be seen as gatekeepers of recipes, which can be contributed just like modules. We don't want to try to make Drupal CMS everything for everyone because it's not scalable, so we want to encourage the community to build the recipes that make sense for them.
Filled in CR.
Didn't read the comments properly, I've updated the CR with info.