*: auth_password_policy, bus, calendar, event, mass_mailing, stock, survey, web_editor, web_tour, website, website_event, website_forum, website_mass_mailing, website_sale This commit is a first step towards a potential deletion of the assets_common bundle, although that step would need more work, specs and discussions as some layouts kinda only use the assets_common bundle (some take the full assets_common but parts of the assets_backend one for example). The main goal of this commit is to have the assets_frontend bundle directly include the "common" files we need. As a first step, this commit only blindly duplicates them all into assets_frontend (without removing the potentially useless ones). The goal is to have those advantages: - Reaching a frontend page only calls two main JS files (one normal and one lazy-loaded) instead of 4 (two normals and two lazy-loaded). This may help reach a better google page speed (which is becoming more and more strict). - The frontend CSS is built as one: the common SCSS which was using bootstrap variables, or even Odoo-based SCSS added by mistake in common instead of both backend and frontend is now computed with the right bootstrap customizations. E.g. the tempusdominus datetimepickers use bootstrap grays... after this PR, they use the right grays as customized by the user on the website. It was also chosen to not have a common "sub-asset" which is included in assets_frontend. Making assets_frontend completely independent makes sense (as it probably will for other "main" asset bundles): we can focus on adding the files each layout needs without the need of worrying if it impacts unrelated layouts. Sub-assets (when not strictly necessary) is also a source of errors: extending the "main" bundle instead of the right sub-asset it may use (like it was the case with the sub-assets of assets_common: _assets_common_scripts and _assets_common_styles as explained in the previous commit). So this is indeed a small drawback of not factorizing the code for the inclusion of "common" files in bundles but it seems more explicit and easier to maintain that way. Note that adding "common" file is not the most common usecase anyway, apps generally only need files in backend or frontend. The __manifest__ declaration will also likely evolve in more and more uses of wildcards to match entire directories. In the future, adding "common" web-app files in both backend, frontend and other "main" bundles could just be about one line duplicated into each bundle. closes odoo/odoo#100314 Related: odoo/enterprise#31394 Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Organize Events, Trainings & Webinars
Schedule, Promote, Sell, Organize
Organize, promote and sell events online. Whether you organize meetings, conferences, trainings or webinars, Odoo gives you all the features you need to manage your events.
Create Awesome Event Pages
Get rid of old WYSIWYG editors
Create beautiful event pages by drag & droping well designed 'Building Blocks'. Publish event photos, speakers, schedule, etc.
Odoo's unique 'edit inline' approach makes website creation surprisingly easy. "Want to introduce a speaker? to change the price of a ticket? to update a banner? promote sponsors?" just click and change.
Sell Tickets Online
Automate the registration and payment process
Sell registrations to your event with the multi-ticketing feature. Events can be free or for a fee. Attendees can pay online with a credit card or on invoice, based on your configuration.
Boost your sales with early-bird prices, special conditions for members, or extra services with multiple tickets.
A Clean Google Analytics Integration
Control your sales funnel with Google Analytics
Get a clear visibility of your sales funnel. Odoo's Google Analytics trackers are configured by default to track all kind of events related to shopping carts, call-to-actions, etc.
As Odoo marketing tools (mass mailing, campaigns, etc) are also linked with Google Analytics, you get a full view of your business.
Promote Events Efficiently
Mass Mailing & Social Media
Use the segmentation, the social network integration and mass mailing features to promote your events to the right audience. Setup automated emails to attendees to send them last minute details.
Designer-Friendly Themes
Designers love working on Odoo
Themes are awesome and easy to design. You don't need to develop to create new pages, themes or building blocks. We use a clean HTML structure, a bootstrap CSS and our modularity allows to distribute your themes easily.
The building block approach allows the website to stay clean after the end-users start creating new contents.
Make Your Event More Visible
SEO tools at your finger tips
SEO tools are ready to use, with no configuration required. Odoo suggests keywords according to Google most searched terms, Google Analytics tracks your shopping cart events and sitemap are created automatically.
We even do structured content automatically to promote your events and products efficiently in Google.
Leverage Social Media
Optimize: from Ads to Conversions
Create new landing pages easily with the Odoo inline editing feature. Send visitors of your different marketing campaigns to event landing pages to optimize conversions.
And Much More...
Schedule
- Calendar of Events
- Publish related documents
- Ressources allocation
- Automate purchases (catering...)
- Multiple locations and organizers
- Mobile Interface
Sell
- Online or offline sales
- Automated invoicing
- Cancellation policies
- Specific prices for members
- Dashboards and reporting
Organize
- Advanced Planification
- Print Badges
- Automate Follow-up Emails
- Min/Max capacities
- Manage classes and ressources
- Create group of attendees
- Automate statisfaction surveys
Fully Integrated With Others Apps
Get hundreds of open source apps for free
eCommerce
Promote products, sell online, optimize visitors' shopping experiences.
Blogs
Write news, attract new visitors, build customer loyalty.
Our Team
Create a great "About us" page by presenting your team efficiently.