Update projects

Author: ctrl-vi

src/assets/333gle-homepage.png

@@ -1,13 +1,14 @@
 ---
-import type { CollectionEntry } from "astro:content";
 import { Image } from "astro:assets";
 
 import astro from "@cardIcons/astro.png";
 import cesium from "@cardIcons/cesium.png";
 import coreml from "@cardIcons/coreml.webp";
+import c from "@cardIcons/c.png";
 import cpp from "@cardIcons/cpp.png";
 import css from "@cardIcons/css.png";
 import figma from "@cardIcons/figma.svg";
+import gdb from "@cardIcons/gdb.jpg";
 import github from "@cardIcons/github.svg";
 import gitlab from "@cardIcons/gitlab.png";
 import html from "@cardIcons/html.png";
@@ -20,6 +21,7 @@ import python from "@cardIcons/python.png";
 import react from "@cardIcons/react.png";
 import ros2 from "@cardIcons/ros2.png";
 import swift from "@cardIcons/swift.webp";
+import valgrind from "@cardIcons/valgrind.png";
 import verilog from "@cardIcons/verilog.png";
 import vite from "@cardIcons/vite.png";
 import wpilib from "@cardIcons/wpilib.png";
@@ -45,10 +47,12 @@ const kvArray: [string, ImageMetadata][] = [
     ["astro", astro],
     ["cesium", cesium],
     ["coreml", coreml],
+    ["c", c],
     ["cpp", cpp],
     ["c++", cpp],
     ["css", css],
     ["figma", figma],
+    ["gdb", gdb],
     ["github", github],
     ["gitlab", gitlab],
     ["html", html],
@@ -62,11 +66,12 @@ const kvArray: [string, ImageMetadata][] = [
     ["ros2", ros2],
     ["react", react],
     ["swift", swift],
+    ["valgrind", valgrind],
     ["verilog", verilog],
     ["vite", vite],
     ["wpilib", wpilib],
 ];
-const iconMap = new Map<string, ImageMetadata>(kvArray);
+const iconMap = new Map<string, ImageMetadata | string>(kvArray);
 
 function formatDate(date?: Date) {
     if (date == null) {

src/assets/cardIcons/c.png

@@ -0,0 +1,33 @@
+// Declarations to allow importing image files and the @cardIcons alias in TypeScript
+
+// Alias pattern for @cardIcons/* (maps to src/assets/cardIcons/* in tsconfig)
+declare module '@cardIcons/*' {
+  const src: string;
+  export default src;
+}
+
+// Generic image module declarations
+declare module '*.png' {
+  const src: string;
+  export default src;
+}
+
+declare module '*.jpg' {
+  const src: string;
+  export default src;
+}
+
+declare module '*.jpeg' {
+  const src: string;
+  export default src;
+}
+
+declare module '*.webp' {
+  const src: string;
+  export default src;
+}
+
+declare module '*.svg' {
+  const src: string;
+  export default src;
+}

src/assets/cardIcons/gdb.jpg

@@ -0,0 +1,135 @@
+---
+article: 
+    publishedTime: "2025-11-25T02:55:00-08:00"
+    modifiedTime: "2025-11-25T02:55:00-08:00"
+    authors: ["Violet Monserate"]
+    section: Class Projects
+    tags: ["c", "c++", "gdb", "valgrind", "gitlab"]
+layout: '@components/MarkdownProjectLayout.astro'
+title: File Explorer
+description: Individual project for CSE 333 Systems Programming course, linking a web server to an inverted index of a file directory
+seoDescription: Group project for CSE 440 Human-Computer Interaction course, where we researched and developed a novel commercial product
+image:
+    src: "@assets/333gle-homepage.png"
+    alt: "Homepage for 333gle: web interface for file explorer. The query is currently 'hello world' and shows a couple links related to the query hello world"
+startDate: '2025-01'
+finishDate: '2025-03'
+icons: ["c", "c++", "gdb", "valgrind", "gitlab"]
+---
+
+![Homepage for 333gle: web interface for file explorer. The query is currently 'hello world' and shows a couple links related to the query hello world](@assets/333gle-homepage.png) 
+
+---
+
+## Key Tools
+
+In order to ensure that my code was working, I utilized 2 debugging tools:
+- **GDB**: This allowed me to go instruction by instruction and inspect the state of the program, which was especially useful when tracking "segfaults"
+- **Valgrind**: This allowed me to see how memory was being utilized by our program, and ensure that we were allocating and freeing memory correctly.
+
+
+## Homework 1: C Data Structures Implementation
+
+### Overview
+Implemented two fundamental C data structures from scratch:
+- **Doubly-linked list** with iterator support
+- **Chained hash table** with dynamic resizing
+
+### Key Features
+- **Generic payload support** for storing arbitrary data types
+- **Memory management** with proper malloc/free handling
+- **Iterator abstractions** for safe data structure traversal
+- **Robust error handling** using Verify333 assertions
+
+### Technical Implementation
+- **LinkedList**: Managed head/tail pointers with node splicing logic
+- **HashTable**: Used FNV hashing with separate chaining collision resolution
+- **Memory safety**: Comprehensive Valgrind testing for leaks and errors
+- **Code quality**: Followed Google C++ style guide with cpplint validation
+
+## Homework 2: In-Memory Search Engine
+
+### Overview
+Built a file system crawler, indexer, and query processor using HW1 data structures.
+
+### Components Implemented
+
+#### Part A: File Parser
+- **Text file ingestion** with memory-efficient string handling
+- **Word parsing** using alphabetic character separation
+- **Position tracking** with byte offset recording
+- **Case normalization** converting all words to lowercase
+
+#### Part B: Crawler and Indexer
+- **Recursive directory traversal** with document ID assignment
+- **Inverted index construction** mapping words → documents → positions
+- **Document table management** for filename ↔ docID bidirectional lookup
+
+#### Part C: Query Processor
+- **Multi-word query processing** with result intersection
+- **Ranking algorithm** based on term frequency summation
+- **Interactive shell** with console-based user interface
+
+### Data Structures Used
+- Document table: Dual hash tables for bidirectional lookup
+- Inverted index: Nested hash tables (word → docID → positions)
+- Position tracking: Linked lists maintaining sorted offsets
+
+## Homework 3: Disk-Based Search Engine
+
+### Overview
+Extended HW2 search engine to persistent storage with architecture-neutral file format.
+
+### Components Implemented
+
+#### Part A: Index Marshaller
+- **Big-endian serialization** for cross-platform compatibility
+- **Complex file format** with header, doctable, and index regions
+- **Checksum validation** for data integrity verification
+- **Hierarchical data storage** maintaining in-memory structure relationships
+
+#### Part B: Index Reader
+- **C++ class hierarchy** for file-based data structure access
+- **Efficient lookup algorithms** for query processing
+- **Memory-mapped style access** without full file loading
+
+#### Part C: Multi-Index Search Shell
+- **Multiple index file support** for distributed searching
+- **Rank aggregation** across multiple corpora
+- **Interactive query interface** with result merging
+
+### File Format Features
+- Magic number identification (0xCAFEF00D)
+- Embedded hash tables with bucket chaining
+- Variable-length string storage
+- Position list compression and sorting
+
+## Final Project: Web Server Security & Session Management
+
+### Security Features Implemented
+
+#### Session Management
+- **Secure cookie generation** with session tracking
+- **HMAC-SHA256 protection** against cookie tampering
+- **Session validation** with cryptographic verification
+
+#### Authentication System
+- **Login page** with credential processing
+- **Admin cookie minting** for privileged access
+- **Plaintext authentication** (noted as potential security concern)
+
+#### Access Control
+- **Admin-only routes** (`/quitquitquit` endpoint protection)
+- **Protected file access** for `$(BASE_DIR)/admin` contents
+- **Role-based authorization** using session cookies
+
+#### Administrative Features
+- **Server logging** of client requests and activities
+- **Admin dashboard** with system overview
+- **Navigation system** with role-appropriate links
+
+### Technical Implementation Details
+- **Cookie security**: HMAC verification prevents unauthorized modifications
+- **Access enforcement**: Session validation on protected endpoints
+- **User experience**: Seamless navigation between public and admin areas
+- **Monitoring**: Comprehensive request logging for administrative oversight

src/assets/cardIcons/valgrind.png

@@ -21,3 +21,8 @@ icons: ["java", "postgres"]
 
 ---
 
+## [WIP] Overview
+
+In this project, I learned about how to link an application to a database, specifically through the use of JDBC, while also going through the whole process of designing a database, including generating an ER diagram to include every entity and relationship we'd possibly need. 
+
+*MORE DETAILS TO COME SOON (PLUS PHOTOS!)*