diff --git a/Gemfile b/Gemfile
index baa0a2e..ce1f377 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,17 +1,17 @@
source "https://rubygems.org"
-
-gem "jekyll", "~> 4.3.3"
-gem "coderay", "~> 1.1.3"
+gem "jekyll", "~> 3.9.0"
+gem "coderay", "~> 1.1.0"
group :jekyll_plugins do
- gem "jekyll-asciidoc", "~> 3.0.1"
+ gem "jekyll-asciidoc", "~> 2.1.1"
gem "jekyll-seo-tag", "~> 2.7.1"
- gem "jekyll-last-modified-at"
+ gem "jekyll-last-modified-at"
end
-gem "kramdown-parser-gfm"
+gem "kramdown-parser-gfm"
-gem "lms-api"
-gem "just-the-docs"
+gem "github-pages", group: :jekyll_plugins
+gem "lms-api"
+gem "just-the-docs"
-gem "webrick", "~> 1.7"
+gem "webrick", "~> 1.7"
diff --git a/tutorials/assets/week4-react/chakra.png b/tutorials/assets/week4-react/chakra.png
deleted file mode 100644
index 174b861..0000000
Binary files a/tutorials/assets/week4-react/chakra.png and /dev/null differ
diff --git a/tutorials/assets/week4-react/start-details.png b/tutorials/assets/week4-react/start-details.png
deleted file mode 100644
index d9359e6..0000000
Binary files a/tutorials/assets/week4-react/start-details.png and /dev/null differ
diff --git a/tutorials/assets/week4-react/start-screen.png b/tutorials/assets/week4-react/start-screen.png
deleted file mode 100644
index 4af45fb..0000000
Binary files a/tutorials/assets/week4-react/start-screen.png and /dev/null differ
diff --git a/tutorials/assets/week4-react/start.png b/tutorials/assets/week4-react/start.png
deleted file mode 100644
index 5520fb4..0000000
Binary files a/tutorials/assets/week4-react/start.png and /dev/null differ
diff --git a/tutorials/week4-react.md b/tutorials/week4-react.md
deleted file mode 100644
index b22fe62..0000000
--- a/tutorials/week4-react.md
+++ /dev/null
@@ -1,689 +0,0 @@
----
-layout: page
-title: React Tutorial
-permalink: /tutorials/week4-react-basics
-parent: Tutorials
-nav_order: 5
----
-
-# React Basics
-This tutorial covers the basic concepts of react. By the end of this tutorial, you will be able to create a new react app, understand the basic concepts of react such as states and props, understand React hooks and handling events.
-
-- [React Basics](#react-basics)
-- [Creating a new NextJs App](#creating-a-new-next-js-app)
-- [Understanding a React App](#react-component)
- - [Components](#react-component)
- - [Template For Structure of Function Component](#template-for-structure-of-function-component)
- - [Props](#props)
- - [State](#state)
- - [Communicating between Components](#communication-between-components)
- - [Parent to Child](#parent-to-child-component-communication)
- - [Child to Parent](#child-to-parent-component-communication)
- - [Handling Events](#handling-events)
-- [React Hooks](#react-hooks)
- - [UseState](#usestate)
- - [Updating Arrays in State](#updating-arrays-in-state)
- - [UseEffect](#useeffect)
- - [Object Dependencies in UseEffect](#object-dependencies-in-useEffect)
-
-
-## Creating a New Next Js App
-
-Let's use **npx** and **create-next-app** to create a new Next.Js project
-
-- **npx** stands for Node Package Execute (Part of the npm package since version 5.2). It is a runner that can execute any package that you want from the npm registry without even installing that package. In this case npx tool temporarily installs the create-next-app npm package and uses it to create our project.
-
-
-- Please check the following reference to the Next.Js boiler plate and getting started with framework
-[Next.Js official documentation](https://nextjs.org/learn/react-foundations)
-
-1. We use the create-next-app npx package to create an application that creates a fully-featured TS package.
-
- ```bash
- npx create-next-app my-app
- ```
-
- - Note 1: This will create a new project directory called my-app under the current directory.
- - Note 2: This will create a git repo in my-app, so you probably shouldn't do this inside a pre-existing git repository.
- - Note 3: Create the project with the following details after executing the command
- 
-
-2. Navigate to the project directory using the command:
- ```bash
- cd my-app
- ```
-3. To start the development server for React, run the command:
- ```bash
- npm run dev
- ```
- - Note: Next.Js renders the content within the `app/pages.tsx` file as the root component.
-
-4. Navigate to http://localhost:3000/ to see the default react page.
- - After a few seconds, a browser window opens, with our app running:
- 
-5. [Chakra UI components](https://chakra-ui.com) can be reused and the library can be installed for Next.js with following command:
- ```bash
- npm i --save @chakra-ui/react @chakra-ui/next-js
- ```
- 
- > The save flag is used to add the dependency in the package.json file.
-
-
-
-## React Component
-React follows a Component based architecture. A component is a
-repeatable html element with built-in state, business logic, and a
-lifecycle. The component may be something as simple as a single html
-element such as an input box, or a button, or a complex entity made up
-of other components.
-
-Components are the basic building blocks of a React application and they allow the developer to split the UI into independent and reusable
-pieces where each piece can be used in isolation.
-### Creating a Function Component in React
-
-view in sandbox
-
-The simplest method to define a component is to write a function in Javascript. These components are also widely referred as functional stateless components but in the recent versions of React, they have the capabilities to contain state as well.
-```tsx
-import * as React from "react";
-
-interface Props {
- name?: string
-};
-
-function App (props: Props) {
- return (
-
-
Welcome to React with Typescript Tutorial.
-
- );
-}
-
-export default App;
-```
-
-### A Few Things to Note About React Components:
-
-- The root (App) component is the entry point for the React App and all other components are nested in it.
-- We define a function component using a javascript function, passing the props type in as a generic parameter.
-- The import statement is used to import the public classes/functions from the `react` library.
-- A function can return a single top level element.
- - div is the top level element in this case and other elements can be nested in it.
- - The attribute `className` is used to specify a CSS class name if CSS properties have been defined seperately for a class.
- - `className` attribute is used to set the value of an element’s class attribute. Using this property, the user can set the class of an element to the desired class.
-- The round brackets (()) after return are used to span a JSX/TSX element across multiple lines.
-- At last , the component needs to be exported from the current file, so that it can be imported somewhere else and can be used either in isolation or combination with other components for rendering on the UI.
-- Elements on one line can be returned directly.
-- Each instance of a component creates a new element independent of other instances of the component.
-- Each component has its own state, props, and lifecycle (which will be explored later in the tutorial).
-
-## Template For Structure of Function Component
-
-view in sandbox
-
-```tsx
-import * as React from "react";
-
-interface Props {
- property1?: value1,
- property2?: value2
-}
-
-function ComponentName (props: Props) {
- const handler = () => {
- /* ... */
- };
-
- return (
-
Our TSX
- );
-};
-
-ComponentName.defaultProps = {
- /* ... */
-};
-
-export default ComponentName;
-```
-
-## Props
-view in sandbox
-
-React components are similar to JavaScript functions and can accept arbitrary arguments called props. Since components are reusable, props are especially useful to display different content in each instance of the component. Let us extract the header elements from the previous code snippet into a new component called Header. We can then use props to say "hello" to different users.
-
-- Create a new file in `src/` directory called `Header.tsx`
-- Create and export a function called Header in the file as below:
-
-```tsx
-import React from "react";
-
-interface IProps {
- name?: string;
-}
-
-const Header = (props: IProps) => {
- return
Hello, {props.name}
;
-};
-
-Header.defaultProps = {
- name: "World"
-};
-
-export default Header;
-```
-
-- The above code snippet creates a new function component `Header` and prints the value of the `name` passed in the props.
-- It defines a defaultProps for the component `Header` where the default value for `name` is used in case the value for props for `name` is not passed in any instance of the component.
-
-
-- In App.tsx:
- - Remove the code in h1 tags.
- - Import the Header component as below:
- - ```tsx
- import Header from './Header';
- ```
- - Update the contents of return as below:
- - ```tsx
-
-
-
-
-
- ```
- - Save all files and run npm start
-
-A few things to note from the above example:
-
-- Component.defaultProps can be used to specify default values for props.
-- Components are rendered to the user interface and the component’s logic contains the data to be displayed in the view(UI).
-- Curly braces ({}) in JSX/TSX are used as a connection between the data to be displayed in the view and the component’s logic for displaying the data in the view.
- - In our example, `{props.name}` will reflect the value of the property `name` in the view(html) for the cases when the values "John" and "Jane" are passed as props for the `name` property.
- - If no props are passed for an instance of the component, then it will display the default value of props.
-> Note: React uses a special syntax called [JSX](https://react.dev/learn/writing-markup-with-jsx) which allows us to mix HTML with JavaScript. The curly brackets `{}` lets the JSX parser know that the content inside the brackets is JavaScript.
-
-
-## State
-State management is just a means of facilitating data sharing and communication among components. It creates a concrete data structure that you can read and write to reflect the state of your program.
-
-```tsx
-const [counter, setCounter] = useState(0)
-```
-
-The above snippet shows creation of counter state with an intial value of 0. Using the [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment) syntax we extract out the state variable and the function to update the counter value.
-
-In its most basic form, a State object is a JavaScript object that represents the part of a component that can change as a result of a user's action. States can also be thought of as a component's memory.
-
-State update calls are asynchronous. As one cannot expect to call the update state function on one line and expect the state to be updated on the next. The reason for this is that update state methods are more of a request than an immediate order to update state. So React schedules an update to a component’s state object. When state changes, the component responds by re-rendering. Also multiple update request may be batched into one for performance reasons.
-
-Changes in state and/or props will both cause our React component to re-render. Changes in state, on the other hand, can only occur internally as a result of components modifying their own state.
-
-## Communication Between Components:
-
-### Parent To Child Component Communication:
-view in sandbox
-
-
-Passing values from a parent component to a child component is simple. We only have to pass the values as props of the child component. The child component can then use the props object to output results. In the example code you will see that CounterContent component accepts a counter prop which is then used to display the value inside div element.
-```tsx
-import { useState } from "react";
-
-interface CounterContentProps {
- counter: Number;
-}
-
-function CounterContent({ counter }: CounterContentProps) {
- return
Counter: {counter}
;
-}
-
-function Counter() {
- const [counter, setCounter] = useState(0);
-
- return (
- <>
-
-
-
- );
-}
-```
-
-
-### Child to Parent Component Communication
-
-view in sandbox
-
-For passing data from child component to parent component do the following steps:
-1. Declare a callback function inside the parent component. This function will get data from the child component.
-2. Pass the callback function to the child component as props.
-3. Child then sends the update to the parent through the use of the callback function.
-
-In the example below we have four children components:
-1. CounterContent: Displays the counter value
-2. IncrementCounterButton: Increments the counter value
-3. DecrementCounterButton: Decrements the counter value
-4. CustomCounterButton: Sets the counter to a particular value.
-
-All callback functions passed to the children component are declared in Counter function which is the parent component that maintains the state value for counter.
-
-```tsx
-import { useState } from "react";
-
-interface CounterContentProps {
- counter: Number;
-}
-
-interface IncrementCounterButtonProps {
- incrementCount(): void;
-}
-
-interface DecrementCounterButtonProps {
- decrementCount(): void;
-}
-
-interface SetCounterButtonProps {
- setCount(value: number): void;
-}
-
-function CounterContent({ counter }: CounterContentProps) {
- return
Counter: {counter}
;
-}
-
-/**
- * Child component accepts a incrementCount callback function as a props.
- * The callback which is declared inside the parent component triggers a state update.
- */
-function IncrementCounterButton({
- incrementCount
-}: IncrementCounterButtonProps) {
- return ;
-}
-
-/**
- * Child component accepts a decrementCount callback function as a props.
- * The callback which is declared inside the parent component triggers a state update.
- */
-function DecrementCounterButton({
- decrementCount
-}: DecrementCounterButtonProps) {
- return ;
-}
-
-function CustomCounterButton({ setCount }: SetCounterButtonProps) {
- // change this value to see how child passes count value data to parent through
- // the use of callback function
-
- const dummyValue = 100;
-
- return (
-
- );
-}
-
-/**
-* Parent Component where state and callbacks are maintained.
-**/
-function Counter() {
- const [counter, setCounter] = useState(0);
-
- const decrementCount = () => {
- if (counter === 0) return;
- setCounter(counter - 1);
- };
-
- const incrementCount = () => {
- setCounter(counter + 1);
- };
-
- const setCount = (value: number) => {
- setCounter(value);
- };
-
- return (
- <>
-
-
-
-
-
- );
-}
-```
-
-
-# Handling Events
-
-view in sandbox
-
-
-- React impelemnts its own system of handling events that is very similar to handling events on DOM elements. There are some syntax differences:
- - React events are named using camelCase, rather than lower case.
- - With JSX a function can be passed as an event handler instead of a string.
-
-For example, the HTML
-
-```html
-
-```
-
-is slightly different in React:
-
-```html
-
-```
-
-- React provides an equivalent of each event that you might be familiar with from
- standard HTML DOM. Events typing can be imported directly from react as shown in the example below:
-
-```tsx
-import { MouseEvent } from "react";
-
-function HelloWorld() {
- const sayHello = (event: MouseEvent) => {
- event.preventDefault();
- console.log(`${event.currentTarget.tagName}: says hello, world.`);
- };
-
- return (
-
-
-
- );
-}
-export default HelloWorld;
-```
-
-For the list of all the supported events refer [here](https://react-typescript-cheatsheet.netlify.app/docs/basic/getting-started/forms_and_events/#list-of-event-types)
-
-Please check the list of common events and instances in which they are used [here](https://react.dev/reference/react-dom/components/common)
-
-## React Hooks
-
-React hooks are built-in functions which allows us to use state and other lifecycle features. The most basic hooks used by react are useState() which adds a state variable to a react component and useEffect() which is the lifecycle hook for a component. State of component refers to the data it is holding at a particular moment in time.
-
-### useState():
-
-view in sandbox
-
-In this section we will see how we can add state to a React Component using the useState() hook provided by React. The useState hook takes the initial value of the state variable as an argument, the initial state can be any type you want (a string, a number, an array, an object or a function). Only on the first render will the initial value be assigned. Each useState call returns a two-element array. The state variable is the first element of the array, followed by a function to change the variable's value.
-
-1. We'll start by defining and initializing state for the number of times the button is clicked, by adding the state variable as follows:
-
-```tsx
-import {useState} from 'react';
-
-function Counter() {
- const [count, setCount] = useState(0);
- ...
-}
-```
-
-This line of code looks a little strange, so let's break it down:
-
-- When the hook useState() is invoked, it returns an array. Where the first item is the state value, and the second item is a function that updates the state.
-- First, we import the useState from react library.
-- useState is a React function that lets us create state, passing in a default value as a parameter. In our case, we pass it a default value of 0.
-- The useState function returns an array containing two elements:
-- - The first array element contains the current value of state.
-- - The second array element contains a function to set state to a different value.
-- We destructure the array and store the first array element (the state value) in count, and the second array element (the function to set state) in setCount.
-- The rest of the function now has access to the count, via the count variable. The function is also able to increment the count, via the setCount variable.
-
-2. Let's add a function to update the state of the variable:
-
-```tsx
-function incrementCount() {
- setCount(count + 1);
-}
-```
-
-- Now, functions to set the piece of state take in the new state as their parameter.
-
-3. Next we'll make the component return the count along with a button to increment the count when clicked. Final function code will be as follows:
-
-```tsx
-import { useState } from "react";
-function Counter() {
- const [count, setCount] = useState(0);
- function incrementCount() {
- setCount(count + 1);
- }
- return (
-
-
Count: {count}
-
-
- );
-}
-
-export default Counter;
-```
-
-If we give this a try in the running app, we should find the count variable's value to keep incrementing by one every time the button is clicked.
-After we've got our heads around the code needed to define state, accessing and setting state is fairly simple and elegant.
-
-
-#### Updating Arrays in State
-Suppose we want to maintain an array in our state object.
-```tsx
-const [list, setList] = useState([]);
-```
-Now suppose we want to add an element to this list and have the component re-render to reflect the changes. We might try pushing an item to the list like so:
-```tsx
-list.push(element); // doesn't work
-```
-However, React will not re-render the component as it does not detect a change in the state. This is because the object referenced in the state is the same before and after pushing the element, and so to React, the object looks the same because the reference is the same. To get around this, we must invoke the `setList` function to create a new reference so that React will detect the change and re-render the component. The easiest way in this case would be to use the spread operator (`...`) to make a copy of the existing list and push a new element to the new list:
-```tsx
-const newList = [...list]; // copy the current list
-newList.push(element);
-setList(newList)
-```
-
-### useEffect():
-view in sandbox
-
-
-Now let's have a look at how to invoke the code to execute at a certain point in the component's lifecycle.
-Older versions of React consisted of different Lifecycle hooks that allowed a user to hook into various phases of component rendering such as componentDidMount, ComponentDidUpdate, etc. which have all been condensed into a single function called useEffect(). Let us observe how this hook behaves by printing out the count in browser console.
-
-> The new functional component system in React (moving away from class based) added amazing syntactic sugar to the React ecosystem. Use of a hook to control component lifecycle is an example such as the `useEffect()` hook.
-
-1. As always, we will start by importing the function from the react library:
-
-```tsx
-import { useEffect } from "react";
-```
-
-2. Next we will add the function to our existing counter component:
-
-```tsx
-useEffect(() => {
- console.log(`The current count is ${count}`);
-}, []);
-```
-
-Let's break down this code to understand what is happening:
-
-- We use React's useEffect function to hook into the component life cycle.
-- The function takes in an arrow function, which executes when the component is first rendered.
-- The function takes in a second parameter, which determines when our arrow function is called. This parameter is an array of values that, when changed, will cause the arrow function to be invoked. In our case, we pass in an empty array, so our arrow function will never be called after the first render.
-- If we now try the running app and open the console, we'll see that the log within the useEffect only appears once.
-
-3. Let's remove the second parameter into useEffect now:
-
-- If no second parameter is provided, it will cause the arrow function to be invoked first on mount and then on every re-render.
-
-```tsx
-useEffect(() => {
- console.log(`The current count is ${count}`);
-});
-```
-
-- Additionally we can also pass the variable in the array to observe only changes related to a particular value (as below).
-- Now we can see that the component will render everytime the value of count is changed.
-
-```tsx
-useEffect(() => {
- console.log(`The current count is ${count}`);
-}, [count]);
-```
-
-- We can also return a function from the useEffect hook which will be called when the component is unmounted. This is useful for cleaning up any resources that the component may have used.
-
-```tsx
-useEffect(() => {
- console.log(`The current count is ${count}`);
- return () => {
- console.log("The component is unmounting");
- };
-}, [count]);
-```
-
-> Let's break this down:
->
->| | useEffect pattern |
->|-----------------------|------------------------------------------------------|
->| Run on every render | `useEffect(() => { /* ... */ });` |
->| Run when some changes | `useEffect(() => { /* ... */ }, [array of Deps]);` |
->| Run on mount | `useEffect(() => { /* ... */ }, []);` |
->| Run on cleanup | `useEffect(() => { return ( /* ... */ ) });` |
-
-4. Finally, our component counter will look like:
-
-```tsx
-import { useState } from "react";
-import { useEffect } from "react";
-
-function Counter() {
- const [count, setCount] = useState(0);
-
- function incrementCount() {
- setCount(count + 1);
- }
-
- useEffect(() => {
- console.log(`The current count is ${count}`);
- }, [count]);
-
- return (
-
-
Count: {count}
-
-
- );
-}
-
-export default Counter;
-```
-#### Object Dependencies in UseEffect
-Consider a case where useEffect depends on an object:
-```tsx
-import { useState } from "react";
-import { useEffect } from "react";
-
-function Counter() {
- const [counter, setCounter] = useState({ count: 0, increment: 1 });
-
- function incrementCount() {
- counter.count += counter.increment;
- setCounter(counter); // will not cause component to rerender
- }
-
- // Will not get called when incrementCount is called
- useEffect(() => {
- console.log(`The current count is ${counter.count}`);
- }, [counter]);
-
- return (
-
-
Count: {count}
-
-
- );
-}
-
-export default Counter;
-```
-In the example above, we've modified the counter to be an object containing both the current count and the amount to increment the counter by when the button is clicked.
-
-Similar to the list case for useState, updating an attribute of an object and setting the state variable to that same object reference will not cause a re-render, and useEffect will not detect a change in its dependencies, even though we have changed one of the attributes. To properly invoke a useEffect call, we must change the object reference itself:
-
-```tsx
-function Counter() {
- const [counter, setCounter] = useState({ count: 0, increment: 1 });
-
- function incrementCount() {
- // we use the spread operator (...) to make a copy of the object
- setCounter({...counter, count: counter.count + counter.increment});
- }
-
- useEffect(() => {
- console.log(`The current count is ${counter.count}`);
- }, [counter]);
-
- return (
-
-
Count: {count}
-
-
- );
-}
-
-export default Counter;
-```
-
-The useEffect hook will now be invoked with each button click. However, our useEffect is dependent on the entire `counter` object, meaning that a change to any of its attributes will cause the useEffect hook to be called, which is not always a desired behavior. We can get around this by being more specific in our dependency list:
-
-```tsx
-function Counter() {
- const [counter, setCounter] = useState({ count: 0, increment: 1 });
-
- function incrementCount() {
- // we use the spread operator (...) to make a copy of the object
- setCounter({...counter, count: counter.count + counter.increment});
- }
-
- function incrementIncrement() {
- // we use the spread operator (...) to make a copy of the object
- setCounter({...counter, increment: counter.increment + 1});
- }
-
- useEffect(() => {
- console.log(`The current count is ${counter.count}`);
- }, [counter.count]); // Now that we only depend on count, this function will not be called if the incrementIncrement function is called
-
- return (
-