Hi Igor,
Feature settings should be defined in your feature definition file which is used by the /Setup/Default.aspx page to define the settings and default values of settings for your feature. This is separate from the initial content and needs to run first from the setup page so your feature is already defined/installed before content is created using your feature. Content installation only works with features that are already installed it does not install features, setup page does that based on feature definition file.
For initial content you can study the examples in the zip file download on the article Configuring Initial Content.
The location attribute determines which panel the feature instance is added to, you can specify center, right or left like these examples used for our demo site home page which has center and left content:
<page
name="Home"
title=""
url="~/home"
menuImage=""
pageOrder="1"
requireSSL="false"
visibleToRoles="All Users;"
editRoles="Content Publishers;"
createChildPageRoles="Content Publishers;"
pageMetaKeyWords=""
pageMetaDescription=""
>
<contentFeature
featureGuid="881e4e00-93e4-444c-b7b0-6672fb55de10"
contentTitle="Welcome"
location="center"
sortOrder="1"
cacheTimeInSeconds="0"
contentInstaller="mojoPortal.Web.HtmlContentInstaller, mojoPortal.Web"
configInfo="~/Setup/initialcontent/democontent/demosite-homepage-content.config"
/>
<contentFeature
featureGuid="881e4e00-93e4-444c-b7b0-6672fb55de10"
contentTitle="more"
contentTemplate="demosite-homepage-content.config"
location="right"
sortOrder="1"
cacheTimeInSeconds="0"
contentInstaller="mojoPortal.Web.HtmlContentInstaller, mojoPortal.Web"
configInfo="~/Setup/initialcontent/democontent/more-html.config"
/>
</page>
You have to create your own content installer for your custom feature, based on what you posted you are trying to use the content installer for the HtmlContent feature but with your own feature guid, that is not going to work. If you don't implement a content installer of your own you can leave "contentInstaller" attribute blank and it will put your feature on the page, but if you need to populate content inside your custom feature you must implement your own content installer. You can study existing content installers for different features to learn how to implement your own, then specify the type for your content installer in the contentInstaller attribute.
Hope that helps,
Joe