Do the following things

• copy the page template named main from MTE to MTK and name it basic; keep the old one!
• html kind-of-starting point: see attachment from topher (which is based on https://html5boilerplate.com/)
• use webresources form 3rd party providers such as cdn or similar to lower maintain efforts

areas to add which (will may have its own area template):

• htmlHeader ; type: noComponent, createAreaNode: false; code could be a mixture of travel-demo/templates/pages/areas/htmlHeader.ftl and the attachment on this ticket based on html5boilerplate.com/
• navigation , added file will be +/- empty; type: noComponent, createAreaNode: false
• main , using "default" template, no file provided
• footer , using "default" template, no file provided; use inheritance (see /modules/travel-demo/config/travel/templates/prototype/areas/footer/areas/footer1/inheritance)

dialog should be based on / be similar as /mte/dialogs/pages/pageProperties.yaml (actually moving this file to /mtk/dialogs/pages/basic.yaml)

i18n should follow "best practices" since we already have ticket (see MTE-74). However ... to not to "depend" on other tickets, let's start using "old" i18n using the bundle info.magnolia.templating.models.messages to start with and later on refactoring it once MTE-74 is ready.

template definition class: Use info.magnolia.templating.definition.PageTemplateDefinition as soon as MTE-63 has been integrated.