tcabuilder issueshttps://git.spooner.io/spooner-web/tcabuilder/-/issues2023-05-15T12:05:51Zhttps://git.spooner.io/spooner-web/tcabuilder/-/issues/14Missing fe_group2023-05-15T12:05:51ZThomas LöfflerMissing fe_grouphttps://git.spooner.io/spooner-web/tcabuilder/-/issues/12Missing start- and endtime2023-03-24T08:09:29ZThomas LöfflerMissing start- and endtimeAdd start- and endtime to the default templatesAdd start- and endtime to the default templatesThomas LöfflerThomas Löfflerhttps://git.spooner.io/spooner-web/tcabuilder/-/issues/11TYPO3 Extension Award - Best Documentation 20212021-11-22T20:24:49ZSybille PetersTYPO3 Extension Award - Best Documentation 2021This issue is for your information only. Please feel free to close
---
**Congratulations**! :sparkles: :tada:
Your extension has been nominated for the **TYPO3 Extension Award - Best Documentation 2021**.
Three extensions will be cho...This issue is for your information only. Please feel free to close
---
**Congratulations**! :sparkles: :tada:
Your extension has been nominated for the **TYPO3 Extension Award - Best Documentation 2021**.
Three extensions will be chosen as winners by a community vote. In case your extension wins, you will be notified shortly after the voting.
> Voting: November 24 - December 8, 2021 (2 weeks)
In order to vote for an extension:
1. Go to https://extensions.typo3.org and login
2. Click on the “Vote now” button on https://extensions.typo3.org/extension-documentation-award
3. Give 3 points, 2 points and 1 point each for each extension, by clicking on the radio button
Please also look for news on https://typo3.org in the next few days or look on “[Community news](https://typo3.org/project/news/community-1)” for a more detailed description.
Thank you for making your extension available for the TYPO3 community.
Best of luck - and keep inspiring people to share.
Sybille :smiley:
If you have any questions, please contact me on TYPO3 Slack (`@Sy`).https://git.spooner.io/spooner-web/tcabuilder/-/issues/10Analysis of rendering on docs.typo3.org2021-11-22T18:46:26ZSybille PetersAnalysis of rendering on docs.typo3.orgI checked the rendering locally. Unfortunately my initial optimism was premature. Sorry about that. The rendering does not look good in some cases, specifically, in the tables with inline, code, e.g.
on Gitlab
![image](/uploads/7ca461...I checked the rendering locally. Unfortunately my initial optimism was premature. Sorry about that. The rendering does not look good in some cases, specifically, in the tables with inline, code, e.g.
on Gitlab
![image](/uploads/7ca461155f25267d1c4ee7a2c4e4608b/image.png)
Rendered locally
![image](/uploads/84f8150811892a40c1addce8bc9f166b/image.png)
What is happening: the rendering with Docker does not directly render the Markdown, it converts the Markdown to .rst and then renders that. This does not get optimal results in all cases.
That is why .rst is also recommended to use .rst for rendering with the official docs Docker image for docs.typo3.org: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/GeneralConventions/Format.html
Also, there are warnings. To interpret the warnings, one must look, not in the markdown source, but in the generated .rst. (This would also make the workflow in the future tedious, I would not recommend that.)
```
cat Documentation-GENERATED-temp/Result/project/0.0.0/_buildinfo/warnings.txt
./Documentation/README.rst:37: WARNING: Field list ends without a blank line; unexpected unindent.
./Documentation/README.rst:201: WARNING: Inline interpreted text or phrase reference start-string without end-string.
./Documentation/README.rst:211: WARNING: Inline interpreted text or phrase reference start-string without end-string.
./Documentation/README.rst:251: WARNING: Definition list ends without a blank line; unexpected unindent.
./Documentation/README.rst:249: WARNING: Inline literal start-string without end-string.
./Documentation/README.rst:249: WARNING: Inline literal start-string without end-string.
$ cat -n Documentation-GENERATED-temp/Result/project/0.0.0/_sources/README.rst.txt | less
```
So, to sum it up, I would either convert to .rst or just render here (which also looks nice). I had just thought it might be good to render on docs.typo3.org to give the extension more visibility.
----
If you do get it rendered nicely locally, either by changing the formatting or converting to .rst (converting to .rst would propably be preferred for less hassle). These would be the steps:
* Add Documentation/Settings.cfg to show title in rendered project: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/GeneralConventions/DirectoryFilenames.html#settings-cfg
* Render locally to check rendering with Docker container: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/RenderingDocs/Index.html
* Add Documentation-GENERATED-temp to .gitignore (this should be done in local git configuration but putting this in the project avoids hassle later by accidentally committing the generated documenation
* When ready, add Webhook for rendering: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingDocForExtension/Migrate.htmlhttps://git.spooner.io/spooner-web/tcabuilder/-/issues/9Using a pointer to handle new fields2021-07-23T06:13:09ZThomas LöfflerUsing a pointer to handle new fieldsWhen copying an existing TCA config oder editing an existing, there should be a possibility to set a pointer.
Otherwise `addField()` without positioning is adding fields to the end of TCA config.When copying an existing TCA config oder editing an existing, there should be a possibility to set a pointer.
Otherwise `addField()` without positioning is adding fields to the end of TCA config.https://git.spooner.io/spooner-web/tcabuilder/-/issues/8Look for custom label when positioning2021-07-23T06:13:19ZThomas LöfflerLook for custom label when positioningIf a field has another label, it should be handled when positioning another element.If a field has another label, it should be handled when positioning another element.https://git.spooner.io/spooner-web/tcabuilder/-/issues/6Edit all types at once2021-07-23T06:13:27ZThomas LöfflerEdit all types at once