All the Azure updates in one place.
https://azurecomcdn.azureedge.net/en-gb/updates/feed/?category=category1%2Ccategory2%2Ccategory3
For example:
https://azurecomcdn.azureedge.net/en-gb/updates/feed/?category=featured%2Cai-machine-learning%2Canalytics
Para cuando lo renderice correctamente materials:
mindmap
root((Pillars))
Reliability(Reliability)
DesignPrinciples(Design Principles)
Design for business requirements["**Design for business requirements:**
Gather business requirements with a focus on the intended utility of the workload."]
Design for resilience["**Design for resilience:**
The workload must continue to operate with full or reduced functionality."]
Design for recovery["**Design for recovery:**
The workload must be able to anticipate and recover from most failures, of all magnitudes, with minimal disruption to the user experience and business objectives."]
Design for operations["**Design for operations:**
Shift left in operations to anticipate failure conditions."]
Keep it simple["**Keep it simple:**
Avoid overengineering the architecture design, application code, and operations."]
Security(Security)
DesignPrinciples(Design Principles)
Plan your security readiness["**Plan your security readiness:**
Strive to adopt and implement security practices in architectural design decisions and operations with minimal friction."]
Design to protect confidentiality["**Design to protect confidentiality:**
Prevent exposure to privacy, regulatory, application, and proprietary information through access restrictions and obfuscation techniques."]
Design to protect integrity["**Design to protect integrity:**
Prevent corruption of design, implementation, operations, and data to avoid disruptions that can stop the system from delivering its intended utility or cause it to operate outside the prescribed limits. The system should provide information assurance throughout the workload lifecycle."]
Design to protect availability["**Design to protect availability:**
Prevent or minimize system and workload downtime and degradation in the event of a security incident by using strong security controls. You must maintain data integrity during the incident and after the system recovers."]
Sustain and evolve your security posture["**Sustain and evolve your security posture:**
Incorporate continuous improvement and apply vigilance to stay ahead of attackers who are continuously evolving their attack strategies."]
CostOptimization(Cost Optimization)
DesignPrinciples(Design Principles)
Develop cost-management discipline["**Develop cost-management discipline:**
Build a team culture that has awareness of budget, expenses, reporting, and cost tracking."]
Design with a cost-efficiency mindset["**Design with a cost-efficiency mindset:**
Spend only on what you need to achieve the highest return on your investments."]
Design for usage optimization["**Design for usage optimization:**
Maximize the use of resources and operations. Apply them to the negotiated functional and nonfunctional requirements of the solution."]
Design for rate optimization["**Design for rate optimization:**
Increase efficiency without redesigning, renegotiating, or sacrificing functional or nonfunctional requirements."]
Monitor and optimize over time["**Monitor and optimize over time:**
Continuously right-size investment as your workload evolves with the ecosystem."]
OperationalExcellence(Operational Excellence)
DesignPrinciples(Design Principles)
Embrace DevOps culture["**Embrace DevOps culture:**
Empower development and operations teams to continuously improve their system design and processes by working together with a mindset of collaboration, shared responsibility, and ownership."]
Establish development standards["**Establish development standards:**
Optimize productivity by standardizing development practices, enforcing quality gates, and tracking progress and success through systematic change management."]
Evolve operations with observability["**Evolve operations with observability:**
Gain visibility into the system, derive insight, and make data-driven decisions."]
Deploy with confidence["**Deploy with confidence:**
Reach the desired state of deployment with predictability."]
Automate for efficiency["**Automate for efficiency:**
Replace repetitive manual tasks with software automation that completes them quicker, with greater consistency and accuracy, and reduces risks."]
Adopt safe deployment practices["**Adopt safe deployment practices:**
Implement guardrails in the deployment process to minimize the effect of errors or unexpected conditions."]
PerformanceEfficiency(Performance Efficiency)
DesignPrinciples(Design Principles)
Negotiate realistic performance targets["**Negotiate realistic performance targets:**
The intended user experience is defined, and there's a strategy to develop a benchmark and measure targets against the pre-established business requirements."]
Design to meet capacity requirements["**Design to meet capacity requirements:**
Provide enough supply to address anticipated demand."]
Achieve and sustain performance["**Achieve and sustain performance:**
Protect against performance degradation while the system is in use and as it evolves."]
Improve efficiency through optimization["**Improve efficiency through optimization:**
Improve system efficiency within the defined performance targets to increase workload value."]
Para cuando lo renderice correctamente materials:
mindmap
root((Pillars))
Reliability(Reliability)
Tradeoffs(Tradeoffs)
Reliability tradeoffs with Security["`**Reliability tradeoffs with Security**`"]
Tradeoff: Increased workload surface area. The Security pillar prioritizes a reduced and contained surface area to minimize attack vectors and reduce the management of security controls.["`**Tradeoff: Increased workload surface area.** The Security pillar prioritizes a reduced and contained surface area to minimize attack vectors and reduce the management of security controls.`"]
Tradeoff: Security control bypass. The Security pillar recommends that all controls remain active in both normal and stressed systems.["`**Tradeoff: Security control bypass.** The Security pillar recommends that all controls remain active in both normal and stressed systems.`"]
Tradeoff: Old software versions. The Security pillar encourages a *get current, stay current* approach to vendor security patches.["`**Tradeoff: Old software versions.** The Security pillar encourages a *get current, stay current* approach to vendor security patches.`"]
Reliability tradeoffs with Cost Optimization["`**Reliability tradeoffs with Cost Optimization**`"]
Tradeoff: Increased implementation redundancy or waste. A cost-optimized workload minimizes underutilized resources and avoids over-provisioning resources.["`**Tradeoff: Increased implementation redundancy or waste.** A cost-optimized workload minimizes underutilized resources and avoids over-provisioning resources.`"]
Tradeoff: Increased investment in operations that aren't aligned with functional requirements. One approach to cost optimization is evaluating the value that's provided by any deployed solution.["`**Tradeoff: Increased investment in operations that aren't aligned with functional requirements.** One approach to cost optimization is evaluating the value that's provided by any deployed solution.`"]
Reliability tradeoffs with Operational Excellence["`**Reliability tradeoffs with Operational Excellence**`"]
Tradeoff: Increased operational complexity. Operational Excellence, like Reliability itself, prioritizes simplicity.["`**Tradeoff: Increased operational complexity.** Operational Excellence, like Reliability itself, prioritizes simplicity.`"]
Tradeoff: Increased effort to generate team knowledge and awareness. The Operational Excellence pillar recommends keeping and maintaining a documentation repository for procedures and topologies. ["`**Tradeoff: Increased effort to generate team knowledge and awareness.** The Operational Excellence pillar recommends keeping and maintaining a documentation repository for procedures and topologies.`"]
Reliability tradeoffs with Performance Efficiency["`**Reliability tradeoffs with Performance Efficiency**`"]
Tradeoff: Increased latency. Performance Efficiency requires a system to achieve performance targets for user and data flows.["`**Tradeoff: Increased latency.** Performance Efficiency requires a system to achieve performance targets for user and data flows.`"]
Tradeoff: Increased over-provisioning. The Performance Efficiency pillar discourages over-provisioning, instead recommending the use of just enough resources to satisfy demand.["`**Tradeoff: Increased over-provisioning.** The Performance Efficiency pillar discourages over-provisioning, instead recommending the use of just enough resources to satisfy demand.`"]
Security(Security)
Tradeoffs(Tradeoffs)
Security tradeoffs with Reliability["`**Security tradeoffs with Reliability**`"]
Tradeoff: Increased complexity. The Reliability pillar prioritizes simplicity and recommends that points of failure are minimized.["`**Tradeoff: Increased complexity.** The Reliability pillar prioritizes simplicity and recommends that points of failure are minimized.`"]
Tradeoff: Increased critical dependencies. The Reliability pillar recommends minimizing critical dependencies. A workload that minimizes critical dependencies, especially external ones, has more control over its points of failure.["`**Tradeoff: Increased critical dependencies.** The Reliability pillar recommends minimizing critical dependencies. A workload that minimizes critical dependencies, especially external ones, has more control over its points of failure.`"]
Tradeoff: Increased complexity of disaster recovery. A workload must reliably recover from all forms of disaster.["`**Tradeoff: Increased complexity of disaster recovery.** A workload must reliably recover from all forms of disaster.`"]
Tradeoff: Increased rate of change. A workload that experiences runtime change is exposed to more risk of reliability impact due to that change.["`**Tradeoff: Increased rate of change.** A workload that experiences runtime change is exposed to more risk of reliability impact due to that change.`"]
Security tradeoffs with Cost Optimization["`**Security tradeoffs with Cost Optimization**`"]
Tradeoff: Additional infrastructure. One approach to cost optimizing a workload is to look for ways to reduce the diversity and number of components and increase density.["`**Tradeoff: Additional infrastructure.** One approach to cost optimizing a workload is to look for ways to reduce the diversity and number of components and increase density.`"]
Tradeoff: Increased demand on infrastructure. The Cost Optimization pillar prioritizes driving down demand on resources to enable the use of cheaper SKUs, fewer instances, or reduced consumption.["`**Tradeoff: Increased demand on infrastructure.** The Cost Optimization pillar prioritizes driving down demand on resources to enable the use of cheaper SKUs, fewer instances, or reduced consumption.`"]
Tradeoff: Increased process and operational costs. Personnel process costs are part of the overall total cost of ownership and are factored into a workload's return on investment. Optimizing these costs is a recommendation of the Cost Optimization pillar.["`**Tradeoff: Increased process and operational costs.** Personnel process costs are part of the overall total cost of ownership and are factored into a workload's return on investment. Optimizing these costs is a recommendation of the Cost Optimization pillar.`"]
Security tradeoffs with Operational Excellence["`**Security tradeoffs with Operational Excellence**`"]
Tradeoff: Complications in observability and serviceability. Operational Excellence requires architectures to be serviceable and observable. The most serviceable architectures are those that are the most transparent to everyone involved.["`**Tradeoff: Complications in observability and serviceability.** Operational Excellence requires architectures to be serviceable and observable. The most serviceable architectures are those that are the most transparent to everyone involved.`"]
Tradeoff: Decreased agility and increased complexity. Workload teams measure their velocity so that they can improve the quality, frequency, and efficiency of delivery activities over time. Workload complexity factors into the effort and risk involved in operations["`**Tradeoff: Decreased agility and increased complexity.** Workload teams measure their velocity so that they can improve the quality, frequency, and efficiency of delivery activities over time. Workload complexity factors into the effort and risk involved in operations`"]
Tradeoff: Increased coordination efforts. A team that minimizes external points of contact and review can control their operations and timeline more effectively.["`**Tradeoff: Increased coordination efforts.** A team that minimizes external points of contact and review can control their operations and timeline more effectively.`"]
Security tradeoffs with Performance Efficiency["`**Security tradeoffs with Performance Efficiency**`"]
Tradeoff: Increased latency and overhead. A performant workload reduces latency and overhead.["`**Tradeoff: Increased latency and overhead.** A performant workload reduces latency and overhead.`"]
Tradeoff: Increased chance of misconfiguration. Reliably meeting performance targets depends on predictable implementations of the design.["`**Tradeoff: Increased chance of misconfiguration.** Reliably meeting performance targets depends on predictable implementations of the design.`"]
Cost Optimization["Cost Optimization`"]
Tradeoffs(Tradeoffs)
Cost Optimization tradeoffs with Reliability["`**Cost Optimization tradeoffs with Reliability**`"]
Tradeoff: Reduced resiliency. A workload incorporates resiliency measures to attempt to avoid and withstand specific types and quantities of malfunction.["`**Tradeoff: Reduced resiliency.** A workload incorporates resiliency measures to attempt to avoid and withstand specific types and quantities of malfunction.`"]
Tradeoff: Limited recovery strategy. A workload that's reliable has a tested incident response and recovery plan for disaster scenarios.["`**Tradeoff: Limited recovery strategy.** A workload that's reliable has a tested incident response and recovery plan for disaster scenarios.`"]
Tradeoff: Increased complexity. A workload that uses straightforward approaches and avoids unnecessary or overengineered complexity is generally easier to manage in terms of reliability.["`**Tradeoff: Increased complexity.** A workload that uses straightforward approaches and avoids unnecessary or overengineered complexity is generally easier to manage in terms of reliability.`"]
Cost Optimization tradeoffs with Security["`**Cost Optimization tradeoffs with Security**`"]
Tradeoff: Reduced security controls. Security controls are established across multiple layers, sometimes redundantly, to provide defense in depth.["`**Tradeoff: Reduced security controls.** Security controls are established across multiple layers, sometimes redundantly, to provide defense in depth.`"]
Tradeoff: Increased workload surface area. The Security pillar prioritizes a reduced and contained surface area to minimize attack vectors and the management of security controls.["`**Tradeoff: Increased workload surface area.** The Security pillar prioritizes a reduced and contained surface area to minimize attack vectors and the management of security controls.`"]
Tradeoff: Removed segmentation. The Security pillar prioritizes strong segmentation to support the application of targeted security controls and to control the blast radius.["`**Tradeoff: Removed segmentation.** The Security pillar prioritizes strong segmentation to support the application of targeted security controls and to control the blast radius.`"]
Cost Optimization tradeoffs with Operational Excellence["`**Cost Optimization tradeoffs with Operational Excellence**`"]
Tradeoff: Compromised software development lifecycle SDLC capacities. A workload's SDLC process provides rigor, consistency, specificity, and prioritization to change management in a workload.["`**Tradeoff: Compromised software development lifecycle capacities.** A workload's SDLC process provides rigor, consistency, specificity, and prioritization to change management in a workload.`"]
Tradeoff: Reduced observability. Observability is necessary to help ensure that a workload has meaningful alerting and successful incident response.["`**Tradeoff: Reduced observability.** Observability is necessary to help ensure that a workload has meaningful alerting and successful incident response.`"]
Tradeoff: Deferred maintenance. Workload teams are expected to keep code, tooling, software packages, and operating systems patched and up to date in a timely and orderly way.["`**Tradeoff: Deferred maintenance.** Workload teams are expected to keep code, tooling, software packages, and operating systems patched and up to date in a timely and orderly way.`"]
Cost Optimization tradeoffs with Performance Efficiency["`**Cost Optimization tradeoffs with Performance Efficiency**`"]
Tradeoff: Underprovisioned or underscaled resources. A performance-efficient workload has enough resources to serve demand but doesn't have excessive unused overhead, even when usage patterns fluctuate.["`**Tradeoff: Underprovisioned or underscaled resources.** A performance-efficient workload has enough resources to serve demand but doesn't have excessive unused overhead, even when usage patterns fluctuate.`"]
Tradeoff: Lack of optimization over time. Evaluating the effects of changes in functionality, changes in usage patterns, new technologies, and different approaches on the workload is one way to try to increase efficiency.["`**Tradeoff: Lack of optimization over time.** Evaluating the effects of changes in functionality, changes in usage patterns, new technologies, and different approaches on the workload is one way to try to increase efficiency.`"]
Operational Excellence["Operational Excellence"]
Tradeoffs(Tradeoffs)
Operational Excellence tradeoffs with Reliability["`**Operational Excellence tradeoffs with Reliability**`"]
Tradeoff: Increased complexity. Reliability prioritizes simplicity, because simple design minimizes misconfiguration and reduces unexpected interactions.["`**Tradeoff: Increased complexity.** Reliability prioritizes simplicity, because simple design minimizes misconfiguration and reduces unexpected interactions.`"]
Tradeoff: Increased potentially destabilizing activities. The Reliability pillar encourages the avoidance of activities or design choices that can destabilize a system and lead to disruptions, outages, or malfunctions["`**Tradeoff: Increased potentially destabilizing activities.** The Reliability pillar encourages the avoidance of activities or design choices that can destabilize a system and lead to disruptions, outages, or malfunctions.`"]
Operational Excellence tradeoffs with Security["`**Operational Excellence tradeoffs with Security**`"]
Tradeoff: Increased surface area. The Security pillar recommends a reduced workload surface area in terms of components and exposure to operations. This reduction minimizes attack vectors and produces a smaller scope for security control and testing.["`**Tradeoff: Increased surface area.** The Security pillar recommends a reduced workload surface area in terms of components and exposure to operations. This reduction minimizes attack vectors and produces a smaller scope for security control and testing.`"]
Tradeoff: Increased desire for transparency. A secure workload is based on designs that protect the confidentiality of data that flows through the components of the system.["`**Tradeoff: Increased desire for transparency.** A secure workload is based on designs that protect the confidentiality of data that flows through the components of the system.`"]
Tradeoff: Reduced segmentation. A key security approach for isolating access and function is to design a strong segmentation strategy. This design is implemented through resource isolation and identity controls.["`**Tradeoff: Reduced segmentation.** A key security approach for isolating access and function is to design a strong segmentation strategy. This design is implemented through resource isolation and identity controls.`"]
Operational Excellence tradeoffs with Cost Optimization["`**Operational Excellence tradeoffs with Cost Optimization**`"]
Tradeoff: Increased resource spending. A major cost driver for a workload is the cost of its resources. Deploying fewer resources, right-sizing resources, and reducing consumption generally helps keep costs low.["`**Tradeoff: Increased resource spending.** A major cost driver for a workload is the cost of its resources. Deploying fewer resources, right-sizing resources, and reducing consumption generally helps keep costs low.`"]
Tradeoff: Decreased focus on delivery activities. Workload team members deliver increased workload value by efficiently performing tasks that are aligned to their capabilities.["`**Tradeoff: Decreased focus on delivery activities.** Workload team members deliver increased workload value by efficiently performing tasks that are aligned to their capabilities.`"]
Tradeoff: Increased tooling demands and diversity. The Cost Optimization pillar recommends the reduction of tooling sprawl, consolidation of vendors, and a right-sized approach to all tooling purchases.["`**Tradeoff: Increased tooling demands and diversity.** The Cost Optimization pillar recommends the reduction of tooling sprawl, consolidation of vendors, and a right-sized approach to all tooling purchases.`"]
Operational Excellence tradeoffs with Performance Efficiency["`**Operational Excellence tradeoffs with Performance Efficiency**`"]
Tradeoff: Increased resource utilization. The Performance Efficiency pillar recommends the allocation of as much of the available compute and network as possible to the requirements of the workload.["`**Tradeoff: Increased resource utilization.** The Performance Efficiency pillar recommends the allocation of as much of the available compute and network as possible to the requirements of the workload.`"]
Tradeoff: Increased latency. To create performant workloads, teams look for ways to reduce the time and resources that workloads consume to perform their tasks.["`**Tradeoff: Increased latency.** To create performant workloads, teams look for ways to reduce the time and resources that workloads consume to perform their tasks.`"]
Performance Efficiency("Performance Efficiency")
Tradeoffs(Tradeoffs)
Performance Efficiency tradeoffs with Reliability["`**Performance Efficiency tradeoffs with Reliability**`"]
Tradeoff: Reduced replication and increased density. A cornerstone of reliability is ensuring resilience by using replication and limiting the blast radius of malfunctions.["`**Tradeoff: Reduced replication and increased density.** A cornerstone of reliability is ensuring resilience by using replication and limiting the blast radius of malfunctions.`"]
Tradeoff: Increased complexity. Reliability prioritizes simplicity.["`**Tradeoff: Increased complexity.** Reliability prioritizes simplicity.`"]
Tradeoff: Testing and observation on active environments. Avoiding the unnecessary use of production systems is a self-preservation approach for reliability.["`**Tradeoff: Testing and observation on active environments.** Avoiding the unnecessary use of production systems is a self-preservation approach for reliability.`"]
Performance Efficiency tradeoffs with Security["`**Performance Efficiency tradeoffs with Security**`"]
Tradeoff: Reduction of security controls. Security controls are established across multiple layers, sometimes redundantly, to provide defense in depth["`**Tradeoff: Reduction of security controls.** Security controls are established across multiple layers, sometimes redundantly, to provide defense in depth.`"]
Tradeoff: Increased workload surface area. Security prioritizes a reduced and contained surface area to minimize attack vectors and reduce the management of security controls.["`**Tradeoff: Increased workload surface area.** Security prioritizes a reduced and contained surface area to minimize attack vectors and reduce the management of security controls.`"]
Tradeoff: Removing segmentation. The Security pillar prioritizes strong segmentation to enable fine-grained security controls and reduce blast radius.["`**Tradeoff: Removing segmentation.** The Security pillar prioritizes strong segmentation to enable fine-grained security controls and reduce blast radius.`"]
Performance Efficiency tradeoffs with Cost Optimization["`**Performance Efficiency tradeoffs with Cost Optimization**`"]
Tradeoff: Too much supply for demand. Both Cost Optimization and Performance Efficiency prioritize having just enough supply to serve demand.["`**Tradeoff: Too much supply for demand.** Both Cost Optimization and Performance Efficiency prioritize having just enough supply to serve demand.`"]
Tradeoff: More components. One cost optimization technique is to consolidate with a smaller number of resources by increasing density, removing duplication, and co-locating functionality.["`**Tradeoff: More components.** One cost optimization technique is to consolidate with a smaller number of resources by increasing density, removing duplication, and co-locating functionality.`"]
Tradeoff: Increased investment on items that aren't aligned with functional requirements. One approach to cost optimization is evaluating the value provided by any solution that's deployed.["`**Tradeoff: Increased investment on items that aren't aligned with functional requirements.** One approach to cost optimization is evaluating the value provided by any solution that's deployed.`"]
Performance Efficiency tradeoffs with Operational Excellence["`**Performance Efficiency tradeoffs with Operational Excellence**`"]
Tradeoff: Reduced observability. Observability is necessary to provide a workload with meaningful alerting and help ensure successful incident response.["`**Tradeoff: Reduced observability.** Observability is necessary to provide a workload with meaningful alerting and help ensure successful incident response.`"]
Tradeoff: Increased complexity in operations. A complex environment has more complex interactions and a higher likelihood of a negative impact from routine, ad hoc, and emergency operations.["`**Tradeoff: Increased complexity in operations.** A complex environment has more complex interactions and a higher likelihood of a negative impact from routine, ad hoc, and emergency operations.`"]
Tradeoff: Culture stress. Operational Excellence is rooted in a culture of blamelessness, respect, and continuous improvement.["`**Tradeoff: Culture stress.** Operational Excellence is rooted in a culture of blamelessness, respect, and continuous improvement.`"]
Azure Communication Services are cloud-based services with REST APIs and client library SDKs available to help you integrate communication into your applications. You can add communication to your applications without being an expert in underlying technologies such as media encoding or telephony.
Azure Communication Services supports various communication formats:
And offers the following services:
Some Use Cases:
You have some data flow diagrams to help you to understand how Azure Communication Services works here
Some aspects to consider:
Azure Communication Services is a pay-as-you-go service. You only pay for what you use, and there are no upfront costs. You can see more information about pricing here.
The bad news are:
Azure Communication Services is a very interesting service but you need to consider the cost of the service and the regional availability before to use it.
That's it folks!, thanks for reading 
!.
I have decided to create a new category on my blog to talk about Azure services.
The main goal of this category is to provide a quick overview of some Azure services and some design considerations.
What is this category due to?
In some cases, it is because I am working with this Service and I think it is a good idea to share my experience with you and write it down for me, in others, it is because I am studying/reviewing an Azure Service and I think it is a good idea. Share my notes with you.
I hope you like it.
I am going to start with Azure Communication Services
That's all folks!, thanks for reading 
!
First, I need to clarify that I'm not a C# developer. I'm learning C# so I can better understand the code that has to be deployed to some Azure services when .NET is used.
If someone that knows me is reading this post, he/she will be thinking:
Maybe the last thought can be really true but I have to say that I have decided to learn a programming language and that I have chosen C# because many of the examples for Azure Developers that I have seen are written in C#.
I repeat, I am not a developer but I'd like to share with you my experience learning C#.
You have a lot of resources for learning on Learn .NET and in c# documentation.
In my case I prefer to simplify and follow csharp-notebooks, these materials are designed to be used with C# 101 SERIES.
After that, I will follow the free course (New) Foundational C# with Microsoft.
And after that, I think that I will be ready to start with Tutorials for getting started with .NET and plan next steps.
That's all folks!!
Trunk is a tool that runs a suite of security and best practice checks against your code. It is designed to be used in CI/CD pipelines, but can also be used as a standalone tool.
Support for the following languages is currently available:
Trunk detects checks to enable in function of the files in the current directory, but you can also enable and disable checks manually.
For example, to enable the Terraform check:
Info
You can also enable checks by modifing .trunk.yml file in your repository. See the configuration page for more information.
Examples:
trunk check
Checking 68% [====================================================================================================================================================================> ] 38/56 9.4s
↳ checkov
↳ modules/webapps/linux_function_app/private_endpoint.tf [lint] ⠧
↳ modules/webapps/linux_function_app/variables.tf [lint] ⠧
↳ terrascan
↳ modules/webapps/linux_function_app/locals.tf [lint] ⠧
↳ modules/webapps/linux_function_app/main.tf [lint] ⠧
In the case of the VSCode extension, you can review your checks in your IDE:
And you can disable checks from quick fix menu:
Trunk is updated regularly with new checks and improvements. You can update Trunk by running the following command:
In the case of the VSCode extension, it will be updated automatically:
In the previous post I explained how to create a blog with MkDocs and mkdocs-material theme.
mkdocs.yml is the configuration file for MkDocs. In this file we can configure the theme, the plugins, the pages, etc.
In this post I am going to explain you how to create a blog with MkDocs and mkdocs-material theme, add some plugins and configure it.
I only change the palette for now.
glightbox add image zoom functionality to your documentation.
Example:
Imagen de marymarkevich en Freepik
An MkDocs plugin to minify HTML, JS or CSS files prior to being written to disk.
MkDocs supports a large number of Python Markdown extensions
mermaid2 is a plugin for MkDocs that allows you to embed diagrams written in mermaid.js in your Markdown documentation.
- pymdownx.superfences:
custom_fences:
- name: mermaid
class: mermaid
format: !!python/name:pymdownx.superfences.fence_code_format
```mermaid
graph LR
A[Square Rect] -- Link text --> B((Circle))
A --> C(Round Rect)
B --> D{Rhombus}
C --> D
```
graph LR
A[Square Rect] -- Link text --> B((Circle))
A --> C(Round Rect)
B --> D{Rhombus}
C --> D
You can find more information about mermaid.js in https://mermaid-js.github.io/mermaid/#/
Admonitions is a markdown extension of materials for MkDocs that allows you to add admonition blocks to your Markdown documentation.
Example:
!!! Example
Example
!!! Error
Error
!!! Warning
Warning
!!! Success
Success
!!! Info
Info
!!! Tip
Tip
!!! Question
Question
!!! Quote
Quote
Example
Example
Error
Error
Warning
Warning
Success
Success
Info
Info
Tip
Tip
Question
Question
Quote
Quote
With material you can use more than 10000 icons and thousand of emojis in your documentation.
markdown_extensions:
- attr_list
- pymdownx.emoji:
emoji_index: !!python/name:material.extensions.emoji.twemoji
emoji_generator: !!python/name:material.extensions.emoji.to_svg
Example:
One of the flagship features of Material for MkDocs is the ability to inject annotations – little markers that can be added almost anywhere in a document and expand a tooltip containing arbitrary Markdown on click or keyboard focus.
Examples:
This is a paragraph with a annotation(1).
{ .annotate }
1. :man_raising_hand: I'm an annotation! I can contain `code`, __formatted
text__, images, ... basically anything that can be expressed in Markdown.
This is a paragraph with a annotation(1).
I'm an annotation! I can contain code, formatted
text, images, ... basically anything that can be expressed in Markdown.This is a paragraph with a annotation(1).
{ .annotate }
1. :man_raising_hand: I'm an annotation! with a nested annotation(1)
{ .annotate }
1. I'm a nested annotation!
This is a paragraph with a annotation(1).
I'm an annotation! with a nested annotation(1)
Examples:
Example:
=== "azcli"
``` azcli
az group create --name myResourceGroup --location westeurope
```
=== "pwsh"
``` pwsh
New-AzResourceGroup -Name myResourceGroup -Location westeurope
```
Example:
This is a paragraph with a footnote1.
markdown_extensions:
- pymdownx.critic
- pymdownx.caret
- pymdownx.keys
- pymdownx.mark
- pymdownx.tilde
Example:
site_name: My Site
site_description: A blog about Azure, DevOps and other stuff
site_author: Rafael Fernández
site_url: https://rfernandezdo.github.io
theme:
name: material
palette:
primary: blue
accent: white
features:
- navigation.tabs
- navigation.expand
- navigation.sections
- toc.integrate
- toc.nested
- toc.smoothscroll
- footer
- content.code.copy
- content.code.annotate
- content.tooltips
extra:
social:
- icon: fontawesome/brands/linkedin
link: https://www.linkedin.com/in/rafaelfernandezd/
name: LinkedIn
- icon: fontawesome/brands/github
link: https://github.com/rfernandezdo
name: GitHub
- icon: fontawesome/solid/square-rss
link: https://rfernandezdo.github.io/feed_rss_created.xml
name: RSS feed
copyright: Copyright © 2023-now Rafael Fernández
plugins:
- search
- mermaid2
- blog
- tags:
tags_file: tags.md
- rss:
match_path: blog/posts/.*
date_from_meta:
as_creation: date
categories:
- categories
- tags
- minify:
minify_html: true
minify_js: true
minify_css: true
htmlmin_opts:
remove_comments: true
cache_safe: true
- glightbox:
zoomable: true
draggable: true
skip_classes:
- skip-lightbox
#- meta in insiders, review in next release
- social
markdown_extensions:
- admonition
- pymdownx.details
- pymdownx.superfences:
custom_fences:
- name: mermaid
class: mermaid
format: !!python/name:pymdownx.superfences.fence_code_format
- md_in_html
- attr_list
- pymdownx.emoji:
emoji_index: !!python/name:material.extensions.emoji.twemoji
emoji_generator: !!python/name:material.extensions.emoji.to_svg
- pymdownx.tabbed:
alternate_style: true
- pymdownx.highlight:
anchor_linenums: true
line_spans: __span
pygments_lang_class: true
- pymdownx.inlinehilite
- pymdownx.snippets
- footnotes
- pymdownx.critic
- pymdownx.caret
- pymdownx.keys
- pymdownx.mark
- pymdownx.tilde
- def_list
- pymdownx.tasklist:
custom_checkbox: true
A few time ago I maintained a blog with Wordpress. I was happy with it, but I wanted to try something new.
I tried Jekyll but it didn't convince me, I discovered mkdocs so I decided to use MkDocs and mkdocs-material. I was happy with the result, so I decided to write this post to explain how to create a blog with MkDocs, mkdocs-material and some plugins.
These is the first post of a serie of posts to create a blog with MkDocs, mkdocs-material and GitHub Pages and some customization.
Some knowledge:
MkDocs is a fast, simple and downright gorgeous static site generator that's geared towards building project documentation. Documentation source files are written in Markdown, and configured with a single YAML configuration file.
Material for MkDocs is a theme for MkDocs, a static site generator geared towards (technical) project documentation. It is built using Google's Material Design guidelines. Material for MkDocs provides a polished and responsive experience out of the box, and it is as easy to use for the beginner as it is for the seasoned developer.
GitHub Pages is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on GitHub, optionally runs the files through a build process, and publishes a website. You can see more information about GitHub Pages here.
This plugin generates an RSS feed for your MkDocs site. You can see more information about mkdocs-rss-plugin here.
Create a new repository on GitHub named username.github.io, where username is your username (or organization name) on GitHub. If the first part of the repository doesn’t exactly match your username, it won’t work, so make sure to get it right.
Go into the repository settings and, if you are not using GitHub Pages already, enable GitHub Pages on the gh-pages branch.
Go to the folder where you want to store your project, and clone the new repository:
In username.github.io$ path:
sudo apt update
sudo apt install libcairo2
sudo apt install python3.10-venv
python3 -m venv mysite
source mysite/bin/activate
pip install -r requirements.txt
For this post I am going to add the following configuration:
site_name: My Site
site_description: A blog about Azure, DevOps and other stuff
site_author: Rafael Fernández
theme:
name: material
features:
- navigation.tabs
- navigation.expand
- navigation.sections
- toc.integrate
- toc.nested
- toc.smoothscroll
- footer
plugins:
- search
- blog
- tags:
tags_file: tags.md
- rss:
match_path: blog/posts/.*
date_from_meta:
as_creation: date
categories:
- categories
- tags
In blog/post folder create a new folder with the name of the post and create a new file with the name of the post and the extension .md. For example: welcome.md
In username.github.io$ path:
You can check your site in http://127.0.0.1:8000/ and make live changes in your site and see the results in your browser.
In username.github.io$ path:
After a seconds, you can check your site in https://username.github.io/
name: ci # (1)!
on:
push:
branches:
- main
permissions:
contents: write
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v4
with:
python-version: 3.x
- run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV # (3)!
- uses: actions/cache@v3
with:
key: mkdocs-material-${{ env.cache_id }}
path: .cache
restore-keys: |
mkdocs-material-
- run: pip install -r requirements.txt # (4)!
- run: mkdocs gh-deploy --force
You can change the name to your liking.
At some point, GitHub renamed master to main. If your default branch
is named master, you can safely remove main, vice versa.
Store the cache_id environmental variable to access it later during cache
key creation. The name is case-sensitive, so be sure to align it with ${{ env.cache_id }}.
--utc option makes sure that each workflow runner uses the same time zone.%V format assures a cache update once a week.%F to have daily cache updates.You can read the [manual page] to learn more about the formatting options of the date command.
Add [MkDocs plugins] or Markdown
extensions with pip to requirements.txt to be used during the build.
In the next post I will explain how to customize your site with mkdocs-material and some plugins writing mkdocs.yml.
That's it folks