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

Edit Content: Explore the posibility to use web components for fields #25434

Closed
2 tasks
Tracked by #25445
fmontes opened this issue Jul 6, 2023 · 1 comment
Closed
2 tasks
Tracked by #25445

Comments

@fmontes
Copy link
Member

fmontes commented Jul 6, 2023

Parent Issue

#25445

Task

We are going to start to reimplement the new design of the edit contentlet, this means we need to create components for each field.

We would like to do web components for each field so we can add them to the JSP (old version) of the edit contentlet and offer the customer improvements as soon as we build it.

In this post there is an approach that is worth to test: https://www.angular.love/en/2023/01/19/nx-angular-elements-case-study/

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

  • Find a way to create web components using angular and primeng
  • Don't use Stencil because we can't use the primeng components library

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

  1. We need to take into consideration performance and file size
  2. Is important that we can use primeng components library because we don't want to style another library to match our design system

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@rjvelazco
Copy link
Contributor

This is a Pull Request (PR): #25581. In this PR, I have explored the potential of creating a web component for content types fields.

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

Successfully merging a pull request may close this issue.

3 participants