Week 1

Part A: Student Weekly Assignment

  • Work Assigned: Develop a web-based e-commerce application.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Clarification on coding standards and best practices.

Part B: Organisation Assessment

  • Work Accomplished: Completed setup of the e-commerce client admin pages.
  • Problem(s) encountered: Roadblocks encountered in payment gateway integration.
  • Steps taken to solve the problem: Adjusted the API structure and fixed missing fields.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good progress.

Description of Work Done

  • Monday: Set up project + structure using Vite, React and TypeScript; configured tailwindcss and AI.
  • Tuesday: Create routing structure for both client and admin sections using React Router.
  • Wednesday: Developed basic client and admin pages and implemented global state management using context API.
  • Thursday: Built and tested admin dashboard layout with basic CRUD operations.
  • Friday: (Code review and testing); worked on responsive design for mobile view.

Week 2

Part A: Student Weekly Assignment

  • Work Assigned: Continue development of the web-based e-commerce application.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Completed the HTML/Tailwind setup for the project and implemented basic client and admin pages.
  • Problem(s) encountered: Critical error in the database during the login process.
  • Steps taken to solve the problem: Resolved database issues and updated the login process.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Reviewed the existing HTML/Tailwind structure; completed setup for the client and admin pages.
  • Tuesday: Started breaking down HTML into reusable React components (Header, Footer, Hero, etc.).
  • Wednesday: Completed creation of the website structure using React Router and set up routing using Next.js.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 3

Part A: Student Weekly Assignment

  • Work Assigned: All customer orders tracking handled by the E-commerce and Implement an Admin Managing dashboard Staff. In-week two React.js and Redux framework.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Added customer orders tracking page in the client side of the e-commerce app.
  • Problem(s) encountered: Conflicts in styling between Admin and Customer pages.
  • Steps taken to solve the problem: Resolved conflicts by adjusting CSS and using a consistent style guide.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Excellent work, continue with the good pace.

Description of Work Done

  • Monday: Returned and reviewed instructor feedback on weeks 1 and 2 tasks. Added order tracking page in the client side of the e-commerce app.
  • Tuesday: Implemented the managing partners page in the admin dashboard.
  • Wednesday: Tested the enabled functionalities and improved visual identity by adjusting colors and overall styling structure.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 4

Part A: Student Weekly Assignment

  • Work Assigned: Separate the Staff portal from the Showcasing website.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Separated the Staff portal from the main site.
  • Problem(s) encountered: Navigation issues between Staff and public site.
  • Steps taken to solve the problem: Split the codebase and used a subdomain for the Staff portal.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Started creating a new React project using Vite, React, and TailwindCSS; researched character traits for the persona.
  • Tuesday: Merged and refined all the drafted individual persona details.
  • Wednesday: Designed and compiled into a presentation slide.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 5

Part A: Student Weekly Assignment

  • Work Assigned: Build a RESTful API dashboard where owners, renters and agents can be added.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment.

  • Work Accomplished: Developed a personal ‘Miiender’ program organised person and venue details.
  • Problem(s) encountered: Some inconsistencies in forms and listing card
  • Steps taken to solve the problem: Used a reusable card component.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: …

Description of Work Done

  • Monday: Discussed tasks and requirement for persons researching characteristics of potential users/attendees/organisation and vendors.
  • Tuesday: Merged and refined all the drafted individual persona details.
  • Wednesday: Designed and compiled into a presentation slide.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 6

Part A: Student Weekly Assignment

  • Work Assigned: Rebuild a dashboard with schema displaying rules that side dashboard (all) search form featured outputs, top flowers and cakes.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Rebuilt the dashboard with schema displaying rules that side dashboard (all) search form featured outputs, top flowers and cakes.
  • Problem(s) encountered: Inconsistency with styling cards.
  • Steps taken to solve the problem: Used a reusable card component.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Set up Express server with MongoDB for a contact form using express npm package and mongoose ODM for MongoDB.
  • Tuesday: Help a colleague debug her Node app (Backend Server and frontend code).
  • Wednesday: Connected backend API routes (Signup, login, verify) to react frontend, fixed backend issues after authentication.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 7

