JASMIN DOC- AZIMUTH Changes request from Matt Pritchard #21
Description
My requests are:
Please use PNG format for screenshots.
This format is more suited to images with a restricted colour palette, whereas JPEG is better for true-colour, like photos. It avoids compression artefacts resulting from how JPEGs are saved, and is loss-less, so doesn't degrade a bit more each time you save them. I realise that creates a bit more work to go back and re-do the screenshots, but read on...
Please check the aspect ratio of all the images when you preview the pages: I think Matt had mentioned this already but one or two looked like they were still stretched vertically (I also remember this from a previous time, perhaps the GWS survey: perhaps it's to do with whatever image editor you're using?).
The directory structure we have for image assets on the site is assets/img/docs//*.png where matches the name of each *.md file.
This structure of one image folder per page is so that we can keep track of which images are used in which page
If they're all together in a general azimuth-images folder then it means we can't easily update one image without knowing where (else) it might be used.
In previous sites, we've ended up with a mess, so I'd like to stick to that structure this time.
Please check the settings for how each image is displayed on the page, particularly the width:
I think I've corrected the ones I could find, but if you're remaking them, they might need re-setting.
In the {{}} shortcode, there must be only one wrapper="" attribute, otherwise all but one of them will get ignored.
This should be wrapper="col-N mx-auto text-center" where N is 3, 6, 9 or 12.
col-12 would span the whole space (100%) of the width of the page, whereas col-3 would span just 3 out of 12 "columns" of that space.
mx-auto and text-center are needed to apply centering and auto-scaling, so leave those in as well.
PS. I've recently found a code spell-checker extension which makes the task of spotting typos a bit easier, as they sometimes don't stand out from code or markdown: well worth looking for a good one in VSCode. I now use this one:
Name: Code Spell Checker
Id: streetsidesoftware.code-spell-checker
Description: Spelling checker for source code
Version: 4.0.34
Publisher: Street Side Software
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker.
marketplace.visualstudio.commarketplace.visualstudio.com
Code Spell Checker - Visual Studio Marketplace
Extension for Visual Studio Code - Spelling checker for source code
#187 Chami-jasmin-cloud-changes
My changes 03-12-2024
https://github.com/[cedadev/jasmin-help-hugo-hinode](https://github.com/cedadev/jasmin-help-hugo-hinode)|cedadev/jasmin-help-hugo-hinodecedadev/jasmin-help-hugo-hinode | 3 Dec 2024 | Added by GitHub
1 reply
22 days agoView thread