Elementor Data Structure#344
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ PR Description
1. Problem & Context
Reorganizing documentation structure to logically group element type documentation under a single section, moving "Responsive Data" from a separate "Special Cases" category into the main element types section for better discoverability.
2. What Changed (Where)
sidebars/data-structure.js: Removed "Special Cases" section; moved "responsive-data" into element types groupdata-structure/index.md: Restructured headers; consolidated "Responsive Data" with other element types3. How It Works
Navigation sidebar now reflects a flatter hierarchy where all element type documentation (general, container, widget, repeaters, responsive-data, global-styles) lives under one collapsible section rather than being split between element types and special cases.
4. Risks
None — documentation-only refactor with no functional impact. Navigation structure clarifies information hierarchy.
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how