diff --git a/doc/general/1-intro.md b/doc/general/1-intro.md
index 9b6e6d7..8d1ed1f 100644
--- a/doc/general/1-intro.md
+++ b/doc/general/1-intro.md
@@ -16,7 +16,7 @@ Fabric Design System includes:
## How can I use it?
Although it is up to you, how you want to use Fabric DS, based on our experience and industry best practices, we prepared following procedure:
-![How use Fabric](/img/intro1.svg)
+![How use Fabric](/src/style/assets/intro1.svg)
##Resources
diff --git a/doc/general/2-colors.md b/doc/general/2-colors.md
index 3be207c..4202b43 100644
--- a/doc/general/2-colors.md
+++ b/doc/general/2-colors.md
@@ -3,7 +3,7 @@
## Colors in General
GUIs (Graphical User Interfaces) present their features and functions visually. Color is used sparingly to draw attention to important elements and those that we want the user to take action on.
-![Colors in general](/img/colors1.png)
+![Colors in general](/src/style/assets/colors1.png)
## System Colors
@@ -11,7 +11,7 @@ Fabric design system differs between the primary **Color Palettes** (system colo
The system colors (pure red, yellow, green and grays) are separated from other palettes, to provide a way to impart visual continuity, communicate status information, give feedback in response to user actions and help people visualize data. The easier it is to use your product and quickly scan information, the less mistakes your users might make.
-![Colors in general](/img/checkmart.svg)
+![Colors in general](/src/style/assets/checkmart.svg)
$snowy-mint: #C9FFD1
@@ -19,7 +19,7 @@ The system colors (pure red, yellow, green and grays) are separated from other p
$forest-green: #1EB234
$kohpayam: #188F2A
-![Colors in general](/img/forbidden-swtone.svg)
+![Colors in general](/src/style/assets/forbidden-swtone.svg)
$pippin: #FFDDDB
@@ -27,7 +27,7 @@ The system colors (pure red, yellow, green and grays) are separated from other p
$flamingo: #F44F41
$mojo: #C74236
-![Colors in general](/img/attention.svg)
+![Colors in general](/src/style/assets/attention.svg)
$bulb: #FFFFCF
@@ -186,4 +186,4 @@ Most of the application is gray, pops of color catch a user’s eye.
## How to use Scheme Colors
Each scheme palette owns 6 shades of a specific color. To offer a well balanced user interface, each color of the scheme is assigned to a specific function.
-![Color Theme](/img/colors2.png)
+![Color Theme](/src/style/assets/colors2.png)
diff --git a/doc/general/3-spacing.md b/doc/general/3-spacing.md
index 81801ac..bb05be7 100644
--- a/doc/general/3-spacing.md
+++ b/doc/general/3-spacing.md
@@ -40,25 +40,25 @@ XXXL, $space-xxl: 4rem
## Grid
Design System is using 24 column grid.
-![Grid](/img/spacing1.svg)
+![Grid](/src/style/assets/spacing1.svg)
Gutter (column padding) width is 0.5 rem (8 px) which means that distance between columns is 1 rem. Column size depends on screen size.
-![Grid](/img/spacing2.svg)
+![Grid](/src/style/assets/spacing2.svg)
During screen design Designer needs to decide how many columns is needed for content area.
-![Grid](/img/spacing3.svg)
+![Grid](/src/style/assets/spacing3.svg)
Designer should also remember that on smaller screens. He needs to:
-![Grid](/img/spacing4.svg)
+![Grid](/src/style/assets/spacing4.svg)
## Layout
1440 screen, 24 col, 0,5rem margin, 1rem gutter
-![Grid](/img/spacing5.svg)
+![Grid](/src/style/assets/spacing5.svg)
## Spatial Concept
Using insets, stacks and inlines will help to organise layouts in a harmonious way.
-![Grid](/img/spatial-concept.svg)
+![Grid](/src/style/assets/spatial-concept.svg)
diff --git a/doc/general/4-typography.md b/doc/general/4-typography.md
index c831e5c..7213dbd 100644
--- a/doc/general/4-typography.md
+++ b/doc/general/4-typography.md
@@ -13,4 +13,4 @@ Typographic hierarchy is created by:
Most commonly these methods are used in combination with each other. Fabric uses the color **“fiord”** for its titles and labels to arise a slight differentiation from other values.
-![Example](/img/typography1.png)
+![Example](/src/style/assets/typography1.png)
diff --git a/doc/general/5-navigation.md b/doc/general/5-navigation.md
index d628c0e..7c3902e 100644
--- a/doc/general/5-navigation.md
+++ b/doc/general/5-navigation.md
@@ -1,34 +1,34 @@
# Navigation
Navigation structure and used elements highly depend on system **Information Architecture** structure. Think about it before you make decision about your navigation and menu structure.
-![Example](/img/navigation1.svg)
+![Example](/src/style/assets/navigation1.svg)
## Context Links
The most natural way to move through the system is a system of well placed context links that leads to proper place.
-![Example](/img/navigation2.svg)
+![Example](/src/style/assets/navigation2.svg)
## Menu Structure
First level
-![Example](/img/navigation3.png)
+![Example](/src/style/assets/navigation3.png)
Second level
-![Example](/img/navigation4.png)
+![Example](/src/style/assets/navigation4.png)
## Tabs
Tabs can be used to divide page content into sections. It should be used to show only content relevant to specific user actions.
-![Example](/img/navigation5.png)
+![Example](/src/style/assets/navigation5.png)
## Overlays
Layers are very efficient in showing detailed data or advanced actions without leaving current context. They should be considered as a standard way to show details in Fabric based products.
-![Example](/img/navigation6.png)
+![Example](/src/style/assets/navigation6.png)
More details in [Overlays](../#/general/7-overlays)
diff --git a/doc/general/6-structure.md b/doc/general/6-structure.md
index 2074023..9e63010 100644
--- a/doc/general/6-structure.md
+++ b/doc/general/6-structure.md
@@ -27,7 +27,7 @@ Don’t:
## Sheet
-
+
Basic view component. Every view need to be built by Sheet or Tile(s). Sheet can be sliced into smaller pieces through grid.
@@ -37,15 +37,15 @@ Don’t:
## Tile
-
+
-
+
Alternative main view component. Every view need to be built by Sheet or Tile(s). Number of used tiles depends on needs. Tiles can be merged into bigger tiles. Standard tile width is 6 grid columns (minimum 3 grid columns)
## Side Panels
-
+
### Left Panel
Should be used only when it is reasonable need for menu or fixed filters panel.
diff --git a/doc/general/7-overlays.md b/doc/general/7-overlays.md
index 371eb27..738f18f 100644
--- a/doc/general/7-overlays.md
+++ b/doc/general/7-overlays.md
@@ -9,26 +9,26 @@ Do not use it when:
## Details Layer
It is the default layer solution for most of Fabric use cases. It is a simple and subtle solution do show element details without hiding screen information.
-![Example](/img/over-ex10.svg)
+![Example](/src/style/assets/over-ex10.svg)
Use it to show limited details data or additional action elements.
For a bigger amount of data use Full-page Layer or Side Panel.
## Modal Window
Should be used ONLY for task stopping events (like critical error).
-![Example](/img/over-ex11.svg)
+![Example](/src/style/assets/over-ex11.svg)
Use it for crucial decisions that interfere user workflow.
For standard system feedback use Notification system.
## Full-page Layer
@@ -36,23 +36,23 @@ Whole page content is hidden under it.
It should be used only if default page content is not needed when user is looking for layer info. It also shouldn’t be used for limited amount of information.
-![Example](/img/over-ex4.svg)
+![Example](/src/style/assets/over-ex4.svg)
Use it when you need to focus additional information about element.
## Side Panel
Side layers can be used on the right (only for filters and navigation elements), left or bottom edge of the screen.
-![Example](/img/over-ex1.svg)
+![Example](/src/style/assets/over-ex1.svg)
Use it when you need to show additional information about element without hiding the main data.
Additonal decision options should be placed on Details Layer.
diff --git a/doc/general/8-feedback.md b/doc/general/8-feedback.md
new file mode 100644
index 0000000..65ce410
--- /dev/null
+++ b/doc/general/8-feedback.md
@@ -0,0 +1,49 @@
+# System Feedback
+System feedback elements should be used to inform user about important system actions.
+
+![Example](/src/style/assets/feed-ex1.jpg)
+
Inform about finished/successful actions.
+
+![Example](/src/style/assets/feed-ex2.jpg)
+
Inform about system errors.
+
+![Example](/src/style/assets/feed-ex3.jpg)
+
Inform about input errors (ex. wrong data format).
+
+![Example](/src/style/assets/feed-ex4.jpg)
+
Skip obvious information.
+
+## Feedback Categories
+### Neutral
+General information
+
+
Error
+Information about system problem
+
+
Success
+Information about successful or finished activity
+
+
Warning
+Information about action that can be potentially harmful
+
+## Feedback forms
+### Contextual Feedback
+It is short feedback (text, icon) shown next to the linked area when feedback action occurs. It can be show for a short time (ex. 3 seconds) or it can stay until it is relevant.
+
+Option to provide feedback next to associated element should be considered as default. Consider alternatives only if contextual feedback is not possible or not linked with any screen area.
+
+![Example](/src/style/assets/feedback1.jpg)
+
+### Notifications
+Used for general system feedback.
+
+![Example](/src/style/assets/feedback2.jpg)
+
+For more info, check [Notifications](../#/components/notification).
+
+### Modal Window
+Used when system feedback breaks user activity and using a system can’t be continued without getting an info or making a decision.
+
+![Example](/src/style/assets/feedback3.jpg)
+
+For more info, check [Overlays](../#/general/7-overlays).