function feeds_ui_edit_help in Feeds 6

Same name and namespace in other branches

1. 8.2 feeds_ui/feeds_ui.admin.inc \feeds_ui_edit_help()
2. 7.2 feeds_ui/feeds_ui.admin.inc \feeds_ui_edit_help()
3. 7 feeds_ui/feeds_ui.admin.inc \feeds_ui_edit_help()

Introductory help for admin/build/feeds/edit/config page

1 call to feeds_ui_edit_help()

feeds_ui_edit_page in feeds_ui/feeds_ui.admin.inc

Edit feed configuration.

File

feeds_ui/feeds_ui.admin.inc, line 12

Contains all page callbacks, forms and theming functions for Feeds administrative pages.

Code

function feeds_ui_edit_help() {
  return t('
    <p>
    You can create as many Feeds importer configurations as you would like to. Each can have a distinct purpose like letting your users aggregate RSS feeds or importing a CSV file for content migration. Here are a couple of things that are important to understand in order to get started with Feeds:
    </p>
    <ul>
    <li>
    Every importer configuration consists of basic settings, a fetcher, a parser and a processor and their settings.
    </li>
    <li>
    The <strong>basic settings</strong> define the general behavior of the importer. <strong>Fetchers</strong> are responsible for loading data, <strong>parsers</strong> for organizing it and <strong>processors</strong> for "doing stuff" with it, usually storing it.
    </li>
    <li>
    In Basic settings, you can <strong>attach an importer configuration to a content type</strong>. This is useful when many imports of a kind should be created, for example in an RSS aggregation scenario. If you don\'t attach a configuration to a content type, you can use it on the !import page.
    </li>
    <li>
    Imports can be <strong>refreshed periodically</strong> - see the minimum refresh period in the Basic settings.
    </li>
    <li>
    Processors can have <strong>mappings</strong> in addition to settings. Mappings allow you to define what elements of a data feed should be mapped to what content fields on a granular level. For instance, you can specify that a feed item\'s author should be mapped to a node\'s body.
    </li>
    </ul>
    ', array(
    '!import' => l(t('Import'), 'import'),
  ));
}