[TASK] Step 2: Create the relevant fluid-template folders

Those should reside in Resources/Private/Templates|Partials|Layouts .

Why? It's an extbase convention. As an integrator or developer, you should stick to those conventions as **close** as possible.
[TASK] Step 3: Wire the static templates

As a backend user, you will be able to select the static TypoScript template for your extension to be included.

What I prepared in the files is just the **standard extbase** extension setup for views. This tells the template resolver
where its templates are to be found.
[TASK] Step 4: Create a page layout

This is not the real page layout! This wires up different partials and breaks the page layout down in its respective parts.

As you see, the Page.html layout file renders a Header and a Footer Partial. Those will be added soon, and let us focus on the content rendering, rather then caring about the whole layout.
[TASK] Step 5: Add the partials

I added the basic partials for Header and Footer now.

This enables you to separate the repeating stuff from your content. We'll get back here later-on.
[TASK] Step 6: Add a 3 rows, 1column backend layout

When utilizing fluidpages for Page layouts (as we do), we define out BackendLayouts with pure fluid.
Like I did, you can render very complex layouts with many rows and columns which can inherit and can contain custom configuration in the Configuration Section.

Page templates are placed into Resources/Private/Templates/Page as per default. To explain it with another convention:
Place the Templates for the flux PageController in Templates/Page. Just as you are used to with any other extbase extension.
[TASK] Step 7: Add a partial for the page assets (js/css)

Assets such as custom JS or CSS-from files or inline-can be inserted wherever you want. EXT:vhs' AssetService will take care of it.
With Assets, you can insert JS and CSS in any order and have it sorted via the ``dependencies`` attribute.

As most of your CSS and JS will have to be loaded on any page (think of modernizr and the common CSS for example), it only makes sense to place them together. We'll do that later on in SharedResources
[TASK] Step 8: Add a partial for the Navigations

Fluid allows you to have more than one section in a template, which makes it possible to put fx. all the different navigations into one template.
This makes your directory much more straightforward.