Compare commits
1 Commits
devops-con
...
fix/team-l
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
fb06f2b3fd |
1
.astro/types.d.ts
vendored
@@ -1,2 +1 @@
|
||||
/// <reference types="astro/client" />
|
||||
/// <reference path="content.d.ts" />
|
||||
@@ -16,7 +16,6 @@
|
||||
"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",
|
||||
|
||||
@@ -926,10 +926,21 @@
|
||||
}
|
||||
]
|
||||
},
|
||||
"remote-config@4ZbGj54WR5iuk0V8X_cpL.md": {
|
||||
"title": "Remote Config",
|
||||
"description": "",
|
||||
"links": []
|
||||
"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"
|
||||
}
|
||||
]
|
||||
},
|
||||
"bVeHBEoR_4kfPsEHmVYbp": {
|
||||
"title": "Cloud Functions",
|
||||
|
||||
@@ -878,6 +878,11 @@
|
||||
"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/",
|
||||
|
||||
@@ -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 into 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 onto another.\n\nVisit the following resources to learn more:",
|
||||
"links": [
|
||||
{
|
||||
"title": "Rebasing",
|
||||
|
||||
@@ -215,7 +215,7 @@
|
||||
"links": [
|
||||
{
|
||||
"title": "Guide to Multiple fields in mutations",
|
||||
"url": "https://graphql.org/learn/mutations/#multiple-fields-in-mutations",
|
||||
"url": "https://graphql.org/learn/queries/#multiple-fields-in-mutations",
|
||||
"type": "article"
|
||||
}
|
||||
]
|
||||
|
||||
@@ -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 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:",
|
||||
"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:",
|
||||
"links": [
|
||||
{
|
||||
"title": "Understanding Process Thread Priorities in Linux",
|
||||
|
||||
@@ -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 = [\"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 = 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:",
|
||||
"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 = [\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 = 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:",
|
||||
"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 = [\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:",
|
||||
"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:",
|
||||
"links": [
|
||||
{
|
||||
"title": "Multi-dimensional Arrays",
|
||||
|
||||
@@ -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 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 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:",
|
||||
"links": [
|
||||
{
|
||||
"title": "Visual Studio Code",
|
||||
@@ -137,6 +137,11 @@
|
||||
"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",
|
||||
|
||||
@@ -49,7 +49,7 @@
|
||||
},
|
||||
"p96fNXv0Z4rEEXJR9hAYX": {
|
||||
"title": "Design Principles",
|
||||
"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.",
|
||||
"description": "",
|
||||
"links": []
|
||||
},
|
||||
"gyQw885dvupmkohzJPg3a": {
|
||||
|
||||
@@ -1321,16 +1321,10 @@
|
||||
}
|
||||
]
|
||||
},
|
||||
"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"
|
||||
}
|
||||
]
|
||||
"queu-based-load-leveling@LncTxPg-wx8loy55r5NmV.md": {
|
||||
"title": "Queu-based Load Leveling",
|
||||
"description": "",
|
||||
"links": []
|
||||
},
|
||||
"2ryzJhRDTo98gGgn9mAxR": {
|
||||
"title": "Publisher/Subscriber",
|
||||
|
||||
@@ -52,7 +52,7 @@
|
||||
]
|
||||
},
|
||||
"j69erqfosSZMDlmKcnnn0": {
|
||||
"title": "Role of Technical Writers in Organizations",
|
||||
"title": "Role of Technical Writers inOrganizations",
|
||||
"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": []
|
||||
},
|
||||
|
||||
|
Before Width: | Height: | Size: 476 KiB After Width: | Height: | Size: 807 KiB |
|
Before Width: | Height: | Size: 335 KiB After Width: | Height: | Size: 354 KiB |
|
Before Width: | Height: | Size: 492 KiB After Width: | Height: | Size: 478 KiB |
|
Before Width: | Height: | Size: 315 KiB After Width: | Height: | Size: 396 KiB |
|
Before Width: | Height: | Size: 291 KiB After Width: | Height: | Size: 175 KiB |
|
Before Width: | Height: | Size: 462 KiB After Width: | Height: | Size: 215 KiB |
|
Before Width: | Height: | Size: 293 KiB After Width: | Height: | Size: 586 KiB |
|
Before Width: | Height: | Size: 490 KiB After Width: | Height: | Size: 311 KiB |
|
Before Width: | Height: | Size: 391 KiB After Width: | Height: | Size: 210 KiB |
|
Before Width: | Height: | Size: 498 KiB After Width: | Height: | Size: 283 KiB |
|
Before Width: | Height: | Size: 376 KiB After Width: | Height: | Size: 235 KiB |
|
Before Width: | Height: | Size: 365 KiB After Width: | Height: | Size: 506 KiB |
|
Before Width: | Height: | Size: 526 KiB After Width: | Height: | Size: 342 KiB |
|
Before Width: | Height: | Size: 427 KiB After Width: | Height: | Size: 786 KiB |
|
Before Width: | Height: | Size: 776 KiB After Width: | Height: | Size: 480 KiB |
|
Before Width: | Height: | Size: 428 KiB After Width: | Height: | Size: 531 KiB |
|
Before Width: | Height: | Size: 331 KiB After Width: | Height: | Size: 586 KiB |
|
Before Width: | Height: | Size: 386 KiB After Width: | Height: | Size: 244 KiB |
|
Before Width: | Height: | Size: 398 KiB After Width: | Height: | Size: 278 KiB |
|
Before Width: | Height: | Size: 470 KiB After Width: | Height: | Size: 723 KiB |
|
Before Width: | Height: | Size: 227 KiB After Width: | Height: | Size: 131 KiB |
|
Before Width: | Height: | Size: 594 KiB After Width: | Height: | Size: 1.1 MiB |
|
Before Width: | Height: | Size: 348 KiB After Width: | Height: | Size: 213 KiB |
|
Before Width: | Height: | Size: 387 KiB After Width: | Height: | Size: 527 KiB |
|
Before Width: | Height: | Size: 218 KiB After Width: | Height: | Size: 120 KiB |
|
Before Width: | Height: | Size: 392 KiB After Width: | Height: | Size: 203 KiB |
|
Before Width: | Height: | Size: 537 KiB After Width: | Height: | Size: 716 KiB |
|
Before Width: | Height: | Size: 550 KiB After Width: | Height: | Size: 545 KiB |
|
Before Width: | Height: | Size: 240 KiB After Width: | Height: | Size: 136 KiB |
|
Before Width: | Height: | Size: 490 KiB After Width: | Height: | Size: 672 KiB |