First stab at `order` property to replace `randomize`, closes #293

[LeaVerou]

Haven't tested it yet, wanted to get some feedback on direction.

Note that right now it will default to the old behavior if no order is set, for backwards compat. Eventually we probably want the default behavior to be the specified order; I cannot think of many use cases where alphabetical sorting is actually desirable (perhaps only demographics questions like Sector etc).

Not sure if order is too general; maybe we want to call it optionsOrder?

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
charts	❌ Failed (Inspect)		Sep 18, 2023 4:41pm

[netlify[bot]]

✅ Deploy Preview for state-of-graphql canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/state-of-graphql/deploys/65087dc0e51de70008055c5a

[netlify[bot]]

❌ Deploy Preview for devographics-static failed.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/devographics-static/deploys/65087dc0868e010008375eba

[netlify[bot]]

✅ Deploy Preview for stateofjs canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/stateofjs/deploys/65087dc0f1e5bc00078a37d8

[netlify[bot]]

✅ Deploy Preview for stateofjs2022 canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/stateofjs2022/deploys/65087dc06363b30008244df1

[netlify[bot]]

✅ Deploy Preview for devographics-graphiql2 canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/devographics-graphiql2/deploys/65087dc0acb77f00096c9c42

[netlify[bot]]

✅ Deploy Preview for stateofcss canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/stateofcss/deploys/65087dc0afe91a00084f1a52

[netlify[bot]]

✅ Deploy Preview for devographics-graphiql-internal canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/devographics-graphiql-internal/deploys/65087dc022c5a200085d91aa

[netlify[bot]]

✅ Deploy Preview for graphiql-devographics canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/graphiql-devographics/deploys/65087dc0e9cb130008e36231

[netlify[bot]]

✅ Deploy Preview for tokyodev2022 canceled.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/tokyodev2022/deploys/65087dc0c5442d00071e9817

[netlify[bot]]

❌ Deploy Preview for css2023 failed.

Name	Link
🔨 Latest commit	bb3fbdb5d727a6e91fbb8d251418e97e89e40828
🔍 Latest deploy log	https://app.netlify.com/sites/css2023/deploys/65087dc0fb1b9f000846f287

[gatsby-cloud[bot]]

:x: State of CSS 2022 deploy preview failed

Your build failed. View the build logs.

[gatsby-cloud[bot]]

:x: State of CSS 2022 deploy preview failed

Your build failed. View the build logs.

[gatsby-cloud[bot]]

:x: State of GraphQL 2022 deploy preview failed

Your build failed. View the build logs.

[gatsby-cloud[bot]]

:x: State of GraphQL 2022 deploy preview failed

Your build failed. View the build logs.

[SachaG]

Looks good!

I cannot think of many use cases where alphabetical sorting is actually desirable (perhaps only demographics questions like Sector etc).

I think alphabetical sorting is appropriate for any question where there are a lot of items and we want to facilitate scanning; especially when these items don't have a pre-existing inherent semantic order.

A good example is lists of resources (podcasts, sites, people, etc.).