Ashbourne Sprint 2023 - focus

This issue is a discussion space to think about what we'd like focus on at the Ashbourne Sprint in the UK in December 2023.

Please see #4 (closed) for general information about the sprint and #3 (closed) for workshops.

The proposals so far are as follows.

Topic	Lead	Description	Issues
Improvements to FormBuilder and SearchKit	@colemanw	Any specific areas to focus on?	dev/core#3761 dev/core#3762 (closed)
Admin UI	@ayduns	Migrating stable forms into core. Converting more screens.	dev/core#3912
Improving documentation	@gibsonoliver @dvhirst	Particular focus on SearchKit and Formbuilder docs. @JoeMurray intends to focus on converting material in https://docs.google.com/document/d/1vQHtwfS1Xg0mGBi_cnNNi7TU7sd7P3hTSHja957o5hk/edit#heading=h.ey6cgh62wg8i into documentation for browser based users and possibly developers.
Standalone	@artfulrobot
Marketing Strategy and Website	@andyburns	Analyze the CRM space, CiviCRM positioning and messaging. Result in a marketing plan to re-orient civicrm.org. Preparation Notes.	marketing/branding#13 (closed)
Better looking, more accessible default Civi	@nicol	There’s a few themes (Haystack, Finsbury, Island) that largely work on all 7 of Civi's CMS setups (D7, D9+, J3, J4+, WP, Backdrop & Standalone) - so why not ship one/all with Civi? Because, imho, it throws a new layer of paint over Civi’s aging brickwork – and themes alone can't tackle Civi’s accessibility fails (see this 6 year old unresolved issue by the late Rachel Olivero who was such an a11y expert, Drupal named Olivero after her). So to improve Civi UI the brickwork needs attention too. For e.g. there’s at least 8 ways Civi does accordions, 3 in FB & SK alone - and none are accessible. Which one should an extension developer use? @nicol & @artfulrobot, with some support from core, have been trying to figure out a path to improve Civi’s UI that both handles tech debt & is future-proof. Our idea is DINO: - DOCUMENT all markup variations in new extension ThemeTest; - IDENTIFY the best (accessible/responsive/themeable) practice version in a public UI guide; - NEW theme that's easily customisable and supports both recommended and deprecated patterns; - OPTIMISE to replace deprecated patterns with recommended (allowing the new theme to shrink in size over time). But it's a big job - is this a priority? Core team capacity is limited, as is available funding (Mozilla & NLNet both said no on first ask). Where do we go next?	dev/user-interface#56, dev/user-interface#57, dev/user-interface#58, dev/user-interface#59, dev/user-interface#60, dev/user-interface#61, dev/core#3294 (closed) dev/core#3302, dev/core#3301, dev/core#3292, dev/core#902, dev/core#3295

Schedule

See #4 (closed)