Skip to content

Commit

Permalink
docs(elevatedview): Corrections after review.
Browse files Browse the repository at this point in the history
  • Loading branch information
carldebilly committed Jul 20, 2020
1 parent 3cd5a3c commit ec25f36
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions doc/articles/features/ElevatedView.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# ElevatedView
On many design language like _Material Design_, there's a notion of elevation where a portion of the UI should be presented as been _elevated_ over the rest of the content.
On many design languages like _Material Design_, there's a notion of elevation where a portion of the UI should be presented has been _elevated_ over the rest of the content.

In this case, the UWP proposed solution can't work on all platforms because of technical limitations. To address this problem, Uno provides a control called `ElevatedView`, able to produce a similar result on all platforms, providing an elevated result.

This control is very useful to create cards with both rounded corners and elevated effect - which could be challenging to produce on some platforms.

## How to use the `ElevatedView`

Fist you need to add the `toolkit` namespace in your XAML file:
First you need to add the `toolkit` namespace in your XAML file:

```
xmlns:toolkit="using:Uno.UI.Toolkit"
Expand All @@ -30,6 +30,8 @@ Will produce the following result:

![ElevatedView sample](../Assets/features/elevatedview/elevatedview-sample.png)

> **ATTENTION FOR UWP**: When there is an error seeing the `<toolkit:ElevatedView>` on UWP, the common mistake is to forget to include the `Uno.UI` package for all platforms, including UWP. On this platform, the only available component is the Toolkit.
## Settings

You can set the following properties:
Expand Down

0 comments on commit ec25f36

Please sign in to comment.