Update articles/getting_started/content_pipeline/content_builder_project.md

SimonDarksideJ · Copilot · web-flow · commit e53a6afa6a97 · 2025-11-09T10:34:24.000Z
Co-authored-by: Copilot &lt;175728472+Copilot@users.noreply.github.com&gt;
diff --git a/articles/getting_started/content_pipeline/content_builder_project.md b/articles/getting_started/content_pipeline/content_builder_project.md
@@ -139,7 +139,7 @@ public class Builder : ContentBuilder
 
 The default `Include` rule simply builds a list of content to process from the target folder when the program is executed.
 
-> [IMPORTANT]
+> [!IMPORTANT]
 > We recommend keeping this default structure of getting all files and then specifying overrides.  You can alter this if you so wish to only use specific includes, but that it would require more maintenance as your content grows.  Try to be generic, design rules based on the structure of your content rather than being too specific.
 >
 > Although check the details later about providing parameters, while samples are currently "hard coding" importer/processor values, this would be improved through your own configuration.

Original file line number	Diff line number	Diff line change
`@@ -139,7 +139,7 @@ public class Builder : ContentBuilder`
`139`	`139`
`140`	`140`	The default `Include` rule simply builds a list of content to process from the target folder when the program is executed.
`141`	`141`
`142`		`-> [IMPORTANT]`
	`142`	`+> [!IMPORTANT]`
`143`	`143`	`> We recommend keeping this default structure of getting all files and then specifying overrides. You can alter this if you so wish to only use specific includes, but that it would require more maintenance as your content grows. Try to be generic, design rules based on the structure of your content rather than being too specific.`
`144`	`144`	`>`
`145`	`145`	`> Although check the details later about providing parameters, while samples are currently "hard coding" importer/processor values, this would be improved through your own configuration.`