Static Web Apps

78
Total Pages
70
Linux-Friendly Pages
8
Pages with Bias
10.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (12)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and PowerShell command examples for environment variable setup, npm usage, and CLI commands, but consistently lists Bash first. There is no exclusive use of Windows tools, and Linux (Bash) is always represented. However, the presence of PowerShell tabs and examples throughout, and the order in which Bash is always presented before PowerShell, may indicate a slight bias towards Windows users by ensuring PowerShell parity, even though the commands are cross-platform. There are no missing Linux examples, and no exclusive mention of Windows-only tools or patterns.
Recommendations:
  • Continue to provide both Bash and PowerShell examples to ensure parity.
  • Consider explicitly mentioning that Bash commands work on Linux and macOS, and PowerShell commands are for Windows, to clarify platform applicability.
  • If possible, add a short section at the start of the tutorial explaining how to choose between Bash and PowerShell based on the user's OS.
  • Ensure that any screenshots or UI references are not Windows-specific, or provide Linux/macOS equivalents if UI differences exist.
  • Maintain the current practice of not favoring Windows-specific tools or patterns, and avoid implying that PowerShell is the default unless it truly is.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for database management, with PgAdmin only mentioned as an alternative. In all code examples (git, npm, environment variable setting), both Bash and PowerShell are shown, but PowerShell is always presented second, not first. However, the documentation does not provide Linux-specific troubleshooting or mention Linux-native tools (like psql CLI) for PostgreSQL management. The focus on Azure Data Studio and the lack of Linux-first or CLI-native workflows indicate a Windows-centric approach.
Recommendations:
  • Provide equal prominence to Linux-native tools such as psql CLI and PgAdmin, including step-by-step instructions for these tools.
  • When listing tools for database management, mention cross-platform and Linux-native tools first or equally (e.g., 'You may use Azure Data Studio, PgAdmin, or the psql command-line tool').
  • Include Linux-specific troubleshooting tips or notes where relevant (e.g., firewall configuration, environment variable syntax).
  • For all command examples, consider using a tabbed interface with Bash (Linux/macOS) as the default or first tab, or explicitly state that both shells are supported equally.
  • Add a section or callout for users developing on Linux, highlighting any differences or additional steps required.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/getting-started.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by referencing Visual Studio Code UI navigation patterns (e.g., 'File > Open Folder') and omitting any mention of Linux-specific instructions or terminal-based workflows. There are no examples or notes for Linux users, nor are there alternative instructions for common Linux environments. The reliance on GUI-based steps and lack of parity for Linux users may hinder accessibility for non-Windows developers.
Recommendations:
  • Add explicit instructions or notes for Linux (and macOS) users, especially where UI navigation or keyboard shortcuts may differ.
  • Include terminal-based alternatives for key steps (e.g., opening folders, installing extensions) that are common in Linux workflows.
  • Where possible, provide screenshots or examples from Linux environments in addition to Windows.
  • Clarify that Visual Studio Code and the Azure extension are cross-platform, and link to platform-specific installation guides.
  • Review all steps for assumptions about the user's operating system and add parity for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/deployment-token-management.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific command-line examples or tooling, but it also does not mention or show any Linux-specific workflows, commands, or screenshots. All instructions are GUI-based and platform-agnostic, but there is a lack of parity for users who may prefer or require command-line or Linux-native approaches.
Recommendations:
  • Add CLI-based instructions for resetting and updating deployment tokens using Azure CLI, PowerShell, and Bash, ensuring both Windows and Linux users are supported.
  • Include examples of how to update GitHub secrets using the GitHub CLI (gh) or via scripts, with both Windows (PowerShell) and Linux (Bash) syntax.
  • Provide screenshots or terminal output from both Windows and Linux environments where relevant.
  • Explicitly mention that the process can be performed on any OS, and link to cross-platform tools or documentation where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench) for database management, omitting explicit Linux-native alternatives (such as the MySQL CLI). While both Bash and PowerShell examples are provided for CLI commands, the database tooling and portal navigation instructions assume a GUI workflow more common on Windows. There are no explicit Linux-specific instructions or screenshots, and the documentation does not mention Linux package managers or command-line tools for MySQL database management.
