Unverified Commit dd8d8326 authored by Gicquel's avatar Gicquel Committed by gitbook-bot
Browse files

GitBook: [master] 2 pages and 3 assets modified

parent 1d4f8e79
.gitbook/assets/image (8).png

230 KB | W: | H:

.gitbook/assets/image (8).png

33 KB | W: | H:

.gitbook/assets/image (8).png
.gitbook/assets/image (8).png
.gitbook/assets/image (8).png
.gitbook/assets/image (8).png
  • 2-up
  • Swipe
  • Onion skin
.gitbook/assets/image (9).png

24.3 KB | W: | H:

.gitbook/assets/image (9).png

230 KB | W: | H:

.gitbook/assets/image (9).png
.gitbook/assets/image (9).png
.gitbook/assets/image (9).png
.gitbook/assets/image (9).png
  • 2-up
  • Swipe
  • Onion skin
......@@ -40,7 +40,7 @@ $ npm run serve
If all goes well you should be directed to a page like this :
![](../../.gitbook/assets/image%20%289%29.png)
![](../../.gitbook/assets/image%20%2810%29.png)
......
......@@ -6,7 +6,15 @@ Since Albiziapp aims to mimic mobile look and feels, it is structured using the
Think of a page as a specific screen of a mobile app. Pages are practical for performing fast interactions. They usually have only one purpose, and they take all the screen.
![A page for entering record](../../.gitbook/assets/image%20%288%29.png)
{% hint style="info" %}
It's a best practice to keep pages focused on only one task
{% endhint %}
### Creating a page
Creating a page is
```
$ give me super-powers
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment