@paroicms/site-generator-plugin 0.5.2 → 0.6.0

package/gen-backend/prompts/generate-fake-content-multiple-documents.md

@@ -14,7 +14,7 @@ Make sure web pages are distinct from each other by:
 
 Guidelines:
 
-- NEVER repeat a title among several sub-contents.
+- NEVER repeat the same title among several sub-contents.
 - Never invite the user to write a comment. There is no comment system.
 
 Each web page is composed by several sub-contents. Use the following exact format:

package/gen-backend/prompts/new-site-1-analysis.md

@@ -55,11 +55,10 @@ Guidelines for creating the hierarchical bullet list:
   - Write `"list of"`, and then the **type name** within backquotes.
   - Append `(parts)`.
   - Add a coma, then write: `"list name:"` and append an identifier for the list name.
-- Each distinct node type must have a unique name through the whole tree structure.
-- Reusing the same node type several times (for recursivity etc.):
-  - When the same node type is reused as a child in several places, then write its children only on the first occurence.
+- Avoid recursivity. But if you can't avoid reusing a node type, then write its children only on the first occurence.
 - On this task, do not focus on fields. If the website description provide fields then you will report them in the unused information. In particular, a collection of medias (a carousel, a slider, an image gallery, a slideshow, etc.) is a type of field.
 - Don't try to provide a comment mechanism when the user requests a blog. Blog comments do not belong to the hierarchy of node types.
+- NEVER ever reuse the same type name for 2 distinct node type. Pay particular attention to words spelled identically in the singular and plural. Each distinct node type must have a unique name through the whole tree structure.
 
 Here's an example of a correct output:
 
@@ -83,27 +82,18 @@ Here is another incorrect example:
 
 <incorrect_example>
 * `home` (routing document)
-  * `animals`
-    * `pages` (regular document)
-      * list of `page` (regular documents)
-  * `vegetals`
-    * `pages` (regular document)
-      * list of `page` (regular documents)
+  * `species` (routing document)
+    * list of `species` (regular documents)
 </incorrect_example>
 
-This incorrect example fails because the children of `pages` node should not be written the second time we use this node type. Here is how to fix that:
+This incorrect example fails because the type name `species` is used for 2 different types. You can distinguish them by suffixing both the collection and the item types:
 
 <correct_example>
 * `home` (routing document)
-  * `animals`
-    * `pages` (regular document)
-      * list of `page` (regular documents)
-  * `vegetals`
-    * `pages` (regular document)
+  * `speciesColl` (routing document)
+    * list of `speciesItem` (regular documents)
 </correct_example>
 
-Notice: the `pages` node will have the same child types for both usage. But we describe them only the first time it appears on the tree.
-
 Here's an example of correct output using parts, and with the default contact and search pages:
 
 <correct_example>
@@ -126,6 +116,7 @@ Guidelines for creating the dictionnary YAML:
 
 - Use a YAML syntax: pay attention to the indentation.
 - Keys: each key is the name of a node type or the name of a list of parts.
+- If the same type is reused several times, then write only one entry in this dictionnary.
 - Values contains the properties. For a node type, provide the following properties:
   - confidence: Your confidence level for the accuracy of this node type (0.0-1.0).
   - kind: Can be `routingDocument`, `regularDocument`, `part`.