Compare commits

..

39 Commits

Author SHA1 Message Date
Javi Canales
8cf645237c add book label 2025-08-08 13:31:19 +02:00
Javi Canales
23407cc208 add Vim book 2025-08-08 13:28:29 +02:00
Javi Canales
d4bd2d9577 remove paid resource 2025-08-08 09:19:41 +02:00
Kamran Ahmed
404859737d Regenerate roadmap assets 2025-08-07 18:27:04 +01:00
Johnny Huang
5e8929c36b add angular resource link (#8926) 2025-08-07 17:49:39 +01:00
Oleksandr Redko
33cb7b9de5 Fix queue-based load leveling content and links 2025-08-07 17:47:53 +01:00
Jawher Kl
cec01c3df5 Fix broken design system pilot links 2025-08-07 17:47:12 +01:00
Kamran Ahmed
126d28f7f2 fix: update technical content 2025-08-07 17:46:33 +01:00
Alex Ivanov
ab432f7be8 Update Vue create-vue link to current guide
Vue CLI is now in maintenance mode.

For new projects, it’s recommended to use create-vue to scaffold Vite‑based applications. You can find the official example on the Vue.js website.
2025-08-07 17:46:08 +01:00
Noodles
65a0a8c5bf Fix typo in Technical Writer label 2025-08-07 17:45:16 +01:00
Jofre Gaston
781721cd54 Remove wrong content (#8927)
Delete wrong content
2025-08-07 17:45:08 +01:00
Hang
f371aa602f Add CompTIA Linux+ training labs resource
Add a new article resource for CompTIA Linux+ Certification Training Labs to the existing list of resources.

Co-authored-by: huhuhang <huhuhang@users.noreply.github.com>
2025-08-07 17:41:50 +01:00
Sepand
1ef8a2746f Remove broken QA backend testing link
The website related to the first resource in this section has been repurposed, and the existing link is no longer active.
2025-08-07 17:41:02 +01:00
Caleb James Smith
0385a97062 Fix grammar in Full Stack Linux Basics 2025-08-07 17:38:11 +01:00
Jilvin Thomas Abraham
a40e9bc0d3 Fix typo in Linux process priorities 2025-08-07 17:37:14 +01:00
Kamran Ahmed
a3cd0fa52e remove python resource 2025-08-07 17:37:07 +01:00
Sudhanwa Kaveeshwar
837f8457cd Add Go var vs := content 2025-08-07 17:36:43 +01:00
Abhishek Raha
b67ca1dab6 remove dead link (#8957)
* Updated dead article link ( bito.ai ) for Method Chaining to new link ( geeksforgeeks )

* Removed unnecessary break-line

* Update src/data/roadmaps/java/content/method-chaining@Ax2ouIZgN1DpPzKDy4fwp.md

---------

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
2025-08-07 17:35:55 +01:00
Paul Wiggers
35e74516c1 Update IT skills article title from 7 to 8 skills and fix formatting
- Updated Coursera article title to reflect current content (7 -> 8 In-Demand IT Skills)
- Added missing newline at end of file

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-07 17:33:22 +01:00
qwAlb3do
6108963b9c Add Python video resource with correct formatting
- Added Python - Basic to Advance YouTube playlist to learn-the-basics content
- Fixed formatting to include proper @video@ type prefix

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-07 17:32:37 +01:00
Vedansh
bcf59df1db refactor(golang): cleanup roadmap content (#8976)
* audit first 36 files

* audit next 25 files

* audit next 26 topics

* audit next 29 topics

* audit last 65 topics.
2025-08-07 17:29:30 +01:00
George Nagib
841bc996a6 Update models-on-hugging-face@dLEg4IA3F5jgc44Bst9if.md (#8978)
* Update models-on-hugging-face@dLEg4IA3F5jgc44Bst9if.md

Added overview of embedding models on Hugging Face

- Added a concise summary explaining what embeddings are and their common use cases
- Listed popular embedding models like MiniLM, GTE, E5, and BGE
- Included an official Hugging Face video on text embeddings
- Linked to the full list of embedding models available on Hugging Face Hub

* Fix formatting issues in Hugging Face embedding models content

- Add missing blank line after title (follows established pattern)
- Fix grammatical error: remove duplicated 'which' and em dash
- Maintain original content structure and meaning

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
2025-08-07 17:27:26 +01:00
Chijioke Ugwuanyi
04947d5b44 Add caching resources for backend performance best practices
Adds high-quality external learning resources for caching strategies, cache invalidation, and caching utilization topics in backend performance best practices.
2025-08-07 17:00:45 +01:00
Ken Nguyen
6000ef92b1 Replace outdated article (#9002)
* Replaced outdated 2020 article with newer article on why blockchain is important

Article by Forbes from 2020 is outdated. The new article from Hedera provides more details on how blockchain matters by discussing new advancements, such as IoT and tokenization.

* Update src/data/roadmaps/blockchain/content/why-it-matters@ecT4W5z8Vq9pXjnuhMdpl.md

---------

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
2025-08-07 16:55:41 +01:00
Mahdi ramezaan zaade
11ad1a8086 Update resource tag (#9003)
the first link is refer to react docs and should be official
2025-08-07 16:39:11 +01:00
Kamran Ahmed
2a840c4f7e Add new guide data analyst vs data engineer 2025-08-07 15:14:36 +01:00
github-actions[bot]
48d33e87cf chore: update roadmap content json (#8995)
Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com>
2025-08-06 22:15:57 +06:00
nonnapopoa
70dac4377e Remove atom from ides-and-rust-toolchains (#8998) 2025-08-05 17:15:30 +01:00
Kamran Ahmed
d405582f50 Remove outdated resource (#8997) 2025-08-05 16:25:00 +01:00
Aboody_01
7112987e54 chore: add explanation for design principles (#8988)
* Update design-principles@p96fNXv0Z4rEEXJR9hAYX.md

add design principles description

* Update src/data/roadmaps/software-design-architecture/content/design-principles@p96fNXv0Z4rEEXJR9hAYX.md

* Update src/data/roadmaps/software-design-architecture/content/design-principles@p96fNXv0Z4rEEXJR9hAYX.md

* Update src/data/roadmaps/software-design-architecture/content/design-principles@p96fNXv0Z4rEEXJR9hAYX.md

---------

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
2025-08-04 17:41:57 +01:00
FedorT22
b6aa554e1d fix: broken link in mutation (#8990)
Seems like the current link is stale
2025-08-04 16:29:59 +01:00
Chijioke Ugwuanyi
b3a8da98f2 chore: add backend performance resources (#8991) 2025-08-04 16:29:32 +01:00
Ahmad Beigi
9e952fe22b fix: resource typo (#8987) 2025-08-04 19:58:40 +06:00
Fakhry
85ec75eff4 fix: typo cnofig should be config (#8992) 2025-08-04 11:13:43 +02:00
Dmitry
47123f575b fix: rename AccounSidebar to AccountSidebar (#8983) 2025-08-02 09:30:15 +06:00
github-actions[bot]
bd2719749d chore: update roadmap content json (#8984)
Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com>
2025-08-02 09:28:36 +06:00
Renato Francia Castillo
bc4e29521b Update code example in PHP roadmap (#8973) 2025-08-01 16:34:31 +01:00
Keiler Guardo Herrera
4037e3bb31 fix typo in the github content (#8980) 2025-08-01 16:31:58 +01:00
Arik Chakma
267d2b54f2 fix: migrated team urls (#8982) 2025-08-01 20:43:04 +06:00
350 changed files with 1670 additions and 289 deletions

1
.astro/types.d.ts vendored
View File

@@ -1 +1,2 @@
/// <reference types="astro/client" />
/// <reference path="content.d.ts" />

View File

@@ -16,6 +16,7 @@
"roadmap-links": "node scripts/roadmap-links.cjs",
"roadmap-dirs": "node scripts/roadmap-dirs.cjs",
"roadmap-assets": "tsx scripts/editor-roadmap-assets.ts",
"refresh-assets": "tsx scripts/refresh-assets.ts",
"editor-roadmap-dirs": "tsx scripts/editor-roadmap-dirs.ts",
"editor-roadmap-content": "tsx scripts/editor-roadmap-content.ts",
"roadmap-content": "node scripts/roadmap-content.cjs",

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

View File

@@ -926,21 +926,10 @@
}
]
},
"4ZbGj54WR5iuk0V8X_cpL": {
"title": "Remote Cnofig",
"description": "Firebase Remote Config, accessed in Flutter via the `firebase_remote_config` plugin, enables dynamic app behavior and appearance changes without app updates. This involves adding the plugin, initializing the service, defining default parameter values in the console or code, fetching and retrieving remote parameters, and updating those parameters either through the console or by activating fetched values, allowing for A/B testing and feature control.\n\nLearn more from the following:",
"links": [
{
"title": "Remote Config",
"url": "https://firebase.google.com/docs/remote-config",
"type": "article"
},
{
"title": "Firebase Remote Config",
"url": "https://www.youtube.com/watch?v=34ExOdNEMXI",
"type": "video"
}
]
"remote-config@4ZbGj54WR5iuk0V8X_cpL.md": {
"title": "Remote Config",
"description": "",
"links": []
},
"bVeHBEoR_4kfPsEHmVYbp": {
"title": "Cloud Functions",

View File

@@ -878,11 +878,6 @@
"url": "https://svelte.dev/",
"type": "article"
},
{
"title": "All About Svelte, the Much-Loved, State-Driven Web Framework",
"url": "https://thenewstack.io/all-about-svelte-the-much-loved-state-driven-web-framework/",
"type": "article"
},
{
"title": "Svelte and the Future of Frontend Development",
"url": "https://thenewstack.io/svelte-and-the-future-of-front-end-development/",

View File

@@ -801,7 +801,7 @@
},
"99FVJ3Zs8n6lr8L95mG6g": {
"title": "Rebase",
"description": "Rebasing in Git is a powerful and potentially complex feature used to reorganize or modify a series of commits. The primary purpose of rebasing is to create a cleaner, more linear project history by moving or combining changes from one branch onto another.\n\nVisit the following resources to learn more:",
"description": "Rebasing in Git is a powerful and potentially complex feature used to reorganize or modify a series of commits. The primary purpose of rebasing is to create a cleaner, more linear project history by moving or combining changes from one branch into another.\n\nVisit the following resources to learn more:",
"links": [
{
"title": "Rebasing",

View File

@@ -215,7 +215,7 @@
"links": [
{
"title": "Guide to Multiple fields in mutations",
"url": "https://graphql.org/learn/queries/#multiple-fields-in-mutations",
"url": "https://graphql.org/learn/mutations/#multiple-fields-in-mutations",
"type": "article"
}
]

View File

@@ -1014,7 +1014,7 @@
},
"5anSYRhaKIs3dCLWlvZfT": {
"title": "Process Priorities",
"description": "Linux assigns priority levels to processes, affecting execution timing and resource allocation. Process priorities use \"nice\" values ranging from -20 (highest priority) to +19 (lowest priority) and only root can set negative nive value. The `/proc` filesystem contains process information including priorities. You can view priorities with `ps -eo pid,pri,user,comm` and modify them using `renice` command.\n\nVisit the following resource to learn more:",
"description": "Linux assigns priority levels to processes, affecting execution timing and resource allocation. Process priorities use \"nice\" values ranging from -20 (highest priority) to +19 (lowest priority) and only root can set negative nice value. The `/proc` filesystem contains process information including priorities. You can view priorities with `ps -eo pid,pri,user,comm` and modify them using `renice` command.\n\nVisit the following resource to learn more:",
"links": [
{
"title": "Understanding Process Thread Priorities in Linux",

View File

@@ -228,7 +228,7 @@
},
"j2S8dP3HlAOOoZdpj-7Dx": {
"title": "Indexed Arrays",
"description": "Indexed arrays in PHP store values that are accessed through numerical indexes, which start at 0 by default. This might be particularly useful when you have a list of items in a specific order. For example, you might use an indexed array to represent a list of your favorite books, where each book is numbered starting from 0. Each individual item in the array, book in this case, can be accessed by their specific index. You can use the array() function or the short array syntax \\[\\] to declare an indexed array.\n\nHere's an Example:\n\n $books = array(\"The Great Gatsby\", \"Moby Dick\", \"To Kill a Mockingbird\");\n echo $books[0]; //Outputs \"The Great Gatsby\"\n \n\nVisit the following resources to learn more:",
"description": "Indexed arrays in PHP store values that are accessed through numerical indexes, which start at 0 by default. This might be particularly useful when you have a list of items in a specific order. For example, you might use an indexed array to represent a list of your favorite books, where each book is numbered starting from 0. Each individual item in the array, book in this case, can be accessed by their specific index. You can use the array() function or the short array syntax \\[\\] to declare an indexed array.\n\nHere's an Example:\n\n $books = [\"The Great Gatsby\", \"Moby Dick\", \"To Kill a Mockingbird\"];\n echo $books[0]; //Outputs \"The Great Gatsby\"\n \n\nVisit the following resources to learn more:",
"links": [
{
"title": "Indexed Arrays",
@@ -239,7 +239,7 @@
},
"i_NRsOJNNp7AOqMgu5Jg8": {
"title": "Associative Arrays",
"description": "Associative arrays in PHP are a type of array that uses named keys instead of numeric ones. This provides a more human-readable way to store data where each value can be accessed by its corresponding string key. An example of an associative array could be storing names as keys and their corresponding ages as values. Here's a brief example:\n\n $ages = array(\n \"Peter\" => 35,\n \"John\" => 42,\n \"Mary\" => 27\n );\n \n\nIn this case, to find out John's age, you would simply use `echo $ages['John']` where 'John' is the key. Associative arrays are also easy to loop through using the `foreach` construct.\n\nVisit the following resources to learn more:",
"description": "Associative arrays in PHP are a type of array that uses named keys instead of numeric ones. This provides a more human-readable way to store data where each value can be accessed by its corresponding string key. An example of an associative array could be storing names as keys and their corresponding ages as values. Here's a brief example:\n\n $ages = [\n \"Peter\" => 35,\n \"John\" => 42,\n \"Mary\" => 27\n ];\n \n\nIn this case, to find out John's age, you would simply use `echo $ages['John']` where 'John' is the key. Associative arrays are also easy to loop through using the `foreach` construct.\n\nVisit the following resources to learn more:",
"links": [
{
"title": "PHP Documentation - Associative Arrays",
@@ -250,7 +250,7 @@
},
"uARTOZ-ZwugSmbCJoRS5Y": {
"title": "Multi-dimensional Arrays",
"description": "Multi-dimensional arrays in PHP are a type of array that contains one or more arrays. Essentially, it's an array of arrays. This allows you to store data in a structured manner, much like a table or a matrix. The fundamental idea is that each array value can, in turn, be another array. For instance, you can store information about various users, where each user (a primary array element) contains several details about them (in a secondary array like email, username etc.).\n\nHere's an example:\n\n $users = array(\n array(\"John\", \"john@example.com\", \"john123\"),\n array(\"Jane\", \"jane@example.com\", \"jane123\"),\n array(\"Doe\", \"doe@example.com\", \"doe123\")\n );\n \n\nVisit the following resources to learn more:",
"description": "Multi-dimensional arrays in PHP are a type of array that contains one or more arrays. Essentially, it's an array of arrays. This allows you to store data in a structured manner, much like a table or a matrix. The fundamental idea is that each array value can, in turn, be another array. For instance, you can store information about various users, where each user (a primary array element) contains several details about them (in a secondary array like email, username etc.).\n\nHere's an example:\n\n $users = [\n [\"John\", \"john@example.com\", \"john123\"],\n [\"Jane\", \"jane@example.com\", \"jane123\"],\n [\"Doe\", \"doe@example.com\", \"doe123\"]\n ];\n \n\nVisit the following resources to learn more:",
"links": [
{
"title": "Multi-dimensional Arrays",

View File

@@ -115,7 +115,7 @@
},
"oyP1ZyOgDC4nYEQXHwdVQ": {
"title": "IDEs and Rust Toolchains",
"description": "For the Rust Programming Language, several Integrated Development Environments (IDEs) and editors provide great support. Visual Studio Code is highly preferred among Rust developers due to its support for Rust via the \"Rust Language Server\" or \"rust-analyzer\" plugins. Another popular choice is RustRover, a dedicated IDE for Rust development by JetBrains. Additionally, Sublime Text and Atom with respective Rust-enhancement plugins are also used. For a more terminal-centric approach, Vim and Emacs are equipped with Rust modes. These IDEs and editors offer various features like auto-completion, syntax highlighting, and debugging tools which prove useful for Rust programming.\n\nVisit the following resources to learn more:",
"description": "For the Rust Programming Language, several Integrated Development Environments (IDEs) and editors provide great support. Visual Studio Code is highly preferred among Rust developers due to its support for Rust via the \"Rust Language Server\" or \"rust-analyzer\" plugins. Another popular choice is RustRover, a dedicated IDE for Rust development by JetBrains. Additionally, Sublime Text with respective Rust-enhancement plugins are also used. For a more terminal-centric approach, Vim and Emacs are equipped with Rust modes. These IDEs and editors offer various features like auto-completion, syntax highlighting, and debugging tools which prove useful for Rust programming.\n\nVisit the following resources to learn more:",
"links": [
{
"title": "Visual Studio Code",
@@ -137,11 +137,6 @@
"url": "https://www.gnu.org/software/emacs/",
"type": "article"
},
{
"title": "Atom",
"url": "https://atom.io",
"type": "article"
},
{
"title": "Sublime Text",
"url": "https://www.sublimetext.com",

View File

@@ -49,7 +49,7 @@
},
"p96fNXv0Z4rEEXJR9hAYX": {
"title": "Design Principles",
"description": "",
"description": "Design principles are fundamental guidelines that help software engineers create systems that are maintainable, scalable, robust, and easy to understand. They represent best practices derived from decades of software engineering experience and are widely used to guide the structure and behavior of code. Applying these principles can lead to better software architecture, easier debugging, and improved collaboration.",
"links": []
},
"gyQw885dvupmkohzJPg3a": {

View File

@@ -1321,10 +1321,16 @@
}
]
},
"queu-based-load-leveling@LncTxPg-wx8loy55r5NmV.md": {
"title": "Queu-based Load Leveling",
"description": "",
"links": []
"LncTxPg-wx8loy55r5NmV": {
"title": "Queue-Based Load Leveling",
"description": "Use a queue that acts as a buffer between a task and a service it invokes in order to smooth intermittent heavy loads that can cause the service to fail or the task to time out. This can help to minimize the impact of peaks in demand on availability and responsiveness for both the task and the service.\n\nTo learn more visit the following links:",
"links": [
{
"title": "Queue-Based Load Leveling pattern",
"url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/queue-based-load-leveling",
"type": "article"
}
]
},
"2ryzJhRDTo98gGgn9mAxR": {
"title": "Publisher/Subscriber",

View File

@@ -52,7 +52,7 @@
]
},
"j69erqfosSZMDlmKcnnn0": {
"title": "Role of Technical Writers inOrganizations",
"title": "Role of Technical Writers in Organizations",
"description": "The role of a **Technical Writer** is primarily to translate complex technical information into simpler language that is easy to understand for a non-technical audience. They design, write, edit, and rewrite technical pieces like operating instructions, FAQs, installation guides, and more. Apart from this, they also gather and disseminate technical information among customers, designers, and manufacturers. Essentially, their job involves communicating technical terminologies and a clear understanding of complex information to those who need it in an easy-to-understand format.",
"links": []
},

Binary file not shown.

Before

Width:  |  Height:  |  Size: 807 KiB

After

Width:  |  Height:  |  Size: 476 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 354 KiB

After

Width:  |  Height:  |  Size: 335 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 478 KiB

After

Width:  |  Height:  |  Size: 492 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 396 KiB

After

Width:  |  Height:  |  Size: 315 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 175 KiB

After

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 215 KiB

After

Width:  |  Height:  |  Size: 462 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 586 KiB

After

Width:  |  Height:  |  Size: 293 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 311 KiB

After

Width:  |  Height:  |  Size: 490 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 210 KiB

After

Width:  |  Height:  |  Size: 391 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 283 KiB

After

Width:  |  Height:  |  Size: 498 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 235 KiB

After

Width:  |  Height:  |  Size: 376 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 506 KiB

After

Width:  |  Height:  |  Size: 365 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 342 KiB

After

Width:  |  Height:  |  Size: 526 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 786 KiB

After

Width:  |  Height:  |  Size: 427 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 480 KiB

After

Width:  |  Height:  |  Size: 776 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 531 KiB

After

Width:  |  Height:  |  Size: 428 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 586 KiB

After

Width:  |  Height:  |  Size: 331 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 244 KiB

After

Width:  |  Height:  |  Size: 386 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 278 KiB

After

Width:  |  Height:  |  Size: 398 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 723 KiB

After

Width:  |  Height:  |  Size: 470 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 131 KiB

After

Width:  |  Height:  |  Size: 227 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 MiB

After

Width:  |  Height:  |  Size: 594 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 213 KiB

After

Width:  |  Height:  |  Size: 348 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 527 KiB

After

Width:  |  Height:  |  Size: 387 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 120 KiB

After

Width:  |  Height:  |  Size: 218 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 203 KiB

After

Width:  |  Height:  |  Size: 392 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 716 KiB

After

Width:  |  Height:  |  Size: 537 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 545 KiB

After

Width:  |  Height:  |  Size: 550 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 136 KiB

After

Width:  |  Height:  |  Size: 240 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 672 KiB

After

Width:  |  Height:  |  Size: 490 KiB

Some files were not shown because too many files have changed in this diff Show More