wp-front-end-editor
Opened 12 years ago
Closed 12 years ago
#2134 closed enhancement (duplicate)
Consideration of structural elements
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Severity: | normal |
| Plugin: | wp-front-end-editor | Keywords: | |
| Cc: | web-comments@… |
Description
What has been built thus far is a positively beautiful! Big props to all who have helped make it happen to date. I'm creating this ticket to prime(1) the conversation about being able to edit structural elements within a front-end editing environment.
Structural elements: rows, columns, grids, fluid containers, etc. I can't offer any meaningful suggestion on how they would be managed between editor and markup, but can offer a as-is and desired use case examples that might help?
Current Use Case Scenario
A nice combination for building templates with a Bootstrap based theme and some external tools:
- Activate a child theme from wp-bootstrap - http://320press.com/wpbs/
- Login to easel.io to drag & drop a mockup with static content
- Use its' export to html/css feature
- Paste CSS into child style.css
- Paste html into page template
- Use ACF to setup meta fields for admin data capture
- Replace static elements with dynamic WP generated tags
I can define all the rows, columns, etc that I want from bootstrap CSS, but the markup is confined to pre-defined templates. Users have as much flexibility in creation of content as I have with this mix of tools.
Future Front-End Editor Scenario
- Activate a child theme from wp-bootstrap
- Go to front-end of site and create new page (or CPT)
- Drag structural elements onto page
- Add content blocks into defined areas
- Press Gear off admin bar to get to meta data entry (if needed)
This probably brings up some related questions about whether/how short codes and widgets could be registered to the front-end editor that may be better suited for other feature plugins to solve. But, I think with the amount of editors which offer columns-via-short codes with a UI in the admin it would be well suited for consideration for front-end editor.
(1) Prime or continue the conversation:
http://torquemag.io/rethinking-the-wordpress-editor/
This ticket moved to https://github.com/avryl/wp-front-end-editor/issues/24.