Currently you get a portfolio with a dummy image with English text.
That text needs localisation, but is part of the image.
Options:
Use a special Level3URL value that gets intercepted by the app, and localised to a different URL with a suffix like _EN and _NL.
Benefit: unintercepted Level3URL field contains something that is more or less understandable. Can even be a working link (e.g. for EN)
Drawback: Level3URL field likely points to a different domain (e.g. Github.org or vdhamer.com) than the actual portfolios. Which isn't too bad: there is no constraint on the Level3URLs in a single Level2.json file.
Same as 1, but trigger when the Level3URL is a broken link.
Benefit: works on broken links.
Drawback: text is not about a broken link, so confuses user who configured the Level 2 file and may not know link is broken.
Currently you get a portfolio with a dummy image with English text. That text needs localisation, but is part of the image.
Options: