[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
/* global Immutable, React */
|
|
|
|
/* global createAtom, findAncestor */
|
2015-02-24 18:02:29 +07:00
|
|
|
(function () {
|
|
|
|
'use strict';
|
2022-12-22 17:46:58 +07:00
|
|
|
// NOTE: cheat_sheet.rst
|
2015-02-24 18:02:29 +07:00
|
|
|
|
|
|
|
var data = createAtom();
|
|
|
|
data.addWatch('chart', function (k, m, prev, next) {
|
|
|
|
React.render(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
React.createElement(Controls, { entry: next }),
|
2015-02-24 18:02:29 +07:00
|
|
|
document.getElementById('entries-control'));
|
|
|
|
React.render(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
React.createElement(FormatEntry, { entry: next }),
|
2015-02-24 18:02:29 +07:00
|
|
|
document.querySelector('.journal-entries'));
|
|
|
|
});
|
|
|
|
document.addEventListener('DOMContentLoaded', function () {
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
var entries_section = findAncestor(document.querySelector('.journal-entries'), 'section');
|
|
|
|
if (!entries_section) { return; }
|
2015-03-17 20:58:55 +07:00
|
|
|
|
|
|
|
var controls = document.createElement('div');
|
2015-02-24 18:02:29 +07:00
|
|
|
controls.setAttribute('id', 'entries-control');
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
entries_section.insertBefore(controls, entries_section.lastElementChild);
|
2015-02-24 18:02:29 +07:00
|
|
|
|
|
|
|
data.reset(entries.first());
|
|
|
|
});
|
|
|
|
|
|
|
|
var Controls = React.createClass({
|
|
|
|
render: function () {
|
|
|
|
var _this = this;
|
|
|
|
return React.DOM.div(
|
|
|
|
null,
|
2015-03-03 16:23:26 +07:00
|
|
|
entries.map(function (entry, index) {
|
|
|
|
return React.DOM.label(
|
|
|
|
{
|
|
|
|
key: index,
|
|
|
|
style: { display: 'block' },
|
|
|
|
},
|
|
|
|
React.DOM.input({
|
|
|
|
type: 'radio',
|
|
|
|
checked: Immutable.is(entry, this.props.entry),
|
|
|
|
onChange: function (e) {
|
|
|
|
data.reset(entry);
|
|
|
|
}
|
|
|
|
}),
|
|
|
|
' ',
|
|
|
|
entry.get('title')
|
|
|
|
);
|
2015-03-11 20:20:13 +07:00
|
|
|
}, this),
|
2015-02-24 18:02:29 +07:00
|
|
|
this.props.entry && React.DOM.p(null, this.props.entry.get('help'))
|
|
|
|
);
|
|
|
|
}
|
|
|
|
});
|
|
|
|
var FormatEntry = React.createClass({
|
|
|
|
render: function () {
|
2015-03-10 19:02:16 +07:00
|
|
|
var entry = this.props.entry;
|
|
|
|
return React.DOM.div(
|
|
|
|
null,
|
|
|
|
React.DOM.table(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ className: 'table table-sm d-c-table' },
|
2015-03-10 19:02:16 +07:00
|
|
|
React.DOM.thead(
|
|
|
|
null,
|
|
|
|
React.DOM.tr(
|
|
|
|
null,
|
|
|
|
React.DOM.th(),
|
|
|
|
React.DOM.th(null, "Debit"),
|
|
|
|
React.DOM.th(null, "Credit")
|
|
|
|
)
|
|
|
|
),
|
|
|
|
React.DOM.tbody(
|
2015-02-24 18:02:29 +07:00
|
|
|
null,
|
2015-03-10 19:02:16 +07:00
|
|
|
this.render_rows()
|
2015-02-24 18:02:29 +07:00
|
|
|
)
|
|
|
|
),
|
2015-03-10 19:02:16 +07:00
|
|
|
React.createElement(Listing, {
|
|
|
|
heading: "Explanation",
|
|
|
|
items: entry && entry.get('explanation')
|
|
|
|
}),
|
|
|
|
React.createElement(Listing, {
|
|
|
|
heading: "Configuration",
|
|
|
|
items: entry && entry.get('configuration')
|
|
|
|
})
|
2015-02-24 18:02:29 +07:00
|
|
|
);
|
|
|
|
},
|
|
|
|
render_rows: function () {
|
|
|
|
if (!this.props.entry) { return; }
|
2015-03-11 20:20:13 +07:00
|
|
|
return this.props.entry.get('operations').map(this.render_row);
|
2015-02-24 18:02:29 +07:00
|
|
|
},
|
|
|
|
render_row: function (entry, index) {
|
|
|
|
if (!entry) {
|
|
|
|
return React.DOM.tr(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ key: 'spacer-' + index },
|
|
|
|
React.DOM.td({ colSpan: 3 }, "\u00A0")
|
2015-02-24 18:02:29 +07:00
|
|
|
);
|
|
|
|
}
|
|
|
|
return React.DOM.tr(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ key: index },
|
2015-02-24 18:02:29 +07:00
|
|
|
React.DOM.td(null, entry.get('account')),
|
2015-02-25 22:02:40 +07:00
|
|
|
React.DOM.td(null, entry.get('debit')),
|
|
|
|
React.DOM.td(null, entry.get('credit'))
|
2015-02-24 18:02:29 +07:00
|
|
|
);
|
|
|
|
}
|
|
|
|
});
|
2015-03-10 19:02:16 +07:00
|
|
|
var Listing = React.createClass({
|
|
|
|
render: function () {
|
|
|
|
if (!this.props.items || this.props.items.isEmpty()) {
|
|
|
|
return React.DOM.div();
|
|
|
|
}
|
2015-03-16 16:27:15 +07:00
|
|
|
var items = this.props.items, epilog = Immutable.List();
|
|
|
|
var idx = items.indexOf(null);
|
|
|
|
if (idx !== -1) {
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
epilog = items.slice(idx + 1);
|
2015-03-16 16:27:15 +07:00
|
|
|
items = items.take(idx);
|
|
|
|
}
|
2015-03-10 19:02:16 +07:00
|
|
|
return React.DOM.div(
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ className: 'entries-listing' },
|
2015-03-10 19:02:16 +07:00
|
|
|
React.DOM.h4(null, this.props.heading, ':'),
|
|
|
|
React.DOM.ul(
|
|
|
|
null,
|
2015-03-16 16:27:15 +07:00
|
|
|
items.map(function (item, index) {
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
return React.DOM.li({ key: index }, item);
|
2015-03-11 20:20:13 +07:00
|
|
|
})
|
2015-03-16 16:27:15 +07:00
|
|
|
),
|
|
|
|
epilog.map(function (item, index) {
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
return React.DOM.p({ key: index }, item);
|
2015-03-16 16:27:15 +07:00
|
|
|
})
|
2015-03-10 19:02:16 +07:00
|
|
|
);
|
|
|
|
}
|
|
|
|
});
|
2015-02-24 18:02:29 +07:00
|
|
|
|
|
|
|
var entries = Immutable.fromJS([
|
|
|
|
{
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Company Incorporation",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Cash', debit: 1000 },
|
|
|
|
{ account: 'Equity: Common Stock', credit: 1000 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"The company receives $1,000 in cash",
|
2015-03-18 21:44:28 +07:00
|
|
|
"Shares worth of $1,000 belong to the founders",
|
|
|
|
null,
|
|
|
|
"The initial capital can be cash, but could also be intellectual property, goodwill from a previous company, licences, know how, etc…",
|
|
|
|
"Sometimes, capital is not released immediately, accounts for \"capital to be released\" may be necessary."
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
configuration: []
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Customer Invoice ($100 + 9% tax)",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Revenue: Goods', credit: 100 },
|
|
|
|
{ account: 'Liabilities: Deferred Tax Liabilities', credit: 9 },
|
|
|
|
{ account: 'Assets: Accounts Receivable', debit: 109 },
|
|
|
|
{ account: 'Assets: Inventory', credit: 50 },
|
|
|
|
{ account: 'Expenses: Cost of Goods Sold', debit: 50 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"Revenues increase by $100",
|
|
|
|
"A tax to pay at the end of the month of $9",
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
"The customer owes $109",
|
2015-03-16 16:07:10 +07:00
|
|
|
"The inventory is decreased by $50 (shipping of the goods)",
|
|
|
|
"The cost of goods sold decreases the gross profit by $50"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Revenue: defined on the product, or the product category if not on the product, field Income Account",
|
2021-05-31 16:56:48 +07:00
|
|
|
"Deferred Tax Liabilities: defined on the tax used on the invoice line",
|
2015-03-16 16:07:10 +07:00
|
|
|
"Accounts Receivable: defined on the customer (property)",
|
|
|
|
"Inventory: defined on the category of the related product (property)",
|
|
|
|
"Expenses: defined on the product, or the category of product (property)",
|
|
|
|
null,
|
|
|
|
"The fiscal position used on the invoice may have a rule that replaces the Income Account or the tax defined on the product by another one."
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-17 20:11:36 +07:00
|
|
|
title: "Customer payment",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Cash', debit: 109 },
|
|
|
|
{ account: 'Assets: Accounts Receivable', credit: 109 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-17 20:11:36 +07:00
|
|
|
"The company receives $109 in cash",
|
2022-12-22 17:46:58 +07:00
|
|
|
"The receivable held against the client is reduced by $109"
|
2015-03-17 20:11:36 +07:00
|
|
|
],
|
|
|
|
configuration: [
|
|
|
|
"Cash: defined on the journal used when registering the payment, fields Default Credit Account and Default Debit Account",
|
|
|
|
"Accounts Receivable: defined on the customer (property)"
|
|
|
|
]
|
|
|
|
}, {
|
|
|
|
title: "Supplier Bill (Purchase Order $50 but Invoice $52)",
|
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Uninvoiced Inventory', debit: 50 },
|
|
|
|
{ account: 'Assets: Deferred Tax Assets', debit: 4.68 },
|
|
|
|
{ account: 'Expenses: Price Difference', debit: 2 },
|
|
|
|
{ account: 'Liabilities: Accounts Payable', credit: 56.68 }
|
2015-03-17 20:11:36 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
|
|
|
"A temporary account is used to note goods to receive",
|
|
|
|
"The purchase order provides prices of goods, the actual invoice may include extra costs such as shipping",
|
|
|
|
"The company still needs to pay the vendor (traded an asset against a liability)"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Uninvoiced Inventory: defined on the product or the category of related product, field: Stock Input Account",
|
2015-03-17 20:11:36 +07:00
|
|
|
"Deferred Tax Assets: defined on the tax used on the purchase order line",
|
|
|
|
"Accounts Payable: defined on the supplier related to the bill",
|
2015-03-16 16:07:10 +07:00
|
|
|
null,
|
2015-03-17 20:11:36 +07:00
|
|
|
"In this scenario, the purchase order was $50 but the company received an invoice for $52 as there were extra shipping costs"
|
2015-03-16 16:07:10 +07:00
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-17 20:11:36 +07:00
|
|
|
title: "Supplier Goods Received (Purchase Order: $50)",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Inventory', debit: 50 },
|
|
|
|
{ account: 'Assets: Uninvoiced Inventory', credit: 50 },
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-17 20:11:36 +07:00
|
|
|
"Inventory is increased by $50, the expected amount coming from the purchase order",
|
|
|
|
"A temporary account is used for the counterpart and will be cleared when receiving the invoice"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
2015-03-17 20:11:36 +07:00
|
|
|
"Uninvoiced Inventory: defined on the product or the category of related product, field: Stock Input Account",
|
|
|
|
"Inventory: defined on the product category, field: Stock Valuation"
|
2015-03-16 16:07:10 +07:00
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Buy an asset ($300,000 - no tax)",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Buildings', debit: 300000 },
|
|
|
|
{ account: 'Liabilities: Accounts Payable', credit: 300000 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"The company gets an asset worth of $300,000",
|
|
|
|
"The company needs to pay $300,000 to the vendor (traded an asset against a liability)"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Buildings: Defined on the Asset category selected on the supplier bill line",
|
|
|
|
"Accounts Payable: defined on the supplier related to the bill (property)"
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Pay supplier invoice",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Liabilities: Accounts Payable', debit: 300000 },
|
|
|
|
{ account: 'Assets: Cash', credit: 300000 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"The company owns $300,000 less to the supplier (liabilities are settled)",
|
|
|
|
"The company's cash is reduced by $300,000 (reduction of asset)"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Accounts Payable: defined on the supplier you pay (property)",
|
|
|
|
"Cash: defined on the journal related to the payment method"
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Cash sale (Sales Receipt)",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Cash', debit: 109 },
|
|
|
|
{ account: 'Revenue: Goods', credit: 100 },
|
|
|
|
{ account: 'Liabilities: Deferred Tax Liabilities', credit: 9 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"Company's cash is increased by $109",
|
|
|
|
"Revenues increase by $100",
|
|
|
|
"A tax of $9 has to be paid"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Cash: Payment method defined on the Sales Receipt",
|
|
|
|
"Sales: Defined on the product used in the sales receipt, or the category of product if empty",
|
|
|
|
"Deferred Tax Liabilities: Defined on the tax used in the sales receipt (coming from the product)"
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Customer pays invoice, 5% early payment rebate",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Assets: Cash', debit: 950 },
|
|
|
|
{ account: 'Revenue: Sales Discount', debit: 50 },
|
|
|
|
{ account: 'Assets: Accounts Receivable', credit: 1000 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"Company's cash is increased by $950",
|
|
|
|
"Sales discounts lowering effective revenues by $50",
|
|
|
|
"The customer owns $1000 less to the company"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"Cash: is defined on the journal related to the payment / bank statement",
|
|
|
|
"Sales Discount: is selected during the payment matching process",
|
|
|
|
"Accounts Receivable: is defined on the customer associated to the payment"
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}, {
|
2015-03-16 16:07:10 +07:00
|
|
|
title: "Fiscal year closing — positive earnings and 50% dividends",
|
2015-02-24 18:02:29 +07:00
|
|
|
operations: [
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
{ account: 'Net Profit', debit: 1000 },
|
|
|
|
{ account: 'Equity: Retained Earnings', credit: 500 },
|
|
|
|
{ account: 'Liabilities: Dividend Payable', credit: 500 }
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
|
|
|
explanation: [
|
2015-03-16 16:07:10 +07:00
|
|
|
"The P&L is cleared (net profit)",
|
|
|
|
"50% is transferred to retained earnings",
|
|
|
|
"50% will be paid to shareholders as dividends"
|
2015-03-10 19:02:16 +07:00
|
|
|
],
|
2015-03-16 16:07:10 +07:00
|
|
|
configuration: [
|
|
|
|
"This transaction is recorded by the advisor before closing the fiscal year, depending on how the company uses its net profit."
|
|
|
|
]
|
2015-02-24 18:02:29 +07:00
|
|
|
}
|
|
|
|
]);
|
|
|
|
}());
|