From 366f393ad46808f8c4c8b2a6e28844462793fda1 Mon Sep 17 00:00:00 2001 From: Lucas Dohmen Date: Wed, 20 Nov 2013 15:15:59 +0100 Subject: [PATCH] Foxx: Adjusted introduction according to @mchacki's idea List instead of one sentence --- Documentation/UserManual/Foxx.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Documentation/UserManual/Foxx.md b/Documentation/UserManual/Foxx.md index c04a185dea..d47a1c7eab 100644 --- a/Documentation/UserManual/Foxx.md +++ b/Documentation/UserManual/Foxx.md @@ -26,8 +26,12 @@ separate application server. Think of an Foxx app as a typical web app similar to any other web app using other technologies. A Foxx app provides one or more URLs, which can either be accessed directly from the browser or from a backend application written e.g. in -Ruby or C#. A Foxx app has a routing, accesses data (in ArangoDB), manipulates data, -it can deliver static HTML pages, CSS, Images and much more. +Ruby or C#. Other features include: + +* **Routing:** Define arbitrary routes namespaced via the `Controllers` +* **Accesses data:** Direct access to all data in ArangoDB using simple queries, AQL, traversals and more +* **Manipulates data:** Create new or manipulate existing entries +* Deliver **static files** like HTML pages, CSS or images directly The typical request to a Foxx application will work as follows (only conceptually, a lot of the steps are cached in reality):