(i really apriciate your reponces @irkode & @bep. You have been a great help)
I guess Im trying to do this in as good a way as possible. With @irkode’s option vscode does not recognise it as YAML (don’t know how to do that) so it will be harder for others to edit.
I’m trying to figure out a good way to organise my pages…
At the moment I use this is the front matter:
sections:
- title: NKD Agility Migration Services
content: Azure DevOps Migration and Process Optimization services overview.
type: features
features:
- media: images/upgrade-2022.png
title: Our Migration Services for Azure DevOps Migration
content: |
- *Complete Transition*: We manage the entire process of moving your on-premises TFS environment to Azure DevOps, including data, code repositories, and builds. We can handle any Collection size from a few hundred to a few thousand gigabytes.
- *Legacy System Migration*: We handle complex integrations, including importing data from outdated systems like Visual SourceSafe or other obsolete systems.
- media: images/nkdagility-azure-devops-process.jpg
title: Process Optimization & Migration
content: |
- *Customized Configurations*: We help you optimize your Azure DevOps environment by customizing process templates and workflows to match your development processes.
- *Change Process*: Ensuring seamless transitions from one process to another when there are lots of changes.
- media: images/nkdagility-azure-devops-migration-tools.jpg
title: Project Optimisation & Migration
content: |
We build, maintain, and support the tools recommended by Microsoft and used by consultants around the world to manage and migrate the contents of TFS & Azure DevOps Projects. We have helped customers migrate nearly two billion work item revisions.
- *Project manipulation*: We have experience in both TFS and Azure DevOps in splitting or merging projects within a collection/account or between them.
- *Account / Collection Consolidation*: We can move a Project from one collection/account to another.
source: inline
- title: Courses For Azure DevOps
content: Here is a list of courses related to Azure DevOps.
type: courses
related:
- /capabilities/training-courses/courses/accentient-managing-projects-using-visual-studio-and-scrum
source: data
- title: null
content: null
type: videos
related:
- resources/videos/youtube/isU2kPc5HFw
- resources/videos/youtube/_rJoehoYIVA
- resources/videos/youtube/Wvdh1lJfcLM
- resources/videos/youtube/3jYFD-6_kZk
source: data
Then I have a single partial in the template that iterates through the “sections” and redners them… however its not as versatile as using the inline shortcodes which would enable me to reorder and organise inline…
What do you guys do when you are building marketing pages?
A bare markdown list has the problem with escaping the _ by the formatter and would need special treatment (also for *…) simple lines only will collapse
If the section is just the video list, I would keep that in the frontmatter and just have a `{{< section-videos >}} shortcode that grabs the data from front matter. or if it’s generic for all/some pages move it to a layout and partial. That depends on the freedom of placing things somewhere.
I think that I may have multiple video lists on some pages. And the video is just a sample…
using
{{< section-courses >}}
\`\`\`YAML
title: Courses For Azure DevOps
content: Here is a list of courses related to Azure DevOps.
type: courses
related:
- /capabilities/training-courses/courses/accentient-managing-projects-using-visual-studio-and-scrum
\`\`\`
{{< /section-courses >}}
or
{{< section-features >}}
\`\`\`YAML
title: NKD Agility Migration Services
content: Azure DevOps Migration and Process Optimization services overview.
type: features
features:
- media: images/upgrade-2022.png
title: Our Migration Services for Azure DevOps Migration
content: |
- *Complete Transition*: We manage the entire process of moving your on-premises TFS environment to Azure DevOps, including data, code repositories, and builds. We can handle any Collection size from a few hundred to a few thousand gigabytes.
- *Legacy System Migration*: We handle complex integrations, including importing data from outdated systems like Visual SourceSafe or other obsolete systems.
- media: images/nkdagility-azure-devops-process.jpg
title: Process Optimization & Migration
content: |
- *Customized Configurations*: We help you optimize your Azure DevOps environment by customizing process templates and workflows to match your development processes.
- *Change Process*: Ensuring seamless transitions from one process to another when there are lots of changes.
- media: images/nkdagility-azure-devops-migration-tools.jpg
title: Project Optimisation & Migration
content: |
We build, maintain, and support the tools recommended by Microsoft and used by consultants around the world to manage and migrate the contents of TFS & Azure DevOps Projects. We have helped customers migrate nearly two billion work item revisions.
- *Project manipulation*: We have experience in both TFS and Azure DevOps in splitting or merging projects within a collection/account or between them.
- *Account / Collection Consolidation*: We can move a Project from one collection/account to another.
\`\`\`
{{< /section-features >}}
My current setup of just iterating through a sections yaml in the front matter restricts what can be put in between to that which is implemented in the sesions layouts… with the above I can have more control over the content.