Skip to content

Commit 57bc8dc

Browse files
committed
link-fragments
1 parent f39d8c7 commit 57bc8dc

5 files changed

Lines changed: 6 additions & 5 deletions

File tree

.markdownlint-cli2.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ config:
1818
blanks-around-tables: true
1919
descriptive-link-text: true
2020
# table-column-style: aligned
21-
# link-fragments: true
21+
link-fragments: true
2222
# no-alt-text: true
2323
single-trailing-newline: true
2424
# no-emphasis-as-heading: true

docs/infrastructure_and_maintenance/cache/http_cache/context_aware_cache.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,10 @@ It also varies on `Authorization` to cover any possible basic authorization head
5656

5757
The only known workaround is to make it SiteAccess aware, and have custom VCL logic tied to your SiteAccess matching with Varnish/Fastly, to send the SiteAccess prefix as URI.
5858

59+
<a name="default-options-for-foshttpcachebundle"></a>
60+
5961
!!! caution "Default options for FOSHttpCacheBundle"
6062

61-
<a name="default-options-for-foshttpcachebundle"></a>
6263
The following configuration is defined by default for FOSHttpCacheBundle.
6364
You should not override these settings unless you know what you're doing.
6465

docs/multisite/siteaccess/siteaccess_matching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ ibexa:
185185

186186
Example URL `http://my_site.com:8080/content` matches SiteAccess `site`.
187187

188-
### `Ibexa\SiteFactory\SiteAccessMatcher` [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]]
188+
### `Ibexa\SiteFactory\SiteAccessMatcher` [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] {#ibexasitefactorysiteaccessmatcher}
189189

190190
Enables the use of [Site Factory](site_factory.md).
191191
Doesn't take any parameters in configuration:

docs/release_notes/ibexa_dxp_v4.4.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ A new welcome page greets you when opening Ibexa Digital Experience Platform.
2121

2222
![New Welcome Page](4.4_welcome_page.png)
2323

24-
### All-new [[= product_name_com =]] packages [[% include 'snippets/commerce_badge.md' %]]
24+
### All-new [[= product_name_com =]] packages [[% include 'snippets/commerce_badge.md' %]] {#all-new-ibexa-commerce-packages}
2525

2626
This release deprecates all Commerce packages that you've known from previous releases and brings a redesigned and reconstructed Commerce offering:
2727

docs/update_and_migration/from_4.5/update_from_4.5.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ php bin/console ibexa:migrations:import vendor/ibexa/image-picker/src/bundle/Res
277277
php bin/console ibexa:migrations:migrate --file=2023_12_06_15_00_image_content_type.yaml
278278
```
279279

280-
### Dashboard migration [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]]
280+
### Dashboard migration [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] {#dashboard-migration}
281281

282282
If you're using [[= product_name_exp =]] or [[= product_name_com =]],
283283
you must run data migration required by the dashboard and other features to finish the upgrade process:

0 commit comments

Comments
 (0)