Open benseverett opened 1 year ago
No idea if it works like this but this is how I imagine the psudo code...
Each project page.mdx
has something like:
sliderTitles: [
'title for slider 1',
'title for slider 2'
],
sliderImages: [
[
'slider1-img1.jpg',
'slider1-img2.jpg'
],
[
'slider2-img1.jpg',
'slider2-img1.jpg'
]
]
A function in wrapper.jsx
:
for i in sliderTitles
draw sliderComponent with {caseStudy.sliderTitle[i]} and {caseStudy.sliderImages[i]}
And then the slider functionality is a "component"(?) and it can just be spawned with the required input data and quantity of sliders given by the project page.mdx
. The sliderComponent class would have the appropriate boarders, styles, etc. so that each of the sliders sit nicely down the page.
Project pages that need specialist sliders:
Slater (oxfordshire manor) Add:
Qualcomm Add:
Goddard (west berkshire hosue) Add:
Hershey (Oxfordshire House) Add:
@SNVes Any more to add?
Main task
Complete image slider functionality.
Is it possible to simplify this set up and have custom titles (potentially with a default?) for each group of images?
For Example
If the
technicalImages
,visualImages
, andphotoImages
objects become one object type, when inserted into the code (page.mdx
) can it be given a header at that point?This will enable more flexibility with generating seperate groupings of image sliders.
E.g., Technical Drawings, Visuals, and Photos are all covered but it would then we could also do Phase 1 Technical Drawings, Phase 1 Visuals, Phase 2 technical drawings, Phase 2 Visuals, etc...