Category: Website Design

  • Database architecture and technical logic for a Laravel-base…

    1. Database Schema Design

    A normalized relational database (MySQL) is ideal for maintaining data integrity.

    • Users & Roles: Tables for users, roles, and permissions to distinguish between customers, admins, and vendors.
    • Product Management:
      • categories: Hierarchical structure (parent/child) for navigation.
      • products: Main details like name, SKU, and description.
      • product_variants: Handles attributes like size, color, and price variations.
    • Inventory & Orders:
      • stocks: Tracks quantity per variant or warehouse.
      • orders: High-level data (total, status, user_id).
      • order_items: Snapshot of products at the time of purchase (price, quantity).
    • Search & Filters: attributes and attribute_values tables to power dynamic sidebar filtering.

    2. Core Technical Logic

    Implementing these patterns ensures the site remains fast and reliable as it grows.

    Live Filtering & Search

    To provide a smooth user interface, use Laravel Scout with an engine like Algolia or Meilisearch.

    • Logic: As a user clicks a “fixed left sidebar” category, an AJAX or Livewire request triggers a query that filters the products table based on attribute_values.
    • Optimization: Use Eager Loading (with('variants')) to prevent N+1 query issues when displaying many products.

    Shopping Cart & Checkout

    • Persistence: Use a database-backed cart for logged-in users so their items follow them across devices.
    • Atomic Transactions: Wrap the checkout process in a DB::transaction. This ensures that if the payment fails, the stock isn’t deducted and the order isn’t createdmaintaining “all or nothing” integrity.
    • Validation: Always re-validate prices and stock levels on the server side at the moment the “Place Order” button is clicked.

    Image Manipulation

    For a professional retail look, you can automate background removal or resizing during the upload process.

    • Tooling: Use the Spatie Media Library or Intervention Image (a PHP library) to handle Photoshop-like manipulations, such as generating thumbnails or removing backgrounds, directly within Laravel.

    3. Scalability Considerations

    • Caching: Store frequent queries (like category lists) in Redis to reduce database hits.
    • Queues: Offload time-consuming tasks like sending order confirmation emails or processing image uploads to Laravel Queues.
  • Tolong bantu selesaikan soal matematika aljabar

    Halo, saya membutuhkan bantuan untuk mengerjakan soal matematika aljabar. Mohon jelaskan langkah-langkah penyelesaiannya agar saya bisa memahami cara mengerjakannya. Jika memungkinkan, sertakan juga rumus yang digunakan dan penjelasan singkatnya. Terima kasih.

  • UX Major Project

    Hey bro, hope youre good. I really need your help with my UX assignment for Weeks 910. I didnt do well in the first assessment and got 5/15, so Im trying to improve this one properly. I already fixed the second assessment, but the marks still havent been released yet. Ill send you the assignment file because it includes the scenario, template, instructions, and everything needed. Ill also send my Week 57 assessment since it might help you understand what I already did. Please follow the instructions carefully and help me finish the rest properly because I really want to get a much better mark this time.

  • amazon website

    Make me a project using wordpress. It will be pretty much amazon but for university students and I want it to match the poster. Keep it very simple and don’t make it too complicated. All the information for the login for aws and wordpress. There is no coding needed just make everything look nice and work.

  • IT404_WD Q

    Question One

    Design the basic structure of a professional academic service website titled:

    Smart Campus Portal

    Requirements:

    1.Create a minimum of 4 interconnected pages (Home, Services, Registration, Contact).

    2.Use correct HTML5 document structure including:

    oDOCTYPE

    ometa charset

    oviewport

    osemantic elements (header, nav, main, section, article, footer)

    3.Implement:

    oA structured navigation bar linking all pages

    oAn academic schedule table using rowspan and colspan

    4.Create a complete registration form using:

    otext, email, number, radio, checkbox

    orequired attributes

    ofieldset and legend

    The structure must reflect professional organization and real-world web design standards.

    Question Two

    Apply professional styling using external CSS only:

    1.Implement layout using Flexbox or Grid.

    2.Use:

    ofont stack

    oem or rem sizing

    oHEX or RGB color system

    3.Apply:

    opseudo-classes (:hover, :focus)

    opseudo-elements (::before or ::after)

    4.Implement:

    oResponsive design with at least 2 breakpoints

    oMobile-first approach

    5.Include:

    oCSS transition or transform effect

    The design must maintain consistency across all pages and reflect usability principles.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    1.A Word file (.docx) containing your report (screenshots and code).

    2.A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

    Question Three

    Enhance the website with dynamic functionality:

    1.Link an external JavaScript file.

    2.Use:

    oVariables

    oCondition (if statement)

    oLoop (for or while)

    3.DOM Manipulation:

    ogetElementById()

    oquerySelector()

    4.Implement:

    oDark/Light mode toggle

    oDynamic form validation with custom error messages

    5.Use addEventListener() for at least one interactive event.

    The JavaScript functionality must improve user interaction and usability.

    Question Four

    Submit a concise structured report (12 pages) explaining:

    1.Design rationale (color, layout, typography).

    2.Target audience and usability considerations.

    3.How the design meets real-world academic portal standards.

    4.Reflection on improvements.

    You can work on it individually or as a group of a maximum of 3 members.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    3.A Word file (.docx) containing your report (screenshots and code).

    4.A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

  • IT404_WD Q

    Question One

    Design the basic structure of a professional academic service website titled:

    Smart Campus Portal

    Requirements:

    1.Create a minimum of 4 interconnected pages (Home, Services, Registration, Contact).

    2.Use correct HTML5 document structure including:

    oDOCTYPE

    ometa charset

    oviewport

    osemantic elements (header, nav, main, section, article, footer)

    3.Implement:

    oA structured navigation bar linking all pages

    oAn academic schedule table using rowspan and colspan

    4.Create a complete registration form using:

    otext, email, number, radio, checkbox

    orequired attributes

    ofieldset and legend

    The structure must reflect professional organization and real-world web design standards.

    Question Two

    Apply professional styling using external CSS only:

    1.Implement layout using Flexbox or Grid.

    2.Use:

    ofont stack

    oem or rem sizing

    oHEX or RGB color system

    3.Apply:

    opseudo-classes (:hover, :focus)

    opseudo-elements (::before or ::after)

    4.Implement:

    oResponsive design with at least 2 breakpoints

    oMobile-first approach

    5.Include:

    oCSS transition or transform effect

    The design must maintain consistency across all pages and reflect usability principles.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    1.A Word file (.docx) containing your report (screenshots and code).

    2.A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

    Question Three

    Enhance the website with dynamic functionality:

    1.Link an external JavaScript file.

    2.Use:

    oVariables

    oCondition (if statement)

    oLoop (for or while)

    3.DOM Manipulation:

    ogetElementById()

    oquerySelector()

    4.Implement:

    oDark/Light mode toggle

    oDynamic form validation with custom error messages

    5.Use addEventListener() for at least one interactive event.

    The JavaScript functionality must improve user interaction and usability.

    Question Four

    Submit a concise structured report (12 pages) explaining:

    1.Design rationale (color, layout, typography).

    2.Target audience and usability considerations.

    3.How the design meets real-world academic portal standards.

    4.Reflection on improvements.

    You can work on it individually or as a group of a maximum of 3 members.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    3.A Word file (.docx) containing your report (screenshots and code).

    4.A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

  • IT404_WEBD

    Question One

    Design the basic structure of a professional academic service website titled:

    Smart Campus Portal

    Requirements:

    1. Create a minimum of 4 interconnected pages (Home, Services, Registration, Contact).

    2. Use correct HTML5 document structure including:

    o DOCTYPE

    o meta charset

    o viewport

    o semantic elements (header, nav, main, section, article, footer)

    3. Implement:

    o A structured navigation bar linking all pages

    o An academic schedule table using rowspan and colspan

    4. Create a complete registration form using:

    o text, email, number, radio, checkbox

    o required attributes

    o fieldset and legend

    The structure must reflect professional organization and real-world web design standards.

    Question Two

    Apply professional styling using external CSS only:

    1. Implement layout using Flexbox or Grid.

    2. Use:

    o font stack

    o em or rem sizing

    o HEX or RGB color system

    3. Apply:

    o pseudo-classes (:hover, :focus)

    o pseudo-elements (::before or ::after)

    4. Implement:

    o Responsive design with at least 2 breakpoints

    o Mobile-first approach

    5. Include:

    o CSS transition or transform effect

    The design must maintain consistency across all pages and reflect usability principles.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    1. A Word file (.docx) containing your report (screenshots and code).

    2. A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

    Question Three

    Enhance the website with dynamic functionality:

    1. Link an external JavaScript file.

    2. Use:

    o Variables

    o Condition (if statement)

    o Loop (for or while)

    3. DOM Manipulation:

    o getElementById()

    o querySelector()

    4. Implement:

    o Dark/Light mode toggle

    o Dynamic form validation with custom error messages

    5. Use addEventListener() for at least one interactive event.

    The JavaScript functionality must improve user interaction and usability.

    Question Four

    Submit a concise structured report (12 pages) explaining:

    1. Design rationale (color, layout, typography).

    2. Target audience and usability considerations.

    3. How the design meets real-world academic portal standards.

    4. Reflection on improvements.

    You can work on it individually or as a group of a maximum of 3 members.

    Submission Guidelines

    The project must be submitted on Blackboard by ONE member of the group.

    Your HTML, CSS, and JavaScript code must be pasted as editable text into your report, not as screenshots.

    You must include screenshots of your output pages in the report file.

    Files to Submit

    You must upload the following files:

    3. A Word file (.docx) containing your report (screenshots and code).

    4. A PDF file (.pdf) of the same report.

    A Zip file (.zip) containing all the project files (HTML, CSS, JavaScript, and images)

  • Bubble.io Developer Needed Build & Optimize Dealer…

    Im building a private multi-dealership inventory portal using Bubble.io and need an experienced Bubble developer to help complete and optimize the platform.

    The system is already partially built and live on a custom domain. Core functionality exists, but I need help refining workflows, fixing bugs, and scaling the platform properly.

    Project Overview:
    This is a dealer portal where multiple dealerships can log in and upload wholesale inventory. Each dealership has its own private dashboard, and only admin can see all listings.

    Whats already built:

    • User authentication (login/signup)
    • Dealer dashboard UI
    • Vehicle listing creation (form + database)
    • Image upload (partially working)
    • Basic workflows for creating listings

    What I need help with:

    • Fixing image upload/display consistency
    • Cleaning up and optimizing workflows
    • Improving database structure (VehicleListings, VehiclePhotos, etc.)
    • Role-based permissions (admin vs dealership users)
    • UI/UX improvements (make it clean and fast)
    • Messaging system between admin and dealers
    • Preparing the app for scale (future marketplace expansion)

    Nice to have (future phases):

    • Multi-image galleries per vehicle
    • Advanced filtering/search
    • Activity tracking/logs
    • Notifications system
    • Mobile optimization

    Requirements:

    • Strong experience with Bubble.io (must show past projects)
    • Understanding of database structure & workflows in Bubble
    • Ability to troubleshoot and explain fixes clearly
    • Good communication (I want to move fast)

    Project Type:

    • Ongoing work (not just one-time fix)
    • I want someone I can continue working with long-term

    To apply:

    • Send examples of Bubble apps youve built
    • Briefly explain how youd approach fixing a broken image upload/display system
    • Confirm availability (I want to start ASAP)

    Budget:
    Flexible based on experience and speed

    Im serious about building this into a large-scale platform, so Im looking for someone who wants to grow with the project.

  • Bubble.io Developer Needed Build & Optimize Dealer Inve…

    Im building a private multi-dealership inventory portal using Bubble.io and need an experienced Bubble developer to help complete and optimize the platform.

    The system is already partially built and live on a custom domain. Core functionality exists, but I need help refining workflows, fixing bugs, and scaling the platform properly.

    Project Overview:
    This is a dealer portal where multiple dealerships can log in and upload wholesale inventory. Each dealership has its own private dashboard, and only admin can see all listings.

    Whats already built:

    • User authentication (login/signup)
    • Dealer dashboard UI
    • Vehicle listing creation (form + database)
    • Image upload (partially working)
    • Basic workflows for creating listings

    What I need help with:

    • Fixing image upload/display consistency
    • Cleaning up and optimizing workflows
    • Improving database structure (VehicleListings, VehiclePhotos, etc.)
    • Role-based permissions (admin vs dealership users)
    • UI/UX improvements (make it clean and fast)
    • Messaging system between admin and dealers
    • Preparing the app for scale (future marketplace expansion)

    Nice to have (future phases):

    • Multi-image galleries per vehicle
    • Advanced filtering/search
    • Activity tracking/logs
    • Notifications system
    • Mobile optimization

    Requirements:

    • Strong experience with Bubble.io (must show past projects)
    • Understanding of database structure & workflows in Bubble
    • Ability to troubleshoot and explain fixes clearly
    • Good communication (I want to move fast)

    Project Type:

    • Ongoing work (not just one-time fix)
    • I want someone I can continue working with long-term

    To apply:

    • Send examples of Bubble apps youve built
    • Briefly explain how youd approach fixing a broken image upload/display system
    • Confirm availability (I want to start ASAP)

    Budget:
    Flexible based on experience and speed

    Im serious about building this into a large-scale platform, so Im looking for someone who wants to grow with the project.

  • INSS 725 – Information Systems Practicum 2

    Here is the link:


    hey my advisor said add these things –

    What You NEED to Add Before Calling It Fully Functional

    1. Authentication & User Roles (CRITICAL)

    If your site involves students + advisors, this is non-negotiable.

    Add:

    • Sign up / login (email, Google, etc.)
    • Role-based access:
      • Student dashboard
      • Advisor dashboard
      • Admin panel

    Without this, your app is just a demonot a real system.

    Tech ideas:

    • Clerk, Firebase Auth, Auth0
    • JWT sessions

    2. Database Integration (Backend Reality)

    Right now, if your site is mostly frontend, it wont scale.

    Add:

    • Persistent database:
      • User data
      • Messages
      • Appointments
      • Notes/history

    Good options:

    • Supabase
    • PostgreSQL
    • MongoDB Atlas

    Vercel itself doesnt handle full backend/database wellyou usually need external services

    3. Core Feature System (Your Value)

    You mentioned advisorsso your site needs a clear core function.

    Examples:

    • Appointment booking system
    • Messaging/chat system
    • Advisor recommendations
    • Document uploads (resumes, plans, etc.)

    Ask yourself:

    Why would someone come back to this site weekly?

    If you dont have a strong answer thats the missing feature.

    4. Real-Time Communication

    For advisor-based platforms:

    Add:

    • Live chat ( / Firebase)
    • Notifications (email + in-app)
    • Status indicators (online/offline)

    5. Proper Testing Layer

    Youre in deployment, so now you need:

    • Unit testing (functions)
    • Integration testing (flows)
    • User testing (real people)

    Tools:

    • Jest
    • Cypress
    • Playwright

    This is what separates it works for me vs works for everyone

    6. Performance Optimization

    To handle many users:

    Add:

    • Lazy loading
    • Image optimization
    • API caching
    • CDN usage (Vercel helps here automatically)

    Vercels edge network improves speed globally

    7. Security & Trust Signals (VERY IMPORTANT)

    Right now your site likely looks like a dev project.

    Add:

    • Custom domain (NOT .vercel.app)
    • HTTPS (already there but upgrade cert if possible)
    • Privacy Policy + Terms of Service
    • Contact page
    • About page with real info

    Low-trust sites often:

    • Have low traffic
    • Use generic hosting
    • Lack real company info

    8. Analytics & Monitoring

    You need to track users:

    • Google Analytics
    • Error tracking (Sentry)
    • Logs (Vercel / backend logs)

    If you dont track users, you cant improve the product.

    9. Mobile Responsiveness

    Test on:

    • iPhone
    • Android
    • Tablet

    Most users = mobile first

    10. UX Polish (What Most People Skip)

    Small things that matter A LOT:

    • Loading states (spinners, skeletons)
    • Error messages (not just something went wrong)
    • Clear navigation
    • Consistent design system

    The BIGGEST Missing Piece (Most Important)

    If I had to guess what your site is missing:

    A clear, structured user journey

    Example:

    1. User signs up
    2. Chooses role (student/advisor)
    3. Lands on dashboard
    4. Takes an action (book, message, upload, etc.)
    5. Gets feedback/confirmation

    If your site doesnt guide users like this it will feel unfinished.

    If You Want This to Be Real Startup Level

    Add these next:

    • Payment system (Stripe)
    • Email system (Resend, SendGrid)
    • AI assistant (OpenAI API)
    • Admin analytics dashboard

    Quick Honest Feedback

    Right now youre likely at:

    Deployed project stage

    To reach:

    Real product used by many people

    You need:

    • Backend + database
    • Authentication
    • Core feature loop
    • Trust + UX polish

    2 days ago

    Last thing is we need a full report of what you did and used and how you did all that stuf

    2 days ago

    The live demo on the login page has to go. We are having issues logging into the account. The life cycle does not need to be connected to the student resource page. The life cycle also isn’t congruent with what it says on our previous website I sent you. There are many issues and this has to be up and running by Sunday.