# HG changeset patch # User Goffi # Date 1538593302 -7200 # Node ID 28789926852af388b6389e2ee66544b80bd92732 # Parent 122dd136d1ab7ecbe61472a0502206b5dca4d437 doc: Libervia web framework quick_start + css_framework, first drafts diff -r 122dd136d1ab -r 28789926852a doc/web_framework/css_framework.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/web_framework/css_framework.rst Wed Oct 03 21:01:42 2018 +0200 @@ -0,0 +1,70 @@ +Libervia CSS Framework +====================== + + +Libervia come with generic CSS styling which is thought to be re-usable. If you create a new theme/site, you don't have to use it and can use something totally different, but building on top of Libervia CSS make theming more easy and consistent as you can re-use existant components without changing the classes. + +Bases +----- +All CSS files must be in the ``static`` directory of your theme. Following names are assumed to be in this directory. + +Libervia may link one to several style sheets when it renders a template. It will always links the following file (if they exist): + - ``fonts.css`` (fonts loading) + - ``styles.css`` (main CSS style, see below) + - ``styles_extra`` (customizations of main style) + +Then it will link styles relative to the current theme (where path is joined with a ``_``). For instance, if your template is ``blog/article.html``, the following files will be linked (in this order, and if they exists): + - ``blog.css`` + - ``blog_article.css`` + +You can suffix any style sheet (but ``fonts.css``) with ``_noscript``: this suffixed file will be loaded only when javascript is not available, allowing to adapt your template to such case. + +The main CSS styling is ``styles.css``, it contains styles for every major elements used in Libervia. +CSS in Libervia follows ``BEM`` (Block Element Modifier) conventions. + +If you create a new theme, you should not touch ``styles.css``, but work on ``styles_extra.css`` instead. The later doesn't exist in default Libervia theme on purpose. + +There are a few "magic" classes, which imply some DOM modification when Javascript is enabled, see below. +Last but not least, there is also a "state system", i.e. classes which are dynamically changed during runtime. + +Magic Classes +------------- +Magic classes are classes which imply a modification of DOM when the page is loaded and Javascript is activated. +The modification is done by a script launched by ``base/base.html``. +There are only a few of them: + +box--expand + When this class is applied, the box will be folded when is higher than 250px, and 2 "expand zone" (buttons) + will be added on top and bottom of the box to expand/reduce it. + +state_init + This is linked to state system (see below). When applied, the element will keep the ``state_init`` class until + clicked for the first time, then it will apply other magic classes effects if suitable. + +State System +------------ +A basic state system is used to do some dynamic operation (like (un)folding a box). The two main states are: + +state_init + This class is present until first clicked + +state_clicked + This state is used with some magic classes (e.g. ``box-expand``) or when a clicking method from ``common.js`` + is used on an element (e.g. ``clicked_cls``). The classes is toggled on each click. + +Some classes are used to manipulate elements according to state: + +show_if_init + Display this class only if in ``state_init``. + +show_if_parent_clicked + display this class only if **parent** is in ``state_clicked`` + +show_if_parent_not_clicked + display this class only if **parent** is **not** in ``state_clicked`` + +show_if_grandparent_clicked + display this class only if **grandparent** is in ``state_clicked`` + +show_if_grandparent_not_clicked + display this class only if **grandparent** is **not** in ``state_clicked`` diff -r 122dd136d1ab -r 28789926852a doc/web_framework/quick_start.rst --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/web_framework/quick_start.rst Wed Oct 03 21:01:42 2018 +0200 @@ -0,0 +1,126 @@ +================================== +Libervia Web Framework Quick Start +================================== + +This documentation will help you getting started with Libervia Web Framework to create your first web site. + +Creating an external site +------------------------- + +First let's get basic vocabulary we'll use: a "site" is all the data necessary to display a full web site. +A site have one or more "themes" which is a way to display it. A theme may be anything from simple style change (e.g. "dark" theme, or "high contrast"), to a complete rework of the apparence of a site, but keep the same pages structure (see below). If you want to change pages structure, you have to make a new site. +A site is made of pages and templates. Pages are the code which gather and manipulate the data, and templates are about the final rendering. +Don't worry too much if you don't get it yet, we'll see that with a practical example. + +We'll create the classical "Salut à Toi le monde" site. + +You first have to choose a location were your site will be. We name "external site" any site which is not the standard Libervia site. +Choose a location, for instance ``~/dev/libervia_quick_start`` then create the following hierarchy or directories inside it: + +- templates/ + - default/ +- pages/ +- i18n/ + +``templates`` is where you'll put… template, used to render the final pages. ``default`` is a theme name, this one is special as is it the main theme of your site and must always exist. +``pages`` is where you'll put python code to manipulate data of your site. +``i18n`` is used for translating your site in other languages, but we'll get to this later. + +Now we have to declare this new site to Salut à Toi and Libervia. When installing Salut à Toi, you should have created a ``sat.conf`` file, if not, just create one at ``~/.sat.conf``. +Edit this file, and in the section ``[DEFAULT]``, add the following setting: + +.. code:: javascript + + sites_path_public_dict = { + "quick_start": "~/dev/libervia_quick_start" + } + +This declare the templates of your websites, you'll now be able to use them with tools like ``jp``. + +Now you have to add your site to Libervia. Choose a host name, and link it the site name by adding a ``vhost_dict`` setting in your ``[libervia]`` section of ``sat.conf``: + +.. code:: javascript + + vhosts_dict = {"quickstart.int": "quick_start"} + +That means that when you'll get to ``quickstart.int``, you'll land to your own site instead of official Libervia one. + +Last but not least, you have to declare this website as alias for your localhost during developments. On GNU/Linux, this is done by editing ``/etc/hosts`` (as root user), to have something like that:: + + 127.0.0.1 localhost.localdomain localhost quickstart.int + ::1 localhost.localdomain localhost quickstart.int + +To see your website, you'll have to use the specified host name, and the port used by Libervia (8080 by default). If you kept default configuration, let's go to http://quickstart.int:8080. + +But for now, you'll just see ``No Such Resource`` (if you see standard Libervia site, that means that something is not working, you can check for assistance in our XMPP room (`sat@chat.jabberfr.org `_)). + +All right? Good, let's start then. + +A first template +---------------- + +For this simple page, we won't have any data to manipulate, so let's start directly with the template. +Create a ``salut.html`` file at ``templates/default/salut/salut.html`` inside your development directory, and put the following content inside: + +.. code:: jinja + + {% if not embedded %}{% extends 'base/base.html' %}{% endif %} + + {% block body %} + Salut à Toi le monde ! + {% endblock body %} + +Let's explain a bit. + +The template use Jinja2_ engine, which is easy to learn and powerful. You have the documentation available on the official website, you should read in particular the `Template Designer Documentation `_. + +.. code:: jinja + + {% if not embedded %}{% extends 'base/base.html' %}{% endif %} + +This firt line should be present on every front page, it extends the base template which handle many things for you and to facilitate integration with the backend. "But I have not written any ``base/base.html`` template" you may say. That's right, that's because SàT template engine is looking for file in several places. When you link a template, first it will check the current theme of your site, then the ``default`` theme, and finally the ``default`` theme of SàT official site. That allows you to have access to the generic features like the backend integration. + +.. code:: jinja + + {% block body %} + Salut à Toi le monde ! + {% endblock body %} + +The ``base/base.html`` define some common blocks (check Jinja2_ documentation for the definitiion and instructions on how to use blocks). Those blocks are ``title``, ``favicon``, ``body``, ``footer``, ``main_menu``, ``confirm`` and ``category_menu``. For now, you can only take care of the first 4. +The ``body`` block is, as you can guess, the main area of your page, the perfect place to say hello to the world. + +A first page +------------ +We have a template, but we need a page to use it. +Pages are put in a directories hierarchy which correspond directly to your URL hierarchy, simple! To be used as a Libervia page, a directory must contain a file named ``page_meta.py``. So to create your first page, you just have to create the file ``pages/salut/page_meta.py`` and put this inside: + +.. code:: python + + #!/usr/bin/env python2.7 + #-*- coding: utf-8 -*- + + template = "salut/salut.html" + +And that's it! Note that we are still using Python 2.7, as the rest of Salut à Toi ecosystem. This will change for ``0.8`` release which will see the port of the whole project to Python 3. + +Now you certainly want to see your rendered page. For this you'll have to restart Libervia (automatic reloading is not yet available for pages, but it works for templates). In Libervia logs, you should see something like this:: + + + [libervia.server.pages] [quickstart.int] Added /salut page + +Now let's go to http://quickstart.int:8080/salut and admire your first Libervia page :). + +But if you go to http://quickstart.int:8080 you still see this annoying ``No Such Resource``, would not it be nice to land directly to your salut page? +All you have to do for that, is to add a couple of lines in your ``sat.conf``, once again in ``[libervia]`` section: + +.. code:: javascript + + url_redirections_dict = { + "quick_start": { + "/": "/salut" + } + } + +That means that the root of your ``quick_start`` site is redirected to your ``salut`` page. After restarting Libervia, you can check again http://quickstart.int:8080, you should see the welcoming message. + +.. _Jinja2: http://jinja.pocoo.org/