14. WYSIWYG Editors
• Designed as one size fits all
• Bloat
• HTML produced can be bag of
hurt
• Just awful for certain tasks
(Blogging about code anyone?)
• Developers love the control
19. Technical Overview
• JavaScript Fieldtype Framework
• Powered by RequireJS
(AMD, load on demand)
• Many fields work without
modification
• A fieldtype can be a single JS file
20. Front end control
Article Page
Title
WYSWYG
• “Linear” story allows layout
control
Gallery • Each “block” can be targeted
with CSS
WYSWYG • RSS + Atom feeds still work
Image
25. Client Side Data
Control Panel Templates
1. AJAX request to custom 1. AJAX request to custom JS/XML
module method template
2. Parse AJAX request 2. Channel Entries Tag
3. Query DB
Not flexible enough
4. EE->output-> No query strings
send_ajax_response()
27. EE JavaScript API
• Why doesn’t it exist?
• Fieldtypes tricky
• What about:
• Channels
• Categories
• Entry meta data
• Site preferences
• Standardised & predictable
34. Data Services
• EEJS makes working with data
easy
• CP & Templates
• What about off-site?
• APIs
• Mobile Apps
35. Data Services
• No standard external API
• Custom APIs possible with
templates
• Tedious
36. Data Services
Like EEJS, standardised data can
be made available
37. Considerations
• REST
• CodeIgniter, not ExpressionEngine
• Performance EE Sessions,
template tracking,
template parsing,
• Output format are not needed !