Skip to content

Commit e81d463

Browse files
author
Bernhard Schmitt
committed
Fix small text formatting in documentation
1 parent 8b6e274 commit e81d463

3 files changed

Lines changed: 9 additions & 9 deletions

File tree

Documentation/01_PresentationObjectsAndComponents.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The most important function of PresentationObjects is to enforce the interface b
1818

1919
For a single component that interface is represented by an actual PHP interface. So let's start with that:
2020

21-
<small>*`EXAMPLE: PresentationObject Interface`*<small>
21+
<small>*`EXAMPLE: PresentationObject Interface`*</small>
2222

2323
```php
2424
<?php declare(strict_types=1);
@@ -38,7 +38,7 @@ Next, we're going to write the actual object implementing the Interface from abo
3838

3939
**Important:** PresentationObject are ValueObjects. In that they are immutable and can only consist of scalar properties, other value objects or arrays of the former two.
4040

41-
<small>*`EXAMPLE: PresentationObject`*<small>
41+
<small>*`EXAMPLE: PresentationObject`*</small>
4242

4343
```php
4444
<?php declare(strict_types=1);
@@ -107,7 +107,7 @@ The first difference to `Neos.Fusion:Component` is the mandatory `@presentationO
107107

108108
The second difference is, that besides the usual `props`-Context, your renderer can now also access the special `presentationObject`-Context, which holds our verified data.
109109

110-
<small>*`EXAMPLE: Resources/Private/Fusion/Presentation/Component/Image/Image.fusion`*<small>
110+
<small>*`EXAMPLE: Resources/Private/Fusion/Presentation/Component/Image/Image.fusion`*</small>
111111

112112
```fusion
113113
prototype(Vendor.Site:Component.Image) < prototype(PackageFactory.AtomicFusion.PresentationObjects:PresentationObjectComponent) {
@@ -145,7 +145,7 @@ It is recommended to model discrete values for presentation object properties as
145145
Since PHP does not support enums yet, this package provides an interface to be implemented by classes that behave similarly to enums.
146146
> **Hint:** For more information on enums in PHP, see https://stitcher.io/blog/php-enums
147147
148-
<small>*`EXAMPLE: Pseudo-enum`*<small>
148+
<small>*`EXAMPLE: Pseudo-enum`*</small>
149149

150150
Given we have a presentation object Headline with properties type and content.
151151
While content can be an arbitrary string, in our project by specification we only support h1-h3 as types for headlines.

Documentation/02_PresentationObjectFactories.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In this tutorial, we're going to write a PresentationObject factory for the imag
1818

1919
PresentationObject factories are co-located with their respective PresentationObjects. It's recommended to create factory methods with a speaking name prefixed with `for*` or `from*` to describe their use-case. When your code base grows, the factory will act like an index showing you all the different places in which the respective component is used.
2020

21-
<small>*`EXAMPLE: PresentationObject Factory`*<small>
21+
<small>*`EXAMPLE: PresentationObject Factory`*</small>
2222

2323
```php
2424
<?php declare(strict_types=1);
@@ -55,7 +55,7 @@ final class ImageFactory extends AbstractComponentPresentationObjectFactory
5555

5656
Each factory that extends `AbstractComponentPresentationObjectFactory` automatically implements the `Neos\Eel\ProtectedContextAwareInterface` and can be used as an Eel helper. To make our factory available in Fusion, we need to register it in the Settings:
5757

58-
<small>*`EXAMPLE: Settings.PresentationHelpers.yaml`*<small>
58+
<small>*`EXAMPLE: Settings.PresentationHelpers.yaml`*</small>
5959

6060
```yaml
6161
Neos:
@@ -70,7 +70,7 @@ Neos uses the `Neos.Neos:ContentCase` to map nodes to rendering prototypes. For
7070

7171
From here, we just need to extend `Neos.Neos:ContentComponent` and provide our PresentationObject component `Vendor.Site:Component.Image` as the renderer. As the `presentationObject` we pass the result of the `forImageNode`-method of our newly registered `ImageFactory`.
7272

73-
<small>*`EXAMPLE: Resources/Private/Fusion/Integration/Content/Image.fusion`*<small>
73+
<small>*`EXAMPLE: Resources/Private/Fusion/Integration/Content/Image.fusion`*</small>
7474

7575
```fusion
7676
prototype(Vendor.Site:Content.Image) < prototype(Neos.Neos:ContentComponent) {

Documentation/03_Slots.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Value wraps any given php value into a `SlotInterface` and sees through that it
177177

178178
In Factories, it can be initialized via static factory method:
179179

180-
<small>*`EXAMPLE: PresentationObject Factory`*<small>
180+
<small>*`EXAMPLE: PresentationObject Factory`*</small>
181181

182182
```php
183183
/* ... */
@@ -215,7 +215,7 @@ In plain AtomicFusion we would use `Neos.Neos:Editable` to integrate a property
215215

216216
In Factories, it can be initialized via static factory method:
217217

218-
<small>*`EXAMPLE: PresentationObject Factory`*<small>
218+
<small>*`EXAMPLE: PresentationObject Factory`*</small>
219219

220220
```php
221221
/* ... */

0 commit comments

Comments
 (0)