Add "Adding your own error / warning"

Author: alvinng4

content/docs/API/error_types.mdx

@@ -77,4 +77,62 @@ screaming snake case. For example, `ResourceWarning` becomes `CTB_RESOURCE_WARNI
     ├── SecurityWarning
     ├── ParseWarning
     └── UserWarning
+```
+
+## Adding your own error / warning
+It is easy to add your own error / warning code. Let's say we want to add `CustomError1`,
+simply follow the steps:
+<Steps>
+    ### Add error code at `include/c_traceback/error_codes.h`
+    Add custom error code at the bottom of `typedef enum CTB_Error`:
+    ```c {14}
+    typedef enum CTB_Error
+    {
+
+        CTB_SUCCESS = 0,
+        CTB_UNKNOWN_ERROR = -1,
+
+        ...
+
+        /* --- Dynamic Link Errors (900-999) --- */
+        CTB_DYNAMIC_LINK_ERROR = 900,
+        CTB_LIBRARY_LOAD_ERROR,
+
+        /* --- 1000+: application-specific --- */
+        CUSTOM_ERROR_1 = 1000,
+    }
+    ```
+
+    ### Add name mapping at `src/error_codes.c`
+    Add the mapping at the bottom of `error_to_string(CTB_Error error)`:
+    ```c {15}
+    const char *error_to_string(CTB_Error error)
+    {
+        switch (error)
+        {
+            case CTB_SUCCESS:                       return "Success";
+            case CTB_UNKNOWN_ERROR:                 return "Unknown Error";
+
+            ...
+
+            /* Dynamic Link */
+            case CTB_DYNAMIC_LINK_ERROR:            return "DynamicLinkError";
+            case CTB_LIBRARY_LOAD_ERROR:            return "LibraryLoadError";
+
+            /* Application */
+            case CUSTOM_ERROR_1:                    return "CustomError1";
+
+            default:                                return "Unrecognized Error Code";
+        }
+    }
+    ```
+</Steps>
+Now you should be able to use it directly:
+```ansi
+────────────────────────────────────────────────────────────────────────────────
+Traceback (most recent call last):
+  (#00) File "/home/alvinng/Desktop/project/project.c", line 6 in main:
+    <Error thrown here>
+CustomError1
+────────────────────────────────────────────────────────────────────────────────
 ```

content/docs/index.mdx

@@ -2,8 +2,6 @@
 title: Get started
 ---
 
-import {Steps} from 'nextra/components'
-
 # Get started
 
 Below is a quick guide for installing C Traceback into your project.
@@ -14,7 +12,7 @@ Before putting C Traceback into your project, you can first try the
 examples.
 Simply follow the steps below.  
 
-Note: `CMake` is required.
+Note: `CMake` is required for building examples.
 
 <Steps>
     ### Install CMake if needed
@@ -65,16 +63,15 @@ Note: `CMake` is required.
 
 ## Setting up a simple project
 
-Adding C Traceback to your project is simple. However, the actual method
+Adding C Traceback to your project is simple. However, the actual setup
 depends on your directory structure. For demonstration, let's setup
 a simple project together:
 
 <FileTree>
     <FileTree.Folder name="project" defaultOpen>
         <FileTree.File name="project.c" />
         <FileTree.File name="CMakeLists.txt" />
-        <FileTree.Folder name="c_traceback">
-        </FileTree.Folder>
+        <FileTree.Folder name="c_traceback" />
     </FileTree.Folder>
 </FileTree>
 

mdx-components.tsx

@@ -1,5 +1,5 @@
 import {useMDXComponents as getThemeComponents} from 'nextra-theme-docs';
-import {Callout, FileTree, Tabs} from "nextra/components";
+import {Callout, FileTree, Tabs, Steps} from "nextra/components";
 
 import { Badge } from "components/ui/badge";
 
@@ -14,5 +14,6 @@ export function useMDXComponents() {
         Callout: Callout,
         FileTree: FileTree,
         Tabs: Tabs,
+        Steps: Steps,
     }
 }