|
1 | 1 | # Tag-specific intros for tag pages. |
2 | | -# Key = tag slug (lowercase, jakim emit by _gentags.rb). |
| 2 | +# Key = tag slug (lowercase, emitted by _plugins/tag_generator.rb via Jekyll::Utils.slugify). |
3 | 3 | # - description: 140-160 char SEO meta description |
4 | 4 | # - intro: rich HTML displayed at the top of the tag page (above the post list) |
5 | 5 | # Tags without an entry here get a generic meta description and no on-page intro. |
@@ -35,3 +35,51 @@ performance: |
35 | 35 | apple-silicon: |
36 | 36 | description: "Posts tagged Apple Silicon — running Optimizely / Episerver CMS development on M1 / M2 Macs with Docker, .NET, and azure-sql-edge." |
37 | 37 | intro: "Posts about <strong>Apple Silicon</strong> (M1 / M2 / ARM Macs) for Optimizely / Episerver development — Docker setups, azure-sql-edge workarounds, and the CMS 13 Alloy Site running cross-platform on .NET." |
| 38 | + |
| 39 | +m1: |
| 40 | + description: "Posts tagged M1 — running Optimizely / Episerver CMS development on Apple Silicon Macs with Docker, .NET, and azure-sql-edge workarounds." |
| 41 | + intro: "Posts about <strong>M1 / Apple Silicon</strong> for Optimizely development — same scope as the <a href='/tags/apple-silicon'>apple silicon</a> tag, kept stable for inbound search results." |
| 42 | + |
| 43 | +arm: |
| 44 | + description: "Posts tagged ARM — running Optimizely / Episerver CMS development on ARM-based Macs with Docker, azure-sql-edge, and .NET cross-platform builds." |
| 45 | + intro: "Posts about <strong>ARM</strong> CPUs for Optimizely development — overlaps the <a href='/tags/apple-silicon'>apple silicon</a> and <a href='/tags/m1'>M1</a> tags." |
| 46 | + |
| 47 | +commerce: |
| 48 | + description: "Posts tagged Commerce — Optimizely Commerce catalog APIs, scheduled jobs, memory-efficient traversal, and integration patterns for large catalogs." |
| 49 | + intro: "Posts about <strong>Optimizely Commerce</strong> — catalog APIs, memory-efficient traversal patterns, scheduled jobs, and Hangfire integration for large product catalogs." |
| 50 | + |
| 51 | +catalog: |
| 52 | + description: "Posts tagged catalog — Optimizely Commerce catalog traversal, content APIs, memory-efficient enumeration, and scheduled-job patterns for large catalogs." |
| 53 | + intro: "Posts about <strong>catalog</strong> work in Optimizely Commerce — traversal patterns, the Content APIs, batched enumeration, and scheduled jobs that respect memory budgets." |
| 54 | + |
| 55 | +database: |
| 56 | + description: "Posts tagged database — SQL Server index maintenance, statistics rebuilds, and database-tooling patterns for Optimizely CMS / Commerce projects." |
| 57 | + intro: "Posts about <strong>databases</strong> for Optimizely projects — SQL Server index and statistics maintenance, scheduled cleanup jobs, and tooling for routine DBA work." |
| 58 | + |
| 59 | +background-jobs: |
| 60 | + description: "Posts tagged background jobs — Hangfire integration for Optimizely CMS, scheduled-job patterns, dashboard work, and progress reporting for long-running tasks." |
| 61 | + intro: "Posts about <strong>background jobs</strong> in Optimizely projects — Hangfire integration, the built-in scheduled-job system, progress reporting, and dashboards for long-running tasks." |
| 62 | + |
| 63 | +optipowertools: |
| 64 | + description: "Posts tagged OptiPowerTools — open-source NuGet packages for Optimizely CMS and Commerce, including Hangfire integration and SQL maintenance tooling." |
| 65 | + intro: "Posts about <strong>OptiPowerTools</strong> — a small set of open-source NuGet packages for Optimizely CMS and Commerce. Source on <a href='https://github.com/szolkowski/OptiPowerTools.Hangfire'>GitHub</a>." |
| 66 | + |
| 67 | +optipowertools-hangfire: |
| 68 | + description: "Posts tagged OptiPowerTools.Hangfire — the open-source NuGet package wiring Hangfire into Optimizely CMS, with dashboards, scheduled jobs, and admin gates." |
| 69 | + intro: "Posts about <strong>OptiPowerTools.Hangfire</strong> — the NuGet package that wires <a href='https://www.hangfire.io/'>Hangfire</a> into Optimizely CMS. Source on <a href='https://github.com/szolkowski/OptiPowerTools.Hangfire'>GitHub</a>; CMS 12 and 13 supported." |
| 70 | + |
| 71 | +ci: |
| 72 | + description: "Posts tagged CI — GitHub Actions and Azure DevOps pipelines for Optimizely CMS, including SonarCloud analysis, Playwright UI tests, and build automation." |
| 73 | + intro: "Posts about <strong>continuous integration</strong> for Optimizely projects — GitHub Actions and Azure DevOps pipelines, SonarCloud quality gates, and UI regression testing with Playwright." |
| 74 | + |
| 75 | +devops: |
| 76 | + description: "Posts tagged DevOps — CI/CD pipelines, build automation, code-quality gates, and developer-experience tooling for Optimizely CMS / Commerce projects." |
| 77 | + intro: "Posts about <strong>DevOps</strong> for Optimizely projects — CI/CD pipelines, build automation, code-quality gates (SonarCloud), and the boring infrastructure that makes shipping uneventful." |
| 78 | + |
| 79 | +sonarcloud: |
| 80 | + description: "Posts tagged SonarCloud — adding code-quality gates to Optimizely CMS pipelines, .NET-specific rules, and integrating analysis into GitHub Actions." |
| 81 | + intro: "Posts about <strong>SonarCloud</strong> for Optimizely / .NET projects — wiring quality gates into Azure DevOps and GitHub Actions, .NET-specific rule sets, and triaging the noise." |
| 82 | + |
| 83 | +nuget: |
| 84 | + description: "Posts tagged NuGet — packaging and distributing Optimizely CMS / Commerce libraries, semantic versioning, and the OptiPowerTools.Hangfire release flow." |
| 85 | + intro: "Posts about <strong>NuGet</strong> packaging for Optimizely projects — semantic versioning, package metadata, and the release flow behind the OptiPowerTools.Hangfire package." |
0 commit comments