4. CONTENT MANAGEMENT SYSTEM Collaborative environment for designing a website (like IDE) Targets large no. of people to contribute and share stored data . Reduces the time involved in building a website Version Control
5. Introduction(contd) Allows people without technical details to post in the website For eg : one cannot expect an person posting a book review to know the coding of a website . Allows easy SEO.
13. MANIFEST FILE Every chrome extension has a JSON-formatted manifest file . Deals with important fields like the name and version no. , favicon . (contd)
14. Manifest (contd) "bookmarks" = reqd if browser uses bookmarks "chrome://favicon/" = <imgsrc="chrome://favicon/http://www.google.com/"> location of favicon. "cookies" =Required if the extension uses the chrome.cookies module. (contd)
15. Manifest (contd) "notifications" = desktop notification for the extension "tabs" Required if the extension uses the chrome.tabs or chrome.windows module.
16. HTML files Dynamic feed control Create html/css file as per requirements
17. Packaging Manifest.json Html files Image files (favicon) CSS Files Javascript files(if necessary) Create a zip file of the folder Package it as crx file (contd)
20. Testing & Publishing Go to developer mode in Google Chrome “Load unpacked extensions” Publish your extensions to Google Chrome extension Library . You need to have a google developer account for publishing (developer fee of 5$)