Static Web Apps

158
Total Pages
152
Linux-Friendly Pages
6
Pages with Bias
3.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

12 issues found
Showing 1-12 of 12 flagged pages
Static Web Apps Tutorial: Add a MySQL database connection in Azure Static Web Apps ...s/blob/main/articles/static-web-apps/database-mysql.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (primarily a Windows tool) is presented as the main database client, with MySQL Workbench mentioned only as an alternative. PowerShell examples are provided alongside Bash, but Windows-centric tools and workflows (Azure portal, Azure Data Studio) are referenced first and most prominently. There are no explicit Linux/macOS-only examples or instructions, and Linux-native tools (e.g., mysql CLI) are not mentioned.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS users using native tools such as the mysql CLI for database management.
  • Include screenshots or instructions for using MySQL Workbench and/or CLI on Linux/macOS platforms.
  • Clarify that Azure Data Studio is cross-platform, but also list alternative Linux/macOS database clients.
  • Ensure that Bash examples are presented before or equally with PowerShell, and clarify shell differences for environment variable setup.
  • Add a section or note on Linux/macOS-specific setup steps, such as firewall rules or networking nuances.
GitHub Create Pull Request
Static Web Apps Tutorial: Publish Azure Static Web Apps using an ARM template ...cles/static-web-apps/publish-azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked only for Windows. The Azure CLI installation instructions list Windows first, and PowerShell is presented as an alternative throughout, with examples for both CLI and PowerShell. However, Linux and macOS installation links are provided, and CLI examples are written for Bash, which is more common on Linux/macOS. No Linux-specific tools or editors are suggested, and PowerShell is emphasized as a primary option.
Recommendations
  • Provide explicit parity for Linux/macOS users by recommending editors and extensions available on those platforms (e.g., Vim, Sublime Text, Atom) and linking to their installation guides.
  • Present installation instructions for Azure CLI in a neutral order (e.g., Windows, Linux, macOS together or alphabetically) rather than Windows first.
  • Clarify that PowerShell is optional and not required for Linux/macOS users, and highlight Bash or other native shells as primary options.
  • Include screenshots or instructions for resource cleanup using the Azure CLI or Azure portal on Linux/macOS.
  • Mention cross-platform alternatives for any Windows-specific tooling or patterns.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a PostgreSQL database connection in Azure Static Web Apps ...b/main/articles/static-web-apps/database-postgresql.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias, primarily through the exclusive recommendation of Azure Data Studio (a Microsoft tool with best support on Windows) for database management, and by listing PowerShell examples alongside Bash in all CLI instructions. Linux alternatives (such as psql or other native PostgreSQL tools) are mentioned only in passing, and Windows-centric tools are presented first or as defaults. This may create friction for Linux/macOS users, though most tasks are still achievable with standard cross-platform tools.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS-native tools such as psql and PgAdmin, including installation and usage instructions.
  • Reorder tool recommendations so that cross-platform or Linux-native tools are listed before or alongside Windows-centric ones.
  • Add Linux/macOS-specific instructions for steps that currently only reference Azure Data Studio or PowerShell.
  • Clarify that all CLI commands work in Bash/zsh on Linux/macOS, and provide troubleshooting tips for platform-specific issues.
  • Include screenshots or terminal outputs from Linux/macOS environments where relevant.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a MySQL database connection in Azure Static Web Apps ...s/blob/main/articles/static-web-apps/database-mysql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias. Azure Data Studio (a Microsoft tool primarily used on Windows) is presented as the default tool for MySQL management, with MySQL Workbench only mentioned as an alternative. The workflow assumes use of the Azure portal, which is web-based but often referenced in a Windows context. Command-line examples are provided for both Bash and PowerShell, but PowerShell is given equal prominence, which is less relevant for Linux/macOS users. There are no explicit Linux/macOS-specific instructions or tool recommendations (e.g., mysql CLI, DBeaver, or Linux-native editors).
Recommendations
  • Explicitly mention and provide examples using Linux/macOS-native tools (e.g., mysql CLI, DBeaver, or terminal-based editors) for database management.
  • Add instructions for installing and using MySQL CLI on Linux/macOS for creating databases and tables.
  • List Bash examples before PowerShell, as Bash is the default shell on Linux/macOS.
  • Clarify that Azure Data Studio is cross-platform, and provide installation links for Linux/macOS.
  • Include screenshots or walkthroughs using Linux/macOS environments where relevant.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a PostgreSQL database connection in Azure Static Web Apps ...b/main/articles/static-web-apps/database-postgresql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page shows a moderate Windows bias. Azure Data Studio (a Microsoft tool most commonly used on Windows) is presented as the primary database management tool, with PgAdmin only briefly mentioned as an alternative. Command-line examples are consistently shown in both Bash and PowerShell, but PowerShell examples are always present and sometimes shown immediately after Bash, suggesting parity but with a slight Windows-first ordering. There are no explicit Linux/macOS-only instructions or examples, and the workflow is generally cross-platform, but the emphasis on Azure Data Studio and PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present PgAdmin and psql as equal alternatives to Azure Data Studio, with explicit instructions or links for Linux/macOS users.
  • Add explicit instructions for installing and using Azure Data Studio on Linux/macOS, or clarify cross-platform support.
  • When showing command-line examples, alternate the order of Bash and PowerShell, or group them together to avoid implicit prioritization.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., environment variable syntax differences, CLI installation quirks).
  • Add a section or note confirming that all steps are supported on Linux/macOS, with links to relevant platform-specific documentation.
GitHub Create Pull Request
Static Web Apps Add an API to Azure Static Web Apps with Azure Functions ...ure-docs/blob/main/articles/static-web-apps/add-api.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is largely cross-platform, but there are minor signs of Windows bias. The only explicit Windows-specific mention is in the Node.js version management tip, which references 'NVM for Windows' and its installation via Winget. Additionally, there is a note about Windows Firewall prompts when running the Azure Functions runtime, which is a Windows-specific concern. However, all command-line instructions use bash syntax, and there are no PowerShell-only examples or Windows-exclusive tools for the main workflow. Linux/macOS users are not blocked from completing the tasks, but Windows-specific details are mentioned before Linux equivalents.
Recommendations
  • When mentioning Node.js version management, provide equal visibility to Linux/macOS tools (e.g., show nvm install instructions for Linux/macOS alongside NVM for Windows).
  • Clarify that firewall prompts are specific to Windows and mention that Linux/macOS users may not encounter this.
  • Where platform-specific behavior is discussed, add notes for Linux/macOS users to ensure parity and clarity.
  • Consider providing explicit instructions or tips for Linux/macOS users where relevant, such as package manager commands or environment setup.
GitHub Create Pull Request
Static Web Apps Tutorial: Add an Azure Cosmos DB database connection in Azure Static Web Apps ...n/articles/static-web-apps/database-azure-cosmos-db.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup, npm commands, and CLI usage. However, PowerShell examples are always shown after Bash, and there is no mention of Linux-specific considerations or tools. The tutorial assumes the use of the Azure portal (web-based), which is platform-neutral, but the CLI and shell instructions could be improved for Linux/macOS parity.
Recommendations
  • Explicitly mention Linux/macOS compatibility for all CLI commands and tools.
  • Provide Linux/macOS-specific troubleshooting tips (e.g., environment variable persistence, file permissions).
  • Include Zsh and other common shell examples, not just Bash and PowerShell.
  • Clarify that all CLI commands work on Linux/macOS, and link to installation instructions for those platforms.
  • Consider showing Bash (Linux/macOS) examples first, or randomize order to avoid implicit Windows-first bias.
GitHub Create Pull Request
Static Web Apps Deploy your web app to Azure Static Web Apps. .../main/articles/static-web-apps/deploy-web-framework.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation generally presents cross-platform instructions, but there are subtle Windows biases. Visual Studio Code is recommended as the editor, which is available on all platforms but has a strong Windows association. In the section on setting environment variables for Angular, Windows-specific shells (PowerShell and CMD) are listed after bash/csh, but their inclusion is notable. No Linux/macOS-specific editors or tools are recommended, and Windows Subsystem for Linux is mentioned as a platform, reinforcing Windows as a primary environment. All command-line examples use bash syntax, which is cross-platform, but the explicit inclusion of PowerShell and CMD instructions suggests a slight Windows-first orientation.
Recommendations
  • Explicitly mention and recommend Linux/macOS editors (e.g., Vim, Sublime Text, Atom) alongside Visual Studio Code.
  • Present environment variable instructions with Linux/macOS examples first, or clarify that all platforms are equally supported.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Avoid mentioning Windows Subsystem for Linux unless specifically relevant; simply state 'Linux' where appropriate.
  • Ensure parity in troubleshooting and tool recommendations for Linux/macOS users.
