Docs: Remove how-tos on customising mixins and overriding core class
These days, to override a mixin it is only required to override the
OrderPlacementMixin; overriding the app and view is not necessary. It is
just a generic case of overriding a core class. A dedicated how-to is
thus unnecessary.
As overriding a core class is the general goal of any advanced
customisation, it has been merged into the customisation section, which
has been given an overhaul as well.
The section regarding modifying apps will be re-added as part of a
higher-level "the Oscar application tree" kind of document.
Attempt at making it clearer what needs to be done for what kind of
customisation. Created a new topic that lines out the prepatory
steps that need to be taken, and moved duplicate information from the
how-tos into the new topic.
my_model_customisations_arent_picked_up now lives in a subsection of the
recipe how_to_customise_models.
The old conventions.rst is now merged into the new coding-style.rst.
The old search.rst has been dropped as it seems outdated.
To set a base for upcoming docs changes, the docs directory structure
has been streamlined to follow a simplified version of Django's docs.
The old _draft folder has been removed. Both files from there and the
current docs that don't fit nicely into the new structure are in _old/
for the moment.
Clean up documentation typos (e.g., use 'e.g.' instead of 'eg'; misspellings; GitHub vs Github; consistent use of Oscar vs oscar or django-oscar when referring to the product)
Maik Hoepfel
David Winterbottom
Sebastian Vetter
Jason Cater