China
Africa
Explore chapters and articles related to this topic
Reconceptualizing Technical Communication Pedagogy in the Context of Content Management
Published in Tracy Bridgeford, Teaching Content Management in Technical and Professional Communication, 2020
CM “is a set of processes and technologies that supports the collection, managing, and publishing of information in any form or medium” (Wikipedia, n.d.). As a result of its more popular sister term “content management system,” “we tend to look at content management as a digital concept, but it’s been around for as long as content. For as long as humans have been creating content, we’ve been searching for solutions to manage it” (Barker, 2016). As “the process for collection, delivery, retrieval, governance and overall management of information in any format” (Kiwak, n.d.), CM may not necessarily involve digital technologies, although in today’s environment it is hard to imagine it not doing so. Another term that has often been used in its place is “asset management,” although this is more context dependent because it could denote other types of assets, such as financial assets. Whichever the term, content management describes the process of content lifecycle from its creation to its presentation, delivery, storage, reuse, etc.
Portal-Based Content Management
Published in Shailesh Kumar Shivakumar, and User Experience Platforms, 2015
Content management process includes steps such as selection of content authoring template, configuring the template for current content, content authoring, attaching static assets, metadata tagging with content, SEO/analytics specification, content categorization, content workflows, content translation, multi-device renditions, content preview, and content promotion.
Usevalia: Managing Inspection-Based Usability Audits
Published in International Journal of Human–Computer Interaction, 2022
Raimel Sobrino-Duque, Juan Manuel Carrillo-de-Gea, Juan José López-Jiménez, Joaquín Nicolás Ros, José Luis Fernández-Alemán
The advancements in hardware and software technologies led to the evolution of the modern-day CMS (Content Management System) which allows anyone to design a website without the need for coding knowledge. CMS is defined as computer applications that allow the editing and publishing of content, along with maintenance from the user interface. Moreover, CMS has been developed as a modular system with the possibility of programming individual features as extensions (Blazek et al., 2019). Furthermore, open-source CMS, such as Drupal have been the choice preferred for the development of several web applications. Many users employ Drupal for website development owing to multiple features, such as flexibility in content creation, easy administration of users, and the capability to handle complex workflows (Iqbal et al., 2020).
Continuous Integration, In-Code Documentation, and Automation for Nuclear Quality Assurance Conformance
Published in Nuclear Technology, 2021
Andrew E. Slaughter, Cody J. Permann, Jason M. Miller, Brian K. Alger, Stephen R. Novascone
Of course, these three automatically generated lists are just a portion the necessary documents for the NQA-1 standard. Recall that in Sec. IV, a key feature of MooseDocs was that documentation, just like physics with MOOSE, are inheritable. In general, this is accomplished by the aforementioned content management system. The concept is extended further for NQA-1 documents with a custom template extension for MooseDocs. This allows the framework documentation of MOOSE to include a complete set of NQA-1 documents, such as the software test plan, the system design description, etc. This inheritance allows for applications, such as BISON, to inherit all the NQA-1 documents, including the requirements from the framework. Therefore, if an application follows the same development process described in Sec. II, it can automatically create design documents and annotate test specifications for a complete set of NQA-1–compliant documentation. The generated documents are comprised of the application’s specific traceability tables and the correct links to the framework-level documentation. This concept allows INL to rapidly deploy any MOOSE-based application to serve a safety function with a minimal impact on the software developers.
Current status and future directions of geoportals
Published in International Journal of Digital Earth, 2020
Hao Jiang, John van Genderen, Paolo Mazzetti, Hyeongmo Koo, Min Chen
The third challenge comes from the functionality. Basic services like data search engine, data online browser can support finding and viewing for ordinary use demand, but not the requirements from the professional users. Some geoportals only act as a content management system or shopping system, instead of a professional web GIS system. Thus the searching ability is provided in default by the template of the system and is sometime not suitable for raster and vector geospatial data. Many Chinese geoportals provide the preview function, but, in some cases, they only provide previews, but not the data itself. Professional users may need to know the coverage and the topology information before downloading, and thus at that time an overlay or add layer function should be developed. In this case, Open Geographic Modeling System (OpenGMS) provides specific data process services (including data mapping services, refactoring services, and visualization services) beyond traditional data services to help modeler to prepare suitable data for geographic simulation the open web environment (e.g. Wang et al. 2018; Yue et al. 2019).