CMS & Chrome Extension Development
Download as PPTX, PDF1 like1,565 views
The document discusses the use of Content Management Systems (CMS) for building websites, emphasizing their advantages such as ease of use, collaboration, and integration with SEO. It also covers the process of developing Chrome extensions, highlighting the importance of a JSON-formatted manifest file and the steps needed for packaging and publishing the extensions. Examples of open-source CMS like Joomla, WordPress, and Drupal are provided, along with a brief tutorial on installation and development.
CMS & Chrome Extension Development
- 1. WEB designing/developmentSarang III yr ,Dept of CSE
- 3. Building chrome extensionWhy go in for a CMS ?Current scenario – we need a website for promoting every product/business. Building websites for organisations , product review websites using html is time consuming . Users of a website are not exposed to coding .Website are often integrated with the latest developments.
- 4. CONTENT MANAGEMENT SYSTEMCollaborative 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 websiteVersion 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.
- 8. Advantages :-Availability of a large no. of :-ThemesWidgetsModulesExtensions/plugins
- 10. How do I install a CMS?Download the setup file.Create db using phpmyadminChange the config.php fileInstallation is done !
- 12. Developing Chrome ExtensionDemo of Chrome Extensions(creating an RSS feed )
- 13. MANIFEST FILEEvery 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 filesDynamic feed controlCreate html/css file as per requirements
- 17. PackagingManifest.jsonHtml filesImage files (favicon)CSS FilesJavascript files(if necessary)Create a zip file of the folderPackage it as crx file (contd)
- 18. Packaging (contd) chrome://extensions Goto developer modePack extension Your extension & private key files are created(contd screenshot)
- 20. Testing & PublishingGo 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$)