You are tasked of assigning predefined fields for each node type (routing document, regular document, or part).

1. Look at the list of available predefined fields (in JSON format):

<predefined_fields_json>
{{predefinedFields}}
</predefined_fields_json>

2. Examine the current site schema, which conforms to the `JtSiteSchema` type:

<site_schema_json>
{{siteSchemaJson}}
</site_schema_json>

3. Check if there are instructions about fields in these user instructions:

<user_request>
{{message}}
</user_request>

4. Now, here is what to do:

Create a key/value dictionnary. Keys are the node type names of the provided site schema. Value are arrays of field names.

Guidelines for creating the dictionnary YAML:

- Use a YAML syntax.
- All the node types must have a key in your result.
- If there is no need of a field for a node type, then leave an empty array.
- Documents and parts already contains a _publish date_ and a _draft_ flag.
- A document already contains a _title_ and a _featured image_, but a part doesn't. That's why the predefined `title` field can be used on part types when needed.
- Default values:
  - By default, for most of node types, if you are not sure about what could be the best fields, then remember that a document is a webpage and just use a `[htmlContent]`.
  - Except if there are specific instructions in the website description, here is the default value for the `_site` node type: `["logo", "footerMention"]`.
- Gallery of medias: there is a predefined field named `"gallery"`. It contains a list of medias. The theme can render it as a carousel, a slider, an image gallery, a slideshow, etc.
- This task is about predefined fields only. Custom fields will be added in a further step.

Here is an example of expected output:

<correct_example>
_site: [logo, footerMention]
home: [htmlContent]
searchPage: []
contactPage: ["introduction"]
regularDocumentExemple1: [gallery, htmlContent]
partExemple2: [title, image, htmlContent]
aBlogPostExample: [leadParagraph, htmlContent]
</correct_example>

Provide the YAML result within <yaml_result> tags. Do not write any explanation or commentary outside the tags.

Additionally, write within <unused_information_md> tags the information from the user instructions that you weren't able to use here, in the form of a short prompt, in markdown format. Do not invent anything. Do not imagine anything. If there is no remaining information, then let this tag empty.