Search 1.9 billion lines of Odoo code on GitHub

website_cms

Author: Simone Orsi - Camptocamp, Odoo Community Association (OCA)
License: AGPL-3
Branch: 9.0-website_cms_theme-jne
Repository: JonathanNEMRY/website-cms
Dependencies: base, web, and website
Languages: JavaScript (61, 1.6%), Python (1973, 53.2%), XML (1046, 28.2%), make (190, 5.1%), and reStructuredText (439, 11.8%)
Other repositories: gfcapalbo/website, guewen/website, oscarolar/website-cms, redcor/website-cms, simahawk/website, and simahawk/website-cms

<img alt="License" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> <a name="website-cms"></a> <h2>Website CMS</h2> <p>This is a module that adds real CMS features to your Odoo website.</p> <p>Documentation: TODO</p> <a name="premise"></a> <h3>Premise</h3> <p>Odoo has no real &quot;Content Management System&quot; features. You cannot manage contents, since - beside blogs and blogposts - you don't have any real &quot;web content&quot;. You can design nice pages on the fly using the website builder - which is indeed a powerful and awesome feature - but that's not the only thing a CMS should be able to do.</p> <p>Yes, you have &quot;pages&quot; but right now an Odoo page is just a template with some specific characteristics (flags, and so on) plus a fixed route &quot;/page&quot;. So, every page's URL in the website will be something like &quot;/page/my-nice-article-about-something&quot;. The same goes for blogs and blogposts: you will always have URLs like &quot;/blog/my-nice-blog-1/posts/my-interesting-post-1&quot;.</p> <p>With this limitations you cannot organize contents (a page, an attachment, etc) in sections and sub sections, hence you cannot build a hierarchy that will allow to expose contents in a meaningful way, for you and your visitors.</p> <p>The goal of this module is to provide base capabilities for creating and managing web contents.</p> <p>Note that this module does not provide a whole theme, but gives you the right tools to create yours. So you should build your own theme to expose your content, navigation, etc.</p> <a name="main-features"></a> <h3>Main features</h3> <ul> <li><p class="first">Separation of concerns between <code>page</code> (content) and <code>view</code> (presentation)</p> <blockquote> <p>A page is the content you publish and you can assign a view to it. A view is just an Odoo template that present your content.</p> </blockquote> </li> <li><p class="first">Page types</p> <blockquote> <p>We define 2 basic types: <cite>Simple</cite> and <cite>News</cite>. You can add more and list, present, search pages in different ways based on types.</p> </blockquote> </li> <li><p class="first">Reusable views</p> <blockquote> <p>Create your own views according to your website design and reuse them when needed.</p> </blockquote> </li> <li><p class="first">Publish media and categorize it</p> <blockquote> <p>A <code>media</code> could be everything: an image, a video, a link to an image or a video. You can categorize it rely on auto-categorization based on mimetypes. Preview images are loaded automatically but you can customize them.</p> </blockquote> </li> <li><p class="first">Automatic navigation and site hierarchy</p> <blockquote> <p>A page can contain other pages, acting like a folder. By nesting pages you create a hierarchy. This can be used to show global and contextual navigation without having to customize menu links every now and then.</p> </blockquote> </li> <li><p class="first">Meaningful URLs</p> <blockquote> <p>Pages' URLs are built using their hierarchy. For instance, if you have a section <cite>cars</cite> that contains a sub section <cite>sport</cite> that contains a page 'Porche' the final URL will be <cite>/cms/cars/sport/porche</cite>.</p> </blockquote> </li> <li><p class="first">Manage redirects within page backend</p> <blockquote> <p>You can force a page to redirect to another page or to an external link, and you can choose which kind of redirect status code to use (301, 302, etc)</p> </blockquote> </li> <li><p class="first">Protect your content</p> <blockquote> <p>On each page you can decide who can view it (edit permission yet to come). This happens at page level not view's, so that you can have different pages presented with same view but with different permissions.</p> </blockquote> </li> <li><p class="first">Full text search</p> <blockquote> <p>The extra module <code>website_cms_search</code> adds features for doing full text searches.</p> </blockquote> </li> </ul> <a name="bug-tracker"></a> <h2>Bug Tracker</h2> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/CMS/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported.</p> <a name="credits"></a> <h2>Credits</h2> <a name="contributors"></a> <h3>Contributors</h3> <p>Read the <a class="reference external" href="./AUTHORS">contributors list</a></p> <a name="maintainer"></a> <h3>Maintainer</h3> <a class="reference external image-reference" href="http://odoo-community.org"><img alt="Odoo Community Association" src="http://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="http://odoo-community.org">http://odoo-community.org</a>.</p>