e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
79 lines
2.5 KiB
ReStructuredText
79 lines
2.5 KiB
ReStructuredText
===========================================================
|
|
Generate leads/opportunities from your website contact page
|
|
===========================================================
|
|
|
|
Automating the lead/opportunity generation will considerably improve
|
|
your efficiency. Any visitor using the contact form on your website will
|
|
create a lead/opportunity in the pipeline.
|
|
|
|
Use the contact us on your website
|
|
==================================
|
|
|
|
You should first go to your website app.
|
|
|
|
|image0|\ |image1|
|
|
|
|
With the CRM app installed, you benefit from a ready-to-use contact form
|
|
on your Odoo website that will generate leads/opportunities
|
|
automatically.
|
|
|
|
.. image:: media/generate_from_website03.png
|
|
:align: center
|
|
|
|
To change to a specific sales channel, go to :menuselection:`Website
|
|
--> Configuration --> Settings` under *Communication* you will find the
|
|
Contact Form info and where to change the *Sales Channel* or
|
|
*Salesperson*.
|
|
|
|
.. image:: media/generate_from_website04.png
|
|
:align: center
|
|
|
|
Create a custom contact form
|
|
============================
|
|
|
|
You may want to know more from your visitor when they use the contact form to
|
|
you will need to build a custom contact form on your
|
|
website. These contact forms can generate multiple types of records in
|
|
the system (emails, leads/opportunities, project tasks, helpdesk
|
|
tickets, etc.)
|
|
|
|
Configuration
|
|
=============
|
|
|
|
You will need to install the free *Form Builder* module, only
|
|
available in Odoo Enterprise.
|
|
|
|
.. image:: media/generate_from_website05.png
|
|
:align: center
|
|
|
|
Create a custom contact form
|
|
----------------------------
|
|
|
|
First, go to the page where you want to put your contact form. In edit mode, drag
|
|
the form builder onto the page, and you will be able to add all the fields
|
|
you wish.
|
|
|
|
.. image:: media/generate_from_website06.png
|
|
:align: center
|
|
|
|
By default, any new contact form will send an email. You can switch to
|
|
lead/opportunity generation in *Change Form Parameters*.
|
|
|
|
.. note::
|
|
If the same visitor uses the contact form twice, the second
|
|
entry will be added to the first lead/opportunity in the chatter.
|
|
|
|
Generate leads instead of opportunities
|
|
=======================================
|
|
|
|
When using a contact form, you should use a qualification step
|
|
before assigning the form to the right sales people. To do so, activate *Leads*
|
|
in CRM settings and refer to :doc:`convert`.
|
|
|
|
.. |image0| image:: ./media/generate_from_website01.png
|
|
:width: 1.04401in
|
|
:height: 1.16146in
|
|
.. |image1| image:: ./media/generate_from_website02.png
|
|
:width: 1.43229in
|
|
:height: 1.16244in
|