Commit 2eac8d0d authored by Vincent Tam's avatar Vincent Tam

Forgetten figure shortcode refactoring after 887e1967

parent eadb868e
Pipeline #40763798 passed with stages
in 36 seconds
......@@ -1682,7 +1682,7 @@ Ubuntu 18.04)
5. Remove the _temporary_ XWD file.
6. Switch back to CLI.
{{< figure src="180826153752-xubu1804-w400.png" link="180826153752-xubu1804.png" title="Screenshot by xwd" caption="Taken with the above script from TTY on Xubuntu 18.04" alt="Xubuntu 18.04 error after login" >}}
{{< beautifulfigure src="180826153752-xubu1804-w400.png" link="180826153752-xubu1804.png" title="Screenshot by xwd" caption="Taken with the above script from TTY on Xubuntu 18.04" alt="Xubuntu 18.04 error after login" >}}
[my_aptitude]: https://vincenttam.github.io/blog/2014/06/30/basic-use-of-aptitude/
[Vim]: http://www.vim.org
......
......@@ -42,25 +42,25 @@ watched before actually grabbing my screwdriver.
I opened the lid and cleaned its inner side. The amount of dust on
the fan blades was as expected.
{{< figure src="IMG-20180701-WA0004.jpg" alt="dusty fan" >}}
{{< beautifulfigure src="IMG-20180701-WA0004.jpg" alt="dusty fan" >}}
However, I was shocked by the dust which had been blocking the
exhaust. This had caused the heat to build up inside the case.
{{< figure src="IMG-20180701-WA0006.jpg" alt="exit blocked" >}}
{{< beautifulfigure src="IMG-20180701-WA0006.jpg" alt="exit blocked" >}}
I had seriously thought about replacing the thermal paste due to Win*
failure. However, having read [Ofey's article][6], I've decided to
*leave it untouched*.
{{< figure src="IMG-20180701-WA0009.jpg" alt="warning" >}}
{{< beautifulfigure src="IMG-20180701-WA0009.jpg" alt="warning" >}}
### Result
After two hours of cleaning, my Fujitsu Lifebook now runs
[Xubuntu 18.04][7] quieter and cooler.
{{< figure src="IMG-20180701-WA0011.jpg" alt="after cleaning" >}}
{{< beautifulfigure src="IMG-20180701-WA0011.jpg" alt="after cleaning" >}}
### Safety precautions and remarks
......
......@@ -20,7 +20,7 @@ own sake, I still performed it as a result of my conversation with a
technician in a computer store. He thought that the display problem
in the current version would be *fixed* in this upgraded version.
{{< figure src="20180706_213156_HDR.jpg" alt="Linux Mint 18.3" >}}
{{< beautifulfigure src="20180706_213156_HDR.jpg" alt="Linux Mint 18.3" >}}
The old version of Linux Mint *couldn't* detect the onboard Intel
graphics card. Therefore, `sensors` reported a higher CPU temperature
......@@ -44,7 +44,7 @@ On the whole, the upgrade was successful. After a reboot, I could
enter into the new OS. The display has become much more clearer.
However, the fonts are too *small*.
{{< figure src="20180706_222740.jpg" alt="Upgraded system" >}}
{{< beautifulfigure src="20180706_222740.jpg" alt="Upgraded system" >}}
### Finishing touch
......
......@@ -13,14 +13,14 @@ tags:
Un événement dans lequel un cavalier essaie de demeurer sur un cheval
avec deux jambes levées.
{{< figure src="rodeo-cheval.png" alt="Texture, Silhouette, Rodeo, Horse, Jumper, Mane" title="Rodéo au sens propre" caption="Source: Pixabay" >}}
{{< beautifulfigure src="rodeo-cheval.png" alt="Texture, Silhouette, Rodeo, Horse, Jumper, Mane" title="Rodéo au sens propre" caption="Source: Pixabay" >}}
- au sens figuré dans l'actualité
Une façon dangereuse de conduite dont le conducteur lève la(les)
roule(s) antérieure(s).
{{< figure src="rodeo-moto.png" alt="Motorcycle, Rear, Road, Rider, Moto Motorcycle" title="Rodéo au sens figuré" caption="Source: Pixabay" >}}
{{< beautifulfigure src="rodeo-moto.png" alt="Motorcycle, Rear, Road, Rider, Moto Motorcycle" title="Rodéo au sens figuré" caption="Source: Pixabay" >}}
Le dicto Collins a recordé [une utilisation très rare][1] de ce mot.
Récemment, on l'utilise plus fréquemment en raison de la lutte contre
......
......@@ -51,7 +51,7 @@ I'm sorry for the blurred photos showing the installer. I tried using
However, the results *didn't* look good. I found keeping media files *under 500
kB difficult* for an article with a lot of photos.
{{< figure src="180729-install-sda.jpg" title="SSD partition table" caption="Partitioned a Fujitsu 120GB SSD drive" alt="SSD partition for Ubuntu install" >}}
{{< beautifulfigure src="180729-install-sda.jpg" title="SSD partition table" caption="Partitioned a Fujitsu 120GB SSD drive" alt="SSD partition for Ubuntu install" >}}
Partition | Type | Mount point | Approximate Size
------------|------|-------------|------------------
......@@ -62,7 +62,7 @@ free space | | | rest of the disk
Device for boot loader installation: `/dev/sda`
{{< figure src="180729-install-sdb.jpg" title="HDD partition table" caption="Partitioned a Fujitsu 1TB HDD drive" alt="HDD partition for Ubuntu install" >}}
{{< beautifulfigure src="180729-install-sdb.jpg" title="HDD partition table" caption="Partitioned a Fujitsu 1TB HDD drive" alt="HDD partition for Ubuntu install" >}}
Partition | Type | Mount point | Approximate Size
------------|------|-------------|------------------
......@@ -91,7 +91,7 @@ a text browser ([lynx][6], [w3c][7], etc).
> -- <cite>John 13:34</cite>
{{< figure src="180729-ubiquity-err.jpg" title="Ubuntu 18.04 installation process" caption="P" alt="Ubiquity installer" >}}
{{< beautifulfigure src="180729-ubiquity-err.jpg" title="Ubuntu 18.04 installation process" caption="P" alt="Ubiquity installer" >}}
Despite the error message inside the black-and-white terminal
<span class="fa-stack">
......@@ -111,13 +111,13 @@ This allows the UEFI to load the installed Ubuntu OS *without* finding other boo
Ubuntu's GRUB bootloader was installed in `/dev/sda` (i.e. the SSD). As a
result, we see **ubuntu** instead of **SSD**.
{{< figure src="180729-uefi.jpg" title="Fubjitsu AH557 UEFI" caption="After boot menu configuration" alt="Fujitsu AH557 UEFI" >}}
{{< beautifulfigure src="180729-uefi.jpg" title="Fubjitsu AH557 UEFI" caption="After boot menu configuration" alt="Fujitsu AH557 UEFI" >}}
### Stage 3: Ubuntu's warm welcome
After login, I was greeted with a series of messages after the installation.
{{< figure src="180729-fin.jpg" title="SSD partition table" caption="Partitioned a Fujitsu 120GB SSD drive" alt="SSD partition for Ubuntu install" >}}
{{< beautifulfigure src="180729-fin.jpg" title="SSD partition table" caption="Partitioned a Fujitsu 120GB SSD drive" alt="SSD partition for Ubuntu install" >}}
![live patch](180729-livepatch.png)
......
......@@ -16,7 +16,7 @@ One loves adding colors to his/her life by adding stunning photos to his/her
social media profile. However, due to various constraints, such as weather,
budget and time, it's possible that the photos taken look dark and somber.
{{< figure src="st-martine.jpg" title="Eglise St Martine" caption="Photo taken at Pont-du-Château, Puy-de-Dôme (63) on 30th June, 2017" alt="Eglise St Martine à Pont-du-Château" >}}
{{< beautifulfigure src="st-martine.jpg" title="Eglise St Martine" caption="Photo taken at Pont-du-Château, Puy-de-Dôme (63) on 30th June, 2017" alt="Eglise St Martine à Pont-du-Château" >}}
Despite a suboptimal choice of camera angle, a right tool enables you to take
the best out of the photo. Let's go [GIMP][1]ing.
......@@ -102,7 +102,7 @@ Ref: [GIMP's doc section 5.7][9]
I followed [his steps on TurboFuture][10] to get the photo below.
{{< figure src="st-martine-bright.jpg" title="Eglise St Martine Again" caption="Photo enhanced in GIMP one year later" alt="Eglise St Martine à Pont-du-Château" >}}
{{< beautifulfigure src="st-martine-bright.jpg" title="Eglise St Martine Again" caption="Photo enhanced in GIMP one year later" alt="Eglise St Martine à Pont-du-Château" >}}
The *cheap* trick works so quick and easy to apply. This becomes my *valuable*
skill.
......
......@@ -10,7 +10,7 @@ tags:
draft: false
---
{{< figure src="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/marais-small.jpg" link="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/20180711_215200.jpg" title="Le Temple du Marais" caption="\"Eglise verte\" means \"green church\"." alt="Le Temple du Marais" >}}
{{< beautifulfigure src="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/marais-small.jpg" link="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/20180711_215200.jpg" title="Le Temple du Marais" caption="\"Eglise verte\" means \"green church\"." alt="Le Temple du Marais" >}}
### Background: 🈶 ⛪ → 🌿
......
......@@ -18,8 +18,8 @@ blanks and then I clicked the "submit" button below. I was greeted with a
`MISSING_REQUIRED_FIELDS` error within a second.
{{< gallery >}}
{{< figure link="comment.png" thumb="-s" title="HTML form" caption="every entry filled in" alt="comment form" >}}
{{< figure src="response-s.png" title="Staticman v2 server response" caption="500 internal server error" alt="html server error" >}}
{{< beautifulfigure link="comment.png" thumb="-s" title="HTML form" caption="every entry filled in" alt="comment form" >}}
{{< beautifulfigure src="response-s.png" title="Staticman v2 server response" caption="500 internal server error" alt="html server error" >}}
{{< /gallery >}}
{{< highlight json >}}
......@@ -44,7 +44,7 @@ The error code suggested that the form fields sent should be inspected.
4. In the **Params** side pane, observe that `fields[replying_to]` has _empty_
value. This is the source of error.
{{< figure src="response-s.png" title="Missing hidden field" caption="fields[replying_to] empty" alt="missing hidden field" >}}
{{< beautifulfigure src="response-s.png" title="Missing hidden field" caption="fields[replying_to] empty" alt="missing hidden field" >}}
### Solution
......@@ -56,8 +56,8 @@ Under
{{< /highlight >}}
{{< gallery >}}
{{< figure src="inject1.png" title="Search \"replying_to\"" caption="fields[replying_to] empty" alt="inspect element for hidden field" >}}
{{< figure src="inject2.png" title="Value \"abc\" injected" caption="fields[replying_to] nonempty" alt="inject value for hidden field" >}}
{{< beautifulfigure src="inject1.png" title="Search \"replying_to\"" caption="fields[replying_to] empty" alt="inspect element for hidden field" >}}
{{< beautifulfigure src="inject2.png" title="Value \"abc\" injected" caption="fields[replying_to] nonempty" alt="inject value for hidden field" >}}
{{< /gallery >}}
inject _whatever_ you like, then click "submit" again.
......@@ -68,8 +68,8 @@ The error disappeared. After submission, I was redirected to the page. The
HTTP status code "302" represented a redirection.
{{< gallery >}}
{{< figure link="result1.png" thumb="-s" title="POST request sent" caption="got 304 status code" alt="Staticman v2 response" >}}
{{< figure link="result2.png" thumb="-s" title="POST request sent" caption="response empty" alt="redirected back to blog" >}}
{{< beautifulfigure link="result1.png" thumb="-s" title="POST request sent" caption="got 304 status code" alt="Staticman v2 response" >}}
{{< beautifulfigure link="result2.png" thumb="-s" title="POST request sent" caption="response empty" alt="redirected back to blog" >}}
{{< /gallery >}}
[form]: https://www.flyinggrizzly.net/2017/12/setting-up-staticman-server/
......@@ -13,7 +13,7 @@ draft: false
### Background
{{< figure src="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/marais-small.jpg" link="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/20180711_215200.jpg" title="Le Temple du Marais" caption="\"Eglise verte\" means \"green church\"." alt="Le Temple du Marais" >}}
{{< beautifulfigure src="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/marais-small.jpg" link="/post/2018-07-23-fujitsu-lh532-keyboard-cleaning/20180711_215200.jpg" title="Le Temple du Marais" caption="\"Eglise verte\" means \"green church\"." alt="Le Temple du Marais" >}}
My churches are going <span class="green">green</span>.
......@@ -37,7 +37,7 @@ However, _only_ the radio buttons <input type="radio"> and checkboxes
were left _blank_! I opened my PDF and double-checked that I had input the text
in <input type="text" value="all text fields" readonly>.
{{< figure link="prerr.jpg" thumb="-s" title="Printed output" caption="Printed by a Konica Monilta bizhub photocopier" alt="PDF file printed" >}}
{{< beautifulfigure link="prerr.jpg" thumb="-s" title="Printed output" caption="Printed by a Konica Monilta bizhub photocopier" alt="PDF file printed" >}}
How can I get back the missing texts _printed_ on paper?
......
......@@ -19,7 +19,7 @@ and [GitLab].
To set up _unauthenticated_ commenting system on [GitLab pages][gl_pages].
{{< figure link="../goal.png" src="../goal800.png" title="Demo GitLab Page with Staticman v3" caption="Built on 14/09/2018" alt="GitLab Page with Staticman" >}}
{{< beautifulfigure link="../goal.png" src="../goal800.png" title="Demo GitLab Page with Staticman v3" caption="Built on 14/09/2018" alt="GitLab Page with Staticman" >}}
This post aims at providing a walkthrough to the GitLab repo setup. If you want to host your own Staticman API instance, you may refer to the
[next post in this series][next].
......
......@@ -31,7 +31,7 @@ _Without sudo privileges_, I've chosen to compile [Julia] from [source][ghsrc].
I was too _lazy_ to get [the dependencies][rpmdep] fixed. I just compiled it
_without_ [GFortran] and [pkg-config] under the `~/src` folder.
{{< figure link="install.png" thumb="-s" alt="julia installing on RHEL 6" title="Julia v1.0.0 installing on RHEL 6" caption="Screenshot taken at around 20:00" >}}
{{< beautifulfigure link="install.png" thumb="-s" alt="julia installing on RHEL 6" title="Julia v1.0.0 installing on RHEL 6" caption="Screenshot taken at around 20:00" >}}
After reassuring that the entire installation process _didn't_ require sudo
privileges, I checkout out to `v1.0.0` and `make -j 6`, hoping that _six_
......@@ -57,7 +57,7 @@ workstation. I _can't_ how long this would take if it's run on a laptop.
I added a symbolic link `~/bin/julia` pointing to `~/src/julia/julia`, which in
turn points to `~/src/julia/usr/bin/julia`.
{{< figure src="result.png" max-width="800" alt="julia running in bash" title="Julia v1.0.0 installed on RHEL 6" caption="Screenshot taken at around 21:30" >}}
{{< beautifulfigure src="result.png" max-width="800" alt="julia running in bash" title="Julia v1.0.0 installed on RHEL 6" caption="Screenshot taken at around 21:30" >}}
$ julia --version
julia version 1.0.0
......
......@@ -39,9 +39,9 @@ the repo using the static site generator [Jekyll]. This is quite convenient.
You may view [the GitHub repo for my demo site][src]. I'm too lazy to re-type
the details.
{{< figure src="staticmanlab-invitation.png" width="800" title="Allow @staticmanlab to accept invitation" caption="Screenshot taken on 30th Sep, 2018" alt="Programmatically accept invitation on Staticman" >}}
{{< beautifulfigure src="staticmanlab-invitation.png" width="800" title="Allow @staticmanlab to accept invitation" caption="Screenshot taken on 30th Sep, 2018" alt="Programmatically accept invitation on Staticman" >}}
{{< figure src="staticman-ok.png" title="A successful comment posted on demo site" caption="Screenshot taken on 30th Sep, 2018" alt="comment posted successfully" >}}
{{< beautifulfigure src="staticman-ok.png" title="A successful comment posted on demo site" caption="Screenshot taken on 30th Sep, 2018" alt="comment posted successfully" >}}
### Other GitHub Pages served by Staticman v3
......
......@@ -30,7 +30,7 @@ could bring this to the theme [Beautiful Hugo][2].
- [Network Hobo's customization of Beautiful Hugo][5] (inspired by the second
one, but contains a logic error)
{{< figure src="networkhobo.png" title="Logic error in Network Hobo's commenting system" caption="Everybody replies to the same person?" alt="staticman nested comment logic error" >}}
{{< beautifulfigure src="networkhobo.png" title="Logic error in Network Hobo's commenting system" caption="Everybody replies to the same person?" alt="staticman nested comment logic error" >}}
All three of them follow the
[double-loop structure suggested by Eduardo Bouças][6].
......@@ -60,7 +60,7 @@ Staticman (`layouts/partials/staticman-comments`), and
It took me hours to come up with three appropriate words describing the problem:
"main comment", "reply target" and "comment reply".
{{< figure class="mysvg" src="drawing.svg" alt="problem OO sketch" title="Nested comments data fields" caption="A sketch of the object models of the comment classes" size="600x200" >}}
{{< beautifulfigure class="mysvg" src="drawing.svg" alt="problem OO sketch" title="Nested comments data fields" caption="A sketch of the object models of the comment classes" size="600x200" >}}
With these clear keywords, it's much easier to decouple the logic of the double
loop presented in [this Hugo + Staticman nested comments guide][11] on Network
......@@ -103,7 +103,7 @@ instead of `options[parent]` in the HTML form in [Staticman issue 42][7].
I opened [Beautiful Hugo issue 221][14] after testing my system with a
definition list.
{{< figure src="bh221a.png" alt="beautiful hugo issue 221" title="Beautiful Hugo issue 221" caption="The paragraph and the definition list weren't properly aligned." >}}
{{< beautifulfigure src="bh221a.png" alt="beautiful hugo issue 221" title="Beautiful Hugo issue 221" caption="The paragraph and the definition list weren't properly aligned." >}}
The cause of the problem is the selector `p` at line 10 in
[`layouts/partials/staticman-comments.html`][15].
......@@ -179,7 +179,7 @@ above
- a left margin of 2em for each comment reply
- a left margin of 58px for each comment timestamp
{{< figure src="bh221b.png" alt="beautiful hugo issue 221 resolved" title="Beautiful Hugo issue 221 resolved" caption="The paragraph and the definition list are now properly aligned." >}}
{{< beautifulfigure src="bh221b.png" alt="beautiful hugo issue 221 resolved" title="Beautiful Hugo issue 221 resolved" caption="The paragraph and the definition list are now properly aligned." >}}
The gravatar is of height and width 48px with a right margin of 10px
floating on the left-hand side. The height of the gravatar is
......
......@@ -11,7 +11,7 @@ tags:
draft: false
---
{{< figure src="/img/staticmanlab.svg" alt="StaticmanLab new logo" title="StaticmanLab's new logo" caption="GitLab logo recreated from Wikimedia's logo by Darby under CC-BY-SA 4.0 and Staticman logo on GitHub by Erlen Masson under MIT.">}}
{{< beautifulfigure src="/img/staticmanlab.svg" alt="StaticmanLab new logo" title="StaticmanLab's new logo" caption="GitLab logo recreated from Wikimedia's logo by Darby under CC-BY-SA 4.0 and Staticman logo on GitHub by Erlen Masson under MIT.">}}
The old icon for [Staticman Lab][StaticmanLab] was made by GIMP from Staticman's
icon in PNG in the GitHub repo. Recently, I've found the SVG version of this
......@@ -41,7 +41,7 @@ To add the "H" of Hugo's logo, I've used Inkscape's clip set tool, which selects
the intersection of the object and the selector. Its variant transformation
leaves the selector visible after the clip.
{{< figure src="/img/staticmanlab-hugo.svg" alt="StaticmanLab's demo site new logo" title="StaticmanLab's demo site new logo" caption="GitLab logo recreated from Wikimedia's logo by Darby under CC-BY-SA 4.0 and Staticman logo on GitHub by Erlen Masson under MIT.">}}
{{< beautifulfigure src="/img/staticmanlab-hugo.svg" alt="StaticmanLab's demo site new logo" title="StaticmanLab's demo site new logo" caption="GitLab logo recreated from Wikimedia's logo by Darby under CC-BY-SA 4.0 and Staticman logo on GitHub by Erlen Masson under MIT.">}}
To improve this favicon of this blog, I've rTo improve this favicon of this blog, I've recreated this with GIMP since it's
_impossible_ to export SVG to ICO from Inkscape. If the canvas is too *small*,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment