🇦🇺Australia @pameeela

I created a child issue to discuss the 'basic' event recipe scope: #3463884: Define scope of 'basic' event recipe that would be offered in the installer →

I think we'll want child issues for individual topics just so we can follow the threads.

@mandclu had a play with the recipe at drupal/events. Some points for discussion:

1. Should there be an optional image field?
2. The upcoming and past event listings are views pages. I think this would be more intuitive as nodes, so they would appear in the content list and be editable.
3. I think it would be good to get some user feedback on the multi-date functionality
4. What should the 'default' date format be? Ideally we could ask users their preference, or if not we could consider how to guide the user to change it.

I am sure others have thoughts!

pameeela → created an issue.

Thanks Gabor, yes I should have also said that :)

We hope to have wireframes soon and I just realised (from looking at the Slack thread) that @zetagraph you have already been in touch about helping out with those wireframes, so it is good to connect those dots!

I think this should be postponed pending the wireframes/designs just so we have a better sense of what specifically is needed.

@sime could you provide a bit more info about what makes this a Starshot blocker?

@drupal a11y just replying here too in case others have the same question, you can make a new submission just noting it's updated and we'll make sure to combine them.

Thank you @breidert!

Thanks @guptahemant!

Just came to create this issue if it didn't already exist :) This drives me nuts!

Surely this change won't break any tests?

I can confirm the same re: extra links. They appear at the wrong level until you uninstall admin_toolbar_tools (Admin Toolbar Extras).

However, the user link, pointing just to "create user" page, remains, as that was added as part of the newly created "Content" menu.

This is by design, that menu is the consolidated 'Create' menu so it provides a link to add users along with content and media.

Great news, thanks @rachelh_design!

Thanks @daften, sounds great!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

This track is in need of a lead. See Dries' blog post for more info, read about the track lead position → , or just apply now!

Belated update, this track was already allocated to Suzanne, who will be working closely with the Starshot marketing group as well as Promote Drupal.

Sure, the sitewide config is definitely the intention (e.g. XML sitemap, meta tags etc) so happy to change it for clarity.

In addition to a list of things we can do, we will need to define what should be always there (in the base recipe) vs what might be better as an opt-in (maybe there is nothing because it all should be there by default, I'm not sure).

Thanks @mherchel!

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

There was some initial discussion of this in an issue in the prototype.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

pameeela → created an issue.

Updating this to remove the 'finish' language, I see others agreed with this change :)

The MR is pretty straightforward but I added a line about the proposed resolution. Not sure if that is what you mean @smustgrave?

Assigning to Tim as his team is going to get started on this for now.

Hiding patches

Crediting @chx for Slack participation.

Created an MR to add a check that $values is an array. There is no test here because it would be very difficult to come up with one, so hoping it qualifies for an exemption given both the simplicity of the fix and the fact that it is only resolving a warning.

Discussed in Slack, will create an MR with a modified fix.

Thank you @dreambubbler! Next week we will put out a formal call for folks who want to be a track lead, we will post the details in each issue so keep an eye out :)

Thank you @mandclu! Next week we will put out a formal call for folks who want to be a track lead, we will post the details in each issue so keep an eye out :)

I've tried to reproduce using the info in the IS on 10.2 and no luck, not seeing any warnings with this config. The steps in #12 are not clear enough to test them. If this is still occurring could someone please update the issue summary with specific steps to reproduce it?

pameeela → created an issue.

This discussion got a bit side tracked I think! Updating the title because I don't think we will be prompting users only to apply recipes. I also don't think that 'Finish your site' is a realistic title for this, considering what would be required to actually 'finish' a site from here.

What we are really doing is providing some suggestions (next steps?) for what to do now that you have installed Drupal.

Thinking of a few things we could prompt, not in any particular order and not at all exhaustive:

1. Create an event / blog / landing page (based on the available content types)
2. Add a new content type (this could be applying a recipe OR creating one from scratch?)
3. Browse module add-ons (not the correct wording but this would take you to Project Browser)
4. Move to hosting (if this is a browser trial)
5. Collaborate with your team (add a user, but this only makes sense if it is on hosting already)

Cross-linking the Github issue where GDPR was being discussed.

I think there are two parts to this:

1. Ensure Starshot is GDPR compliant OOTB
2. Provide a recipe for users who are planning to use cookies/tracking so they can easily remain compliant

Not sure if #2 is in v1? I guess it depends on how complex it would be.

pameeela → created an issue.

I’m not totally sold on the grouping idea, that was proposed in the other issue. I guess I don’t have the solution, just raising a concern about the current UX.

I myself find it hard to parse even the shortest list to find the content type I’m after. But I'm willing to concede that this is just because it’s a change and new users may not find the same.

pameeela → created an issue.

pameeela → created an issue.

I created ✨ Grouping or prioritisation for items in create menu Active for the first part of this. The second two items are a separate feature request I think, to allow individual users to customise their own menu. Separate to that could be a feature to allow customisation of it globally. I haven't created issues for those although they may already exist.

pameeela → created an issue.

This should not be postponed as the latest comment says it can be reproduced in several core themes. Updated IS to reflect this.

Going to close this since there is no recent info on seeing it, or specific steps to test.

Thanks for confirming.

@nicxvan could you expand on why you think this change should be called out? The setting doesn't do anything. Why would it be disruptive for it to not be set on a new install?

Edit: going to move my comment to the specific issue.