New Setup Installer w/ a11y Preferences

At the MODX Malta meetup we worked on reimagining a new Setup Installer with accessibility upfront and center. The idea is that, even if we add accessibility preferences to the MODX System Settings page, that page itself might not be accessible for users to get to and update their preferences. So accessibility preferences should be front and center with options to adjust them as you are installing MODX.

In the spirit of open source and inclusive design, I'd like to start a discussion with the community on what accessibility preferences they would like to have.



The current preferences available are:
Legibility (Font size)

• Regular
• Large
• Extra Large

Typeface

• System
• OpenDyslexic
• Open Sans
• Raleway
• Ubuntu
• Fira
• Anonymous Pro

Contrast

• Normal
• Black on White
• White on Black
• Automatic

Motor

• Disable Drag 'n Drop
• Increase Hit Area

Animation

• Reduce Motion

Visibility

• Exaggerate Focus Styles

Also see the Accessible Setup MAB DRAFT:
https://github.com/modxcms/mab-recommendations/pull/14

This concept is being actively developed on GitHub:
https://github.com/jpdevries/modx-setup

You'll find working code and a demo there.



The installer features an unboxing user experience that allows users to specify what they will be building along with preferences and it automatically decides what packages to install. Not only does this save an enormous number of clicks, perhaps more importantly you don't need a degree in the MODX Extra Vocabulary to know what the various packages are. You just need to tell MODX what you want to do.

[ed. note: dinocorn last edited this post 7 years, 6 months ago.]

Outstanding!

+1

Looks great. Anything to speed up the install process is great. Will there be any options for a advanced install?

Quote from: glynszasz at May 18, 2017, 03:40 AM

Looks great. Anything to speed up the install process is great. Will there be any options for a advanced install?

Yes, it also has advanced options for file permissions and connector paths, etc.

Speeding up the installation process is certainly one of the goals. For example on the Installation Success screen you can tell the installer what you want to build and it will install the necessary Extras automagically for you. That saves about a billion clicks, but perhaps more importantly it makes the process of installing MODX more accessible. You don't need a Master's Degree in the MODX Extra vocabulary anymore. You don't need to spend days reading up on RTFM and the Forums to find out what Extras to use for what. You just tell MODX what you want to build.

GIF Screencast:
http://j4p.us/050G0L3J3h2K/adv.gif

Contributions are greatly appreciated, and not just with coding. Perhaps more importantly, I'm hoping to get some feedback on what types of sites (or not sites) people are building with MODX, and what Packages they frequently use.

Reoccuring packages that always tend to make it onto most of the sites I work on are:

Primary:

Ace
pdoMenu
Collections
FormIt
reCaptchaV2
pThumb
getResources
Google Analytics Dashboard Widget
SEO Pro
SEO Tab


Secondary:

BackupMODX
Breadcrumbs
ClassExtender
Login
getPage
SimpleSearch
VersionX

Maybe worth setting up a poll if you're looking for averages? [ed. note: lkfranklin last edited this post 7 years, 6 months ago.]

Quote from: lkfranklin at May 18, 2017, 11:48 AM

Maybe worth setting up a poll if you're looking for averages?

Thanks for the comprehensive list! I'll discuss setting up a poll with the MODX Advisory Board.

I think we will love it !

This new setup concept has been initially presented to the MODX Advisory Board and I'm actually really excited about part of it being rejected because I think a potential solution will be much better.

• MODX will not ship with a finite list of Extras

This means that to get the functionality shown, we'll need to hit an API to get that list. This way the list can be kept up to date and managed independently of the MODX core distribution. It also means that if we figure out a way for you to customize the API endpoint, so it hits your own endpoint, it would allow developers to customize "the list" of Extras presented during the Setup of MODX sites they maintain.

https://github.com/jpdevries/modx-setup/issues/3