Odoo Documentation¶
Welcome to the Odoo Documentation Homebase. Any question that might be left unanswered, you can ask the experts at forum.odoo.com. When you feel ready don’t hesitate to contact your nearby implementation partner. (Link) Below, we gathered together the most interesting articles for you. Enjoy the steep learning curve with which we aim to provide you here!
Note
If you consider yourself a user, pleas note, that we have built in great walk-through into the software itself. You can just explore:
- For Playing: Clean Database (link: demo.odoo.com/clean)
- For Exploring: Full Demo-Database (link: demo.odoo.com/full)
Customers | PwrUser/Consultant | Web-Designer | Developer |
---|---|---|---|
Welcome to Odoo | Welcome to Odoo | Welcome to Odoo | Welcome to Odoo |
Installation | Installation | Installation | Installation |
Apps Docu | Apps Docu | Apps Docu | Apps Docu |
Tutorial: PowerUser | Tutorial: Web-Designer | Tutorial: Developper |
Table is better than the following structure, right?
Customers¶
Welcome to Odoo¶
Overview¶
[General Onboearding Video for Customers and PowerUsers/Developers alike]
Audiences¶
The target audience of this documentation are Customers, PowerUsers and Developers alike. For your ease, we will give you a hint on top of every page, if it is meant for your audience. If you want to get answers about the actual how-to-this’, how-to-thats you will have a great learning experience with our walk-throughs built into the software.
Structure¶
The structure of the whole documentation (not this document, but the whole documentation topic)
- This “Homebase”
- Forum
- Implementation Partners / Bilateral
- Walk-Trhough
- Code
(By now the structure of this documentation should be clear already, so - althoug the title - not a topic here)
Installation¶
Overview¶
Installation of Odoo is really easy. We built a comprehensive library of best practices coded into a human readable installation protocol language called Ansible. Those protocols are well commented so you might find all the information you need right at the source.
What you need for a kickstart is:
1 2 3 4 5 | ubuntu 14.04 LTS # A local Virtual Machine is recommended, you can find some preconfigured boxes at vagrant.com/odoo
if Windows == True: Oracle VirtualBox
sudo apt-get install ansible # you cann browse available protocols ("playbooks") here: www.github.com/odoo/playbooks
# Probably you should adapt them to your needs, they are all very well commented
ansible go # that's it
|
Dev-Tools¶
If you want start coding, we collected here some tools we love:
- Pycharm
- Vim
- Vagrant/Docker Environment
- A collection of useful and approved code snippets for your IDE: link here to a github
- Xpath browser
(with links to further information)
Security and Performance¶
Advanced section, which is written in a way that lets the customer know, that this is all very secure and very performant, cutting edge technology
Scalability¶
Here some vps, opennebula, amazon, private serverfarm, etc... stuff to guide (professionals) AND impress (customers)
Apps Docu¶
Accounting¶
Features & Limitations¶
Odoo | SAP | Header 3 |
---|---|---|
lila | blue | column 3 |
easy | Very difficult. | |
Fast | Slow and costly. |
|
Affordable |
The Odoo Way¶
Typical highlevel workflows explained to let customers/powerusers quickly know if it is compliant with their needs, or where they need to dig further
-> prominent and highlighted link to walk-through
Module Index¶
module 1¶
autogenerated with short description (from sourcecode)
Feature | Description |
---|---|
lila | blue column 3 |
easy | Very difflt. |
Fast | Slow and - Cells costly. - contain
|
Affordable |
English Name | Python Name | Type | Help String | visible |
---|---|---|---|---|
Is Company? | is_company | bol | blablabla | yes |
Category | category_id | m2m | blablabla | yes/no |
Field glossary (sic!) with english name, technical name, help string - should be somewhat grouped per class and should be indicated if it is visible or not.
module 2¶
...
module 3¶
...
Manufacturing¶
[...]
etcetera¶
Power Users / Consultants¶
Developers¶
Tutorial: Developper¶
All basic concepts explained generically. For detailed understanding provide commented/”hinted” links to source code.
Module-Design¶
Viewdesign¶
explain clearly every concept (such as: xpath (with tools), inheritance, priority, client side vs backend execution (!!!), available xml-tags) but let views itself unexplained (refer probably to field glossary in the apps documentation and see visibility there)
Reports/Output¶
QWeb
Security¶
Odoo-Inheritance¶
Api-Documentation¶
(link to structured, searchable documentation)