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.

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

[FEATURE] Finish package @yoopta/renderer #122

Open
1 task done
Darginec05 opened this issue Apr 21, 2024 · 0 comments · May be fixed by #128
Open
1 task done

[FEATURE] Finish package @yoopta/renderer #122

Darginec05 opened this issue Apr 21, 2024 · 0 comments · May be fixed by #128
Assignees

Comments

@Darginec05
Copy link
Owner

Is this a unique feature?

  • I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.

Just upgrating package @yoopta/renderer from v2 to v4

Proposed Solution

Package @yoopta/renderer is used for just rendering content without any edit tools and external packages.
In simple it useful when you care about page perfomance and good SEO indicators

So, the solution is next:

  1. Every element inside block should have default renderers
  2. These default renderers can be replaced by custom renders
import Callout from '@yoopta/callout'

const CustomCalloutRender = () => ...

const plugins = [
  ...,
  Callout.extends({
     renders: {
       callout: CustomCalloutRender
     }
  })
]
  1. These renderers should be used in @yoopta/renderer package

Screenshots

No response

Do you want to work on this issue?

Yes

If "yes" to the above, please explain how you would technically implement this (issue will not be assigned if this is skipped)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant