-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added empty state - Variant 2 #4276
Conversation
Demo starting at https://vanilla-framework-4276.demos.haus |
f66a418
to
e5e9223
Compare
e5e9223
to
761eeef
Compare
@ilayda21 the example I see is a 404, whereas the design shows a search with no results. Am I looking at the right thing? |
I changed the url sorry about that @lyubomir-popov. I updated the url in the PR. |
Thanks. I know this is built on an existing design mockup, but can't help but notice a bit of a disconnect between text and layout. The text contains suggestions that feel like consecutive steps but the layout presents those as equal alternatives - left choice or right choice. How about something like this:
The above should look end up looking like this: |
@lyubomir-popov can you check it again? |
Thanks, looks good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great Ilayda! I've left a few comments about the HTML. We need to try and use semantically correct elements where possible.
Please see the pastebin with my suggestion on how to structure it
templates/docs/examples/layouts/empty-state/user-triggered.html
Outdated
Show resolved
Hide resolved
templates/docs/examples/layouts/empty-state/user-triggered.html
Outdated
Show resolved
Hide resolved
templates/docs/examples/layouts/empty-state/user-triggered.html
Outdated
Show resolved
Hide resolved
templates/docs/examples/layouts/empty-state/user-triggered.html
Outdated
Show resolved
Hide resolved
Co-authored-by: ilayda21 <ilayda.cavusoglu@canonical.com>
629ab20
to
256f4b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebased and cleaned up. LGTM.
LGTM! |
Should be merged after #4274
Done
Fixes #1010
QA
Check if PR is ready for release
If this PR contains Vanilla SCSS code changes, it should contain the following changes to make sure it's ready for the release:
Feature 馃巵
,Breaking Change 馃挘
,Bug 馃悰
,Documentation 馃摑
,Maintenance 馃敤
.package.json
should be updated relative to the most recent release, following semver convention: