Specifications are structured data
Trailer attributes and descriptive tags are represented separately from the sales copy, supporting the catalog and detailed product pages.
CLIENT WORK / EQUIPMENT CATALOGClient project
DRD Trailers
Make the next trailer easier to find.
DRD Trailers is client work for DRD Truck and Equipment Sales. The website gives commercial inventory a structured home, with product detail pages and a straightforward route to the business.
The problem
Equipment buyers need specifics. The site needs to present trailer listings and their supporting details without making the catalog difficult to navigate.
The implementation
A Laravel catalog organizes inventory and product detail pages, with galleries, specification filters, company information, and contact pages.
- Trailer inventory and specification browsing
- Product detail pages and image galleries
- Company, contact, and announcement pages
01Browse inventory02Filter specifications03Inspect a trailer04Contact the business
02 / ENGINEERING DECISIONS
Where the details matter.
Editorial control belongs with the business
The administrative catalog gives the business a place to maintain inventory, photographs and supporting content.
A stable listing address
Product slugs provide readable listing URLs. The detail page connects photographs and equipment information to the next contact step.
03 / PACKAGES & CODE
Inside the implementation.
NestedTerms is used here as an embedded legacy implementation. Product specifications and descriptors flow through BiMorphable, term-scoped correlations and parent-linked tags. These are the application’s existing APIs; the current Composer release has a different interface.
APPLICATION EXCERPT
NestedTerms powers product specifications
The product reads the specification term and turns each entered hierarchy into a Tag before assigning its correlations. BiMorphable resolves those relationships; the public inventory filters and product details consume them.
NestedTerms package ↗public function getSpecificationsAttribute(){
return $this->getCorrelation('specification');
}
public function setSpecificationsAttribute($specifications){
$specs = [];
foreach(array_filter($specifications) as $specification){
$specs[] = Tag::firstOrCreateFromString($specification);
}
return $this->setCorrelation('specification', $specs);
}
Embedded legacy NestedTerms usage: Product → BiMorphable → Term / Correlation / Tag. This is existing application code, not the current v2 API.
APPLICATION EXCERPT
Build the hierarchy from an entered path
The embedded Tag implementation walks each segment, carries the parent ID forward and returns the most specific tag. That keeps equipment attributes structured beyond their display labels.
NestedTerms package ↗public static function firstOrCreateFromString($string)
{
$strings = array_map(fn($piece)=>trim($piece), explode(">", $string));
$parent_id = null;
$nested_value = "";
foreach($strings as $s){
$nested_value = $nested_value ? $nested_value . " > " . $s : $s;
$tag = Tag::firstOrCreate(['name'=>$s, 'slug'=>Str::slug($nested_value), "value"=>$nested_value, 'parent_id'=>$parent_id]);
$parent_id = $tag->id;
}
return $tag;
}
Existing NestedTerms hierarchy implementation. Parent-linked tags support the same specifications shown in the inventory and detail templates.
04 / VERIFICATION & CURRENT SCOPE
What holds it together.
- This is an established client website, distinct from the newer product applications.
- The original BWD credit remains after the client’s own footer.
- The source audit follows specification editing through Product, BiMorphable, Term, Correlation and Tag into the public filters and detail template.
CURRENT RELEASE
Completed client website for DRD Truck and Equipment Sales.