Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Discuss, test and document interoperability with fluid_styled_content et al #29

Open
jonaseberle opened this issue Nov 21, 2020 · 1 comment
Open

Discuss, test and document interoperability with fluid_styled_content et al #29

jonaseberle opened this issue Nov 21, 2020 · 1 comment

Comments

@jonaseberle
Copy link
Collaborator

jonaseberle commented Nov 21, 2020 •
edited
Loading

While moving to a proper lib.contentBlock we should reevaluate the best way to integrate with other existing (and coming) rendering possiblities.

We should deliver:

  • good standards that don't leave shown backend fields inoperable
  • a system that can be added to an existing EXT:fluid_styled_content-based system
  • a system that is extensible
@jonaseberle jonaseberle mentioned this issue Nov 21, 2020
Closed
5 tasks
jonaseberle added a commit that referenced this issue Jan 9, 2021
@jonaseberle
[TASK] inherit from lib.contentBlock, remove current fluid_styled_con…
313498a 
…tent / bootstrap_package integration

This is meant as a cleanup step now until we tackle the topic again in #26 and #29.

(fixes #27)
@typecat
Copy link
Contributor

typecat commented Sep 9, 2022

I would discard this due to https://forge.typo3.org/issues/98134

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonaseberle @typecat