狠狠撸

狠狠撸Share a Scribd company logo

Mobile CMS made simple

?Download as KEY, PDF?
?
Jonathan Schmid
Jonathan Schmid

The document discusses a module for CMS Made Simple that transforms the backend into a responsive HTML5 web app for mobile devices. The module allows the backend to be available offline and content to be edited offline. When online again, it checks for conflicts and pushes any changes. It takes an approach of using client-side storage to make the backend available as a web app that can do most of what a native mobile app can do, without needing to go through app stores.

1 of 11
Download to read offline
Mobile Back-end for by Jonathan Schmid CMS made simple 1
What? ? Module running in CMS made simple 1.11 and newer. ? Transforms the back-end into an HTML5 web app following the approach of responsive web development. ? Works with 1.11 standard theme "oneeleven". ? Other themes can make use of the functionality via the module's API. 2
Requirements ? Admin theme needs to be fundamentally viewable on mobile devices like ?oneeleven“.
Purpose ? Customize the back-end. ? Show only the most important information to ?t the device's viewport using responsive tables. ? Transform the back-end into a web app. ? Make the back-end available of?ine. Content is also editable of?ine. ? Check for con?icts if online again and push the changes that have been made. 4
Purpose ? As the implementation of HTML5 in mobile browsers develops it will probably be possible to use the device's ?le API in near future. ? Provide an API that can simply apply all needed changes to the backend themes. 5
Approach ? Web app ? Makes the back-end available of?ine using client-based storage. ? Works on clients like iOS and Android browsers. ? No need to pass the app stores' guidelines or pay fees. ? Can nearly do everything a native app can do. 6
Approach ? Of?ine editing ? Client-side time log for changes (via JavaScript). ? Use the event ContentPreSave and the time log in order to check for con?icts with changes other people have made meanwhile. 7
Approach ? Customization ? Set the name of the web app that will appear on the phone‘s home screen. ? Set a web app icon that will be delivered along with the name. 8
Approach ? Theme tools easily usable from inside admin templates. ? Detect whether the client is a mobile device or not. ? Include all needed JavaScripts and CSS. ? Generate mobile-speci?c meta data. 9
Perspectives ? Settings can be extended once new needs / ideas appear.
Realization ? The realization of the module requires an effort of approx. 60 working hours. ? The module might be ?nished at the time when CMS made simple 1.11 will be released. 11

More Related Content

Mobile CMS made simple

  • 1. Mobile Back-end for by Jonathan Schmid CMS made simple 1
  • 2. What? ? Module running in CMS made simple 1.11 and newer. ? Transforms the back-end into an HTML5 web app following the approach of responsive web development. ? Works with 1.11 standard theme "oneeleven". ? Other themes can make use of the functionality via the module's API. 2
  • 3. Requirements ? Admin theme needs to be fundamentally viewable on mobile devices like ?oneeleven“.
  • 4. Purpose ? Customize the back-end. ? Show only the most important information to ?t the device's viewport using responsive tables. ? Transform the back-end into a web app. ? Make the back-end available of?ine. Content is also editable of?ine. ? Check for con?icts if online again and push the changes that have been made. 4
  • 5. Purpose ? As the implementation of HTML5 in mobile browsers develops it will probably be possible to use the device's ?le API in near future. ? Provide an API that can simply apply all needed changes to the backend themes. 5
  • 6. Approach ? Web app ? Makes the back-end available of?ine using client-based storage. ? Works on clients like iOS and Android browsers. ? No need to pass the app stores' guidelines or pay fees. ? Can nearly do everything a native app can do. 6
  • 7. Approach ? Of?ine editing ? Client-side time log for changes (via JavaScript). ? Use the event ContentPreSave and the time log in order to check for con?icts with changes other people have made meanwhile. 7
  • 8. Approach ? Customization ? Set the name of the web app that will appear on the phone‘s home screen. ? Set a web app icon that will be delivered along with the name. 8
  • 9. Approach ? Theme tools easily usable from inside admin templates. ? Detect whether the client is a mobile device or not. ? Include all needed JavaScripts and CSS. ? Generate mobile-speci?c meta data. 9
  • 10. Perspectives ? Settings can be extended once new needs / ideas appear.
  • 11. Realization ? The realization of the module requires an effort of approx. 60 working hours. ? The module might be ?nished at the time when CMS made simple 1.11 will be released. 11

Editor's Notes

  1. \n
  2. \n
  3. \n
  4. \n
  5. \n
  6. \n
  7. \n
  8. \n
  9. \n
  10. \n
  11. \n