Part A: Student Weekly Assignment

  • Work Assigned: Continue developing the work dashboard from week 6.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Added top courses and categories filtering.
  • Problem(s) encountered: Incorrect results.
  • Steps taken to solve the problem: Reimplemented filtering logic and tested with multiple courses.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Created the Search form functionality for searching courses. Also helped a course mate about her project.
  • Tuesday: Refactored and organized the codebase for better readability and maintainability.
  • Wednesday: Asked for clarification on how to offer top courses and featured courses, and implemented them along with categories section.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 8

Part A: Student Weekly Assignment

  • Work Assigned: Be well asked to come up with a pivoted topic and prepare a presentation slide for the SWOT analysis of the selected media API.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on how to conduct SWOT analysis and present a SWOT analysis for a startup idea.

Part B: Organisation Assessment

  • Work Accomplished: Set up an event booking platform including the frontend, backend, and database.
  • Problem(s) encountered: Difficulty in aligning all group members’ ideas.
  • Steps taken to solve the problem: Help discussions and reached consensus on the analysis.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Introduction to Entrepreneurship class and explanation of the group project to brainstorm ideas in groups and select a topic.
  • Tuesday: Worked on SWOT Analysis (Strengths, Weaknesses, Opportunities, and Threats of the project).
  • Wednesday: Compiled findings into a presentation slide.
  • Thursday: Group review and final touch-ups on the presentation slide.
  • Friday: (No work done)

Week 9

Part A: Student Weekly Assignment

  • Work Assigned: Design and build an extensive capital website platform for a growing company in the technology and consumer sector.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication and handling keyC form best practices for investors.

Part B: Organisation Assessment

  • Work Accomplished: Designed and completed a website prototype using HTML/CSS and JavaScript.
  • Problem(s) encountered: Failed challenges with creating Tailwind Shadows in React Router.
  • Steps taken to solve the problem: Debugged and corrected reading paths in React Router.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Began designing the website prototype in Figma; completed 5/10 page layouts (Home, About, Investment, Plans, Shariah Compliance Team, Contact).
  • Tuesday: Developed the UI using TailwindCSS as a shorthand UI components and set up routing using Next.js.
  • Wednesday: Resolved running issues and implemented Sign up/login and keyC form for investors.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 10

Part A: Student Weekly Assignment

  • Work Assigned: We were tasked to come up with a persona for the project and start building.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on identifying key user characteristics and persona design.

Part B: Organisation Assessment

  • Work Accomplished: Developed a personal ‘Miiender’ program organized person and vendor design.
  • Problem(s) encountered: …
  • Steps taken to solve the problem: …
  • Work outstanding from last week’s primary assignment: …
  • Comment by immediate supervisor: …

Description of Work Done

  • Monday: Discussed tasks and requirement for persons/researched characteristics of potential users/attendees/organizers and vendors.
  • Tuesday: Merged and refined all the drafted individual persona details.
  • Wednesday: Designed and compiled into a presentation slide.
  • Thursday: (No work done)
  • Friday: (No work done)

We

ek 11

Part A: Student Weekly Assignment

  • Work Assigned: Deliver into backend development using node.js build an Express Server, middleware to manage user signup.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on connecting Express with MongoDB.

Part B: Organisation Assessment

  • Work Accomplished: Set up contact form served by Express.js and ImmersalDB.
  • Problem(s) encountered: Not Redirecting after form submission.
  • Steps taken to solve the problem: Had to correct “success” endpoint to be redirected to.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Keep going.

Description of Work Done

  • Monday: Set up Express Server with MongoDB for a contact form using express npm package and mongoose ODM for MongoDB.
  • Tuesday: Help a colleague debug her Node app (Backend Server and frontend code).
  • Wednesday: (No work done)
  • Thursday: (No work done)
  • Friday: (No work done)

Week 12

Part A: Student Weekly Assignment

  • Work Assigned: Update and complete the vendor capital website (week 9 project).
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Updated content on vendor capital website as instructed.
  • Problem(s) encountered: Issues with the JSON request.
  • Steps taken to solve the problem: Had to configure body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Updated and changed content on the vendor’s capital website (Investment plans page).
  • Tuesday: Set up a new Express server using Hypescript and connected it to MongoDB database for the Social media API.
  • Wednesday: (No work done)
  • Thursday: (No work done)
  • Friday: (No work done)

Week 13

Part A: Student Weekly Assignment

  • Work Assigned: Set up an Express server for the vendor capital website.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Set up Express server for the vendor and connected it to the backend.
  • Problem(s) encountered: Challenges with configuring environment variables.
  • Steps taken to solve the problem: Had to install dotenv npm package.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Set up Express server and installed dependencies (Express, mongoose, swig to begin).
  • Tuesday: Proposed and implemented user schema in the Authentication and verification fields in MongoDB.
  • Wednesday: Connected backend API routes (Signup, login, verify) to react frontend, fixed backend issues after authentication.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 14

Part A: Student Weekly Assignment

  • Work Assigned: Continue development of the Social Media API.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Successfully deployed the API to Vercel for live testing.
  • Problem(s) encountered: Connecting MongoDB Atlas to the deployed API.
  • Steps taken to solve the problem: Had to add env variable to Vercel.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Added Post schema using mongoose, defining fields such as title, content, author, and timestamps.
  • Tuesday: Built Posts (create) to handle (creating), fetching and managing posts.
  • Wednesday: Connected push and user models associating them with each other, and deploy the API to Vercel.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 15

Part A: Student Weekly Assignment

  • Work Assigned: Refactor the backend server and deploy it on a deployment platform.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on deploying applications.

Part B: Organisation Assessment

  • Work Accomplished: Successfully deployed the backend server on a platform.
  • Problem(s) encountered: Errors in server deployment configuration.
  • Steps taken to solve the problem: Debugged issues and configured environment variables.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Keep going.

Description of Work Done

  • Monday: Refactored the Express server for modularity and scalability, prepared the backend for deployment and tested the production build of react app.
  • Tuesday: Deploy the Series and hosted the frontend on a platform.
  • Wednesday: Create admin endpoint (get all users, verify user) added email verification in the frontend.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 16

Part A: Student Weekly Assignment

  • Work Assigned: Add a crucial component on homepage in the food catering (order/deliver) Implement a meal to lunchbox using Semba.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Set up a component structure application for meal delivery including meal delivery and lunchbox.
  • Problem(s) encountered: Coding and data reading.
  • Steps taken to solve the problem: Had to correct body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Added a dynamic caused component on the home page (controllable family through the admin dashboard).
  • Tuesday: Designed and implemented a carousel component in the homepage, built admin panel (labels for adding and removing carousel items dynamically).
  • Wednesday: Updated about page with the company’s mission and model canvas, integrated student designed API for meal slots + buy, and tested email testing.
  • Thursday: Created startup application for the end and connect it to the backend.
  • Friday: (No work done)

Week 17

Part A: Student Weekly Assignment

  • Work Assigned: Implement (private) verification form to allow the creation of users (personal details) corporate level and support.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Clarification on verification form fields.

Part B: Organisation Assessment

  • Work Accomplished: Set up the verification form.
  • Problem(s) encountered: Conflict with input elements because LUSE reusable component.
  • Steps taken to solve the problem: Reimplemented body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Designed the duplicate schema for corporate verification.
  • Tuesday: Implemented new API endpoints for submission and retrieval by admin.
  • Wednesday: Integrated API with the frontend using React context and implemented corporate verification page for admin.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 18

Part A: Student Weekly Assignment

  • Work Assigned: Implement customer support and manage user signup for the platform.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Successfully built an API to verify user information.
  • Problem(s) encountered: Issues with the JSON request.
  • Steps taken to solve the problem: Had to configure body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Created new API endpoints for super admin to create and delete subadmins.
  • Tuesday: Built (create sub admin) Subadmin project with form validation and build and integration.
  • Wednesday: Updated user filling logic to ensure subadmin is registered with super admin and super admin.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 19

Part A: Student Weekly Assignment

  • Work Assigned: Continue debugging and set up continuous integration.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Asked AT.

