software:picocms_welcome
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| software:picocms_welcome [2025/06/05 16:59] – [```] timb | software:picocms_welcome [2025/06/05 17:03] (current) – timb | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| See also: [[software: | See also: [[software: | ||
| - | Contents | + | Contents |
| < | < | ||
| - | ``` | + | |
| --- | --- | ||
| - | Title: | + | Title: |
| - | e | + | |
| Description: | Description: | ||
| --- | --- | ||
| Line 98: | Line 98: | ||
| by default. If you want to use some assets (e.g. a image) in one of your content | by default. If you want to use some assets (e.g. a image) in one of your content | ||
| files, use Pico's `assets` folder. You can then access them in your Markdown | files, use Pico's `assets` folder. You can then access them in your Markdown | ||
| - | using the < | + | using the <\code>&# |
| - | < | + | < |
| ### Text File Markup | ### Text File Markup | ||
| Line 132: | Line 132: | ||
| `img.small { width: 80%; }`). You can then use these CSS classes in your | `img.small { width: 80%; }`). You can then use these CSS classes in your | ||
| Markdown files, for example: | Markdown files, for example: | ||
| - | < | + | < |
| There are also certain variables that you can use in your text files: | There are also certain variables that you can use in your text files: | ||
| - | * < | + | * < |
| - | * < | + | * < |
| - | can be specified using < | + | can be specified using < |
| - | * < | + | * < |
| - | * < | + | * < |
| - | * < | + | * < |
| - | don't confuse this with < | + | don't confuse this with < |
| - | * < | + | * < |
| - | * < | + | * < |
| - | * < | + | * < |
| - | page, e.g. < | + | page, e.g. < |
| - | * < | + | * < |
| - | e.g. < | + | e.g. < |
| ### Blogging | ### Blogging | ||
| Line 259: | Line 259: | ||
| seeing `My < | seeing `My < | ||
| actually get it parsed, you must use `{{ meta.headline|raw }}` (resulting in | actually get it parsed, you must use `{{ meta.headline|raw }}` (resulting in | ||
| - | the expected < | + | the expected < |
| are Pico's `content` variable (e.g. `{{ content }}`), Pico's `content` filter | are Pico's `content` variable (e.g. `{{ content }}`), Pico's `content` filter | ||
| (e.g. `{{ " | (e.g. `{{ " | ||
| Line 336: | Line 336: | ||
| * Pass the unique ID of a page to the `link` filter to return the page's URL | * Pass the unique ID of a page to the `link` filter to return the page's URL | ||
| (e.g. `{{ " | (e.g. `{{ " | ||
| - | * You can replace URL placeholders (like < | + | * You can replace URL placeholders (like < |
| arbitrary strings using the `url` filter. This is helpful together with meta | arbitrary strings using the `url` filter. This is helpful together with meta | ||
| - | variables, e.g. if you add < | + | variables, e.g. if you add < |
| to the YAML header of a page, `{{ meta.image|url }}` will return | to the YAML header of a page, `{{ meta.image|url }}` will return | ||
| `%assets_url%/ | `%assets_url%/ | ||
| Line 346: | Line 346: | ||
| you might use Markdown in the `description` meta variable and later parse it | you might use Markdown in the `description` meta variable and later parse it | ||
| in your theme using `{{ meta.description|markdown }}`. You can also pass meta | in your theme using `{{ meta.description|markdown }}`. You can also pass meta | ||
| - | data as parameter to replace < | + | data as parameter to replace < |
| (e.g. `{{ " | (e.g. `{{ " | ||
| *John Doe*" | *John Doe*" | ||
| Line 445: | Line 445: | ||
| [OfficialThemes]: | [OfficialThemes]: | ||
| [PluginUpgrade]: | [PluginUpgrade]: | ||
| - | ``` | + | |
| + | </ | ||
software/picocms_welcome.1749142773.txt.gz · Last modified: by timb