Recommendations:
  • Include explicit instructions and examples for using the MySQL CLI (mysql, mysqladmin) for database creation, querying, and data manipulation, especially for Linux users.
  • Mention Linux-native tools (e.g., DBeaver, command-line MySQL clients) alongside Azure Data Studio and MySQL Workbench.
  • Provide package manager installation commands for Azure Data Studio, MySQL CLI, or other recommended tools on Linux (e.g., apt, yum, snap).
  • Add screenshots or terminal output examples from Linux environments where appropriate.
  • Clarify that all steps can be performed on Linux, and highlight any differences or prerequisites for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/local-development.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Visual Studio Code Heavy Missing Linux Example
Summary:
The documentation demonstrates a subtle Windows bias by emphasizing Visual Studio Code (a Microsoft product popular on Windows) for debugging, and by not providing any Linux- or macOS-specific instructions, terminal commands, or troubleshooting notes. All examples are generic but implicitly assume a Windows-centric workflow, especially in the debugging section. There are no explicit references to Windows-only tools or PowerShell, but the absence of Linux/macOS parity in examples and tool recommendations is notable.
Recommendations:
  • Include explicit instructions or notes for Linux and macOS users, such as alternative editors (e.g., VS Code, Vim, or JetBrains IDEs) and terminal usage.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, environment variables, or port conflicts).
  • Provide example commands or screenshots from Linux/macOS terminals to demonstrate cross-platform compatibility.
  • Mention that Visual Studio Code is cross-platform, and suggest alternatives for users who may not use it.
  • Clarify that all CLI commands are platform-agnostic, and note any platform-specific differences if they exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/deployment-token-management.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not display overt Windows bias in terms of command-line examples or tool references, but it also does not provide any platform-specific instructions. However, there is a subtle bias in that the documentation omits any mention of Linux or cross-platform command-line methods for managing deployment tokens (e.g., using CLI tools or scripts), focusing solely on GUI-based steps that are platform-agnostic but may implicitly align with Windows-centric workflows.
Recommendations:
  • Add instructions for managing deployment tokens using the Azure CLI or GitHub CLI, which are cross-platform and can be run on Linux, macOS, and Windows.
  • Include examples of updating GitHub secrets via command line (e.g., using gh CLI), which is especially relevant for Linux users.
  • Explicitly mention that the steps are applicable regardless of operating system, or provide alternative workflows for users who prefer command-line interfaces.
  • If screenshots are included, ensure they are not exclusively from Windows environments, or provide notes about cross-platform applicability.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/azure-dns-zone.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any command-line examples or tooling instructions for either Windows or Linux. However, it implicitly assumes a graphical, portal-based workflow (Azure portal and domain registrar websites), which is platform-neutral but omits parity for users who prefer or require CLI-based automation, especially common in Linux environments. There are no references to Windows-specific tools, but the absence of Azure CLI, PowerShell, or other command-line examples means Linux users do not see their typical workflows represented.
Recommendations:
  • Add Azure CLI examples for creating DNS zones and retrieving name server information.
  • Include instructions for updating DNS records using command-line tools where possible.
  • If mentioning PowerShell, ensure equivalent Azure CLI (cross-platform) commands are provided.
  • Explicitly state that the process can be completed via CLI and provide links to relevant documentation.
  • Consider including a section or callout for automation or scripting approaches, which are common in Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/add-api.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates some Windows bias, particularly in the way it references Windows-specific tools and installation patterns. For example, the Node.js version manager (nvm) is mentioned with a Windows-specific alternative (NVM for Windows) and installation via Winget, a Windows package manager. There is also a reference to Windows Firewall prompts, which is not relevant to Linux or macOS users. No explicit Linux or macOS-specific instructions or troubleshooting are provided, and the only OS-specific tool mentioned is for Windows. While most commands are cross-platform, the lack of parity in OS-specific guidance and the order of tool recommendations indicate a subtle Windows-first bias.
Recommendations:
  • When mentioning tools like nvm, provide equal visibility to Linux/macOS installation methods (e.g., Homebrew for macOS, apt/yum for Linux) alongside Windows options.
  • If referencing Windows Firewall prompts, add notes about equivalent network/security prompts or considerations on Linux and macOS, or clarify that this step is Windows-specific.
  • Include troubleshooting tips or environment setup notes for Linux/macOS users, such as permissions, path configuration, or common issues.
  • Where possible, avoid mentioning Windows-specific tools (like Winget) without also mentioning cross-platform or Linux/macOS alternatives.
  • Consider adding a short section or callout for Linux/macOS users in the prerequisites or setup steps to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench), referencing the Azure portal UI, and providing PowerShell examples alongside Bash. There is no mention of Linux-native tools (e.g., mysql CLI, DBeaver) or headless/server workflows, and the prerequisite tooling and workflow instructions assume a GUI environment typical of Windows users. Linux alternatives are not offered, and the order of examples often lists Windows/PowerShell first.
Recommendations:
  • Explicitly mention and provide examples for Linux-native tools such as the mysql CLI, DBeaver, or other cross-platform database clients.
  • Include instructions for performing database setup and queries using the mysql command-line client, especially for headless/server environments.
  • When listing tools, avoid Windows-first ordering; instead, present cross-platform options or group by OS.
  • For shell commands, always provide Bash examples first or equally, and clarify which commands are cross-platform.
  • Add a section or notes for users working in Linux environments, including how to install required tools and perform equivalent actions.
  • Reference the Azure CLI for portal actions where possible, as it is cross-platform.
  • Ensure screenshots and UI references are supplemented with CLI alternatives for users who may not use the Azure portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and PowerShell command examples for environment variable setup, npm usage, and CLI commands. However, in each case, Bash (Linux/macOS) instructions are presented before PowerShell (Windows), which is a positive sign for Linux parity. There is no exclusive use of Windows tools, and no steps are limited to Windows. However, the inclusion of PowerShell-specific tabs and commands throughout the tutorial, even for simple npm or CLI usage, may indicate a slight bias toward Windows users, as PowerShell is not the default shell on all Windows systems and is rarely used on Linux/macOS. No Linux-specific tools or patterns are highlighted, and there are no Linux-only troubleshooting tips or considerations.
Recommendations:
  • Continue presenting Bash instructions first to reinforce Linux parity.
  • Consider adding explicit notes about shell compatibility (e.g., Bash, Zsh, Fish) for Linux/macOS users.
  • Where possible, provide a generic shell example and mention that PowerShell is optional for Windows users who prefer it.
  • Include troubleshooting tips or common issues for Linux users, such as file permissions or npm installation differences.
  • Ensure that screenshots and UI references are OS-agnostic or include both Windows and Linux/macOS visuals where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/getting-started.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by referencing Visual Studio Code UI navigation patterns (e.g., 'File > Open Folder') and omitting any mention of Linux-specific instructions or terminal-based workflows. There are no examples or guidance for Linux users, such as using the command line or addressing differences in file navigation and shortcuts. All instructions assume a GUI workflow typical of Windows environments.
Recommendations:
  • Include Linux-specific instructions or notes, such as how to open folders in VS Code from the terminal (e.g., 'code .') and alternative keyboard shortcuts.
  • Provide examples or guidance for users who prefer or require command-line workflows, which are common on Linux.
  • Mention any platform-specific differences in installing prerequisites (e.g., Git, VS Code extension installation) and provide links or steps for Linux distributions.
  • Ensure that screenshots and navigation steps are inclusive of both Windows and Linux environments, or clarify when instructions are platform-agnostic.