Cleanup frontend roadmap links (#7026)
* cleaning up FE links * astro topics * 52 topics completed * finish updating fe content * correct angular site link * webpack topic --------- Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>pull/7253/head
dsh
2 months ago
committed by
GitHub
parent
8e9d1df3d2
commit
f2bc4548ba
114 changed files with 278 additions and 387 deletions
@ -1,11 +1,9 @@ |
||||
# Accessibility |
||||
|
||||
Web accessibility means that websites, tools, and technologies are designed and developed in such a way that people with disabilities can use them easily. |
||||
Website accessibility is the practice of designing and developing websites that can be used by everyone, including people with disabilities. It involves implementing features and standards that make web content perceivable, operable, understandable, and robust for all users, regardless of their physical or cognitive abilities. This includes providing text alternatives for images, ensuring keyboard navigation, using sufficient color contrast, offering captions for audio content, and creating a consistent and predictable layout. Adhering to accessibility guidelines not only improves usability for people with disabilities but also enhances the overall user experience for all visitors while potentially increasing a site's reach and legal compliance. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Developing for Web Accessibility by W3C WAI](https://www.w3.org/WAI/tips/developing/) |
||||
- [@article@Accessibility Tutorial](https://www.w3schools.com/accessibility/index.php) |
||||
- [@video@Complete Playlist on Accessibility](https://youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g) |
||||
- [@article@Accessibility for Developers by Google](https://web.dev/accessibility) |
||||
- [@feed@Explore top posts about Accessibility](https://app.daily.dev/tags/accessibility?ref=roadmapsh) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# Angular |
||||
|
||||
Angular is a component based front-end development framework built on TypeScript which includes a collection of well-integrated libraries that include features like routing, forms management, client-server communication, and more. |
||||
Angular is a popular open-source web application framework developed and maintained by Google. It uses TypeScript, a statically typed superset of JavaScript, to build scalable and efficient single-page applications (SPAs). Angular follows a component-based architecture, where the user interface is composed of reusable, self-contained components. The framework provides features like two-way data binding, dependency injection, and a powerful template syntax, which simplify the development of complex web applications. Angular also includes a comprehensive set of tools for testing, routing, and state management, making it a full-fledged solution for front-end development. Its modular structure and emphasis on best practices make it particularly suitable for large-scale enterprise applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official - Getting started with Angular](https://angular.io/start) |
||||
- [@roadmap@Angular Roadmap](https://roadmap.sh/angular) |
||||
- [@official@Angular Website](https://angular.dev) |
||||
- [@feed@Explore top posts about Angular](https://app.daily.dev/tags/angular?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Apollo |
||||
|
||||
Apollo is a platform for building a unified graph, a communication layer that helps you manage the flow of data between your application clients (such as web and native apps) and your back-end services. |
||||
Apollo GraphQL is a comprehensive platform for building and managing GraphQL-based data layers in modern applications. It provides a set of open-source tools and libraries that simplify the implementation of GraphQL on both the client and server sides. On the client side, Apollo Client offers powerful caching, state management, and data fetching capabilities, integrating seamlessly with various front-end frameworks. On the server side, Apollo Server facilitates the creation of GraphQL APIs, handling queries, mutations, and subscriptions efficiently. The Apollo platform also includes developer tools for schema management, performance monitoring, and API governance. By abstracting away much of the complexity of GraphQL implementation, Apollo enables developers to build faster, more scalable, and more maintainable applications with a unified data graph. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Apollo Website](https://www.apollographql.com) |
||||
- [@official@Apollo Website](https://www.apollographql.com) |
||||
- [@article@Official Docs](https://www.apollographql.com/docs/) |
||||
- [@video@Official YouTube Channel](https://www.youtube.com/c/ApolloGraphQL/) |
||||
- [@video@GraphQL With React Tutorial - Apollo Client](https://www.youtube.com/watch?v=YyUWW04HwKY) |
||||
- [@roadmap@](https://roadmap.sh/graphql) |
||||
- [@feed@Explore top posts about Apollo](https://app.daily.dev/tags/apollo?ref=roadmapsh) |
||||
|
||||
@ -1,15 +1,9 @@ |
||||
# Astro |
||||
|
||||
Astro is an all-in-one web framework for building fast, content-focused websites. Astro combines the power of a modern component-based framework with the performance and flexibility of a static site generator. |
||||
|
||||
- Component Islands: A new web architecture for building faster websites. |
||||
- Server-first API design: Move expensive hydration off of your users’ devices. |
||||
- Zero JS, by default: No JavaScript runtime overhead to slow you down. |
||||
- Edge-ready: Deploy anywhere, even a global edge runtime like Deno or Cloudflare. |
||||
- Customizable: Tailwind, MDX, and 100+ other integrations to choose from. |
||||
- UI-agnostic: Supports React, Preact, Svelte, Vue, Solid, Lit and more. |
||||
Astro is a modern static site generator (SSG) and web framework designed for building fast, content-focused websites. It allows developers to use multiple frontend frameworks (like React, Vue, or Svelte) within the same project, automatically rendering components to static HTML at build time. Astro's unique "partial hydration" approach only sends JavaScript to the browser when necessary, resulting in significantly smaller bundle sizes and faster load times. The framework supports file-based routing, markdown content, and built-in optimizations for images and assets. Astro's component islands architecture enables developers to create interactive components while maintaining the performance benefits of static HTML, making it particularly well-suited for content-rich sites like blogs, documentation, and marketing pages. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Astro Website](https://astro.build/) |
||||
- [@article@Official Astro Docs](https://docs.astro.build/) |
||||
- [@official@Astro Website](https://astro.build/) |
||||
- [@article@What is Astro?](https://www.contentful.com/blog/what-is-astro/) |
||||
- [@course@Astro Web Framework Crash Course](https://www.youtube.com/watch?v=e-hTm5VmofI) |
||||
|
||||
@ -1,15 +1,9 @@ |
||||
# Astro |
||||
|
||||
Astro is an all-in-one web framework for building fast, content-focused websites. Astro combines the power of a modern component-based framework with the performance and flexibility of a static site generator. |
||||
|
||||
- Component Islands: A new web architecture for building faster websites. |
||||
- Server-first API design: Move expensive hydration off of your users’ devices. |
||||
- Zero JS, by default: No JavaScript runtime overhead to slow you down. |
||||
- Edge-ready: Deploy anywhere, even a global edge runtime like Deno or Cloudflare. |
||||
- Customizable: Tailwind, MDX, and 100+ other integrations to choose from. |
||||
- UI-agnostic: Supports React, Preact, Svelte, Vue, Solid, Lit and more. |
||||
Astro is a modern static site generator (SSG) and web framework designed for building fast, content-focused websites. It allows developers to use multiple frontend frameworks (like React, Vue, or Svelte) within the same project, automatically rendering components to static HTML at build time. Astro's unique "partial hydration" approach only sends JavaScript to the browser when necessary, resulting in significantly smaller bundle sizes and faster load times. The framework supports file-based routing, markdown content, and built-in optimizations for images and assets. Astro's component islands architecture enables developers to create interactive components while maintaining the performance benefits of static HTML, making it particularly well-suited for content-rich sites like blogs, documentation, and marketing pages. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Astro Website](https://astro.build/) |
||||
- [@article@Official Astro Docs](https://docs.astro.build/) |
||||
- [@official@Astro Website](https://astro.build/) |
||||
- [@article@What is Astro?](https://www.contentful.com/blog/what-is-astro/) |
||||
- [@course@Astro Web Framework Crash Course](https://www.youtube.com/watch?v=e-hTm5VmofI) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# Build Tools |
||||
|
||||
Task runners automatically execute commands and carry out processes behind the scenes. This helps automate your workflow by performing mundane, repetitive tasks that you would otherwise waste an egregious amount of time repeating yourself. |
||||
|
||||
Common usages of task runners include numerous development tasks such as: spinning up development servers, compiling code (ex. SCSS to CSS), running linters, serving files up from a local port on your computer, and many more! |
||||
Build tools are software utilities designed to automate the process of creating executable applications from source code. They handle tasks such as compiling, linking, minifying, and bundling code, as well as running tests and managing dependencies. Common build tools include Make, Gradle, Maven, Webpack, and Gulp. These tools streamline development workflows by reducing manual steps, ensuring consistency across different environments, and optimizing output for production. They often support features like incremental builds, parallel processing, and custom task definitions. Build tools are crucial in modern software development, especially for large-scale projects, as they improve efficiency, reduce errors, and facilitate continuous integration and deployment processes. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@webpack is a static module bundler for modern JavaScript applications](https://webpack.js.org/) |
||||
- [@article@Vite Next Generation Frontend Tooling](https://vitejs.dev) |
||||
- [@article@Parcel is a zero configuration build tool for the web](https://parceljs.org/) |
||||
- [@official@Webpack Website](https://webpack.js.org/) |
||||
- [@official@Vite Website](https://vitejs.dev) |
||||
- [@official@Parcel Website](https://parceljs.org/) |
||||
- [@feed@Explore top posts about Tools](https://app.daily.dev/tags/tools?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,9 @@ |
||||
# CORS |
||||
|
||||
Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. |
||||
Cross-Origin Resource Sharing (CORS) is a security mechanism implemented by web browsers to control access to resources (like APIs or fonts) on a web page from a different domain than the one serving the web page. It extends and adds flexibility to the Same-Origin Policy, allowing servers to specify who can access their resources. CORS works through a system of HTTP headers, where browsers send a preflight request to the server hosting the cross-origin resource, and the server responds with headers indicating whether the actual request is allowed. This mechanism helps prevent unauthorized access to sensitive data while enabling legitimate cross-origin requests. CORS is crucial for modern web applications that often integrate services and resources from multiple domains, balancing security needs with the functionality requirements of complex, distributed web systems. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) |
||||
- [@video@CORS in 100 Seconds](https://www.youtube.com/watch?v=4KHiSt0oLJ0) |
||||
- [@video@CORS in 6 minutes](https://www.youtube.com/watch?v=PNtFSVU-YTI) |
||||
- [@article@Understanding CORS](https://rbika.com/blog/understanding-cors) |
||||
|
||||
@ -1,11 +1,8 @@ |
||||
# Credentials API |
||||
|
||||
The Credential Management API is a web API that allows web developers to integrate password-based and federated login flows into their applications. It provides a standardized, browser-based interface for storing and retrieving user credentials, such as username and password combinations and OAuth tokens. |
||||
|
||||
To use the Credential Management API, a web page must first create a Credential object and specify the credentials that the user wishes to store. The page can then use the navigator.credentials object to store and retrieve the user's credentials. The API provides several methods for storing and retrieving credentials, as well as for prompting the user to sign in or sign up. |
||||
|
||||
The Credential Management API is supported by most modern web browsers and is designed to improve the security and usability of login flows by allowing the user to store and reuse their credentials across multiple sites and devices. |
||||
The Credential Management API is a web standard that allows websites to interact with the browser's credential manager to store, retrieve, and manage user credentials. It provides a programmatic interface for seamless and secure user authentication, enabling features like automatic sign-in and one-tap sign-up. The API supports various credential types, including passwords, federated identities, and public key credentials. By leveraging this API, developers can improve user experience by reducing login friction, implementing smoother account switching, and enhancing overall security. It works in conjunction with password managers and platform authenticators, helping to streamline authentication processes across devices and browsers while adhering to modern security practices. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Credential Management API - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Credential_Management_API) |
||||
- [@article@The Credential Management API](https://web.dev/articles/security-credential-management) |
||||
|
||||
@ -1,11 +1,9 @@ |
||||
# CSS Architecture |
||||
|
||||
CSS is notoriously difficult to manage in large, complex, rapidly-iterated systems. There are different ways of writing CSS that allows in writing more maintainable CSS. |
||||
CSS architecture refers to the methodologies and organizational strategies used to structure and maintain CSS code in large-scale web projects. It focuses on creating scalable, maintainable, and modular stylesheets to manage the growing complexity of web applications. Key concepts include naming conventions (like BEM or SMACSS), component-based design, separation of concerns, and the use of preprocessors (such as Sass or Less). CSS architecture often employs techniques like CSS modules, utility classes, or CSS-in-JS solutions to improve code reusability and reduce specificity conflicts. The goal is to create a systematic approach to styling that enhances collaboration among developers, reduces code duplication, and facilitates easier updates and maintenance of the visual design across an entire application or website. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@A Look at Some CSS Methodologies](https://www.webfx.com/blog/web-design/css-methodologies/) |
||||
- [@article@BEM Official Website](https://en.bem.info) |
||||
- [@article@OOCSS Official Website](http://oocss.org/) |
||||
- [@article@SMACSS Official Website](http://smacss.com/) |
||||
- [@article@How to Organize Your CSS with a Modular Architecture](https://snipcart.com/blog/organize-css-modular-architecture) |
||||
- [@video@Modern CSS For Dynamic Component-Based Architecture](https://www.youtube.com/watch?v=Y50iqMlrqU8) |
||||
- [@feed@Explore top posts about Architecture](https://app.daily.dev/tags/architecture?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# CSS |
||||
|
||||
CSS or Cascading Style Sheets is the language used to style the frontend of any website. CSS is a cornerstone technology of the World Wide Web, alongside HTML and JavaScript. |
||||
CSS (Cascading Style Sheets) is a styling language used to describe the presentation of a document written in HTML or XML. It defines how elements should be displayed on screen, on paper, or in other media. CSS separates the design from the content, allowing for greater flexibility and control over the layout, colors, and fonts of web pages. It uses a system of selectors to target HTML elements and apply styles to them. CSS supports responsive design through media queries, enabling the creation of layouts that adapt to different screen sizes and devices. The cascade, inheritance, and specificity are key concepts in CSS that determine how styles are applied when multiple rules target the same element. Modern CSS includes features like Flexbox and Grid for advanced layout control, animations, and transitions for creating dynamic user interfaces. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@video@CSS Complete Course](https://youtu.be/n4R2E7O-Ngo) |
||||
- [@video@HTML and CSS Tutorial](https://www.youtube.com/watch?v=D-h8L5hgW-w) |
||||
- [@article@W3Schools — Learn CSS](https://www.w3schools.com/css/) |
||||
- [@course@CSS Complete Course](https://youtu.be/n4R2E7O-Ngo) |
||||
- [@course@HTML & CSS Full Course - Beginner to Pro](https://www.youtube.com/watch?v=G3e-cpL7ofc) |
||||
- [@article@Web.dev by Google — Learn CSS](https://web.dev/learn/css/) |
||||
- [@feed@Explore top posts about CSS](https://app.daily.dev/tags/css?ref=roadmapsh) |
||||
|
||||
@ -1,8 +1,3 @@ |
||||
# Desktop Applications in JavaScript |
||||
|
||||
A while back, developing a desktop app using JavaScript was impossible. But now JavaScript developers can create desktop applications using their knowledge for web development. Here is the list of options to create desktop applications in JavaScript. |
||||
|
||||
- [@article@Electron](https://www.electronjs.org/) |
||||
- [@article@NodeGUI](https://docs.nodegui.org/) |
||||
- [@article@NW.js](https://nwjs.io/) |
||||
- [@article@Meteor](https://www.meteor.com/) |
||||
Desktop applications applications typically use frameworks like Electron, NW.js (Node-WebKit), or Tauri, which combine a JavaScript runtime with a native GUI toolkit. This approach allows developers to use their web development skills to create cross-platform desktop apps. Electron, developed by GitHub, is particularly popular, powering applications like Visual Studio Code, Atom, and Discord. These frameworks provide APIs to access native system features, enabling JavaScript to interact with the file system, system tray, and other OS-specific functionalities. While offering rapid development and cross-platform compatibility, JavaScript desktop apps can face challenges in terms of performance and resource usage compared to traditional native applications. However, they benefit from the vast ecosystem of JavaScript libraries and tools, making them an attractive option for many developers and businesses. |
||||
|
||||
@ -1,11 +1,8 @@ |
||||
# Device Orientation API |
||||
|
||||
The Device Orientation API is a web API that provides access to the device's orientation and motion data, such as its pitch, roll, and yaw. It allows web developers to build applications that can respond to the device's orientation and motion, such as augmented reality and motion-controlled games. |
||||
|
||||
To use the Device Orientation API, a web page must first request permission from the user to access the device's orientation data. If permission is granted, the page can then use the DeviceOrientationEvent object to access the device's orientation data and respond to changes in orientation. The API provides several properties for accessing the device's orientation and motion data, as well as events for detecting changes in orientation. |
||||
|
||||
The Device Orientation API is supported by most modern web browsers and is often used in conjunction with other APIs, such as the Geolocation API, to build location-based applications. |
||||
The Device Orientation API is a web API that provides access to the device's orientation and motion data, such as its pitch, roll, and yaw. It allows web developers to build applications that can respond to the device's orientation and motion, such as augmented reality and motion-controlled games. To use the Device Orientation API, a web page must first request permission from the user to access the device's orientation data. If permission is granted, the page can then use the DeviceOrientationEvent object to access the device's orientation data and respond to changes in orientation. The API provides several properties for accessing the device's orientation and motion data, as well as events for detecting changes in orientation. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Device Orientation API - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Device_orientation_events) |
||||
- [@video@Detect the device orientation with JS](https://www.youtube.com/watch?v=fMDuFoqSQfw) |
||||
|
||||
@ -1,10 +1,10 @@ |
||||
# Electron |
||||
|
||||
Electron allows you to build cross-platform desktop applications with HTML, CSS, and Javascript/Typescript. It uses Chromium and Node.js, so essentially it is a "Browser" like application that is compatible with Mac, Windows, and Linux. |
||||
Electron is an open-source framework developed by GitHub that enables developers to build cross-platform desktop applications using web technologies. It combines the Chromium rendering engine with the Node.js runtime, allowing applications to be written in HTML, CSS, and JavaScript. Electron provides APIs to access native operating system functions, bridging the gap between web and desktop development. It's widely used for creating popular applications like Visual Studio Code, Atom, and Discord. Electron apps benefit from rapid development cycles, cross-platform compatibility, and access to a vast ecosystem of web technologies and Node.js modules. However, they can face challenges with resource usage and performance compared to native applications. Despite these trade-offs, Electron remains a popular choice for developers seeking to leverage web skills for desktop app development. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Electron Website](https://www.electronjs.org/) |
||||
- [@article@Electron Docs](https://www.electronjs.org/docs/latest/) |
||||
- [@official@Electron Website](https://www.electronjs.org/) |
||||
- [@official@Electron Docs](https://www.electronjs.org/docs/latest/) |
||||
- [@video@Create a Desktop App With JavaScript & Electron](https://www.youtube.com/watch?v=ML743nrkMHw) |
||||
- [@feed@Explore top posts about Electron](https://app.daily.dev/tags/electron?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# esbuild |
||||
|
||||
Our current build tools for the web are 10-100x slower than they could be. The main goal of the esbuild bundler project is to bring about a new era of build tool performance, and create an easy-to-use modern bundler along the way. |
||||
esbuild is a high-performance JavaScript bundler and minifier designed for speed and efficiency. Created by Evan Wallace, it's written in Go and compiles to native code, making it significantly faster than traditional JavaScript-based build tools. esbuild supports modern JavaScript features, TypeScript, and JSX out of the box, with near-instant bundling times even for large projects. It offers a simple API and command-line interface, making it easy to integrate into existing build pipelines. While primarily focused on speed, esbuild also provides basic code splitting, tree shaking, and source map generation. Its extreme performance makes it particularly suitable for development environments and as a foundation for other build tools, though it may lack some advanced features found in more mature bundlers. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Esbuild Official Website](https://esbuild.github.io/) |
||||
- [@article@Esbuild Documentation](https://esbuild.github.io/api/) |
||||
- [@video@Why are People Obsessed with esbuild?](https://www.youtube.com/watch?v=9XS_RA6zyyU) |
||||
- [@official@Esbuild Official Website](https://esbuild.github.io/) |
||||
- [@course@Let's Learn esbuild! (with Sunil Pai) — Learn With Jason](https://www.youtube.com/watch?v=KLdF1yu_bmI) |
||||
- [@video@What Is ESBuild?](https://www.youtube.com/watch?v=ZY8Vu8cbWF0) |
||||
- [@feed@Explore top posts about Web Development](https://app.daily.dev/tags/webdev?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,10 @@ |
||||
# ESLint |
||||
|
||||
With ESLint you can impose the coding standard using a certain set of standalone rules. |
||||
ESLint is a popular open-source static code analysis tool for identifying and fixing problems in JavaScript code. It enforces coding standards, detects potential errors, and promotes consistent coding practices across projects. ESLint is highly configurable, allowing developers to define custom rules or use preset configurations. It supports modern JavaScript features, JSX, and TypeScript through plugins. ESLint can be integrated into development workflows through IDE extensions, build processes, or git hooks, providing real-time feedback to developers. Its ability to automatically fix many issues it detects makes it a valuable tool for maintaining code quality and consistency, especially in large teams or projects. ESLint's extensibility and wide adoption in the JavaScript ecosystem have made it a standard tool in modern JavaScript development. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@ESLint Official Website](https://eslint.org/) |
||||
- [@article@Introduction to ESLint](https://dev.to/shivambmgupta/eslint-what-why-when-how-5f1d) |
||||
- [@article@What is ESLint and How to Use ESLint to Detect and Fix Code for JavaScript Projects](https://2coffee.dev/en/articles/what-is-eslint-and-how-to-use-eslint-to-detect-fix-code-for-javascript-projects) |
||||
- [@video@ESLint Quickstart - find errors automatically](https://www.youtube.com/watch?v=qhuFviJn-es) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,13 +1,12 @@ |
||||
# Flutter |
||||
|
||||
Flutter is a free and open-source multi-platform UI framework created by Google and released in May 2017. In a few words, it allows you to create a native mobile application with only one codebase. This means that you can use one programming language and one codebase to create three different apps (for iOS, Android and Desktop). |
||||
Flutter is an open-source UI software development kit created by Google for building natively compiled, multi-platform applications from a single codebase. It uses the Dart programming language and provides a rich set of pre-designed widgets for creating responsive and visually appealing user interfaces. Flutter's architecture allows for fast development with hot reload, enabling developers to see changes instantly. It supports iOS, Android, web, and desktop platforms, offering true cross-platform development. Flutter uses a custom rendering engine, Skia, to draw UI components, ensuring consistent appearance across devices. While known for mobile app development, Flutter's expanding ecosystem and performance improvements have increased its adoption for web and desktop applications as well. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Visit Dedicated Flutter Roadmap](https://roadmap.sh/flutter) |
||||
- [@official@Flutter Website](https://flutter.dev) |
||||
- [@official@Flutter for Desktop](https://flutter.dev/multi-platform/desktop) |
||||
- [@video@Flutter Tutorial for Beginners](https://www.youtube.com/watch?v=1ukSR1GRtMU\&list=PL4cUxeGkcC9jLYyp2Aoh6hcWuxFDX6PBJ) |
||||
- [@article@Learn Dart Programming](https://www.tutorialspoint.com/dart_programming/index.htm) |
||||
- [@course@Flutter course for beginners](https://www.youtube.com/watch?v=VPvVD8t02U8) |
||||
- [@article@12 Ways Flutter Streamlines App Development](https://thenewstack.io/12-ways-flutter-streamlines-app-development/) |
||||
- [@feed@Explore top posts about Flutter](https://app.daily.dev/tags/flutter?ref=roadmapsh) |
||||
|
||||
@ -1,22 +1,12 @@ |
||||
# Flutter |
||||
|
||||
Flutter is a free and open-source mobile UI framework created by Google and released in May 2017. In a few words, it allows you to create a native mobile application with only one codebase. This means that you can use one programming language and one codebase to create two different apps (for iOS and Android). |
||||
|
||||
Flutter consists of two important parts: |
||||
|
||||
- An SDK (Software Development Kit): A collection of tools that are going to help you develop your applications. This includes tools to compile your code into native machine code (code for iOS and Android). |
||||
- A Framework (UI Library based on widgets): A collection of reusable UI elements (buttons, text inputs, sliders, and so on) that you can personalize for your own needs. |
||||
To develop with Flutter, you will use a programming language called Dart. The language was created by Google in October 2011, but it has improved a lot over these past years. |
||||
|
||||
Dart focuses on front-end development, and you can use it to create mobile and web applications. |
||||
|
||||
If you know a bit of programming, Dart is a typed object programming language. You can compare Dart's syntax to JavaScript. |
||||
Flutter is an open-source UI software development kit created by Google for building natively compiled, multi-platform applications from a single codebase. It uses the Dart programming language and provides a rich set of pre-designed widgets for creating responsive and visually appealing user interfaces. Flutter's architecture allows for fast development with hot reload, enabling developers to see changes instantly. It supports iOS, Android, web, and desktop platforms, offering true cross-platform development. Flutter uses a custom rendering engine, Skia, to draw UI components, ensuring consistent appearance across devices. While known for mobile app development, Flutter's expanding ecosystem and performance improvements have increased its adoption for web and desktop applications as well. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Visit Dedicated Flutter Roadmap](https://roadmap.sh/flutter) |
||||
- [@official@Flutter Website](https://flutter.dev) |
||||
- [@video@Flutter Tutorial for Beginners](https://www.youtube.com/watch?v=1ukSR1GRtMU\&list=PL4cUxeGkcC9jLYyp2Aoh6hcWuxFDX6PBJ) |
||||
- [@article@Learn Dart Programming](https://www.tutorialspoint.com/dart_programming/index.htm) |
||||
- [@official@Flutter for Desktop](https://flutter.dev/multi-platform/desktop) |
||||
- [@course@Flutter course for beginners](https://www.youtube.com/watch?v=VPvVD8t02U8) |
||||
- [@article@12 Ways Flutter Streamlines App Development](https://thenewstack.io/12-ways-flutter-streamlines-app-development/) |
||||
- [@feed@Explore top posts about Flutter](https://app.daily.dev/tags/flutter?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,11 @@ |
||||
# Git |
||||
|
||||
[Git](https://git-scm.com/) is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. |
||||
Git is a distributed version control system designed to handle projects of any size with speed and efficiency. Created by Linus Torvalds in 2005, Git tracks changes in source code during software development, allowing multiple developers to work together on non-linear development. It provides strong support for branching, merging, and distributed development workflows. Git maintains a complete history of all changes, enabling easy rollbacks and comparisons between versions. Its distributed nature means each developer has a full copy of the repository, allowing for offline work and backup. Git's speed, flexibility, and robust branching and merging capabilities have made it the most widely used version control system in software development, particularly for open-source projects. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Learn Git & GitHub](/git-github) |
||||
- [@video@Git & GitHub Crash Course For Beginners](https://www.youtube.com/watch?v=SWYqp7iY_Tc) |
||||
- [@article@Learn Git with Tutorials, News and Tips - Atlassian](https://www.atlassian.com/git) |
||||
- [@article@Git Cheat Sheet](https://cs.fyi/guide/git-cheatsheet) |
||||
- [@article@Tutorial: Git for Absolutely Everyone](https://thenewstack.io/tutorial-git-for-absolutely-everyone/) |
||||
- [@feed@Explore top posts about Git](https://app.daily.dev/tags/git?ref=roadmapsh) |
||||
|
||||
@ -1,13 +1,11 @@ |
||||
# GitHub |
||||
|
||||
[GitHub](https://github.com) is a provider of internet hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features. |
||||
GitHub has become a central hub for open-source projects and is widely used by developers, companies, and organizations for both private and public repositories. It was acquired by Microsoft in 2018 but continues to operate as a relatively independent entity. GitHub's popularity has made it an essential tool in modern software development workflows and a key platform for showcasing coding projects and contributing to open-source software. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@GitHub: Quickstart](https://docs.github.com/en/get-started/quickstart/hello-world) |
||||
- [@article@Learn GitHub by doing](https://skills.github.com/) |
||||
- [@roadmap@Learn Git & GitHub](/git-github) |
||||
- [@official@GitHub: Quickstart](https://docs.github.com/en/get-started/quickstart/hello-world) |
||||
- [@official@Learn GitHub by doing](https://skills.github.com/) |
||||
- [@video@What is GitHub?](https://www.youtube.com/watch?v=w3jLJU7DT5E) |
||||
- [@video@Git vs. GitHub: Whats the difference?](https://www.youtube.com/watch?v=wpISo9TNjfU) |
||||
- [@video@Git and GitHub for Beginners](https://www.youtube.com/watch?v=RGOj5yH7evk) |
||||
- [@video@Git and GitHub - CS50 Beyond 2019](https://www.youtube.com/watch?v=eulnSXkhE7I) |
||||
- [@feed@Explore top posts about GitHub](https://app.daily.dev/tags/github?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,10 @@ |
||||
# GitLab |
||||
|
||||
[GitLab](https://gitlab.com) is a provider of internet hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features. |
||||
GitLab is a web-based DevOps platform that provides a complete solution for the software development lifecycle. GitLab emphasizes an all-in-one approach, integrating various development tools into a single platform. It's available as both a cloud-hosted service and a self-hosted solution, giving organizations flexibility in deployment. GitLab's focus on DevOps practices and its comprehensive feature set make it popular among enterprises and teams seeking a unified platform for their entire development workflow. While similar to GitHub in many respects, GitLab's integrated CI/CD capabilities and self-hosting options are often cited as key differentiators. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@GitLab Documentation](https://docs.gitlab.com/) |
||||
- [@opensource@GitLab Website](https://gitlab.com/) |
||||
- [@official@GitLab Documentation](https://docs.gitlab.com/) |
||||
- [@official@GitLab Website](https://gitlab.com/) |
||||
- [@article@Development: Connect git to GitLab for Small Projects](https://thenewstack.io/development-connect-git-to-gitlab-for-small-projects/) |
||||
- [@feed@Explore top posts about GitLab](https://app.daily.dev/tags/gitlab?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Internet |
||||
# How Does The Internet Work |
||||
|
||||
The Internet is a global network of computers connected to each other which communicate through a standardized set of protocols. |
||||
The Internet works through a global network of interconnected computers and servers, communicating via standardized protocols. Data is broken into packets and routed through various network nodes using the Internet Protocol (IP). These packets travel across different physical infrastructures, including fiber optic cables, satellites, and wireless networks. The Transmission Control Protocol (TCP) ensures reliable delivery and reassembly of packets at their destination. Domain Name System (DNS) servers translate human-readable website names into IP addresses. When you access a website, your device sends a request to the appropriate server, which responds with the requested data. This process, facilitated by routers, switches, and other networking equipment, enables the seamless exchange of information across vast distances, forming the backbone of our digital communications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@How does the Internet Work?](https://cs.fyi/guide/how-does-internet-work) |
||||
- [@article@How Does the Internet Work? MDN Docs](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/How_does_the_Internet_work) |
||||
- [@roadmap.sh@Introduction to Internet](/guides/what-is-internet) |
||||
- [@video@How does the Internet work?](https://www.youtube.com/watch?v=TNQsmPf24go) |
||||
- [@video@How the Internet Works in 5 Minutes](https://www.youtube.com/watch?v=7_LPdttKXPc) |
||||
|
||||
@ -1,13 +1,3 @@ |
||||
# Internet |
||||
|
||||
The Internet is a global network of computers connected to each other which communicate through a standardized set of protocols. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@How does the Internet Work?](https://cs.fyi/guide/how-does-internet-work) |
||||
- [@article@The Internet Explained](https://www.vox.com/2014/6/16/18076282/the-internet) |
||||
- [@article@How Does the Internet Work?](http://web.stanford.edu/class/msande91si/www-spr04/readings/week1/InternetWhitepaper.htm) |
||||
- [@article@Introduction to Internet](/guides/what-is-internet) |
||||
- [@website@Learn How the Web Works](https://internetfundamentals.com) |
||||
- [@video@How does the Internet work?](https://www.youtube.com/watch?v=x3c1ih2NJEg) |
||||
- [@video@How the Internet Works in 5 Minutes](https://www.youtube.com/watch?v=7_LPdttKXPc) |
||||
The Internet is a global network of interconnected computer networks that use the Internet Protocol Suite (TCP/IP) to communicate. It enables the exchange of data, information, and services across the world, connecting billions of devices and users. The Internet has revolutionized communication, commerce, education, and entertainment, becoming an integral part of modern society. It supports various applications and services, from web browsing and instant messaging to streaming media and online gaming. While offering unprecedented access to information and connectivity, the Internet also raises concerns about privacy, security, and digital divide issues. |
||||
|
||||
@ -1,10 +1,10 @@ |
||||
# Ionic |
||||
|
||||
Ionic framework is an open-source UI toolkit for building performant, high-quality mobile apps, desktop apps, and progressive web apps using web technologies such as HTML, CSS, and JavaScript. |
||||
Ionic is an open-source UI toolkit for building high-quality, cross-platform mobile and desktop applications using web technologies (HTML, CSS, and JavaScript). It leverages popular web frameworks like Angular, React, or Vue.js for application logic, while providing a rich set of pre-built UI components and native device functionalities. Ionic uses Cordova or Capacitor to wrap web apps for native deployment, allowing developers to create hybrid apps that can access device features through plugins. The framework emphasizes performance and native look-and-feel, offering adaptive styling for different platforms. With its focus on web standards and cross-platform compatibility, Ionic enables developers to maintain a single codebase for multiple platforms, making it a popular choice for rapid mobile app development. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Official Website](https://ionicframework.com/) |
||||
- [@article@Official Getting Started to Ionic framework](https://ionicframework.com/docs/) |
||||
- [@video@Ionic Framework 4 - Full Tutorial](https://www.youtube.com/watch?v=AvbuIRg8_Jg) |
||||
- [@official@Official Website](https://ionicframework.com/) |
||||
- [@article@Ionic 8 Announcment](https://ionic.io/blog/ionic-8-is-here) |
||||
- [@opensource@ionic-team/ionic-framework](https://github.com/ionic-team/ionic-framework) |
||||
- [@feed@Explore top posts about Ionic](https://app.daily.dev/tags/ionic?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# JavaScript |
||||
|
||||
JavaScript allows you to add interactivity to your pages. Common examples that you may have seen on the websites are sliders, click interactions, popups and so on. |
||||
JavaScript is a high-level, interpreted programming language that is a core technology of the World Wide Web. It allows for dynamic, client-side scripting in web browsers, enabling interactive web pages and user interfaces. JavaScript supports object-oriented, imperative, and functional programming styles. It's also used server-side through Node.js, for desktop application development with frameworks like Electron, and in various other contexts. The language features dynamic typing, first-class functions, and prototype-based object-orientation. JavaScript's ubiquity in web development, coupled with its versatility and continuous evolution through ECMAScript standards, has made it one of the most popular programming languages in use today. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Visit Dedicated JavaScript Roadmap](https://roadmap.sh/javascript) |
||||
- [@article@The Modern JavaScript Tutorial](https://javascript.info/) |
||||
- [@video@JavaScript Crash Course for Beginners](https://youtu.be/hdI2bqOjy3c?t=2) |
||||
- [@article@Build 30 Javascript projects in 30 days](https://javascript30.com/) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,9 @@ |
||||
# Jest |
||||
|
||||
Jest is a delightful JavaScript Testing Framework with a focus on simplicity. |
||||
It works with projects using: Babel, TypeScript, Node, React, Angular, Vue and more! |
||||
Jest is a popular JavaScript testing framework developed by Facebook. It provides a comprehensive solution for unit testing JavaScript code, with a focus on simplicity and minimal configuration. Jest offers features such as automatic mocking, code coverage reporting, and snapshot testing. It supports testing of both synchronous and asynchronous code, and can be used with various JavaScript frameworks and libraries, including React, Angular, and Vue. Jest's built-in assertion library and test runner make it easy to write and execute tests quickly. Its ability to run tests in parallel and its intelligent test-watching mode contribute to fast test execution, making it a preferred choice for many developers and organizations in the JavaScript ecosystem. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Jest Website](https://jestjs.io/) |
||||
- [@official@Jest Website](https://jestjs.io/) |
||||
- [@video@JavaScript Testing With Jest](https://youtu.be/IPiUDhwnZxA?si=2_lE2bDo2fRuo2CU) |
||||
- [@feed@Explore top posts about Jest](https://app.daily.dev/tags/jest?ref=roadmapsh) |
||||
|
||||
@ -1,9 +1,8 @@ |
||||
# Location API |
||||
|
||||
The Geolocation API is a web API that provides access to the device's location data, such as latitude and longitude. It allows web developers to build location-based applications, such as mapping and location sharing, by using the device's GPS, Wi-Fi, and other sensors to determine the user's location. |
||||
|
||||
To use the Geolocation API, a web page must first request permission from the user to access their location. If permission is granted, the page can then use the `navigator.geolocation` object to access the device's location data. The API provides several methods for getting the user's current location, watching for location changes, and calculating distances between two locations. |
||||
The Geolocation API is a web API that provides access to the device's location data, such as latitude and longitude. It allows web developers to build location-based applications, such as mapping and location sharing, by using the device's GPS, Wi-Fi, and other sensors to determine the user's location. To use the Geolocation API, a web page must first request permission from the user to access their location. If permission is granted, the page can then use the `navigator.geolocation` object to access the device's location data. The API provides several methods for getting the user's current location, watching for location changes, and calculating distances between two locations. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Geolocation API - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API) |
||||
- [@article@Geolocation API overview](https://developers.google.com/maps/documentation/geolocation/overview) |
||||
|
||||
@ -1,15 +1,20 @@ |
||||
# Making layouts |
||||
|
||||
Float, grid, flexbox, positioning, display and box model are some of the key topics that are used for making layouts. Use the resources below to learn about these topics: |
||||
Making layouts in web design involves organizing content and visual elements on a page to create an effective and aesthetically pleasing user interface. Modern layout techniques primarily use CSS, with key approaches including: |
||||
|
||||
1. Flexbox for one-dimensional layouts (rows or columns) |
||||
2. CSS Grid for two-dimensional layouts |
||||
3. Responsive design principles for adaptability across devices |
||||
4. CSS frameworks like Bootstrap or Tailwind for rapid development |
||||
5. Custom CSS properties (variables) for consistent styling |
||||
6. Media queries for device-specific adjustments |
||||
7. CSS positioning and float for specific element placement |
||||
|
||||
These tools allow designers to create complex, responsive layouts that maintain consistency and usability across various screen sizes and devices. Effective layouts consider visual hierarchy, user flow, accessibility, and content prioritization to enhance the overall user experience and achieve design goals. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Learn and Practice Flexbox](https://flexboxfroggy.com/) |
||||
- [@article@Game for learning CSS Grid](https://cssgridgarden.com/) |
||||
- [@article@All about Floats](https://css-tricks.com/all-about-floats/) |
||||
- [@article@Positioning Types: How Do They Differ?](https://css-tricks.com/absolute-relative-fixed-positioining-how-do-they-differ/) |
||||
- [@article@The Box Model](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/The_box_model) |
||||
- [@article@A Complete Guide to Flexbox](https://css-tricks.com/snippets/css/a-guide-to-flexbox) |
||||
- [@article@A Complete Guide to Grid](https://css-tricks.com/snippets/css/complete-guide-grid) |
||||
- [@article@Learn CSS Grid - Course](https://cssgrid.io/) |
||||
- [@article@Get on the Grid at Last with the CSS Grid Layout Module](https://thenewstack.io/get-grid-last-css-grid-template-markup/) |
||||
|
||||
@ -1,9 +1,9 @@ |
||||
# Mobile applications |
||||
|
||||
A while back, developing a mobile app using JavaScript was impossible. But now JavaScript developers can create mobile applications using their knowledge for web development. Here is the list of options to create mobile applications in JavaScript. |
||||
Mobile applications are software programs designed to run on mobile devices such as smartphones and tablets. They are typically distributed through app stores like Google Play or Apple's App Store. Mobile apps can be native (built specifically for one platform using languages like Swift for iOS or Kotlin for Android), hybrid (web technologies wrapped in a native container), or cross-platform (using frameworks like React Native or Flutter). These apps leverage device-specific features such as GPS, cameras, and sensors to provide rich, interactive experiences. They cover a wide range of functions from productivity and entertainment to social networking and e-commerce. Mobile app development considers factors like user interface design, performance optimization, offline functionality, and security to ensure a smooth user experience across various devices and operating systems. |
||||
|
||||
- [@article@React Native](https://reactnative.dev/) |
||||
- [@article@Flutter](https://flutter.dev) |
||||
- [@article@Ionic](https://ionicframework.com) |
||||
- [@article@NativeScript](https://nativescript.org/) |
||||
- [@official@React Native](https://reactnative.dev/) |
||||
- [@official@Flutter](https://flutter.dev) |
||||
- [@official@Ionic](https://ionicframework.com) |
||||
- [@official@NativeScript](https://nativescript.org/) |
||||
- [@feed@Explore top posts about Mobile Development](https://app.daily.dev/tags/mobile?ref=roadmapsh) |
||||
|
||||
@ -1,9 +1,10 @@ |
||||
# Module Bundlers |
||||
|
||||
A module bundler is a tool that takes pieces of JavaScript and their dependencies and bundles them into a single file, usually for use in the browser. You may have used tools such as Browserify, Webpack, Rollup or one of many others. |
||||
|
||||
It usually starts with an entry file, and from there it bundles up all of the code needed for that entry file. |
||||
Module bundlers are development tools that combine multiple JavaScript files and their dependencies into a single file, optimized for web browsers. They resolve and manage dependencies, transform and optimize code, and often support features like code splitting and lazy loading. Popular module bundlers include Webpack, Rollup, and Parcel. These tools address challenges in managing complex JavaScript applications by organizing code into modules, eliminating global scope pollution, and improving load times. Bundlers typically support various file formats, enable the use of modern JavaScript features through transpilation, and integrate with task runners and other build tools. Their primary goal is to streamline the development process and enhance application performance in production environments. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@The Complete JavaScript Module Bundlers Guide](https://snipcart.com/blog/javascript-module-bundler) |
||||
- [@official@Rollup Bundler](https://rollupjs.org/) |
||||
- [@official@Webpack Website](https://webpack.js.org/) |
||||
- [@video@Module Bundlers Explained](https://www.youtube.com/watch?v=5IG4UmULyoA) |
||||
|
||||
@ -1,13 +1,9 @@ |
||||
# Next.js |
||||
|
||||
Next.js is an open-source development framework built on top of Node.js |
||||
enabling React based web applications functionalities such as server-side |
||||
rendering and generating static websites. |
||||
Next.js is a React-based open-source framework for building server-side rendered and statically generated web applications. It provides features like automatic code splitting, optimized performance, and simplified routing out of the box. Next.js supports both static site generation (SSG) and server-side rendering (SSR), allowing developers to choose the most appropriate rendering method for each page. The framework offers built-in CSS support, API routes for backend functionality, and easy deployment options. Next.js is known for its developer-friendly experience, with features like hot module replacement and automatic prefetching. Its ability to create hybrid apps that combine static and server-rendered pages makes it popular for building scalable, SEO-friendly web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://nextjs.org/) |
||||
- [@official@Official Docs for Getting Started](https://nextjs.org/docs/getting-started) |
||||
- [@article@Mastering Next.js](https://masteringnextjs.com/) |
||||
- [@video@Next.js for Beginners - Full Course at freeCodeCamp YouTube Channel](https://youtu.be/1WmNXEVia8I) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,9 @@ |
||||
# Next.js |
||||
|
||||
Next.js is an open-source development framework built on top of Node.js enabling React based web applications functionalities such as server-side rendering and generating static websites. |
||||
Next.js is a React-based open-source framework for building server-side rendered and statically generated web applications. It provides features like automatic code splitting, optimized performance, and simplified routing out of the box. Next.js supports both static site generation (SSG) and server-side rendering (SSR), allowing developers to choose the most appropriate rendering method for each page. The framework offers built-in CSS support, API routes for backend functionality, and easy deployment options. Next.js is known for its developer-friendly experience, with features like hot module replacement and automatic prefetching. Its ability to create hybrid apps that combine static and server-rendered pages makes it popular for building scalable, SEO-friendly web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://nextjs.org/) |
||||
- [@official@Official Docs for Getting Started](https://nextjs.org/docs/getting-started) |
||||
- [@article@Mastering Next.js](https://masteringnextjs.com/) |
||||
- [@video@Next.js for Beginners - freeCodeCamp](https://www.youtube.com/watch?v=KjY94sAKLlw) |
||||
- [@video@Introduction to Next.js and React by Lee Robinson](https://www.youtube.com/watch?v=h2BcitZPMn4) |
||||
- [@video@Next.js for Beginners - Full Course at freeCodeCamp YouTube Channel](https://youtu.be/1WmNXEVia8I) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,9 @@ |
||||
# Notifications API |
||||
|
||||
The Notifications API is a web API that allows web pages to display system-level notifications to the user. These notifications can be used to alert the user of important events, such as new messages or updates, even when the web page is not open in the browser. |
||||
|
||||
To use the Notifications API, a web page must first request permission from the user to display notifications. If permission is granted, the page can then use the `Notification` constructor to create a new notification and display it to the user. The notification can include a title, body text, and an icon, and it can be customized with options such as a timeout and a click action. |
||||
The Notifications API is a web API that allows web pages to display system-level notifications to the user. These notifications can be used to alert the user of important events, such as new messages or updates, even when the web page is not open in the browser. To use the Notifications API, a web page must first request permission from the user to display notifications. If permission is granted, the page can then use the `Notification` constructor to create a new notification and display it to the user. The notification can include a title, body text, and an icon, and it can be customized with options such as a timeout and a click action. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Get Started With The Notifications API](https://web.dev/articles/codelab-notifications-get-started) |
||||
- [@article@Notifications API - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API) |
||||
- [@video@How To Send Push Notifications With JavaScript](https://youtu.be/Bm0JjR4kP8w?si=-2Nu0I2Zl9f-R1zj) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# npm |
||||
|
||||
npm is a package manager for the JavaScript programming language maintained by npm, Inc. npm is the default package manager for the JavaScript runtime environment Node.js. |
||||
npm (Node Package Manager) is the default package manager for Node.js, providing a vast ecosystem of reusable JavaScript code. It allows developers to easily share, discover, and install packages (libraries and tools) for their projects. npm consists of a command-line interface for package installation and management, and an online repository of open-source packages. It handles dependency management, version control, and script running for Node.js projects. The npm registry is the largest software registry in the world, containing over a million packages. npm's package.json file defines project metadata and dependencies, enabling reproducible builds across different environments. Despite competition from alternatives like Yarn, npm remains the most widely used package manager in the JavaScript ecosystem. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Modern JavaScript for Dinosaurs](https://peterxjang.com/blog/modern-javascript-explained-for-dinosaurs.html) |
||||
- [@article@An Absolute Beginners Guide to Using npm](https://nodesource.com/blog/an-absolute-beginners-guide-to-using-npm/) |
||||
- [@opensource@How to NPM](https://github.com/workshopper/how-to-npm) |
||||
- [@video@NPM tutorial for Beginners](https://www.youtube.com/watch?v=2V1UUhBJ62Y) |
||||
- [@video@NPM Crash Course](https://www.youtube.com/watch?v=jHDhaSSKmB0) |
||||
- [@feed@Explore top posts about NPM](https://app.daily.dev/tags/npm?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# Nuxt.js |
||||
|
||||
Nuxt.js is a free and open source JavaScript library based on Vue.js, Node.js, Webpack and Babel.js. Nuxt is inspired by Next.js, which is a framework of similar purpose, based on React.js. |
||||
Nuxt.js is a higher-level framework built on top of Vue.js, designed to create universal or single-page Vue applications. It simplifies the development process by providing a structured directory layout, automatic routing, and server-side rendering capabilities out of the box. Nuxt.js offers features like static site generation, code splitting, and asynchronous data fetching. It supports both client-side and server-side rendering, allowing developers to choose the most appropriate approach for each page. Nuxt.js emphasizes developer experience and performance optimization, making it popular for building scalable, SEO-friendly Vue applications. Its modular architecture and extensive plugin ecosystem enable easy integration of additional functionalities. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Nuxt Website](https://nuxtjs.org/) |
||||
- [@official@Nuxt Docs](https://nuxtjs.org/docs/get-started/installation) |
||||
- [@official@Nuxt Tutorials](https://nuxtjs.org/tutorials) |
||||
- [@article@Get Started with Nuxt](https://explorers.netlify.com/learn/get-started-with-nuxt) |
||||
- [@article@Nuxt.js Fundamentals](https://vueschool.io/courses/nuxtjs-fundamentals) |
||||
- [@course@Nuxt.js Fundamentals](https://vueschool.io/courses/nuxtjs-fundamentals) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,13 +1,10 @@ |
||||
# Nuxt js |
||||
# Nuxt.js |
||||
|
||||
Nuxt.js is an open-source development framework built on top of Node.js |
||||
enabling Vue based web applications functionalities such as server-side |
||||
rendering and generating static websites. |
||||
Nuxt.js is a higher-level framework built on top of Vue.js, designed to create universal or single-page Vue applications. It simplifies the development process by providing a structured directory layout, automatic routing, and server-side rendering capabilities out of the box. Nuxt.js offers features like static site generation, code splitting, and asynchronous data fetching. It supports both client-side and server-side rendering, allowing developers to choose the most appropriate approach for each page. Nuxt.js emphasizes developer experience and performance optimization, making it popular for building scalable, SEO-friendly Vue applications. Its modular architecture and extensive plugin ecosystem enable easy integration of additional functionalities. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://nuxtjs.org/) |
||||
- [@official@Official Docs for Getting Started](https://nuxtjs.org/docs/get-started) |
||||
- [@article@Mastering Nuxt.js](https://masteringnuxt.com/) |
||||
- [@video@Vue.js for Beginners - Full Course at freeCodeCamp YouTube Channel](https://www.youtube.com/watch?v=FXpIoQ_rT_c) |
||||
- [@official@Nuxt Website](https://nuxtjs.org/) |
||||
- [@article@Get Started with Nuxt](https://explorers.netlify.com/learn/get-started-with-nuxt) |
||||
- [@course@Nuxt.js Fundamentals](https://vueschool.io/courses/nuxtjs-fundamentals) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,11 @@ |
||||
# OWASP Security Risks |
||||
|
||||
OWASP or Open Web Application Security Project is an online community that produces freely-available articles, methodologies, documentation, tools, and technologies in the field of web application security. |
||||
OWASP (Open Web Application Security Project) identifies and ranks the most critical security risks to web applications. The OWASP Top 10 list includes vulnerabilities such as injection flaws, broken authentication, sensitive data exposure, XML external entities (XXE), broken access control, security misconfigurations, cross-site scripting (XSS), insecure deserialization, using components with known vulnerabilities, and insufficient logging and monitoring. These risks represent common attack vectors exploited by malicious actors to compromise web applications and their underlying systems. OWASP provides guidelines and best practices for mitigating these risks, emphasizing the importance of secure coding practices, regular security assessments, and implementing robust security controls throughout the software development lifecycle. Understanding and addressing these risks is crucial for developers and organizations to enhance the security posture of their web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Wikipedia - OWASP](https://en.wikipedia.org/wiki/OWASP) |
||||
- [@official@OWASP Website](https://owasp.org/) |
||||
- [@opensource@OWASP Web Application Security Testing Checklist](https://github.com/0xRadi/OWASP-Web-Checklist) |
||||
- [@article@OWASP Top 10 Security Risks](https://sucuri.net/guides/owasp-top-10-security-vulnerabilities-2021/) |
||||
- [@article@OWASP Cheatsheets](https://cheatsheetseries.owasp.org/cheatsheets/AJAX_Security_Cheat_Sheet.html) |
||||
- [@official@OWASP Cheatsheets](https://cheatsheetseries.owasp.org/cheatsheets/AJAX_Security_Cheat_Sheet.html) |
||||
- [@article@OWASP Top 10: A Guide to the Worst Software Vulnerabilities](https://thenewstack.io/owasp-top-10-a-guide-to-the-worst-software-vulnerabilities/) |
||||
- [@feed@Explore top posts about Security](https://app.daily.dev/tags/security?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# Package Managers |
||||
|
||||
Package managers allow you to manage the dependencies (external code written by you or someone else) that your project needs to work correctly. |
||||
Package managers are tools that automate the process of installing, updating, configuring, and removing software packages in a consistent manner. They handle dependency resolution, version management, and package distribution for programming languages and operating systems. Popular package managers include npm for JavaScript, pip for Python, and apt for Debian-based Linux distributions. These tools maintain a centralized repository of packages, allowing developers to easily share and reuse code. Package managers simplify project setup, ensure consistency across development environments, and help manage complex dependency trees. They play a crucial role in modern software development by streamlining workflow, enhancing collaboration, and improving code reusability. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Modern JavaScript for Dinosaurs](https://peterxjang.com/blog/modern-javascript-explained-for-dinosaurs.html) |
||||
- [@article@An Absolute Beginners Guide to Using npm](https://nodesource.com/blog/an-absolute-beginners-guide-to-using-npm/) |
||||
- [@article@Yarn - Getting Started](https://yarnpkg.com/en/docs/getting-started) |
||||
- [@video@NPM tutorial for Beginners](https://www.youtube.com/watch?v=2V1UUhBJ62Y) |
||||
- [@official@Yarn - Getting Started](https://yarnpkg.com/en/docs/getting-started) |
||||
- [@video@NPM Crash Course](https://www.youtube.com/watch?v=jHDhaSSKmB0) |
||||
- [@video@Yarn Crash Course](https://www.youtube.com/watch?v=g9_6KmiBISk) |
||||
|
||||
@ -1,9 +1,9 @@ |
||||
# Parcel |
||||
|
||||
Parcel is a web application bundler, differentiated by its developer experience. It offers blazing-fast performance utilizing multicore processing and requires zero configuration. |
||||
Parcel is a zero-configuration web application bundler that simplifies the process of building and deploying web projects. It supports multiple programming languages and file types out of the box, including JavaScript, CSS, HTML, and various image formats. Parcel automatically analyzes dependencies, transforms code, and optimizes assets without requiring a complex configuration file. It offers features like hot module replacement, code splitting, and tree shaking by default. Parcel's main selling point is its ease of use and fast build times, achieved through parallel processing and caching. While it may lack some advanced features of more established bundlers like Webpack, Parcel's simplicity and performance make it an attractive option for rapid prototyping and smaller projects. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Official Website and Docs](https://parceljs.org/plugin-system/bundler/) |
||||
- [@video@Using Parcel Bundler with React](https://www.youtube.com/watch?v=hCxvp3_o0gM) |
||||
- [@official@Official Website and Docs](https://parceljs.org/plugin-system/bundler/) |
||||
- [@video@How to Build a Web App with Parcel.js](https://www.youtube.com/watch?v=R02ehdTzi3I) |
||||
- [@feed@Explore top posts about Web Development](https://app.daily.dev/tags/webdev?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,8 @@ |
||||
# Payments |
||||
|
||||
The Payment Request API is a web API that allows web developers to build checkout flows within their web applications. It provides a standardized, browser-based interface for collecting payment and shipping information from the user, and it supports a wide range of payment methods, including credit cards, debit cards, and digital wallets. |
||||
|
||||
To use the Payment Request API, a web page must first create a `PaymentRequest` object and specify the payment and shipping options that are available to the user. The page can then invoke the Payment Request UI by calling the `show()` method on the `PaymentRequest` object. The user can then select their preferred payment and shipping options and confirm the payment, at which point the Payment Request API will return a payment response object that can be used to complete the transaction. |
||||
|
||||
The Payment Request API is supported by most modern web browsers and is designed to be simple and efficient for both the developer and the user. |
||||
The Payment Request API is a web API that allows web developers to build checkout flows within their web applications. It provides a standardized, browser-based interface for collecting payment and shipping information from the user, and it supports a wide range of payment methods, including credit cards, debit cards, and digital wallets. To use the Payment Request API, a web page must first create a `PaymentRequest` object and specify the payment and shipping options that are available to the user. The page can then invoke the Payment Request UI by calling the `show()` method on the `PaymentRequest` object. The user can then select their preferred payment and shipping options and confirm the payment, at which point the Payment Request API will return a payment response object that can be used to complete the transaction. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Payment Request API - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API) |
||||
- [@article@The Payment Request API](https://www.w3.org/TR/payment-request/) |
||||
|
||||
@ -1,10 +1,9 @@ |
||||
# Playwright |
||||
|
||||
Playwright is an open-source test automation library initially developed by Microsoft contributors. It supports programming languages such as Java, Python, C#, and NodeJS. Playwright comes with Apache 2.0 License and is most popular with NodeJS with Javascript/Typescript. |
||||
Playwright is an open-source automation framework developed by Microsoft for end-to-end testing of web applications. It provides a single API to automate Chromium, Firefox, and WebKit browsers across Windows, macOS, and Linux. Playwright supports multiple programming languages including JavaScript, TypeScript, Python, and .NET. It offers features like auto-waiting, network interception, and mobile emulation. The framework excels in handling modern web apps with dynamic content, providing reliable automation through its ability to wait for elements to be ready before acting on them. Playwright's cross-browser and cross-platform capabilities, combined with its powerful tooling for debugging and test generation, make it a robust choice for automated testing of web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Playwright Website](https://playwright.dev/) |
||||
- [@video@Get started with end-to-end testing: Playwright](https://www.youtube.com/playlist?list=PLQ6Buerc008ed-F9OksF7ek37wR3y916p) |
||||
- [@article@Playwright Tutorial: Learn Basics and Setup](https://www.browserstack.com/guide/playwright-tutorial) |
||||
- [@article@Playwright, a Time-Saving End-to-End Testing Framework](https://thenewstack.io/playwright-a-time-saving-end-to-end-testing-framework/) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# pnpm |
||||
|
||||
PNPM is an alternative package manager for Node. js which stands for “Performant NPM”. The main purpose of PNPM is to hold all the packages at a global (centralized) store and use them if needed by other projects too by creating hard links to it. |
||||
pnpm (performant npm) is a fast, disk-space efficient package manager for JavaScript and Node.js projects. It addresses inefficiencies in npm and Yarn by using a unique approach to storing and linking dependencies. pnpm creates a single, global store for all packages and uses hard links to reference them in project node_modules, significantly reducing disk space usage and installation time. It strictly adheres to package.json specifications, ensuring consistent installs across environments. pnpm offers features like workspace support for monorepos, side-by-side versioning, and improved security through better isolation of dependencies. While less widely adopted than npm or Yarn, pnpm's performance benefits and efficient disk usage are attracting increasing attention in the JavaScript community. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://pnpm.io) |
||||
- [@article@Meet PNPM: The Faster, More Performant NPM](https://blog.bitsrc.io/pnpm-javascript-package-manager-4b5abd59dc9) |
||||
- [@video@Get started with pnpm](https://www.youtube.com/watch?v=MvbReZDSKHI) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# PostCSS |
||||
|
||||
PostCSS is a tool for transforming styles with JS plugins. These plugins can lint your CSS, support variables and mixins, transpile future CSS syntax, inline images, and more. |
||||
PostCSS is a tool for transforming CSS with JavaScript plugins. It allows developers to enhance their CSS workflow by automating repetitive tasks, adding vendor prefixes, and implementing future CSS features. PostCSS works as a preprocessor, but unlike Sass or Less, it's highly modular and customizable. Users can choose from a wide range of plugins or create their own to suit specific needs. Popular plugins include Autoprefixer for adding vendor prefixes, cssnext for using future CSS features, and cssnano for minification. PostCSS integrates well with various build tools and can be used alongside traditional CSS preprocessors. Its flexibility and performance make it a popular choice for optimizing CSS in modern web development workflows. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://postcss.org/) |
||||
- [@video@Learn PostCSS in 15 minutes](https://www.youtube.com/watch?v=Kn2SKUOaoT4) |
||||
- [@feed@Explore top posts about CSS](https://app.daily.dev/tags/css?ref=roadmapsh) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# Prettier |
||||
|
||||
Prettier is an opinionated code formatter with support for JavaScript, HTML, CSS, YAML, Markdown, GraphQL Schemas. By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. |
||||
Prettier is an opinionated code formatter that supports multiple programming languages, including JavaScript, TypeScript, CSS, and more. It automatically formats code to adhere to a consistent style, eliminating debates about code formatting in development teams. Prettier parses code and reprints it with its own rules, taking maximum line length into account and wrapping code when necessary. It integrates with most editors and can be run as part of the development workflow or in pre-commit hooks. Prettier's main benefits include saving time on code reviews, reducing cognitive load for developers, and maintaining a consistent code style across projects. Its "zero-config" philosophy and wide language support have made it a popular tool in modern development environments. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Prettier Website](https://prettier.io) |
||||
- [@official@Why Prettier](https://prettier.io/docs/en/why-prettier.html) |
||||
- [@video@How to set up Prettier](https://www.youtube.com/watch?v=DqfQ4DPnRqI) |
||||
|
||||
@ -1,14 +1,8 @@ |
||||
# PRPL Pattern |
||||
|
||||
The PRPL pattern is a performance optimization pattern for web applications that focuses on minimizing the time it takes for the initial rendering of a web page. It stands for Push, Render, Pre-cache, and Lazy-load, and it involves the following steps: |
||||
|
||||
- Push: Prioritize the delivery of critical resources, such as HTML, CSS, and JavaScript, to the client as early as possible. |
||||
- Render: Start rendering the web page as soon as the critical resources are received, even if some non-critical resources are still being downloaded. |
||||
- Pre-cache: Pre-cache non-critical resources in the background so that they are available when needed. |
||||
- Lazy-load: Defer the loading of non-critical resources until they are needed, such as when the user scrolls to them or interacts with them. |
||||
|
||||
The PRPL pattern is designed to improve the perceived performance of a web page by reducing the time it takes for the page to become interactive. It is particularly useful for applications that are served over slow or unreliable networks, as it allows the page to render as quickly as possible and then gradually load the remaining resources. |
||||
The PRPL pattern is a web application architecture strategy designed to improve performance, especially on mobile devices. PRPL stands for Push, Render, Pre-cache, and Lazy-load. It focuses on optimizing the initial load time and subsequent navigation speed. The pattern involves pushing critical resources for the initial route, rendering the initial route as quickly as possible, pre-caching remaining routes, and lazy-loading other routes and non-critical assets. This approach aims to deliver a near-instant loading experience for users, particularly on slower networks and less powerful devices. PRPL is often implemented using modern web technologies like service workers and is commonly associated with Progressive Web Apps (PWAs), though it can be applied to various web application architectures. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@PRPL Pattern - Google Developers](https://developers.google.com/web/fundamentals/performance/prpl-pattern) |
||||
- [@article@PRPL Pattern](https://www.patterns.dev/vanilla/prpl/) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Progressive Web Apps |
||||
|
||||
Progressive Web Apps (PWAs) are websites that are progressively enhanced to function like installed, native apps on supporting platforms, while functioning like regular websites on other browsers. |
||||
Progressive Web Apps (PWAs) are web applications that use modern web capabilities to deliver an app-like experience to users. They combine the best features of web and native apps, offering reliability, speed, and engagement. PWAs are built using web technologies (HTML, CSS, JavaScript) but provide features typically associated with native apps, such as offline functionality, push notifications, and home screen installation. They are responsive, work across different devices and browsers, and are discoverable through search engines. PWAs use service workers for background processing and caching, enabling faster load times and offline access. This approach allows developers to create cross-platform applications that are both cost-effective to develop and easy to maintain, while providing users with a seamless, app-like experience directly through their web browser. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Learn PWA](https://web.dev/learn/pwa/) |
||||
- [@article@MDN Web Docs: Progressive Web Apps ](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/) |
||||
- [@article@Building a simple offline-capable Notepad app ](https://www.amitmerchant.com/Building-Simple-Offline-Notepad-Using-Service-Worker/) |
||||
- [@video@Build a Progressive Web App](https://www.youtube.com/watch?v=sFsRylCQblw) |
||||
- [@video@Progressive Web Apps in 2024](https://www.youtube.com/watch?v=3ODP6tTpjqA) |
||||
- [@feed@Explore top posts about Web Development](https://app.daily.dev/tags/webdev?ref=roadmapsh) |
||||
|
||||
@ -1,5 +1,8 @@ |
||||
# Qwik |
||||
|
||||
Qwik is a new kind of web framework that can deliver instant loading web applications at any size or complexity. Your sites and apps can boot with about 1kb of JS (regardless of application complexity), and achieve consistent performance at scale. |
||||
Qwik is an open-source front-end framework designed for optimal performance and near-instant loading of web applications. It focuses on delivering a "resumable" application model, where the app can start running with minimal JavaScript downloaded. Qwik achieves this through fine-grained lazy loading, serialization of the application state, and prefetching. It uses a unique approach to hydration, only loading JavaScript for interactive elements when needed. Qwik is built for modern web standards and aims to solve performance issues common in large-scale web applications. While still relatively new compared to established frameworks, Qwik's innovative approach to performance optimization is garnering attention in the web development community. |
||||
|
||||
Read more about Qwik [on the official website](https://qwik.builder.io/). |
||||
Learn more from the following resources: |
||||
|
||||
- [@official@Qwik Website](https://qwik.dev) |
||||
- [@video@Qwik… the world's first O(1) JavaScript framework?](https://www.youtube.com/watch?v=x2eF3YLiNhY) |
||||
@ -1,14 +1,8 @@ |
||||
# RAIL Model |
||||
|
||||
The RAIL model is a performance optimization model for web applications that focuses on improving the perceived performance of a web page. It stands for Response, Animation, Idle, and Load, and it involves the following four performance goals: |
||||
|
||||
- Response: The time it takes for the web page to respond to user input should be under 100 milliseconds. |
||||
- Animation: The time it takes for an animation to run should be under 10 milliseconds. |
||||
- Idle: The web page should take advantage of idle time to perform non-critical tasks. |
||||
- Load: The time it takes for the web page to fully load should be under 1 second. |
||||
|
||||
The RAIL model is designed to provide a framework for optimizing the performance of a web page by focusing on the four key areas that impact the user's perception of performance. It is particularly useful for applications that require high levels of interactivity, such as games and social media applications. |
||||
The RAIL Model is a user-centric performance model developed by Google that focuses on improving web application responsiveness and user experience. RAIL stands for Response, Animation, Idle, and Load. It provides specific performance goals: Responses to user input should occur within 100ms; Animations should run at 60 frames per second (16ms per frame); Idle time should be used to complete deferred work; and Load time for interactive content should be under 5 seconds. The model emphasizes the importance of perceived performance, encouraging developers to prioritize user interactions and break up long tasks. By adhering to RAIL guidelines, developers can create web applications that feel fast and responsive, enhancing user satisfaction and engagement. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@RAIL Model - Google Developers](https://developers.google.com/web/fundamentals/performance/rail) |
||||
- [@article@An Overview of the RAIL performance model](https://www.keycdn.com/blog/rail-performance-model) |
||||
|
||||
@ -1,9 +1,9 @@ |
||||
# React Native |
||||
|
||||
React Native is a popular JavaScript-based mobile app framework that allows you to build natively-rendered mobile apps for iOS and Android. The framework lets you create an application for various platforms by using the same codebase. |
||||
React Native is an open-source mobile application development framework created by Facebook. It allows developers to build native mobile apps for iOS and Android using JavaScript and React. React Native translates JavaScript code into native components, providing near-native performance and a genuine native user interface. It enables code reuse across platforms, speeding up development and reducing costs. The framework offers hot reloading for quick iterations, access to native APIs, and a large ecosystem of third-party plugins. React Native's "learn once, write anywhere" philosophy and its ability to bridge web and mobile development make it popular for creating cross-platform mobile applications, especially among teams already familiar with React for web development. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@React Native Roadmap](/react-native) |
||||
- [@official@Official Website](https://reactnative.dev/) |
||||
- [@official@Official Getting Started to React Native](https://reactnative.dev/docs/getting-started) |
||||
- [@feed@Explore top posts about React](https://app.daily.dev/tags/react?ref=roadmapsh) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# react-router |
||||
|
||||
There used to be Remix in this list but they announced to merge Remix into react-router after v7. |
||||
React Router is a popular routing library for React applications that enables dynamic, client-side routing. It allows developers to create single-page applications with multiple views, managing the URL and history of the browser while keeping the UI in sync with the URL. React Router provides a declarative way to define routes, supporting nested routes, route parameters, and programmatic navigation. It offers components like BrowserRouter, Route, and Link to handle routing logic and navigation. The library also supports features such as lazy loading of components, route guards, and custom history management. React Router's integration with React's component model makes it a go-to solution for managing navigation and creating complex, multi-view applications in React ecosystems. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://remix.run/) |
||||
- [@official@Official Docs for Getting Started](https://remix.run/docs/en/v1#getting-started) |
||||
- [@official@Official Website](https://reactrouter.com/en/main) |
||||
- [@article@A complete guide to routing in react](https://hygraph.com/blog/routing-in-react) |
||||
- [@video@React router - Complete tutorial](https://www.youtube.com/watch?v=oTIJunBa6MA) |
||||
|
||||
@ -1,13 +1,10 @@ |
||||
# React |
||||
|
||||
React is the most popular front-end JavaScript library for building user interfaces. React can also render on the server using Node and power mobile apps using React Native. |
||||
React is an open-source JavaScript library for building user interfaces, primarily for single-page applications. Developed and maintained by Facebook, it allows developers to create reusable UI components that efficiently update and render as data changes. React uses a virtual DOM for performance optimization and supports a unidirectional data flow. Its component-based architecture promotes modularity and reusability. React's ecosystem includes tools like Redux for state management and React Native for mobile app development. The library's declarative nature, efficient rendering, and strong community support have made it one of the most popular choices for front-end development in modern web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Visit Dedicated React Roadmap](https://roadmap.sh/react) |
||||
- [@official@React Website](https://react.dev) |
||||
- [@official@Official Getting Started](https://react.dev/learn/tutorial-tic-tac-toe) |
||||
- [@video@React JS Course for Beginners](https://www.youtube.com/watch?v=nTeuhbP7wdE) |
||||
- [@video@React Course - Beginners Tutorial for React JavaScript Library \[2022\]](https://www.youtube.com/watch?v=bMknfKXIFA8) |
||||
- [@video@Understanding Reacts UI Rendering Process](https://www.youtube.com/watch?v=i793Qm6kv3U) |
||||
- [@course@Full Stack React Developer Course](https://www.youtube.com/watch?v=Bvwq_S0n2pk) |
||||
- [@feed@Explore top posts about React](https://app.daily.dev/tags/react?ref=roadmapsh) |
||||
|
||||
@ -1,13 +1,10 @@ |
||||
# React |
||||
|
||||
React is the most popular front-end JavaScript library for building user interfaces. React can also render on the server using Node and power mobile apps using React Native. |
||||
React is an open-source JavaScript library for building user interfaces, primarily for single-page applications. Developed and maintained by Facebook, it allows developers to create reusable UI components that efficiently update and render as data changes. React uses a virtual DOM for performance optimization and supports a unidirectional data flow. Its component-based architecture promotes modularity and reusability. React's ecosystem includes tools like Redux for state management and React Native for mobile app development. The library's declarative nature, efficient rendering, and strong community support have made it one of the most popular choices for front-end development in modern web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@roadmap@Visit Dedicated React Roadmap](https://roadmap.sh/react) |
||||
- [@official@React Website](https://react.dev) |
||||
- [@official@Official Getting Started](https://react.dev/learn/tutorial-tic-tac-toe) |
||||
- [@video@React JS Course for Beginners](https://www.youtube.com/watch?v=nTeuhbP7wdE) |
||||
- [@video@React Course - Beginners Tutorial for React JavaScript Library \[2022\]](https://www.youtube.com/watch?v=bMknfKXIFA8) |
||||
- [@video@Understanding Reacts UI Rendering Process](https://www.youtube.com/watch?v=i793Qm6kv3U) |
||||
- [@course@Full Stack React Developer Course](https://www.youtube.com/watch?v=Bvwq_S0n2pk) |
||||
- [@feed@Explore top posts about React](https://app.daily.dev/tags/react?ref=roadmapsh) |
||||
|
||||
@ -1,8 +1,9 @@ |
||||
# Relay Modern |
||||
|
||||
Relay is a JavaScript client used in the browser to fetch GraphQL data. It's a JavaScript framework developed by Facebook for managing and fetching data in React applications. It is built with scalability in mind in order to power complex applications like Facebook. The ultimate goal of GraphQL and Relay is to deliver instant UI-response interactions. |
||||
Relay is a JavaScript framework developed by Facebook for building data-driven React applications. It's specifically designed to work with GraphQL, providing a declarative approach to fetching and managing data in complex web applications. Relay optimizes data fetching by colocating data requirements with components, enabling efficient updates and minimizing over-fetching. It handles caching, real-time updates, and optimistic UI updates out of the box. Relay's architecture promotes scalability and performance in large applications by managing data dependencies and reducing network requests. While it has a steeper learning curve compared to simpler data-fetching solutions, Relay offers significant benefits for applications with complex data requirements, especially when used in conjunction with React and GraphQL. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://relay.dev/) |
||||
- [@official@Introduction to Relay modern](https://relay.dev/docs/) |
||||
- [@video@ELI5 - Relay](https://www.youtube.com/watch?v=A4POd93GI_I) |
||||
- [@opensource@facebook/relay](https://github.com/facebook/relay) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# Responsive Web Design |
||||
|
||||
Responsive Web Designing is the technique to make your webpages look good on all screen sizes. There are certain techniques used to achieve that e.g. CSS media queries, percentage widths, min or max widths heights etc. |
||||
Responsive web design is an approach to web development that creates dynamic changes to the appearance of a website, depending on the screen size and orientation of the device being used to view it. It uses fluid grids, flexible images, and CSS media queries to adapt the layout to the viewing environment. The goal is to build web pages that detect the visitor's screen size and orientation and change the layout accordingly, providing an optimal viewing experience across a wide range of devices, from desktop computers to mobile phones. This approach eliminates the need for a different design and development phase for each new gadget on the market, while ensuring a consistent and intuitive user experience across all devices. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Responsive Web Design](https://www.w3schools.com/css/css_rwd_intro.asp) |
||||
- [@article@Learn Responsive Design](https://web.dev/learn/design/) |
||||
- [@article@The Beginner’s Guide to Responsive Web Design](https://kinsta.com/blog/responsive-web-design/) |
||||
- [@article@The guide to responsive web design in 2022](https://webflow.com/blog/responsive-web-design) |
||||
- [@video@5 simple tips to making responsive layouts the easy way](https://www.youtube.com/watch?v=VQraviuwbzU) |
||||
- [@video@Introduction To Responsive Web Design](https://www.youtube.com/watch?v=srvUrASNj0s) |
||||
- [@video@Introduction To Responsive Web Design](https://www.youtube.com/watch?v=srvUrASNj0s) |
||||
- [@course@Conquering Responsive Layouts](https://courses.kevinpowell.co/conquering-responsive-layouts) |
||||
@ -1,10 +1,9 @@ |
||||
# Sass |
||||
|
||||
Sass is a preprocessor scripting language that is interpreted or compiled into Cascading Style Sheets. It lets you write maintainable CSS and provides features like variable, nesting, mixins, extension, functions, loops, conditionals and so on. |
||||
Sass (Syntactically Awesome Style Sheets) is a mature, stable, and powerful professional-grade CSS extension language. It extends CSS with features like variables, nested rules, mixins, inline imports, and more, all with fully CSS-compatible syntax. Sass allows for more organized, maintainable, and reusable styles in complex projects. It compiles to clean, standard CSS, supporting two syntaxes: the original indented syntax and the more popular SCSS (Sassy CSS) syntax. Sass provides functionality like control directives for libraries, making it easier to write well-structured, scalable CSS. Its features help reduce repetition in CSS and save time, making it a popular choice among frontend developers for managing large, complex stylesheets. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Sass Website](https://sass-lang.com/) |
||||
- [@article@Official Documentation](https://sass-lang.com/documentation) |
||||
- [@video@Sass Tutorial for Beginners](https://www.youtube.com/watch?v=_a5j7KoflTs) |
||||
- [@video@Sass, BEM, & Responsive Design](https://www.youtube.com/watch?v=jfMHA8SqUL4) |
||||
|
||||
@ -1,10 +1,10 @@ |
||||
# Basics of SEO |
||||
|
||||
SEO or Search Engine Optimization is the technique used to optimize your website for better rankings on search engines such as Google, Bing etc. |
||||
SEO (Search Engine Optimization) basics involve strategies to improve a website's visibility and ranking in search engine results. Key elements include creating relevant, high-quality content, proper use of keywords, optimizing meta tags and URLs, ensuring mobile-friendliness, improving site speed, and building quality backlinks. SEO also focuses on user experience, including easy navigation and responsive design. Technical aspects like XML sitemaps, HTTPS security, and structured data markup play crucial roles. Understanding user intent, regularly updating content, and adhering to search engine guidelines are essential practices. Effective SEO combines on-page optimization, off-page tactics, and technical enhancements to increase organic traffic, improve user engagement, and enhance online presence in an increasingly competitive digital landscape. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Google Search Central — SEO Docs](https://developers.google.com/search/docs) |
||||
- [@video@Complete SEO Course for Beginners](https://www.youtube.com/watch?v=xsVTqzratPs) |
||||
- [@video@SEO Expert Course](https://www.youtube.com/watch?v=SnxeXZpZkI0) |
||||
- [@course@Complete SEO Course for Beginners](https://www.youtube.com/watch?v=xsVTqzratPs) |
||||
- [@course@SEO for 2024: The Complete Guide](https://www.youtube.com/watch?v=8YDUP-RH_4g) |
||||
- [@feed@Explore top posts about SEO](https://app.daily.dev/tags/seo?ref=roadmapsh) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Server Sent Events |
||||
|
||||
Server-Sent Events (SSE) is a technology that allows a web server to push data to a client in real-time. It uses an HTTP connection to send a stream of data from the server to the client, and the client can listen for these events and take action when they are received. |
||||
|
||||
SSE is useful for applications that require real-time updates, such as chat systems, stock tickers, and social media feeds. It is a simple and efficient way to establish a long-lived connection between a client and a server, and it is supported by most modern web browsers. |
||||
Server-Sent Events (SSE) is a technology that allows a web server to push data to a client in real-time. It uses an HTTP connection to send a stream of data from the server to the client, and the client can listen for these events and take action when they are received. SSE is useful for applications that require real-time updates, such as chat systems, stock tickers, and social media feeds. It is a simple and efficient way to establish a long-lived connection between a client and a server, and it is supported by most modern web browsers. |
||||
|
||||
To use SSE, the client must create an EventSource object and specify the URL of the server-side script that will send the events. The server can then send events by writing them to the response stream with the proper formatting. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Server-Sent Events - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events) |
||||
- [@video@Server-Sent Events - Postman](https://www.youtube.com/watch?v=KrE044J8jEQ) |
||||
|
||||
@ -1,11 +1,9 @@ |
||||
# Service Workers |
||||
|
||||
Service Workers are a type of web worker that acts as a proxy between a web page and the network, allowing web developers to build offline-first and reliable applications. Service Workers can intercept network requests, access the cache, and make decisions on how to respond to a request based on the available resources. |
||||
|
||||
Service Workers are written in JavaScript and are registered by a web page. Once registered, they can control the page and all its requests, even when the page is not open in a browser. This allows Service Workers to enable features such as push notifications, background synchronization, and offline support. |
||||
|
||||
Service Workers are supported by most modern web browsers, and they are an essential component of progressive web applications (PWAs). |
||||
Service Workers are a type of web worker that acts as a proxy between a web page and the network, allowing web developers to build offline-first and reliable applications. Service Workers can intercept network requests, access the cache, and make decisions on how to respond to a request based on the available resources. Service Workers are written in JavaScript and are registered by a web page. Once registered, they can control the page and all its requests, even when the page is not open in a browser. This allows Service Workers to enable features such as push notifications, background synchronization, and offline support. Service Workers are supported by most modern web browsers, and they are an essential component of progressive web applications (PWAs). |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Service Workers - MDN](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) |
||||
- [@article@Service Workers - Google](https://web.dev/learn/pwa/service-workers) |
||||
- [@video@Web Workers Explained](https://www.youtube.com/watch?v=JMKLXGwltGc) |
||||
|
||||
@ -1,9 +1,10 @@ |
||||
# SolidJS |
||||
|
||||
Solid is a reactive JavaScript toolkit for building user interfaces without a virtual DOM. To ensure that only the relevant code is executed when a state update occurs, it compiles templates down to real DOM nodes once and wraps modifications into fine-grained reactions. |
||||
SolidJS is a declarative, efficient, and flexible JavaScript library for building user interfaces. It uses a fine-grained reactivity system that updates only what changes, resulting in high performance. SolidJS compiles templates to real DOM nodes and updates them in-place, avoiding the overhead of a virtual DOM. It offers a syntax similar to React, making it familiar to many developers, but with a different underlying mechanism. SolidJS supports JSX, provides built-in state management, and emphasizes composition over inheritance. Its small size and lack of runtime overhead make it particularly suitable for applications requiring high performance. While newer compared to some frameworks, SolidJS is gaining popularity for its simplicity, performance, and developer-friendly approach to reactive programming. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website - SolidJS](https://www.solidjs.com/) |
||||
- [@official@SolidJS Tutorial](https://www.solidjs.com/tutorial/introduction_basics) |
||||
- [@video@SolidJS in 100 Seconds](https://www.youtube.com/watch?v=hw3Bx5vxKl0) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,10 @@ |
||||
# Server-side rendering |
||||
|
||||
Server-side rendering refers to the process that the service side completes the HTML structure splicing of the page, sends it to the browser, and then binds the status and events for it to become a fully interactive page. |
||||
Server-side rendering (SSR) is a technique used in web development where web pages are generated on the server and sent to the client as fully rendered HTML. This approach contrasts with client-side rendering, where the browser builds the page using JavaScript. SSR improves initial page load time and search engine optimization (SEO) by providing complete content to crawlers. It's particularly beneficial for content-heavy sites and applications requiring fast first-page loads. SSR can be implemented with various frameworks like Next.js for React or Nuxt.js for Vue.js. While it can increase server load and complexity, SSR offers advantages in performance perception, especially on slower devices or networks, and can be combined with client-side hydration for dynamic interactivity after initial load. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@what is server side rendering](https://www.educative.io/answers/what-is-server-side-rendering) |
||||
- [@article@When should I Server-Side Render?](https://medium.com/@mbleigh/when-should-i-server-side-render-c2a383ff2d0f) |
||||
- [@article@Server-Side Rendering (SSR)](https://vuejs.org/guide/scaling-up/ssr.html) |
||||
- [@video@what is server side rendering?](https://www.youtube.com/watch?v=GQzn7XRdzxY) |
||||
- [@video@wWhat are Server Side Rendering (SSR) & Client Side Rendering (CSR)](https://www.youtube.com/watch?v=ObrSuDYMl1s) |
||||
- [@video@What is server-side rendering for web development?](https://www.youtube.com/watch?v=okvg3MRAPs0) |
||||
- [@feed@Explore top posts about Web Development](https://app.daily.dev/tags/webdev?ref=roadmapsh) |
||||
|
||||
@ -1,9 +1,10 @@ |
||||
# Svelte Kit |
||||
|
||||
Svelte Kit is a framework for building web applications with the Svelte JavaScript framework. It is designed to be a complete solution for building web applications, with support for server-side rendering, automatic code splitting, and optimized performance. |
||||
SvelteKit is a framework for building web applications using Svelte, a component-based JavaScript framework. It provides a full-stack development experience, handling both server-side and client-side rendering. SvelteKit offers features like file-based routing, code-splitting, and server-side rendering out of the box. It supports both static site generation and server-side rendering, allowing developers to choose the most appropriate approach for each page. SvelteKit emphasizes simplicity and performance, leveraging Svelte's compile-time approach to generate highly optimized JavaScript. It includes built-in development tools, easy deployment options, and integrates well with various backend services. SvelteKit's efficient development experience and flexibility make it an attractive option for building modern, performant web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Svelte Kit Official Website](https://kit.svelte.dev/) |
||||
- [@article@Official Svelte Kit Docs](https://kit.svelte.dev/docs/introduction) |
||||
- [@video@Sveltekit in 100 Seconds](https://www.youtube.com/watch?v=H1eEFfAkIik) |
||||
- [@feed@Explore top posts about Svelte](https://app.daily.dev/tags/svelte?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,11 @@ |
||||
# Svelte |
||||
|
||||
Svelte is a javascript framework that unlike Vue and React does not use vertical DOM diffing but instead knows exactly what and where to update when the state changes. It's mainly focused on frontend and building user interfaces. |
||||
Svelte is a modern JavaScript framework for building user interfaces that takes a unique approach to web development. Unlike traditional frameworks that do most of their work in the browser, Svelte shifts that work into a compile step that happens when you build your app. It compiles your code to efficient vanilla JavaScript, resulting in smaller bundle sizes and better runtime performance. Svelte uses a component-based architecture and features a simple, intuitive syntax that allows developers to write less code. It includes built-in state management, CSS scoping, and animations. Svelte's approach eliminates the need for a virtual DOM, leading to faster initial loads and updates. Its simplicity and performance benefits have been gaining it increasing popularity in the front-end development community. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Svelte Website](https://svelte.dev/) |
||||
- [@official@Svelte Documentation](https://svelte.dev/docs) |
||||
- [@video@Svelte Course Playlist for beginners](https://www.youtube.com/playlist?list=PL4cUxeGkcC9hlbrVO_2QFVqVPhlZmz7tO) |
||||
- [@course@Svelte Course Playlist for beginners](https://www.youtube.com/playlist?list=PL4cUxeGkcC9hlbrVO_2QFVqVPhlZmz7tO) |
||||
- [@article@All About Svelte, the Much-Loved, State-Driven Web Framework](https://thenewstack.io/all-about-svelte-the-much-loved-state-driven-web-framework/) |
||||
- [@article@Svelte and the Future of Frontend Development](https://thenewstack.io/svelte-and-the-future-of-front-end-development/) |
||||
- [@feed@Explore top posts about Svelte](https://app.daily.dev/tags/svelte?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,11 @@ |
||||
# Svelte |
||||
|
||||
Svelte is a javascript framework that unlike Vue and React does not use vertical DOM diffing but instead knows exactly what and where to update when the state changes. It's mainly focused on frontend and building user interfaces. |
||||
Svelte is a modern JavaScript framework for building user interfaces that takes a unique approach to web development. Unlike traditional frameworks that do most of their work in the browser, Svelte shifts that work into a compile step that happens when you build your app. It compiles your code to efficient vanilla JavaScript, resulting in smaller bundle sizes and better runtime performance. Svelte uses a component-based architecture and features a simple, intuitive syntax that allows developers to write less code. It includes built-in state management, CSS scoping, and animations. Svelte's approach eliminates the need for a virtual DOM, leading to faster initial loads and updates. Its simplicity and performance benefits have been gaining it increasing popularity in the front-end development community. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Svelte Website](https://svelte.dev/) |
||||
- [@official@Svelte Documentation](https://svelte.dev/docs) |
||||
- [@video@Svelte Course Playlist for beginners](https://www.youtube.com/playlist?list=PL4cUxeGkcC9hlbrVO_2QFVqVPhlZmz7tO) |
||||
- [@course@Svelte Course Playlist for beginners](https://www.youtube.com/playlist?list=PL4cUxeGkcC9hlbrVO_2QFVqVPhlZmz7tO) |
||||
- [@article@All About Svelte, the Much-Loved, State-Driven Web Framework](https://thenewstack.io/all-about-svelte-the-much-loved-state-driven-web-framework/) |
||||
- [@article@Svelte and the Future of Frontend Development](https://thenewstack.io/svelte-and-the-future-of-front-end-development/) |
||||
- [@feed@Explore top posts about Svelte](https://app.daily.dev/tags/svelte?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,11 @@ |
||||
# SWC (Speedy Web Compiler) |
||||
|
||||
**SWC** (Speedy Web Compiler) is a JavaScript and TypeScript compiler and bundler built in Rust. Unlike Babel, which is JavaScript-based, SWC leverages Rust for blazing-fast performance, making it an ideal choice for large-scale projects. It focuses on speed while offering modern features like tree shaking, JSX transformation, and module bundling, catering to frontend development and build optimization. |
||||
The Speedy Web Compiler (SWC) is a fast, extensible JavaScript/TypeScript compiler written in Rust. It's designed as a faster alternative to Babel for transpiling modern JavaScript code into backwards-compatible versions. SWC can be used for both compilation and bundling, offering significant performance improvements over traditional JavaScript-based tools. It supports latest ECMAScript features, JSX, and TypeScript, and can be configured for custom transformations. SWC is commonly used in development environments to speed up build times and in production builds to optimize code. Its speed and compatibility make it increasingly popular in large-scale JavaScript projects and as a core component in other build tools and frameworks aiming for improved performance. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@SWC Website](https://swc.rs/) |
||||
- [@official@SWC Documentation](https://swc.rs/docs/) |
||||
- [@video@Introduction to SWC](https://www.youtube.com/watch?v=wlmbNWC3yB8) |
||||
- [@article@SWC vs Babel: A Rust-Powered Speed Revolution](https://blog.logrocket.com/swc-vs-babel/) |
||||
- [@video@Introduction to Speedy Web Compiler](https://www.youtube.com/watch?v=RXQlPpbdn_E) |
||||
- [@article@Why SWC is the Future of JavaScript Tooling](https://dev.to/somelink/why-swc-is-the-future-of-javascript-tooling) |
||||
- [@feed@Explore top posts about SWC](https://app.daily.dev/tags/swc?ref=roadmapsh) |
||||
|
||||
@ -1,12 +1,11 @@ |
||||
# Tailwind CSS |
||||
|
||||
CSS Framework that provides atomic CSS classes to help you style components e.g. `flex`, `pt-4`, `text-center` and `rotate-90` that can be composed to build any design, directly in your markup. |
||||
Tailwind CSS is a utility-first CSS framework that provides low-level utility classes to build custom designs without leaving your HTML. It offers a highly customizable set of pre-defined classes for layout, typography, color, and more, allowing rapid UI development. Tailwind emphasizes flexibility and composability, enabling developers to create unique designs without writing custom CSS. It uses a mobile-first approach and includes a built-in purge feature to remove unused styles in production, resulting in smaller file sizes. Tailwind's philosophy promotes consistency in design while maintaining the freedom to create custom looks. Its popularity has grown due to its efficiency in prototyping and building responsive designs quickly. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Tailwind Website](https://tailwindcss.com) |
||||
- [@video@Tailwind CSS Full Course for Beginners](https://www.youtube.com/watch?v=lCxcTsOHrjo) |
||||
- [@video@Tailwind CSS Crash Course](https://www.youtube.com/watch?v=UBOj6rqRUME) |
||||
- [@course@Tailwind CSS Full Course for Beginners](https://www.youtube.com/watch?v=lCxcTsOHrjo) |
||||
- [@video@Should You Use Tailwind CSS?](https://www.youtube.com/watch?v=hdGsFpZ0J2E) |
||||
- [@video@Official Screencasts](https://www.youtube.com/c/TailwindLabs/videos) |
||||
- [@feed@Explore top posts about CSS](https://app.daily.dev/tags/css?ref=roadmapsh) |
||||
|
||||
@ -1,10 +1,21 @@ |
||||
# Testing your apps |
||||
|
||||
Before delivering your application to users, you need to be sure that your app meets the requirements it was designed for, and that it doesn't do any weird, unintended things (called 'bugs'). To accomplish this, we 'test' our applications in different ways. |
||||
Testing apps involves systematically evaluating software to ensure it meets requirements, functions correctly, and maintains quality. Key testing types include: |
||||
|
||||
1. Unit testing: Verifying individual components or functions |
||||
2. Integration testing: Checking interactions between different parts of the app |
||||
3. Functional testing: Ensuring the app meets specified requirements |
||||
4. UI/UX testing: Evaluating the user interface and experience |
||||
5. Performance testing: Assessing app speed, responsiveness, and stability |
||||
6. Security testing: Identifying vulnerabilities and ensuring data protection |
||||
7. Accessibility testing: Verifying usability for people with disabilities |
||||
8. Compatibility testing: Checking functionality across different devices and platforms |
||||
|
||||
Modern testing often incorporates automated testing tools and continuous integration/continuous deployment (CI/CD) pipelines. Test-driven development (TDD) and behavior-driven development (BDD) are popular methodologies that emphasize writing tests before or alongside code. Effective testing strategies help identify bugs early, improve code quality, and ensure a reliable user experience. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@A comprehensive dive into software testing.](https://www.softwaretestingmaterial.com/software-testing/) |
||||
- [@article@The different types of software tests](https://www.atlassian.com/continuous-delivery/software-testing/types-of-software-testing) |
||||
- [@article@Testing React apps with Jest](https://jestjs.io/docs/tutorial-react) |
||||
- [@video@How to test web applications - dotJS 2024](https://www.youtube.com/watch?v=l3qjQpYBR8c) |
||||
- [@feed@Explore top posts about Testing](https://app.daily.dev/tags/testing?ref=roadmapsh) |
||||
|
||||
@ -1 +0,0 @@ |
||||
# topic node |
||||
@ -1,3 +1,3 @@ |
||||
# Type Checkers |
||||
|
||||
Type checker helps developers write code with fewer bugs by adding types to their code, trying to catch type errors within your code, and then removing them during compile time. Flow and TypeScript are two popular static type checkers for JavaScript. |
||||
Type checkers are tools that analyze code to detect and prevent type-related errors without executing the program. They enforce type consistency, helping developers catch mistakes early in the development process. Popular type checkers include TypeScript for JavaScript, Flow for JavaScript, and mypy for Python. These tools add static typing to dynamically typed languages, offering benefits like improved code reliability, better documentation, and enhanced developer tooling support. Type checkers can infer types in many cases and allow for gradual adoption in existing projects. They help prevent common runtime errors, facilitate refactoring, and improve code maintainability. While adding some overhead to the development process, type checkers are widely adopted in large-scale applications for their ability to catch errors before runtime and improve overall code quality. |
||||
|
||||
@ -1,20 +1,20 @@ |
||||
# Browser DevTools |
||||
|
||||
Most of the browsers have built-in developer tools that help you perform web development specific tasks on a webpage. My personal recommendation would be to use Chrome DevTools as it is the most advanced and has the most features. However, if you are using a different browser, you can still use the DevTools to debug your web application. |
||||
Browser Developer Tools, commonly known as DevTools, are built-in features in modern web browsers that provide a suite of debugging and development capabilities. These tools allow developers to inspect, edit, and debug HTML, CSS, and JavaScript in real-time on web pages. Key features include: |
||||
|
||||
Chrome DevTools is a set of web development tools built into the Google Chrome browser. It allows web developers to debug and optimize web pages by providing a range of features for inspecting and manipulating the page's HTML, CSS, and JavaScript. |
||||
1. DOM inspector for viewing and modifying page structure |
||||
2. Console for JavaScript debugging and logging |
||||
3. Network panel for analyzing HTTP requests and responses |
||||
4. Performance profiler for optimizing page load and runtime performance |
||||
5. Application panel for managing storage, caches, and service workers |
||||
6. Source panel for setting breakpoints and debugging JavaScript |
||||
7. Elements panel for live CSS editing |
||||
8. Device emulation for testing responsive designs |
||||
|
||||
Some of the features provided by Chrome DevTools include: |
||||
|
||||
- **Elements panel**: Inspect and modify the page's HTML and CSS. |
||||
- **Console panel**: View and debug JavaScript errors and log messages. |
||||
- **Network panel**: Monitor network requests and responses, and analyze performance issues. |
||||
- **Performance panel**: Analyze the performance of the page and identify bottlenecks. |
||||
- **Application panel**: Inspect the page's resources, such as cookies and local storage. |
||||
|
||||
Chrome DevTools is a powerful and essential tool for web developers, and it is widely used to debug and optimize web pages. It is constantly updated with new features and improvements, and it is available on all modern web browsers. |
||||
DevTools are essential for front-end development, performance optimization, and cross-browser compatibility testing, providing developers with crucial insights into web application behavior and structure. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Chrome DevTools - Google Developers](https://developers.google.com/web/tools/chrome-devtools) |
||||
- [@article@Firefox DevTools User Docs](https://firefox-source-docs.mozilla.org/devtools-user/) |
||||
- [@feed@Explore top posts about DevTools](https://app.daily.dev/tags/devtools?ref=roadmapsh) |
||||
|
||||
@ -1,13 +1,9 @@ |
||||
# Lighthouse |
||||
|
||||
Lighthouse is an open-source tool developed by Google that is used to audit the performance, accessibility, and SEO of web pages. It is available as a browser extension and as a command-line tool, and it can be run on any web page to generate a report with recommendations for improvement. |
||||
|
||||
Lighthouse works by simulating the load and interaction of a web page and measuring various performance metrics, such as load time, time to first paint, and time to interactive. It also checks for common issues such as incorrect image sizes, missing alt text, and broken links. |
||||
|
||||
Lighthouse provides a comprehensive and easy-to-use tool for identifying and fixing performance and accessibility issues on web pages. It is widely used by web developers and is integrated into many popular development tools. |
||||
Lighthouse is an open-source tool developed by Google that is used to audit the performance, accessibility, and SEO of web pages. It is available as a browser extension and as a command-line tool, and it can be run on any web page to generate a report with recommendations for improvement. Lighthouse works by simulating the load and interaction of a web page and measuring various performance metrics, such as load time, time to first paint, and time to interactive. It also checks for common issues such as incorrect image sizes, missing alt text, and broken links. Lighthouse provides a comprehensive and easy-to-use tool for identifying and fixing performance and accessibility issues on web pages. It is widely used by web developers and is integrated into many popular development tools. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Lighthouse - Google Developers](https://developers.google.com/web/tools/lighthouse) |
||||
- [@video@Improving Load Performance - Chrome DevTools 101](https://www.youtube.com/watch?v=5fLW5Q5ODiE) |
||||
- [@video@What is Google Lighthouse and how to use it](https://www.youtube.com/watch?v=VyaHwvPWuZU) |
||||
- [@feed@Explore top posts about Lighthouse](https://app.daily.dev/tags/lighthouse?ref=roadmapsh) |
||||
|
||||
@ -1,9 +1,11 @@ |
||||
# Repo Hosting Services |
||||
|
||||
There are different repository hosting services with the most famous one being GitHub, GitLab and BitBucket. I would recommend creating an account on GitHub because that is where most of the OpenSource work is done and most of the developers are. |
||||
Repo hosting services provide platforms for storing, managing, and collaborating on software projects using version control systems, primarily Git. These services offer features like issue tracking, pull requests, code review tools, wikis, and continuous integration/continuous deployment (CI/CD) pipelines. Popular platforms include GitHub, GitLab, Bitbucket, and SourceForge, each with unique offerings. GitHub, owned by Microsoft, is the largest and most widely used, known for its open-source community. GitLab offers a complete DevOps platform with built-in CI/CD. Bitbucket, part of Atlassian's suite, integrates well with other Atlassian tools. These services facilitate team collaboration, code sharing, and project management, making them integral to modern software development workflows. They also often provide features like access control, branch protection, and integration with various development tools, enhancing the overall development process. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@opensource@GitHub: Where the world builds software](https://github.com) |
||||
- [@opensource@GitLab: Iterate faster, innovate together](https://gitlab.com) |
||||
- [@article@BitBucket: The Git solution for professional teams](https://bitbucket.com) |
||||
- [@roadmap@Learn Git & Github](/git-github) |
||||
- [@official@Codeberg Website](https://codeberg.org/) |
||||
- [@official@GitHub Website](https://github.com) |
||||
- [@official@GitLab Website](https://gitlab.com) |
||||
- [@article@BitBucket Website](https://bitbucket.com) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Version Control Systems |
||||
|
||||
Version control systems allow you to track changes to your codebase/files over time. They allow you to go back to some previous version of the codebase without any issues. Also, they help in collaborating with people working on the same code – if you’ve ever collaborated with other people on a project, you might already know the frustration of copying and merging the changes from someone else into your codebase; version control systems allow you to get rid of this issue. |
||||
Version Control Systems (VCS) are tools that help developers track and manage changes to code over time. They allow multiple people to work on a project simultaneously, maintaining a history of modifications. Git is the most popular VCS, known for its distributed nature and branching model. Other systems include Subversion (SVN) and Mercurial. VCS enables features like branching for parallel development, merging to combine changes, and reverting to previous states. They facilitate collaboration through remote repositories, pull requests, and code reviews. VCS also provides backup and recovery capabilities, conflict resolution, and the ability to tag specific points in history. By maintaining a detailed record of changes and supporting non-linear development, VCS has become an essential tool in modern software development, enhancing productivity, code quality, and team collaboration. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@video@Version Control System Introduction](https://www.youtube.com/watch?v=zbKdDsNNOhg) |
||||
- [@video@Git & GitHub Crash Course For Beginners](https://www.youtube.com/watch?v=SWYqp7iY_Tc) |
||||
- [@video@Learn Git in 20 Minutes](https://youtu.be/Y9XZQO1n_7c?t=21) |
||||
- [@article@Git Documentation](https://git-scm.com/docs) |
||||
- [@roadmap@Learn Git and GitHub](/git-github) |
||||
- [@video@What is a Version Control System and why you should always use it](https://www.youtube.com/watch?v=IeXhYROClZk) |
||||
- [@official@Git Documentation](https://git-scm.com/docs) |
||||
- [@article@Learn Git by Atlassian](https://www.atlassian.com/git) |
||||
|
||||
@ -1,11 +1,10 @@ |
||||
# Vite |
||||
|
||||
Vite is a build tool that aims to provide a faster and leaner development experience for modern web projects. |
||||
Vite is a modern build tool and development server designed for fast and lean development of web applications. Created by Evan You, the author of Vue.js, Vite leverages native ES modules in the browser to enable near-instantaneous server start and lightning-fast hot module replacement (HMR). It supports various frameworks including Vue, React, and Svelte out of the box. Vite uses Rollup for production builds, resulting in highly optimized bundles. It offers features like CSS pre-processor support, TypeScript integration, and plugin extensibility. Vite's architecture, which separates dev and build concerns, allows for faster development cycles and improved developer experience, particularly for large-scale projects where traditional bundlers might struggle with performance. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Vite Website](https://vitejs.dev) |
||||
- [@article@Vite Documentation](https://vitejs.dev/guide) |
||||
- [@video@Vite Crash Course](https://youtu.be/LQQ3CR2JTX8) |
||||
- [@video@Vite Tutorial Video](https://www.youtube.com/watch?v=VAeRhmpcWEQ) |
||||
- [@feed@Explore top posts about Vite](https://app.daily.dev/tags/vite?ref=roadmapsh) |
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue