Category: Content creation and design(Page 50 of 72)
Technologies and strategies for authoring and editing, including word processors, structured editors, web and page layout and formatting, content conversion and migration, multichannel content, structured and unstructured data integration, and metadata creation.
8th Wall is launching Face Effects, a new cloud tool that enables developers to create facial effects that wrap around someone’s face using augmented reality technology. The face filter developer tools are based on WebAR, which enables AR experiences to be accessed via a web browser instead of an app. 8th Wall Face Effects is designed to give developers and brands control to create face filters that are interactive, real-time, and that live on their own websites. Beyond WebAR, 8th Wall Face Effects can also be used across all devices (iOS/Android and desktops using a webcam) and benefit from no app required. You just click a link to experience it. Developers can choose the asset types, file sizes, and content to maximize the value for their audience.
Fans could connect multiple users together to create a shared shopping experience, and integrate with developers’ preferred analytics, customer relationship management system, and payment systems in virtual try-on products. Developers can simply scan a QR code to open up a cloud editor that adds a 3D object to your face. The edges of virtual sunglasses can stop at the edge of your face because an occluder prevents it from going right through your face. You can put virtual tattoos on your face to see what they look like before you make them permanent. With 8th Wall Face Effects, developers can anchor 3D objects to face attachment points, render face mesh with face components with textures and shaders, and design custom effects. Similar to 8th Wall’s existing World Effects and Image Target AR, Face Effects supports development with web frameworks such as A-Frame and Three.js. New developers can sign up for a 14-day free trial of the 8th Wall platform. Existing developers can log in and get started using the Face Effects project templates.
Microsoft introduced the first way for end users to experience the Fluid Framework in Microsoft 365 with the upcoming availability in preview of Fluid Workspaces and Fluid Components. Fluid Workspaces and Components work like the web to bring the right level of context and connection as well as seamlessly capture follow-ups in-line and edit action items with an entire team. Fluid Components and Fluid Workspaces will become available in more places over time. This initial public preview includes basic text, tables, lists, agendas and action items. These Fluid components will be available for creation in Outlook for the web and Office.com. Microsoft also announced the Fluid Framework will be made open source and hosted as a repository available on GitHub in the next month, allowing developers and creators to use infrastructure from Fluid Framework in their own applications. Coupled with the release of additional developer documentation and tooling, developers can work alongside Microsoft to create and evolve Fluid Framework as it is developed. Developers can take advantage of JavaScript APIs that give them access to collaborative, shared data structures which can be used to power collaborative experiences. They also can create Fluid components — elements that can be reused within Microsoft 365 and across applications.
The Gilbane Report on Open Information & Document Systems (ISSN 1067-8719) was periodical launched in March, 1993 by Publishing Technology Management Inc. which was founded by Frank Gilbane, its president, in June, 1987.
The Gilbane Report was sold to CAP Ventures Inc in December 1994, who published it until May, 1999, when it was bought by Bluebill Advisors, Inc. a consulting and advisory firm founded by Frank Gilbane. Bluebill Advisors continued to publish the Gilbane Report until March, 2005. The Gilbane Report issues from 1993 – 2005 remain available in either HTML or PDF (or both), on the Gilbane Advisor website, which is owned by Bluebill Advisors Inc.
Below is a link to the first issue of the Gilbane Report. There is also a PDF version.
Information architecture (IA) is the structural design of shared information environments; the art and science of organizing and labelling websites, intranets, online communities and software to support usability and findability; and an emerging community of practice focused on bringing principles of design and architecture to the digital landscape. Typically, it involves an information model or concept of information that is used and applied to activities which require explicit details of complex information systems. These activities include library systems and database development.
Digital experience (DX) emerged from work in the 1990s on “experience management” which included customers, employees, suppliers, and other stakeholders. Customer experience (CX) became the primary focus of experience management in the 2000s fueled by the growth of web commerce and other digital marketing channels. Technology suppliers and analysts serving marketing organizations began targeting CX in their products and services with features and their own marketing and branding efforts. In particular many “web content management (WCM) systems” became “customer experience management” (CXM), web experience management” or “web engagement management” systems (both using the WEM acronym). Most of these same products and services were also applicable and already in use for managing other stakeholder experiences, and became “digital experience” (DX) systems or platforms (DXPs), with CX being one component.
A positive digital experience requires much more than a pretty and fast web page or mobile app. There are other marketing technologies, internal back-end systems, supply chains, and operational workflows, digital or not, that need to be integrated with to ensure a smooth and informed experience. See Digital Experience is all about integration and agility.
The 2014 edition of the Gilbane Conference in Boston focused on Content Management, and Digital Experience: manage, measure, mobilize, monetize, and was designed for marketers, content managers, technologists, and executives responsible for building strategies and implementations for compelling multichannel digital experiences for customers, employees, and partners.
Chaired by: Frank Gilbane ∙ Organized by: Information Today Inc
The idea behind ‘information objects’ was that discrete pieces of information, along with metadata, were what should be the raw data for computing. Computing with information objects rather than bits or bytes or fixed-length records was the evolutionary step in information processing that would make the next big difference.
The concept of an ‘information model’ goes back at least to the 1970s with the growth of digital information and database software to manage structured data. In the 1980s information models became a key tool for organizing and managing documents and unstructured data, and in the 1990s emerged as a critical requirement for complex content management applications. A ‘content model’ is an information model for unstructured data, or a combination of unstructured data types and structured data.
“An Information Model provides the framework for organizing your content so that it can be delivered and reused in a variety of innovative ways. Once you have created an Information Model for your content repository, you will be able to label information in ways that will enhance search and retrieval, making it possible for authors and users to find the information resources they need quickly and easily… The Information Model is the ultimate content-management tool.” (The Gilbane Report, Vol 10, Num 1, 2002 , What is an Information Model & Why do You Need One?).
“An information model provides formalism to the description of a problem domain without constraining how that description is mapped to an actual implementation in software. There may be many mappings of the information model. Such mappings are called data models, irrespective of whether they are object models (e.g. using UML), entity relationship models or XML schemas.” (Wikipedia).