Part B: Organisation Assessment

  • Work Accomplished: Set up services for the view and connect it to the backend.
  • Problem(s) encountered: Challenges with configuring environment variables.
  • Steps taken to solve the problem: Had to install dotenv npm package.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Fixed minor bugs in backend API routes and UI.
  • Tuesday: Set up new pm2 project in a new panel for app management and created new website page.
  • Wednesday: Configured these proxies and verified CI/CD deployment flow.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 20

Part A: Student Weekly Assignment

  • Work Assigned: Develop a tools API with full fledged authentication.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Built the tools API.
  • Problem(s) encountered: Connecting better with the prisma ORM.
  • Steps taken to solve the problem: Had to check documentation and resolve the issues.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Keep going.

Description of Work Done

  • Monday: Set up the project structure and installed dependencies (React, prisma, tailwindcss), studied React Query, Bell, Auth, Express, etc.
  • Tuesday: Implemented Signup and login authentication flow, using React Router, main and pass, and Google Signin using Bell.
  • Wednesday: Developed template (RUP operations for todos (create, read, update, and delete).
  • Thursday: (No work done)
  • Friday: (No work done)

Week 21

Part A: Student Weekly Assignment

  • Work Assigned: Develop a business application that will allow business owners to manage their sales and make decisions on how to invest more effectively.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Set up the project structure for the client and server.
  • Problem(s) encountered: Issues with the JSON request.
  • Steps taken to solve the problem: Had to correct “success” endpoint to be redirected to.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Keep going.

Description of Work Done

  • Monday: Conducted research and planning for the app to populate a tools library and architecture to be used for both the frontend and backend.
  • Tuesday: Set up the entire project structure for the client and server, installed all required dependencies and added project routing and navigation setup.
  • Wednesday: Designed and developed the full marketing landing page for the app, implemented Hero-Scener, Startup features etc.
  • Thursday: Aided basic animation and improved layout.
  • Friday: (No work done)

Week 22

Part A: Student Weekly Assignment

  • Work Assigned: Continue development of the authentication system and set up the login task for the platform.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Set up the verification form and attached it to the API project.
  • Problem(s) encountered: Issues with the JSON request.
  • Steps taken to solve the problem: Had to configure body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Wrote database models with prisma, configured Better Auth for support organizations, set up protected routing and completed the citizen setting page.
  • Tuesday: Implemented organization creation flow, built organization pages and added member management page with different roles.
  • Wednesday: Prototyped backend endpoints for products and sales and updated the prisma model to support analytics.
  • Thursday: (No work done)
  • Friday: (No work done)

Week 23

Part A: Student Weekly Assignment

  • Work Assigned: Build the core dashboard into the platform for regular email verification on a sample deployment using Docker for both client and server.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Built the dashboard.
  • Problem(s) encountered: Issues with the JSON request.
  • Steps taken to solve the problem: Had to configure body-parser.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Good work, keep it up.

Description of Work Done

  • Monday: Built dashboard kept, empty state components and seller entry form and introduced product (rename).
  • Tuesday: Set up automatic deployment with docker files on railing for both the client and server, configured environment variables and nginx to bundle deployment for the MVP.
  • Wednesday: (No work done)
  • Thursday: (No work done)
  • Friday: (No work done)

Week 24

Part A: Student Weekly Assignment

  • Work Assigned: Fix existing errors, implement reporting APIs for daily, weekly, and monthly business insights and key metrics.
  • Would students need assistance this week? YES/NO
  • If YES state the type of assistance: Guidance on integrating authentication.

Part B: Organisation Assessment

  • Work Accomplished: Fixed errors in the dashboard, created user interface for daily, weekly, and monthly reports.
  • Problem(s) encountered: Challenges with output for the generated reports.
  • Steps taken to solve the problem: Grouped data by date ranges.
  • Work outstanding from last week’s primary assignment: None.
  • Comment by immediate supervisor: Keep going.

Description of Work Done

  • Monday: Fixed prior issues in the dashboard implemented daily, weekly and monthly reports UI.
  • Tuesday: Implemented CSV and PDF exports API and added MTP metrics for revenue push and expenses.
  • Wednesday: Tested report accuracy and export functionality and fixed some errors.
  • Thursday: (No work done)
  • Friday: (No work done)