1. Assignment Overview

1.1 Application Domain & Context

Your task is to build a Laravel-powered “Timber Structural Project Manager” that allows authenticated users to manage Projects and their associated Building Part. A “Project” represents a physical timber structure (e.g., “House”, “Google Office”), and each Project can contain multiple Building Part(constraint: floors, walls, beams, columns).

• “Users” should be able to create, read, update, and delete their own Projects and nested Building Part.
• Building Part data must respect Material Type Rules (e.g., Floors/Walls → CLT only; Beams → CLT or GLT; Columns → GLT only).
• The “supplier” field in the Building Part form should use the provided API endpoint (e.g., /api/suppliers) to populate its options, emulating real-world HTTP integration.

2. Functional Requirements

2.1 Project Management (CRUD)

• Index page: List all Projects belonging to the authenticated user, paginated (10 per page).
• Create page: Form with fields: name (string, required), description (text, optional).
• Store action: Validate input, save to projects table, redirect to Project detail.
• Show/Detail page: Display Project metadata and a list of associated Building Part (if any), with links/buttons to edit/delete.
• Edit page: Form pre-filled with Project data; allow updating name and description.
• Update action: Validate & persist changes.
• Delete action: Soft delete or hard delete the Project and cascade delete its Building Part.

2.2 Building Part (Floor, Wall, Beam, Column) Management (Nested CRUD)

• Each Building Part belongs to a specific Project (project_id foreign key).
• Building Part form (used for both Create & Edit) includes:
• name (string, required)
• building_part_type (enum: “floor,” “wall,” “beam,” “column”; required)
• material_type (enum, validated according to rules below; required)
• supplier (string, selected from a dropdown loaded via API or dummy JSON; required)
• Material Type Validation Rules:
  • If building_parttype is “floor” or “wall,” only material_type = “CLT” is valid.
  • If building_part_type is “beam,” material_type may be “CLT” or “GLT.”
  • Ifbuilding_part_type is “column,” only material_type = “GLT.”
• On Create or Update, enforce the above rules via Laravel’s FormRequest or inline validation. If validation fails, show error messages next to form fields.
• Index page (Building Part list) within a Project: Display a table of Building Part with columns: name, building_part_type, material_type, supplier, and action buttons.
• Edit/Delete: Allow modifying or removing a Building Part; enforce that a Building Part belongs to the authenticated user’s Project.

2.3 Supplier Data (fetch from API)

• Use the already provided API, which is, GET /api/suppliers, which returns a static JSON array of supplier objects:

[ 
	{ "id": 1, "name": "Xlam", "material-type": "CLT" }, 
	{ "id": 2, "name": "CUSP", "material-type": "CLT" }, 
	{ "id": 3, "name": "Kalvasta Timber", "material-type": "GLT" }, 
	{ "id": 4, "name": "Timberlink", "material-type": "GLT" }
]

• The Building Part form’s supplier dropdown must fetch this JSON (at page load or via AJAX) and list supplier.name as options.
• This simulates an external data integration without requiring a real third-party API.

3. UI/UX

This is a visual representation of the task. Please note that it is for reference only — there's no need to match the exact style. https://www.figma.com/design/IjHne28E5eQNEA20FJK6bR/Skill-test--Timber-Sturctural-Project-Management-?node-id=0-1&p=f&t=enCpQX3APOHBiyrO-0