GitHub Create Pull Request
Static Web Apps Deploy your web app to Azure Static Web Apps. .../main/articles/static-web-apps/deploy-web-framework.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. In the environment variable section, Windows-specific shells (PowerShell, CMD) are included alongside bash and csh, but Windows examples are listed after Linux/macOS shells. No Linux/macOS tools are omitted, and all CLI commands are shown in bash syntax by default. There are no critical sections that are Windows-only, and Linux/macOS users can follow all steps without friction.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux/macOS, or suggest other editors as alternatives.
  • Ensure that Linux/macOS shell examples (bash, csh) are shown first in environment variable sections to reinforce parity.
  • Add a note clarifying that all commands work on Linux/macOS, and highlight any platform-specific caveats if present.
  • Consider including screenshots from Linux/macOS environments to visually reinforce cross-platform support.
GitHub Create Pull Request
Static Web Apps Add an API to Azure Static Web Apps with Azure Functions ...ure-docs/blob/main/articles/static-web-apps/add-api.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely cross-platform, but there are subtle Windows biases. The Node.js version manager tip mentions 'NVM for Windows' and its installation via Winget before any Linux/macOS instructions, and the section about running the app locally references a Windows Firewall prompt, which is Windows-specific. There are no PowerShell-only examples, and most commands are platform-agnostic (npm, git, etc.), but Windows tools and behaviors are mentioned where Linux/macOS equivalents could be included.
Recommendations
  • When mentioning Node.js version managers, provide equal instructions for nvm on Linux/macOS (e.g., installation via curl/bash) alongside Windows instructions.
  • In the section about firewall prompts, clarify that this is a Windows-specific behavior and note that Linux/macOS users may need to allow network access differently or may not see such prompts.
  • Where Windows-specific tools (like Winget) are mentioned, also mention Linux/macOS package managers (apt, brew, etc.) for installing dependencies.
  • Review all tips and notes to ensure Linux/macOS users are equally supported and not left to infer their own steps.
GitHub Create Pull Request
Static Web Apps Tutorial: Add an Azure Cosmos DB database connection in Azure Static Web Apps ...n/articles/static-web-apps/database-azure-cosmos-db.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for environment variable setup, npm commands, and CLI usage. However, PowerShell examples are consistently shown after Bash, and there is no mention of Linux-specific nuances or macOS-specific instructions. The documentation does not reference any Windows-only tools, but the inclusion of PowerShell examples may suggest a slight Windows bias. No critical steps are Windows-only, and Linux/macOS users can follow the tutorial without significant friction.
Recommendations
  • Explicitly mention Linux and macOS compatibility in prerequisites and CLI instructions.
  • Provide notes on common Linux/macOS shell environments (e.g., zsh, fish) and how to set environment variables in those shells.
  • Alternate the order of Bash and PowerShell examples, or group them under clear OS headings.
  • Add troubleshooting tips for Linux/macOS users (e.g., file permissions, npm install issues).
GitHub Create Pull Request
Static Web Apps Tutorial: Publish Azure Static Web Apps using an ARM template ...cles/static-web-apps/publish-azure-resource-manager.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias by listing Windows installation instructions first, referencing Visual Studio Code (a Microsoft tool) as the recommended editor, and providing both Azure CLI and PowerShell examples (with PowerShell being a Windows-centric tool). However, Linux and macOS users are mentioned for CLI installation, and Bash is referenced for CLI examples, which helps mitigate the bias. There are no Linux-specific tool recommendations, and PowerShell examples are given equal prominence to CLI, which may create friction for non-Windows users.
Recommendations
  • Explicitly recommend cross-platform editors (such as VS Code, Sublime Text, or Vim) and clarify that VS Code is available on Linux/macOS.
  • Provide Bash and/or zsh shell examples for common Linux/macOS workflows, especially for scripting deployments.
  • Clarify that Azure PowerShell is available on Linux/macOS, or prioritize Azure CLI examples since CLI is more universal.
  • List installation instructions for all platforms in parallel, not with Windows first.
  • Add notes or links for Linux/macOS users about alternative tools or shell environments.
GitHub Create Pull Request