Hi Juan,
technically, you could use any node type, even an nt:unstructured, but using a base template has the advantage that you have all the functionality of a cq:Page. I would recommend you to create a basic template that you use for structure initially. If it should contain any paragraph system or not is up to you, but it might be the one that holds stuff like header, footer, logos and other meaningful design items that is a part of the site.
One good thing with having an empty parsys on the basic page is that you also could use it for anything that "doesn't really fit in any other template" or just simply as the render for a template. You can define your components in the template and have the basic page as the resourceType so that the same /apps/mysite/content/page/basic renders a lot of templates.
What you also then can do is place utility components on the page that can pick up Sling selectors, extensions and request parameters. Using your structure, you could quite easy get the node to list everything that is a child of its node. Say you want to get all pages from 2011, paged from index 0 to 24, as a list. Then the call could be something like http://.../home/section/2011.list.0.25.html. Filter all that is of type Feature could be http://.../home/section/2011.list.0.25.html/Feature.
/Ove
