项目介绍

loryanstrant/MicrosoftCloudLogos 是一个托管在 GitHub 上的开源项目,主要使用 Python 编写,目前获得 314 个 Star、57 次 Fork。

仓库全名
loryanstrant/MicrosoftCloudLogos
Star 数
314
Fork 数
57
未关闭 Issue
1

README 摘要

Microsoft Cloud Product Logos This collection of logos has been built up over the years using both official Microsoft logo packages, as well as hard to find places (i.e. scraping websites or blog posts, AppSource, product screens, presentations, and anywhere I can find them). It originally lived in my OneDrive for use in documents, but then I kept sharing it with colleagues whenever I'd spot an incorrect or dated…

完整内容见 GitHub 原始 README 或本页 。

常见问题

MicrosoftCloudLogos 用什么语言开发?

主要使用 Python 编写,目前有 314 个 Star。

如何获取 MicrosoftCloudLogos 的源码?

可以直接克隆仓库:git clone https://github.com/loryanstrant/MicrosoftCloudLogos.git,默认分支为 main;安装与运行步骤见仓库 README。

MicrosoftCloudLogos 最近还在维护吗?

仓库最近一次更新为 10月7日,当前有 1 个未关闭 Issue;Star 数为 314,可作为社区活跃度的参考。

关于

A collection of Microsoft cloud product logos

描述取自 GitHub 官方 API,中文内容由 GitRead 中文社区 编辑团队整理。

语言占比

Python

README

Microsoft Cloud Product Logos

This collection of logos has been built up over the years using both official Microsoft logo packages, as well as hard to find places (i.e. scraping websites or blog posts, AppSource, product screens, presentations, and anywhere I can find them).

It originally lived in my OneDrive for use in documents, but then I kept sharing it with colleagues whenever I’d spot an incorrect or dated product logo.

As it continued to grow, I decided it was time for it to live on GitHub instead so the rest of the community can benefit from it, and hopefully contribute.

I’ll try to keep this current as possible, and will also retain legacy logos just for the sake of it.

If you have any to add or update any, please feel free to contribute!

Enjoy!

You can also access the collection at www.mscloudlogos.com, where you’ll find an easy-to-use interface for sorting and filtering the icons.

The website is built and deployed independently from this logo repository. Changes to this repository are picked up by the site’s scheduled source check; contributors do not need to regenerate or commit website data.

Contributing

Everyone is welcome to contribute. The only ask is that you thoroughly check through the repo before raising an issue or creating a pull request.

If you see something that is incorrect; either raise an issue or submit a pull request directly.

If you are adding or updating a logo, please try to stick to the structure outlined below.

File & folder structure

I have attempted to bring order to the challenge of keeping track of current and legacy logos by applying the following logic:

  • Logos are grouped by their (current) product family grouping, as defined by Microsoft marketing (i.e. website).
    • There are some outliers to clear logic here, such as Entra ID being part of Microsoft 365 and Entra suite, or Intune, or Power BI being part of Power Platform and Fabric. I do my best to apply reasoning for these.
  • Where multiple versions of a logo exist - older versions are stored in sub-folders prefixed by their years of (official) existence.
  • Where a product has been retired entirely - it is moved into the “zzFORMER_PRODUCTS” folder within its product family (where applicable, and possible).
  • Where a product has had a significant rename - the old logos are in a sub-folder of the current name, for example:
    • Azure Active Directory is found under the Entra folder
    • MyAnalytics and Workplace Analytics are found under the Viva Insights folder
    • Yammer is found under the Viva Engage folder
    • Power Virtual Agents is found under the Copilot Studio folder
    • Office is found under the Microsoft 365 Apps folder (note the capital “A”)
  • Exceptions to the rename logic are where the current product is significantly different from the previous and/or has itself had numerous logo versions (e.g. Skype for Business).
  • Current versions of logos live in the root of the folder for their product, OR (if there are multiple styles) under sub-folders that will have the year and the word “current” in them (e.g. “2019-current_full-color”).
  • Historical versions of logos live in folders based on their year of existence and logo style.
  • Folders and files do not contain spaces, so that they can be easily used for external reference.

I know it seems a bit messy, but I’m doing my best to make it seem logical!

References and sources

Azure

Dynamics 365

Entra ID

Fabric

Power Platform

Viva (courtesy of Viva Explorers)

Microsoft Trademarks and Branding Guidelines

Disclaimer: I do not work for Microsoft, do not claim copyright or ownership of any of these files. All logos are the property of Microsoft Corporation.

评论

暂无评论