* Comment out redirect
* Back to where we were
* Add basic generalization to onboarding
* Update app/javascript/onboarding/Onboarding.jsx
Co-authored-by: Vaidehi Joshi <vaidehi.sj@gmail.com>
* Update app/javascript/onboarding/components/IntroSlide.jsx
* Update app/javascript/onboarding/components/ProfileForm.jsx
Co-authored-by: Vaidehi Joshi <vaidehi.sj@gmail.com>
* wip
* no comment
* tests
* typo
* typo
* crayons example page
* doc
* boxes fix
* fix
* Update index.html.erb
* Small refactor to return null when the modal is not visible.
* Update app/assets/stylesheets/components/modals.scss
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* tiny fixes & improvements
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* Dynamically render forward text in Navigation component
* Render either "Skip for now" or "Continue" on the FollowTags, ProfileForm, and FollowUsers components.
* Refactor the ProfileForm component to dynamically change the button text based on the form's state.
* Render specific button text for last onboarding slide
* Fix back arrow styles for accessibility
Also set an explicit width on the containing button around the svg.
* Use min-width to specify back-button size
* Move Terms & Conditions, CoC into Intro slide of onboarding
Closes https://github.com/thepracticaldev/dev.to/issues/6545.
* Rename ClosingSlide in Onboarding tests
* Rename EmailListTermsConditionsForm to EmailPreferencesForm
* Proper lint and prepend `v2:` to some onboarding components
* Move email preferences to last slide
Closes https://github.com/thepracticaldev/dev.to/issues/6550.
* Use crayons variables for padding
* Remove backToSlide function, rename buttonIsDisabled function
* Render the user's name on intro slide of onboarding
* Refactor terms + conditions form in onboarding view
* Style the back button using crayons design system.
* Remove redundant scroll styles (only need `overflow-y: scroll` here).
* Ensure that content is readable, and back button doesn't conflict with content.
* Ensure size of content is same size as "intro slide".
* Remove unnecesary inline styles, use CSS class instead.
* Fix missing userData issue
* Onboarding test cleanup, inline greeting instead of in a variable
* Improve onboarding UI and UX (P1)
- Introduce Crayons variables
- Remove unnecessary CSS files to have just one CSS file
* Add new onboarding tests
* Update onboarding yarn test to reflect updated class names
* Remove Report Button from user's own profile sidebar
* Update UserDetails test file to include window
* Uncomment code and Add tests
* Resolve issue with display property change persisting
* Update snapshot
* Uncomment line of code
* Reduce code duplication in onboarding tests
* Update variable names for consistency
* Improve test descriptions and format
* Refactor a useless test
This test was fairly pointless, but hopefully with this refactor it
could detect a regression? Although, I think it's really just testing
the that the Preact framework's state mechanism is working the way we
expect it to, but it might be worth leaving this test in.
* Add jext-axe package and introduce a11y testing
Automated a11y testing is NOT comprehensive. We cannot expect this to
even scratch the surface of potential a11y issues.
However, we can expect to find a percentage of issues that are currently
flying under the radar. Adopting some automation around a11y testing
also allows us to use CI to find a11y regressions -- which should be
really handy.
I've never really used Jest before, and Preact seems to make it a little
more complicated, but as far as I can tell, this is a decent way to add
at least some minor automated a11y testing.
* Add doc about automated a11y tests
* Fix some eslint complaints
* Fix some basic a11y issues in onboarding
- Missing a main element
- TODO to enable zooming
- Rename a duplicate ID attribute
I may need some context on the zooming thing, why did we decided to
disable that in the first place? It is a pretty bad a11y issue, we will
need to fix whatever that is a workaround for instead of making it
difficult for some people to use our onboarding.
* Update screenshots
