Compare commits
29 Commits
frontend-c
...
devops-con
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8cf645237c | ||
|
|
23407cc208 | ||
|
|
d4bd2d9577 | ||
|
|
404859737d | ||
|
|
5e8929c36b | ||
|
|
33cb7b9de5 | ||
|
|
cec01c3df5 | ||
|
|
126d28f7f2 | ||
|
|
ab432f7be8 | ||
|
|
65a0a8c5bf | ||
|
|
781721cd54 | ||
|
|
f371aa602f | ||
|
|
1ef8a2746f | ||
|
|
0385a97062 | ||
|
|
a40e9bc0d3 | ||
|
|
a3cd0fa52e | ||
|
|
837f8457cd | ||
|
|
b67ca1dab6 | ||
|
|
35e74516c1 | ||
|
|
6108963b9c | ||
|
|
bcf59df1db | ||
|
|
841bc996a6 | ||
|
|
04947d5b44 | ||
|
|
6000ef92b1 | ||
|
|
11ad1a8086 | ||
|
|
2a840c4f7e | ||
|
|
48d33e87cf | ||
|
|
70dac4377e | ||
|
|
d405582f50 |
1
.astro/types.d.ts
vendored
@@ -1 +1,2 @@
|
||||
/// <reference types="astro/client" />
|
||||
/// <reference path="content.d.ts" />
|
||||
@@ -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",
|
||||
|
||||
@@ -926,21 +926,10 @@
|
||||
}
|
||||
]
|
||||
},
|
||||
"4ZbGj54WR5iuk0V8X_cpL": {
|
||||
"remote-config@4ZbGj54WR5iuk0V8X_cpL.md": {
|
||||
"title": "Remote Config",
|
||||
"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"
|
||||
}
|
||||
]
|
||||
"description": "",
|
||||
"links": []
|
||||
},
|
||||
"bVeHBEoR_4kfPsEHmVYbp": {
|
||||
"title": "Cloud Functions",
|
||||
@@ -1933,4 +1922,4 @@
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -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/",
|
||||
|
||||
@@ -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"
|
||||
}
|
||||
]
|
||||
|
||||
@@ -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",
|
||||
|
||||
@@ -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",
|
||||
|
||||
@@ -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": {
|
||||
|
||||
@@ -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",
|
||||
|
||||
@@ -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": []
|
||||
},
|
||||
|
||||
|
Before Width: | Height: | Size: 807 KiB After Width: | Height: | Size: 476 KiB |
|
Before Width: | Height: | Size: 354 KiB After Width: | Height: | Size: 335 KiB |
|
Before Width: | Height: | Size: 478 KiB After Width: | Height: | Size: 492 KiB |
|
Before Width: | Height: | Size: 396 KiB After Width: | Height: | Size: 315 KiB |
|
Before Width: | Height: | Size: 175 KiB After Width: | Height: | Size: 291 KiB |
|
Before Width: | Height: | Size: 215 KiB After Width: | Height: | Size: 462 KiB |
|
Before Width: | Height: | Size: 586 KiB After Width: | Height: | Size: 293 KiB |
|
Before Width: | Height: | Size: 311 KiB After Width: | Height: | Size: 490 KiB |
|
Before Width: | Height: | Size: 210 KiB After Width: | Height: | Size: 391 KiB |
|
Before Width: | Height: | Size: 283 KiB After Width: | Height: | Size: 498 KiB |
|
Before Width: | Height: | Size: 235 KiB After Width: | Height: | Size: 376 KiB |
|
Before Width: | Height: | Size: 506 KiB After Width: | Height: | Size: 365 KiB |
|
Before Width: | Height: | Size: 342 KiB After Width: | Height: | Size: 526 KiB |
|
Before Width: | Height: | Size: 786 KiB After Width: | Height: | Size: 427 KiB |
|
Before Width: | Height: | Size: 480 KiB After Width: | Height: | Size: 776 KiB |
|
Before Width: | Height: | Size: 531 KiB After Width: | Height: | Size: 428 KiB |
|
Before Width: | Height: | Size: 586 KiB After Width: | Height: | Size: 331 KiB |
|
Before Width: | Height: | Size: 244 KiB After Width: | Height: | Size: 386 KiB |
|
Before Width: | Height: | Size: 278 KiB After Width: | Height: | Size: 398 KiB |
|
Before Width: | Height: | Size: 723 KiB After Width: | Height: | Size: 470 KiB |
|
Before Width: | Height: | Size: 131 KiB After Width: | Height: | Size: 227 KiB |
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 594 KiB |
|
Before Width: | Height: | Size: 213 KiB After Width: | Height: | Size: 348 KiB |
|
Before Width: | Height: | Size: 527 KiB After Width: | Height: | Size: 387 KiB |
|
Before Width: | Height: | Size: 120 KiB After Width: | Height: | Size: 218 KiB |
|
Before Width: | Height: | Size: 203 KiB After Width: | Height: | Size: 392 KiB |
|
Before Width: | Height: | Size: 716 KiB After Width: | Height: | Size: 537 KiB |
|
Before Width: | Height: | Size: 545 KiB After Width: | Height: | Size: 550 KiB |
|
Before Width: | Height: | Size: 136 KiB After Width: | Height: | Size: 240 KiB |
|
Before Width: | Height: | Size: 672 KiB After Width: | Height: | Size: 490 KiB |
|
Before Width: | Height: | Size: 512 KiB After Width: | Height: | Size: 268 KiB |
|
Before Width: | Height: | Size: 244 KiB After Width: | Height: | Size: 429 KiB |