There is a business logic case for referencing install sheets on the applications guides page that follows the following format: https://www.curtmfg.com/masterlibrary/01ARIES/206003-2/installsheet/${part.oldPartNumber}_INS.pdf. There are two problems with this approach:
We shouldn't have a hard-coded business logic reference to the install sheet and should use the data in the API: http://ariesautomotive.com/api/appguide/Jeep%20Accessories/:0.json.
There is a business logic case for referencing install sheets on the applications guides page that follows the following format:
https://www.curtmfg.com/masterlibrary/01ARIES/206003-2/installsheet/${part.oldPartNumber}_INS.pdf. There are two problems with this approach:https://www.curtmfg.com/masterlibrary/01ARIES/206003-2/installsheet/${part.oldPartNumber}_INS.pdfand it needs to include the part number in 2 places: `https://www.curtmfg.com/masterlibrary/01ARIES/206003-2/installsheet/${part.oldPartNumber}_INS.pdf.http://ariesautomotive.com/api/appguide/Jeep%20Accessories/:0.json.