-
Notifications
You must be signed in to change notification settings - Fork 36
documentation(976110): updated the built-in block sections for the block editor in the core and mvc platforms #4459
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
Conversation
The running CI Job is terminated due to changes committed on the source branch for this Merge Request and CI triggered for latest commit. |
CI Status: ABORTED ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
|
||
# Blocks in ##Platform_Name## Block Editor control | ||
|
||
The Block Editor control enables you to create block-based content editing solution using various types of blocks. The [blocks](../api/blockeditor/#blocks) property allows you to define and manage the content structure of your editor. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for core and MVC the API mapping is not proper @KaviBharathi-SF5060 change in all places it is mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mapped the proper API reference sir
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Feature description
Need to update the built-in block sections for the block editor in the Vue and Core, MVC platforms
976110
Restructured the Blocks section into the following subcategories:
Requirement and specification document.
NA
API Review task
NA
Feature matrix document
Provide the details about the areas or combinations which have been tested against this code changes.
Feature acceptance criteria (Test-case document)
NA
Automation details
Mark 'Is Automated' field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the feature is automated.
Test bed sample location
NA
Feature completion checklist
UX changes got approval if UI is added or modified?
Drafted UG for this feature?
Content team reviewed the UI content changes.
Is this the common feature which needs to be addressed in the same component or on other components in our platform?
Is there any existing behavior change due to this code change?
breaking-change
label.Blazor Checklist
Confirm whether the ensured feature is in both Blazor Server and WASM.
Do the code changes cause any memory leak and performance issue?
Reviewer Checklist
Created task in Blazor to synchronize if the feature is not available and applicable.