diff --git a/Documentation/Developer/Index.rst b/Documentation/Developer/Index.rst index 3efe9a44..edd82956 100644 --- a/Documentation/Developer/Index.rst +++ b/Documentation/Developer/Index.rst @@ -13,7 +13,7 @@ This chapter will explain different usecases for developer working with `headles Internal Extbase plugins ======================== -To integrate a custom frontend plugin which return its data inside the JSON object, we have to do the following: +To integrate a custom frontend plugin which returns its data inside the JSON object, we have to do the following: Follow the standard proceeding to `register and configure extbase plugins `__: @@ -122,7 +122,7 @@ Main part is a user function definition to run a plugin from TypoScript: For any other plugin, just change the `vendorName`, `extensionName`, `pluginName` and `controller` options, and import needed constant and setup values (like for view, persistence and settings in this case). -Than use the constants of that extension to overwrite the paths to the fluid templates: +Then use the constants of that extension to overwrite the paths to the fluid templates: .. code-block:: typoscript @@ -328,13 +328,13 @@ EXT:headless out of box provides for developers: elements: [] } -You can anytime extend & customize for your needs simply by create custom -decorator which implements `DefinitionDecoratorInterface` or extend provided -`AbstractFormDefinitionDecorator` which provides you ability to override -definition of each element or whole form definition. +You can anytime extend & customize for your needs simply by creating a custom +decorator which implements `DefinitionDecoratorInterface` or extend the provided +`AbstractFormDefinitionDecorator` which provides the ability to override the +definition of each element or the whole form definition. -After creating custom decorator you can attach to your form simply by setting -`formDecorator` in rendering options of form, :ref:`see more ` +After creating a custom decorator you can attach it to your form simply by setting +`formDecorator` in the rendering options of the form, :ref:`see more ` .. _developer-snippets: diff --git a/Documentation/Installation/Index.rst b/Documentation/Installation/Index.rst index fcd8f4bd..64d035b7 100644 --- a/Documentation/Installation/Index.rst +++ b/Documentation/Installation/Index.rst @@ -22,7 +22,7 @@ After TYPO3 is running, we can continue installing the headless extension: the page, we can see already the JSON output. #. **Create a site configuration:** The site URL is needed as endpoint URL for the frontend. - In TYPO3 v10 an autogenerated site configuration might exsist which we can rename and configure to our preferences. + In TYPO3 v10 an autogenerated site configuration might exist which we can rename and configure to our preferences. .. important:: diff --git a/Documentation/Introduction/Index.rst b/Documentation/Introduction/Index.rst index fcd54188..fba11ced 100644 --- a/Documentation/Introduction/Index.rst +++ b/Documentation/Introduction/Index.rst @@ -28,6 +28,7 @@ The JSON response object and the content elements are customizable with TypoScri * Easily extensible with custom fields or custom CE's * Support for EXT:felogin and EXT:form * Support for EXT:news (see additional extension `EXT:headless_news `__) -* Support for (`EXT:solr `__) -* Support for EXT:powermail (`EXT:powermail `__) -* Support for EXT:gridelements (`EXT:gridelements `__) +* Support for EXT:solr (`EXT:headless_solr `__) +* Support for EXT:powermail (`EXT:headless_powermail `__) +* Support for EXT:gridelements (`EXT:headless_gridelements `__) +* Support for EXT:container (`EXT:headless_container `__)