# assets Published articles for assets. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Doctave Studio 2.0 Beta: The editor for technical writing and docs-as-code DevFeed: [Doctave Studio 2.0 Beta: The editor for technical writing and docs-as-code]() Original publisher: [Read original article]() Author: Doctave Team Published: 2024-10-08T05:00:00Z Content type: release Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Documentation](), [Tooling](), [Markdown](), [OpenAPI Specification](), [CI/CD]() Tags: [announce](), [assets](), [auto-complete](), [beta](), [blog](), [ci-cd](), [components](), [docs](), [docs-as-code](), [editor](), [real-time](), [technical-writing]() ### AI overview Doctave announces the public beta of Doctave Studio 2.0, an editor for technical writing and docs-as-code. The beta includes a modern editor, real-time Markdown and OpenAPI previews, auto-complete for links and assets, and inline Markdown error reporting. ### Source excerpt We're excited to announce that Doctave Studio 2.0 is now available in public beta! Doctave Studio is a new editor for technical writing and docs-as-code, and we're excited to share it with you. Want to see it in action? Here's a quick introductory video of Doctave Studio 2.0: If you just want to see how to participate in the beta, you can jump straight to the end of this post Why build a new editor? One of the biggest issues with docs-as-code is inconsistent tooling. While there are great tools out there (like Vale), it's really hard to create a great authoring environment for docs-as-code. Getting spell check, broken links checking, auto-complete, and more configured is often too complex or time consuming, that lots of authors live without these tools. This problem is compounded when you have multiple authors collaborating on the same documentation. One will have a spell checker configured, one will have auto-complete configured, another doesn't have a broken links checker. The lack of a common authoring system causes friction, confusion, and ultimately raises the barrier for contributions. And after all that, you still need to set up these same checks in your CI/CD pipeline! This is what we set out to solve with Doctave Studio 2.0. We've already made it easy to host, version, and review docs-as-code projects with our existing product. Now we're taking the next logical step and improving the docs-as-code authoring experience. What's in the Doctave Studio 2.0 beta? Today we're launching Doctave Studio 2.0 into beta with a few key features: A new, modern editor with a focus on the authoring experience Real-time previews of your content as you type (Markdown and OpenAPI!) Powerful auto-complete for your links, assets, and components Great error-reporting inline in your Markdown Let's see some of these in action! Real-time previews The right-side panel in Doctave Studio is dedicated to a real-time preview window. It shows you what your content will look like once publi ## Threat Modeling Google Cloud (Threat Model Thursday) DevFeed: [Threat Modeling Google Cloud (Threat Model Thursday)]() Original publisher: [Read original article]() Author: Adam Published: 2023-03-01T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Google Cloud Platform (GCP)](), [Security](), [Google](), [Architecture & Design]() Tags: [assets](), [cloud](), [cloud-platform](), [data](), [diagram](), [google](), [google-cloud](), [google-cloud-platform](), [processes](), [security]() ### AI overview The article reviews NCC's threat model for Google Cloud Platform, examining its methodology, diagrams, assets, boundaries, threat actors, attack goals, weaknesses, and potential threats. It offers constructive observations about the model's organization, readability, and use of STRIDE-related categories. ### Source excerpt NCC has released a threat model for Google Cloud Platform. What can it teach us? ## Setting Up AWS S3 Buckets + CloudFront CDN for your Assets DevFeed: [Setting Up AWS S3 Buckets + CloudFront CDN for your Assets]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-01-23T23:01:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Amazon S3](), [Amazon Web Services](), [Cloud](), [Content Management System](), [cloud-infrastructure](), [Caching](), [Website]() Tags: [assets](), [aws](), [aws-s3](), [cdn](), [cloud](), [cloud-storage](), [cloudfront](), [cms](), [convenient](), [distribution](), [here-s](), [how-to](), [inexpensive](), [insights](), [latency](), [like](), [right](), [s3](), [storage](), [store](), [using]() ### AI overview A tutorial on storing website and CMS assets in Amazon S3 and serving them through CloudFront. It explains the benefits of cloud storage, recommends using CloudFront rather than serving files directly from S3 buckets, and describes how cached assets are delivered from nearby edge locations. ### Source excerpt Using a cloud storage system like AWS S3 with a CDN distribution can be a convenient and inexpensive way to store your assets. Here's how to set it up right. ## Animations are assets: using Core Animation archives on iOS DevFeed: [Animations are assets: using Core Animation archives on iOS]() Original publisher: [Read original article]() Published: 2018-11-11T14:00:00Z Content type: tutorial Language: en Sources: [Rambo Codes]() Topics: [iOS](), [Graphics](), [coding]() Tags: [animation](), [assets](), [coding](), [format](), [ios]() ### AI overview This tutorial explains why complex, relatively static animations can be treated as assets on iOS. It presents Core Animation Archives as a way to store an archived Core Animation layer tree and load it at runtime, while noting that video may be suitable for simpler cases. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Database & Asset Syncing Between Environments in Craft CMS DevFeed: [Database & Asset Syncing Between Environments in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-06T08:41:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Databases](), [Git](), [Development](), [MySQL]() Tags: [assets](), [cms](), [database](), [development](), [environment](), [environments](), [git](), [help](), [here-s](), [important](), [insights](), [it-s](), [maintenance](), [pain](), [syncing](), [workflow]() ### AI overview This tutorial presents a practical workflow for syncing Craft CMS databases and assets across local development, staging, and production environments. It recommends using Git for one-way code flow and limiting the approach to small- and mid-size projects where more elaborate replication or migration techniques may be excessive. ### Source excerpt Syncing the database & assets between environments is an important workflow, but it's a pain. Here's some help ## A bug affecting ReactOS helper utilities DevFeed: [A bug affecting ReactOS helper utilities]() Original publisher: [Read original article]() Published: 2014-09-23T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [bug](), [Tool]() Tags: [assets](), [bug](), [core](), [free](), [open-source](), [opensource](), [os](), [project](), [react](), [reactos](), [tools](), [useful](), [utilities](), [win32](), [winapi](), [windows]() ### AI overview The article discusses helper utilities in the ReactOS project and the need to fix a bug affecting them because they were considered core assets of the project. ### Source excerpt The answer to the mystery about the bunnies' extracurricular activities came soon enough, in no small part thanks to the amount of time the two spent investigating. The bunnies were extremely useful helper utilities and if they were suffering from a bug, it needed fixing otherwise the project would risk losing one of its more useful tools. By the end of these events the bunnies would be considered one of the core assets underpinning the entire project.