Explore chapters and articles related to this topic
Conclusion
Published in Carlos Evia, Creating Intelligent Content with Lightweight DITA, 2018
My main recommendation for any plan for implementing ideas discussed in this book is the same for all scenarios: do not jump directly to writing code and copying all your existing content from, say, a word processor to a text editor or LwDITA-aware software application. Writing is a process regardless of medium; paper and pen, word processor, or cross-format LwDITA content repository. . . all these writing environments need a plan. Focus on the abstractions from Chapter 8 and develop a strategy that works for your content requirements. Maybe things in your world are complex and full DITA XML will be the way to go, or maybe you are not ready to adopt LwDITA and will just want some ideas about computational thinking to improve your process in a web content management system. As long as you keep in mind the abstractions behind the process and the structure that enables the production of discoverable, reconfigurable, and adaptable content, my job will be done.
A Framework for Identifying the Drivers of Information Systems Development Method Emergence
Published in Roger H.L. Chiang, Keng Siau, Bill C. Hardgrave, Systems Analysis and Design, 2017
Sabine Madsen, Karlheinz Kautz
From the outset, the application was envisioned as an RDR to be implemented based on a commercial Web content management system, which would support the market research department’s internal work practices (i.e., the report production process) and external sale to customers through storage and online analysis and reporting of data at a high granularity. Before project initiation, the contingency approach Multiview/WISDM (Vidgen et al., 2002) was chosen as the formalized method and used to inform the construction of a situation-specific method outlined in the form of a detailed project plan, which was included in the original TCS project proposal and formally approved by the TCS program. The development process was planned as a prototype driven approach where two of the department’s core products, paper-based market reports on the bottled water and watercooler markets, would be used as the point of departure for implementing the first working prototype. As the application was expected to be based on a Web content management system, the development approach was planned with an emphasis on the Web-based front-end, organizational change and implementation.
Find the right solution
Published in Jens Jacobsen, Tilman Schlenker, Lisa Edwards, Implementing a Digital Asset Management System, 2012
Jens Jacobsen, Tilman Schlenker, Lisa Edwards
Digital Rights Management (DRM) solutions usually are not systems on their own, but part of another software like a Web Content Management system or an e-commerce database. They manage the access rights a customer has for files, usually media. DRM is commonly used today in software for media playback like Apple’s iTunes, which makes sure you can only listen to AAC files that you bought yourself in its web shop. In the same way, Microsoft Windows controls the handling of WMA files that are locked by WM DRM (Windows Media Digital Rights Management).
Towards Digital Forensics Investigation of WordPress Applications Running Over Kubernetes
Published in IETE Journal of Research, 2023
Muhammad Faraz Hyder, Syeda Hafsa Ahmed, Mustafa Latif, Kehkashan Aslam, Ata. U. Rab, Mussab T. Siddiqui
There has been very little work in the domain of forensics investigation of the WordPress application. Specifically, to the best of our knowledge, there is no previous work that investigated WordPress applications running over a container-based environment. Some works focus on the security of WordPress. The authors in [19] proposed and developed a tool for finding the vulnerabilities in websites running over a Web Content Management System like WordPress. However, they did not cover any forensics investigation process. The authors in [20] highlighted the importance of securing the different plugins of WordPress. They provided a comparative analysis of additional security plugins for WordPress in terms of their capability to detect malicious plugins. The authors in [21] assessed different vulnerabilities in WordPress plugins. The authors in [22] proposed a Semantic-aware log decoding and generation algorithm (SAG) to prepare network monitoring and forensics for higher-level reasonings. Also, demonstrate the novelty of SAG by considering a synthetic case study based on WordPress. The authors in [23] proposed a mechanism for monitoring microservices using Blackbox tracing and event logs. The work used different microservices and aggregated their logs. Zipkin [24], the distributed tracer for microservices developed by Twitter, is one of the open-source options available. Zipkin uses collectors on the target system's nodes to track and save data. The authors in [25] presented forensics investigation challenges of web content management tools, including Joomla, WordPress, Drupal, etc. The work, however, didn't present any prototype. The work in [26] analyses WordPress's malicious plugins. Although many useful plugins are available, some may also contain malicious behaviour that can lead to serious data breaches incidents.