====== Yocto Project Customization Guide for TQ Systems Modules ======

<panel type="info" title="Introduction">
This guide provides instructions on how to customize U-Boot and the Linux kernel within the Yocto Project build system. It also covers creating patches and simple BitBake recipes. This is essential for adapting the system to specific hardware or software requirements for your TQ modules.

We assume you have a working Yocto Project build environment set up and are familiar with basic BitBake commands.
For TQ-specific layers, please refer to our official repositories:
  * [[https://github.com/tq-systems/meta-tq|meta-tq]]
  * [[https://github.com/tq-systems/ci-meta-tq|ci-meta-tq]]
</panel>

===== Prerequisites =====

<panel type="default" title="Required Tools and Setup">
Before you begin, ensure you have:
  * A configured Yocto Project build environment for your target TQ module.
  * The `devtool` utility, which is part of Yocto Project (often included in `poky/scripts` and added to `PATH` when sourcing the build environment script like `oe-init-build-env`).
  * Your TQ-specific meta-layer (e.g., `meta-tq`) added to your `bblayers.conf` file.

Source your build environment:
<code bash>
source poky/oe-init-build-env <build-directory>
</code>
</panel>

===== 1. Customizing U-Boot =====

<panel type="default" title="Modifying U-Boot">
U-Boot (Das U-Boot Universal Boot Loader) is often the first piece of software that runs on your embedded device. Customizations might include changing boot commands, enabling/disabling drivers, or adjusting hardware initialization.

=== 1.1. Setting up the U-Boot Source for Development ===

To modify U-Boot, use `devtool` to extract and prepare the source code. Replace `u-boot-tq` (or the specific U-Boot recipe name for your platform, often found in `meta-tq`) if it differs. You can find the recipe name by looking into your machine configuration file or by searching in your layers.

<code bash>
devtool modify u-boot-tq
</code>

This command will:
  * Fetch the U-Boot source code.
  * Unpack it into your `<build-directory>/workspace/sources/u-boot-tq`.
  * Create a new Git repository there for your changes.
  * Create an append file (`.bbappend`) in your workspace layer to point the build system to this local source.

<alert type="info">
**Tip:** If you don't know the exact recipe name for U-Boot, you can try a more generic name often used if a specific `u-boot-tq` doesn't exist, like `u-boot-imx` for i.MX platforms, or check your machine's configuration file for `PREFERRED_PROVIDER_virtual/bootloader`.
</alert>

=== 1.2. Making Changes to U-Boot ===

Navigate to the U-Boot source directory:
<code bash>
cd <build-directory>/workspace/sources/u-boot-tq
</code>

You can now make your changes. Common modifications include:
  * **Environment Variables:** Edit files like `include/configs/<your-board-name>.h` or `env/common.c`.
  * **Board Configuration:** Modify `configs/<your-board-defconfig>` or related board files in `board/tq/<your-board>/`.
  * **Device Tree:** For U-Boot specific device tree files (if used), these are typically in `arch/<arch>/dts/`.

After making your changes, commit them using Git:
<code bash>
git add <changed-files>
git commit -m "My U-Boot customization: <brief description>"
</code>

=== 1.3. Building and Testing U-Boot ===

Build U-Boot with your changes:
<code bash>
bitbake u-boot-tq
</code>

Or, if you want to build only U-Boot and deploy it to your image for faster testing (this might skip some image generation steps):
<code bash>
devtool build u-boot-tq
</code>

Then, deploy the image containing your U-Boot to your target hardware and test thoroughly.
The resulting U-Boot binary (e.g., `u-boot.imx`, `u-boot.bin`, `u-boot.img` depending on the platform) will be in `<build-directory>/tmp/deploy/images/<your-machine>/`.

=== 1.4. Creating a Patch for U-Boot ===

Once you are satisfied with your changes, create a patch. Ensure you are in the U-Boot source directory (`<build-directory>/workspace/sources/u-boot-tq`).

If you have one commit:
<code bash>
git format-patch -1 -o <path-to-your-meta-layer>/recipes-bsp/u-boot/files/
</code>

If you have multiple commits, you might want to squash them or create multiple patches:
<code bash>
git format-patch HEAD~N -o <path-to-your-meta-layer>/recipes-bsp/u-boot/files/
</code>
(Replace `N` with the number of commits).

Name your patch descriptively, e.g., `0001-my-custom-u-boot-feature.patch`.

=== 1.5. Updating the U-Boot Recipe ===

Create or edit the U-Boot append file (`.bbappend`) in your custom layer. This is typically located at `<your-meta-layer>/recipes-bsp/u-boot/u-boot-tq_%.bbappend` or a similar path.

Add your patch to `SRC_URI`:
<file u-boot-tq_%.bbappend>
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI += " \
    file://0001-my-custom-u-boot-feature.patch \
"
</file>

<alert type="warning">
**Important:** After creating the patch and updating the `.bbappend` file, you should tell `devtool` that you are done with the source:
<code bash>
devtool reset u-boot-tq
</code>
This will remove the workspace version and the build system will use your patched recipe from your meta-layer.
</alert>
</panel>

===== 2. Customizing the Linux Kernel =====

<panel type="default" title="Modifying the Linux Kernel">
Kernel customization allows you to change device drivers, enable kernel features, modify the device tree, and more.

=== 2.1. Setting up the Kernel Source for Development ===

Use `devtool` to prepare the kernel source. The recipe name is usually `virtual/kernel`.
<code bash>
devtool modify virtual/kernel
</code>

This command works similarly to the U-Boot one:
  * Fetches the kernel source code.
  * Unpacks it into `<build-directory>/workspace/sources/linux`. (The directory name might vary, e.g., `linux-imx`, `linux-yocto`).
  * Creates a Git repository for your changes.
  * Creates an append file in your workspace layer.

=== 2.2. Making Changes to the Kernel ===

Navigate to the kernel source directory:
<code bash>
cd <build-directory>/workspace/sources/linux
</code>

Common kernel modifications:

  * **Kernel Configuration:**
    To change kernel configuration options (`.config`), use `menuconfig`:
    <code bash>
    bitbake virtual/kernel -c menuconfig
    </code>
    Or, using `devtool`:
    <code bash>
    devtool menuconfig virtual/kernel
    </code>
    Save your changes. This will typically create a `defconfig` file or a configuration fragment.

  * **Device Tree Files (.dts, .dtsi):**
    These are usually located in `arch/<your-arch>/boot/dts/`. For TQ modules, you might find them under a vendor-specific path (e.g., `arch/arm64/boot/dts/freescale/` for NXP i.MX based modules or `arch/arm64/boot/dts/st/` for STM32MP1 based modules). Edit the relevant device tree source file for your board.

  * **Driver Code:** Modify existing drivers or add new ones in the `drivers/` directory.

Commit your changes using Git:
<code bash>
git add <changed-files-or-defconfig>
git commit -m "My kernel customization: <brief description>"
</code>

=== 2.3. Building and Testing the Kernel ===

Build the kernel with your changes:
<code bash>
bitbake virtual/kernel
</code>
Or:
<code bash>
devtool build virtual/kernel
</code>

The kernel image (e.g., `zImage`, `uImage`, `Image`) and device tree blobs (`.dtb`) will be in `<build-directory>/tmp/deploy/images/<your-machine>/`. Deploy and test on your hardware.

=== 2.4. Creating a Kernel Patch ===

In the kernel source directory (`<build-directory>/workspace/sources/linux`):

  * **For code changes (drivers, dts):**
    <code bash>
    git format-patch HEAD~N -o <path-to-your-meta-layer>/recipes-kernel/linux/files/
    </code>
    (Replace `N` with the number of commits). Name it descriptively, e.g., `0001-my-kernel-driver-fix.patch`.

  * **For kernel configuration changes:**
    After running `menuconfig` and saving, `devtool` often helps manage configuration fragments. Alternatively, you can generate a configuration fragment:
    <code bash>
    bitbake virtual/kernel -c savedefconfig
    </code>
    This will create a `defconfig` file in `<build-directory>/tmp/work/<your-machine>-poky-linux-gnueabi/linux-yocto/<kernel-version>/linux-<your-machine>-standard-build/`. Rename this to something like `my_custom_config.cfg` and copy it to your layer: `<path-to-your-meta-layer>/recipes-kernel/linux/files/`.

=== 2.5. Updating the Kernel Recipe ===

Create or edit the kernel append file (`.bbappend`) in your layer. This is often `<your-meta-layer>/recipes-kernel/linux/linux-yocto_%.bbappend` or specific to the kernel version/type (e.g., `linux-imx_%.bbappend`).

Add your patch(es) and/or configuration fragment to `SRC_URI`:
<file linux-yocto_%.bbappend>
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI += " \
    file://0001-my-kernel-driver-fix.patch \
    file://my_custom_config.cfg \
"
</file>

<alert type="warning">
**Important:** After creating patches/config fragments and updating the `.bbappend`, reset the `devtool` workspace:
<code bash>
devtool reset virtual/kernel
</code>
</alert>
</panel>

===== 3. Creating Patches and Simple Recipes =====

<panel type="default" title="Patches and Basic Recipes">

=== 3.1. General Patch Creation ===

The process described for U-Boot and Kernel (using `git format-patch`) is the standard way to create patches for any software component modified via `devtool modify <recipe-name>`.

Key steps:
  1. `devtool modify <recipe-name>`
  2. Make changes in `<build-directory>/workspace/sources/<recipe-name>`
  3. Commit changes with `git`.
  4. Generate patch(es) with `git format-patch`.
  5. Copy patch(es) to your layer, typically under `<your-meta-layer>/<category>/<recipe-name>/files/`.
  6. Add `file://<patch-name>.patch` to `SRC_URI` in the recipe's `.bbappend` file.
  7. `devtool reset <recipe-name>`

=== 3.2. Creating a Simple Recipe ===

Let's say you want to add a custom script or a small, pre-compiled binary to your image.

==== 3.2.1. Recipe File Structure ====

Create a directory structure in your meta-layer:
<code bash>
<your-meta-layer>/
  recipes-custom/
    my-custom-app/
      files/
        my_script.sh  # Your script or binary
      my-custom-app_0.1.bb # Your recipe file
</code>

==== 3.2.2. Example: Recipe for a Shell Script ====

**1. Create your script:** `<your-meta-layer>/recipes-custom/my-custom-app/files/my_script.sh`
<file my_script.sh>
#!/bin/sh
echo "Hello from TQ Custom App!"
</file>
Make sure it's executable: `chmod +x my_script.sh`.

**2. Create the recipe file:** `<your-meta-layer>/recipes-custom/my-custom-app/my-custom-app_0.1.bb`
<file my-custom-app_0.1.bb>
SUMMARY = "My Custom Application"
DESCRIPTION = "A simple shell script example for TQ."
LICENSE = "MIT" # Or your preferred license
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

# Point to the files directory within this recipe
SRC_URI = "file://my_script.sh"

# Source directory (where files from SRC_URI are unpacked)
S = "${WORKDIR}"

# Installation: Copy the script to /usr/bin in the target image
do_install() {
    install -d ${D}${bindir}
    install -m 0755 ${S}/my_script.sh ${D}${bindir}/
}

# If you have other files, like service files for systemd:
# SRC_URI += " file://my-custom-app.service"
# FILES_${PN} += "${systemd_system_unitdir}/my-custom-app.service"
# SYSTEMD_SERVICE_${PN} = "my-custom-app.service" (if it's a systemd service)
</file>

<alert type="info">
**Explanation of terms:**
  * `SUMMARY`, `DESCRIPTION`: Basic information about the package.
  * `LICENSE`, `LIC_FILES_CHKSUM`: Crucial for licensing compliance.
  * `SRC_URI`: Points to the source files. `file://` indicates files local to the recipe.
  * `S`: Specifies the source directory after unpacking. For simple file additions, `${WORKDIR}` is common.
  * `do_install()`: This function defines how to install files into the target image's filesystem (`${D}` is the destination directory for staging). `${bindir}` usually resolves to `/usr/bin`.
</alert>

==== 3.2.3. Adding the Recipe to Your Image ====

To include `my-custom-app` in your image, add it to your image recipe (e.g., `core-image-minimal.bbappend` or your custom image recipe):
<code bash>
IMAGE_INSTALL_append = " my-custom-app"
</code>
Or, for testing, you can build it directly:
<code bash>
bitbake my-custom-app
</code>

Then, build your full image:
<code bash>
bitbake <your-image-name>
</code>

After deploying and booting the image, `/usr/bin/my_script.sh` should be present.
</panel>

===== 4. Further Information =====

<panel type="default" title="Tips and Best Practices">
  * **Layer Organization:** Keep your custom patches and recipes in a dedicated meta-layer (like `meta-tq` or a customer-specific layer).
  * **Commit Messages:** Write clear and descriptive commit messages when making changes with `devtool`. These messages often become the description in your patch files.
  * **Testing:** Thoroughly test all changes on target hardware.
  * **Upstream Sources:** When possible, try to contribute generic changes back to the upstream projects (U-Boot, Kernel, etc.).
  * **Yocto Project Documentation:** The official Yocto Project Mega-Manual and Development Tasks Manual are invaluable resources.
    * [[https://docs.yoctoproject.org/mega-manual/index.html|Yocto Project Mega-Manual]]
    * [[https://docs.yoctoproject.org/dev-manual/index.html|Yocto Project Development Tasks Manual]]

<alert type="success">
This guide provides a starting point. The Yocto Project is powerful and flexible, and there are many ways to achieve specific customizations. Always refer to official documentation and the specifics of your TQ module's BSP.
</alert>
</panel>






<page-header>
===== Accordion  =====
</page-header>
<accordion>
<panel title="Collapsible Group Item #1">
Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
</panel>
<panel title="Collapsible Group Item #2">Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.</panel>
<panel title="Collapsible Group Item #3">Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.</panel>
</accordion>

<page-header>
===== Alerts without Icons =====
</page-header>

<alert type="success">Well done! You successfully read this important alert message.</alert>
<alert type="info">Heads up! This alert needs your attention, but it's not super important.</alert>
<alert type="warning">Warning! Better check yourself, you're not looking too good.</alert>
<alert type="danger">Oh snap! Change a few things up and try submitting again.</alert>

<page-header>
===== Dismissable Alerts without Icons =====
</page-header>

<alert type="success" dismiss="true">Well done! You successfully read this important alert message.</alert>
<alert type="info" dismiss="true">Heads up! This alert needs your attention, but it's not super important.</alert>
<alert type="warning" dismiss="true">Warning! Better check yourself, you're not looking too good.</alert>
<alert type="danger" dismiss="true">Oh snap! Change a few things up and try submitting again.</alert>

<page-header>
===== Dismissable Alerts with Icons =====
</page-header>

<alert type="success" dismiss="true" icon="fa fa-check-circle">Well done! You successfully read this important alert message.</alert>
<alert type="info" dismiss="true" icon="fa fa-info">Heads up! This alert needs your attention, but it's not super important.</alert>
<alert type="warning" dismiss="true" icon="fa fa-warning">Warning! Better check yourself, you're not looking too good.</alert>
<alert type="danger" dismiss="true" icon="fa fa-minus-circle">Oh snap! Change a few things up and try submitting again.</alert>

<page-header>
===== Callouts =====
</page-header>

<callout>
=== Default Callout ===
This is a default callout.
</callout>

<callout type="primary" icon="true">
=== Primary Callout ===
This is a primary callout with icon.
</callout>

<callout type="success" icon="true">
=== Success Callout ===
This is a Success callout with icon.
</callout>

<callout type="info" icon="true">
=== Info Callout ===
This is a info callout with icon.
</callout>

<callout type="warning" icon="true">
=== Warning Callout ===
This is a warning callout with icon.
</callout>

<callout type="danger" icon="true">
=== Danger Callout ===
This is a danger callout with icon.
</callout>

<callout type="question" icon="true">
=== Question Callout ===
This is a question callout with icon.
</callout>

<callout type="tip" icon="true">
=== Tip Callout ===
This is a Tip callout with icon.
</callout>

<page-header>
===== Form with Captcha =====
</page-header>


<form>
Action mail me@example.com
Thanks "Thanks for submitting your valuable data."
Fieldset "A set of fields"
Textbox  "Employee Name" "=Your Name"
number "Your Age" >13 <99
email "Your E-Mail Address"
textbox "Occupation (optional)" !
password "Some password"
fieldset "even more fields"
select "Please select an option" "Peaches|Apples|Oranges"
static "Some static text that could be an agreement"
yesno "Read the agreement?"
radio "Radio Button Group" "Peaches|Apples|Oranges"
fieldset  "Date Field"
date "Enter your date"
textarea "Tell me about your self"
textbox "You need to write 'agree' here" /^agree$/
fieldset
submit "Submit Query"
</form>

<page-header>
===== Badges =====
</page-header>

<label type="default">default</label>
<label type="primary">primary</label>
<label type="success">success</label>
<label type="info">info</label>
<label type="warning">warning</label>
<label type="danger">danger</label>

<page-header>
===== Badges with icons =====
</page-header>

<label type="primary" icon="fa fa-exclamation-circle">primary</label>
<label type="success" icon="fa fa-check-circle">success</label>
<label type="info" icon="fa fa-info-circle">info</label>
<label type="warning" icon="fa fa-exclamation-triangle">warning</label>
<label type="danger" icon="fa fa-minus-circle">danger</label>

<page-header>
===== List Groups =====
</page-header>

<list-group>
  * Cras justo odio
  * Dapibus ac facilisis in
  * Morbi leo risus
  * Porta ac consectetur ac
  * Vestibulum at eros
</list-group>

<list-group>
  * Cras justo odio <badge>14</badge>
  * Dapibus ac facilisis in <badge>2</badge>
  * Morbi leo risus <badge>1</badge>
</list-group>

<list-group>
  * [[:start]]
  * [[:wiki:welcome]]
  * [[:wiki:syntax]]
</list-group>

<list-group>
  * [[:start]] \\ Homepage \\ Test
  * [[:wiki:welcome]] \\ DokuWiki Welcome
  * [[:wiki:syntax]] \\ DokuWiki Syntax
</list-group>

<list-group>
  * {{fa>home}} [[:start|Home-Page]]
</list-group>

<page-header>
===== Nav Tabs and Nav Pills =====
</page-header>

<nav type="tabs">
  * [[:start]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>
\\
<nav type="tabs" justified="true">
  * [[:start]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>
\\
<nav type="pills">
  * [[:start]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>
\\
<nav type="pills" stacked="true">
  * [[:start]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>
\\
<nav type="pills" justified="true">
  * [[:start]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>
\\
<tabs>
  * [[#tab-foo|Foo]]
  * [[#tab-bar|Bar]]
 
<pane id="tab-foo">
=== Foo ===
Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquid ex ea commodi consequat. Quis aute iure reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint obcaecat cupiditat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</pane>
 
<pane id="tab-bar">
=== Bar ===
Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquid ex ea commodi consequat. Quis aute iure reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint obcaecat cupiditat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</pane>
 
</tabs>

<page-header>
===== Panels =====
</page-header>

<panel type="default">Basic panel example</panel>

<panel type="default" title="Panel with heading">
Panel content
</panel>

<panel type="default" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>

<panel type="primary" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>
<panel type="success" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>
<panel type="info" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>
<panel type="warning" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>
<panel type="danger" title="Panel title" subtitle="Panel subtitle">
Panel content
</panel>

<panel type="default" title="Panel title" no-body="true">
<panel-body>Some default panel content here. Nulla vitae elit libero, a pharetra augue. Aenean lacinia bibendum nulla sed consectetur. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Nullam id dolor id nibh ultricies vehicula ut id elit.</panel-body>
^ # ^ First Name ^ Last Name ^ Username ^
^ 1 | Mark       | Otto      | @mdo     |
^ 2 | Jacob      | Thornton  | @fat     |
^ 3 | Larry      | the Bird  | @twitter |
</panel>

<panel type="default" title="Panel title" no-body="true">
^ # ^ First Name ^ Last Name ^ Username ^
^ 1 | Mark       | Otto      | @mdo     |
^ 2 | Jacob      | Thornton  | @fat     |
^ 3 | Larry      | the Bird  | @twitter |
</panel>

<page-header>
===== Tooltip =====
</page-header>

<tooltip title="Sample Text" placement="top">Lorem ipsum</tooltip> dolor sit amet...
\\
<tooltip title="Sample Text" placement="left">Lorem ipsum</tooltip> dolor sit amet...
\\
<tooltip title="Sample Text" placement="right">Lorem ipsum</tooltip> dolor sit amet...
\\
<tooltip title="Sample Text" placement="bottom">Lorem ipsum</tooltip> dolor sit amet...
\\

<page-header>
===== Buttons =====
</page-header>

<btn type="default">Default</btn>
<btn type="primary">Primary</btn>
<btn type="success">Success</btn>
<btn type="info">Info</btn>
<btn type="warning">Warning</btn>
<btn type="danger">Danger</btn>
<btn type="link">Link</btn>


<page-header>
===== Images (in grid) =====
</page-header>

<grid>
<col md="4">
<image shape="rounded">
{{https://via.placeholder.com/400x400?.png?}}
</image>
</col>
<col md="4">
<image shape="circle">
{{https://via.placeholder.com/400x400?.png?}}
</image>
</col>
<col md="4">
<image shape="thumbnail">
{{https://via.placeholder.com/400x400?.png?}}
</image>
</col>
</grid>
<affix offset-top="50" position-top="100" position-right="20">
<panel title="Affix">
Scroll the page!
</panel>
</affix>