6f125de01b
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 closes odoo/documentation#2006 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
49 lines
1.8 KiB
ReStructuredText
49 lines
1.8 KiB
ReStructuredText
======================
|
||
Track and Manage Talks
|
||
======================
|
||
|
||
Allow partners to submit talk proposals so they can share their knowledge and expertise. Good
|
||
speakers and talks are what make your event great.
|
||
|
||
Configuration
|
||
=============
|
||
|
||
| Go to :menuselection:`Events --> Configuration --> Settings` and enable *Schedule & Tracks*.
|
||
| Now, in your event's form, once *Website menu* is enabled, the options *Tracks on Website* and
|
||
*Track Proposals on Website* become available. Enabling them adds the menus *Talks*,
|
||
*Talk Proposals*, and *Agenda* to your website.
|
||
|
||
.. image:: track_talks/track_proposals_website.png
|
||
:align: center
|
||
:alt: View of an event form and the options to track and propose speaker in Odoo Events
|
||
|
||
Besides having the ability to suggest their own talks, the website now allows users to see a list of
|
||
the whole agenda and scheduled talks.
|
||
|
||
.. image:: track_talks/website_menus.png
|
||
:align: center
|
||
:alt: View of the published website and the menus talks, talk proposal and agenda in Odoo Events
|
||
|
||
.. tip::
|
||
To handle tracks internally and not have the menus *Talks*, *Talk Proposals*, and *Agenda*
|
||
online, use the menu *Tracks* individually.
|
||
|
||
Publishing speaker proposals
|
||
----------------------------
|
||
|
||
Once partners have filled in the appropriate form and submitted their proposals, a new *Proposal* is
|
||
instantly created under the menu *Track*.
|
||
|
||
.. image:: track_talks/proposals_list.png
|
||
:align: center
|
||
:alt: View of the talks’ proposals page emphasizing the column proposal in Odoo Events
|
||
|
||
If the proposal is accepted and can go online, simply open its form and click on *Go to Website*.
|
||
From the website page, turn *Published* on.
|
||
|
||
.. image:: track_talks/publish_speakers.png
|
||
:align: center
|
||
:alt: View of the website page to publish a proposed talk for Odoo Events
|
||
|
||
.. seealso::
|
||
- :doc:`../integrations/integration_sms` |