# Publishing Publishing is the creation of documents using page layout skills on a personal computer primarily for print. Desktop publishing software can generate layouts and produce typographic quality text and images comparable to traditional typography and printing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Shinji Mikami to join AIAS Hall of Fame at 2026 DICE Awards DevFeed: [Shinji Mikami to join AIAS Hall of Fame at 2026 DICE Awards]() Original publisher: [Read original article]() Author: Diego Argüello Published: 2026-09-16T16:31:40Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Game Development](), [Publishing]() Tags: [2026](), [awards](), [developer](), [industry]() ### AI overview Shinji Mikami will receive the AIAS Hall of Fame Award at the 2026 DICE Awards. Goichi Suda will present the award, which recognizes Mikami's more than 30-year career in the game industry. ### Source excerpt Goichi Suda will be presenting the award to the Resident Evil director. ## Adobe's Shift from a Content-Rich Website to a Product-Focused Site DevFeed: [Adobe's Shift from a Content-Rich Website to a Product-Focused Site]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-09-14T16:21:36Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Website](), [Publishing]() Tags: [adobe](), [articles](), [content](), [content-first](), [content-strategy](), [damned-fine-journalism](), [design](), [how-to](), [interviews](), [money](), [opinion](), [products](), [publishing](), [state-of-the-web](), [web-design](), [web-design-history](), [websites](), [zeldman]() ### AI overview The article reflects on Adobe's website in 2000 as a content-rich publication featuring how-to articles, opinions, artist interviews, and product information. It contrasts that model with Adobe's later shift toward a conventional product-focused site and argues that brands did not broadly replace the publishing opportunities lost as journalism declined. ### Source excerpt 2000 was the peak year for Adobe's website. It was a content site filled with creative how-to articles, opinion pieces, and artist interviews where you could also, if you wished, buy or get info on Adobe products. Now this is how you create a product site for a suite of creative products, I told myself [...] The post Remembrance of Websites Past appeared first on Jeffrey Zeldman Presents. ## Xbox to publish Kojima Productions' Physint after PlayStation ends partnership DevFeed: [Xbox to publish Kojima Productions' Physint after PlayStation ends partnership]() Original publisher: [Read original article]() Author: Diego Argüello Published: 2026-09-10T19:35:18Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Xbox](), [Publishing]() Tags: [company](), [news](), [partner](), [partnership](), [partnerships](), [xbox]() ### AI overview PlayStation Studios ended its publishing partnership with Kojima Productions on Physint, and Xbox will take over publishing the game. The companies also plan collaborations across film and television. ### Source excerpt Xbox is committing to the project during a significant period of change for the company that has so far included mass layoffs and after numerous canceled publishing partnerships. ## 📚 Books I Read in July and August 2026 DevFeed: [📚 Books I Read in July and August 2026]() Original publisher: [Read original article]() Author: Sergio Visinoni Published: 2026-09-09T05:00:34Z Content type: opinion Language: en Sources: [Sudo Make Me a CTO]() Topics: [Artificial Intelligence](), [Publishing]() Tags: [2026](), [ai](), [books](), [reviews]() ### AI overview A July and August 2026 roundup of books read by the author, including a highlighted review of Cory Doctorow's The Reverse Centaur's Guide to Life After AI. The review describes the book's argument that the current AI rush is a bubble driven by big tech's pursuit of investor growth narratives, with investors rather than users as the primary target of the hype. ### Source excerpt Back from a long break with a long list of summer reads. Two highlights, one of which comes with some caveats. Also, a great biography, more vibe writing and a bunch of sci-fi reading because why not? ## Aggro Crab launches publishing label for games costing up to $500,000 to launch DevFeed: [Aggro Crab launches publishing label for games costing up to $500,000 to launch]() Original publisher: [Read original article]() Author: Chris Kerr Published: 2026-09-01T17:02:48Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Publishing](), [Generative AI]() Tags: [generative-ai]() ### AI overview Aggro Crab has launched Aggro Crab Presents, a publishing label for intense, stylized games. The label will consider projects requiring $500,000 or less to launch within two years and has already signed Rebounder and Subway Midnight. ### Source excerpt The studio wants to support 'intense, stylized games with an attitude' - but isn't interested in 'generative AI slop.' ## How Non-Coders Use AI to Build Vibe-Coded Businesses DevFeed: [How Non-Coders Use AI to Build Vibe-Coded Businesses]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-08-30T14:03:13Z Content type: article Language: en Sources: [Behind the Craft]() Topics: [Vibe coding](), [coding](), [Artificial Intelligence](), [Publishing](), [Security]() Tags: [ai](), [apps](), [business](), [coding](), [distribution](), [examples](), [payments](), [prototype](), [revenue](), [security](), [vibe-coding]() ### AI overview The article presents three examples of vibe-coded apps that reached six-figure revenue and outlines four steps for turning a prototype into a business, covering publishing, security, payments, and distribution. ### Source excerpt 3 examples of vibe-coded apps that reached six figures in revenue, plus 4 steps to turn your prototype into a real business, including publishing, security, payments, and distribution. ## Publishing Playwright HTML reports on GitLab Pages DevFeed: [Publishing Playwright HTML reports on GitLab Pages]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-29T23:56:10Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [GitLab](), [Playwright](), [CI/CD](), [CI/CD Pipeline](), [Publishing]() Tags: [bun-create-playwright](), [ci-cd](), [ci-cd-pipeline](), [github-pages](), [gitlab](), [gitlab-ci](), [playwright]() ### AI overview This tutorial explains how to add a deploy stage to a GitLab CI/CD pipeline for a Bun-based Playwright project. The stage publishes generated Playwright HTML reports, including screenshots and videos, to GitLab Pages so they can be viewed online. ### Source excerpt We've added a lot to our demo project, bun--create-playwright. We've explored setting up a Playwright framework using bun, a new package manager bundled into Claude Code. We've added typechecking, and formatting and linting. We've set up a CI/ CD pipeline for our tests using GitLab, one with three stages: Quality: We check that the formatting, linting and typechecking is correct for any changes we attempt to push to the code base. Test: We run the smoke and then the regression tests to make sure that everything still works. Report: We bundle an archive of the Playwright generated HTML report, with screenshots and videos if things fail. For this post, we will add a new stage to this GitLab pipeline: Deploy: Where we will deploy the HTML report to GitLab Pages, so we can view it online. What is GitLab Pages? GitLab Pages is a built-in feature of GitLab that allows you to publish static websites directly from a repository in GitLab. Similar to GitHub Pages, it is commonly used to host project documentation, personal blogs, portfolios, or corporate landing pages for free. From the GitLab Docs / Pages: "To use GitLab Pages, you must create a project in GitLab to upload your website's files to. These projects can be either public, internal, or private. "By default, GitLab deploys your website from a specific folder called public in your repository. You can also set a custom folder to be deployed with Pages. When you create a new project in GitLab, a repository becomes available automatically. "To deploy your site, GitLab uses its built-in tool called GitLab CI/CD to build your site and publish it to the GitLab Pages server. The sequence of scripts that GitLab CI/CD runs to accomplish this task is created from a file named .gitlab-ci.yml, which you can create and modify. A user-defined job with pages: true property in the configuration file makes GitLab aware that you're deploying a GitLab Pages website. "You can either use the GitLab default domain for GitLab Pages websit ## Journey maker thatgamecompany announces thatgamepublisher DevFeed: [Journey maker thatgamecompany announces thatgamepublisher]() Original publisher: [Read original article]() Author: Nicole Carpenter Published: 2026-08-25T14:10:19Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Publishing]() Tags: [community](), [funding](), [games](), [indie-developers](), [marketing](), [publisher](), [strategy]() ### AI overview thatgamecompany, the developer of Journey and Sky: Children of the Light, has launched thatgamepublisher, a publishing department funded by profits from Sky. It has signed a couple of unreleased games and offers funding, marketing, community, and strategy services to game teams of varying sizes and at different development stages. ### Source excerpt Profit from Sky: Children of the Light will support the initiative. ## Ship agent skills like packages: discovery index, digests, and install sources DevFeed: [Ship agent skills like packages: discovery index, digests, and install sources]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Agent Skills](), [Agent Skill](), [ai-coding](), [Publishing](), [GitHub](), [make](), [rubygems]() Tags: [agent-experience](), [agent-skill](), [agent-skills](), [ai](), [coding](), [coding-agents](), [dx](), [github](), [jamstack](), [json](), [llms](), [npm](), [rubygems](), [sha-256](), [skills]() ### AI overview This tutorial explains how to publish agent skills so AI coding agents can discover and install them. It covers a .well-known/agent-skills/index.json discovery index, SHA-256 integrity digests, single-file, multi-file, and bundle packaging, multiple install commands, and hosting skills from a GitHub repository while re-hosting the served files on the publisher's domain. ### Source excerpt How to publish agent skills so any AI coding agent can find and install them: the .well-known/agent-skills/index.json discovery index, SHA-256 integrity digests, single-file vs multi-file vs bundle packaging, and every install command. Worked from the catalog we just open-sourced. ## Logic for Programmers is Done DevFeed: [Logic for Programmers is Done]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-07-29T15:43:52Z Content type: release Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Publishing](), [LaTeX]() Tags: [announcement](), [blog](), [book](), [free](), [latex](), [typography]() ### AI overview Logic for Programmers has reached version 1.0 and is available in print. Early ebook buyers can download the completed edition for free through Leanpub. ### Source excerpt It's done. Logic for Programmers is now 1.0 and available in print. Full announcement here, official website here, direct Amazon link here. If you got an early version of the ebook, you can go back to leanpub to download the 1.0 for free. This marks the completion of a project that took five years of work, six bookwriting professionals, fourteen domain experts, and fifteen public alphas. This has been, without a doubt, the biggest and most exhausting project I've ever done. The examples in the discarded drafts alone could make a second book. The cursed knowledge I've gained on LaTeX and typography could fill a third (or at least a couple of entertaining blog posts). Self-publishing was simultaneously the worst and best decision I made. Now excuse me I am going to sleep for a month. ## System Cards and Datasheets: A Technical Writers Guide DevFeed: [System Cards and Datasheets: A Technical Writers Guide]() Original publisher: [Read original article]() Author: Selvaraaju Murugesan Published: 2026-07-24T12:57:29Z Content type: article Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [Large Language Model](), [technical-documentation](), [Frontier Model](), [data](), [Publishing](), [trust]() Tags: [ai](), [ai-models](), [data](), [documentation](), [frontier-model](), [governance](), [guide](), [large-language-model](), [publishing](), [technical](), [transparency](), [trust]() ### AI overview This article explains how system cards, model cards, and datasheets document AI model behavior, capabilities, limitations, evaluation methods, safety controls, intended use, and the data behind models. It presents these documents as transparency and governance tools for developers, researchers, regulators, and enterprise buyers. ### Source excerpt Large Language Model providers are publishing system cards to bring transparency into their ... The post System Cards and Datasheets: A Technical Writers Guide appeared first on Document360. ## Codename One Publishes a CI-Backed Port Status Matrix DevFeed: [Codename One Publishes a CI-Backed Port Status Matrix]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ci](), [Development](), [Publishing]() Tags: [ci](), [report](), [screenshots](), [test](), [validation]() ### AI overview Codename One's new port status page maps 49 user-facing feature groups across 10 portability targets to current conformance results, environment data, skip reasons, and run dates. CI converts test and screenshot results into standardized reports that the website renders as a matrix. ### Source excerpt The Codename One port status page maps 49 feature groups across 10 targets to dated CI evidence and explicit skip explanations. ## A tool for generating Google Play feature graphics DevFeed: [A tool for generating Google Play feature graphics]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-05-07T13:41:05Z Content type: release Language: en Sources: [Effective Android]() Topics: [Google Play](), [App](), [Google](), [Publishing]() Tags: [app](), [color](), [feature](), [generate](), [google-play](), [publishing]() ### AI overview The article introduces a tool for generating Google Play feature graphics. Users provide an app name and brief description, then choose a brand color. ### Source excerpt Introducing the fastest way to generate feature graphic for Google Play out there 🔥 ## The Promise of Ethereum: Introducing the EF Mandate DevFeed: [The Promise of Ethereum: Introducing the EF Mandate]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2026-03-13T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Publishing](), [Open Source](), [Protocol (disambiguation)]() Tags: [ethereum](), [open-source](), [organizational](), [protocol](), [source]() ### AI overview The Ethereum Foundation is publishing the EF Mandate, a document that sets out its purpose, decision-making principles, and responsibilities. The mandate emphasizes Ethereum's commitment to user self-sovereignty, censorship resistance, open source, privacy, security, and resistance to extraction. ### Source excerpt Dearest Friends, Today we are publishing the EF Mandate, a document that serves as part constitution, part manifesto, and part guide for the Ethereum Foundation. It is written primarily for the EF itself: to be clear about what we are here to do, the principles by which we... ## Mintlify Adds Flexible Documentation Publishing and Content Management Features DevFeed: [Mintlify Adds Flexible Documentation Publishing and Content Management Features]() Original publisher: [Read original article]() Author: Hahnbee Lee Published: 2026-02-18T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Publishing](), [Markdown](), [MDX](), [OpenAPI Specification](), [configuration]() Tags: [api-documentation](), [best-practices](), [customizable](), [documentation](), [flexible](), [markdown](), [mdx](), [new-features]() ### AI overview Mintlify describes new features for technical writers, including granular publishing controls, plain Markdown files alongside MDX, more flexible OpenAPI references, relative imports, and implicit snippets. ### Source excerpt New features for technical writers who need customizable, flexible documentation systems. ## Addendum to GPT-5 System Card: Sensitive conversations DevFeed: [Addendum to GPT-5 System Card: Sensitive conversations]() Original publisher: [Read original article]() Published: 2025-10-27T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Jailbreak](), [Publishing]() Tags: [benchmarks](), [chatgpt](), [gpt](), [improvements](), [jailbreak](), [mental-health](), [model](), [safety](), [update]() ### AI overview This addendum to the GPT-5 system card presents baseline safety evaluations for sensitive conversations. It describes an October 3 update to ChatGPT's default model, GPT-5 Instant, intended to improve recognition of emotional distress, compassionate responses, and guidance toward real-world support, based on work with more than 170 mental health experts. ### Source excerpt This system card details GPT-5's improvements in handling sensitive conversations, including new benchmarks for emotional reliance, mental health, and jailbreak resistance. ## How I Wrote a Tech Book Without Finishing It First DevFeed: [How I Wrote a Tech Book Without Finishing It First]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-30T17:30:47Z Content type: opinion Language: en Sources: [Effective Android]() Topics: [Publishing](), [Jetpack Compose](), [Compose]() Tags: [book](), [compose](), [developers](), [opinion](), [publishing](), [revenue](), [sales](), [technical]() ### AI overview The author describes publishing Jetpack Compose Internals before the manuscript was complete, using Leanpub to release an initial version and update it with new chapters. Launching on the day Compose 1.0 became stable provided early validation and momentum, with reported revenue reaching around $70,000 in total. ### Source excerpt A lot of Android developers tell me they've thought about writing a technical book. ## New Maven Central signing key and snapshot location DevFeed: [New Maven Central signing key and snapshot location]() Original publisher: [Read original article]() Author: Jake Wharton Published: 2025-06-13T00:00:00Z Content type: release Language: en Sources: [Cash App Code Blog]() Topics: [Maven Central](), [Maven](), [Publishing](), [Open Source]() Tags: [end-of-life](), [maven-central](), [open-source-artifacts](), [public-key](), [release](), [server-android](), [signing](), [snapshot](), [snapshots](), [verification]() ### AI overview Cash App migrated its open source artifact publishing to Sonatype's new platform after OSSRH reached end of life. The change introduces a company-wide GPG signing key and moves snapshot builds to the Central Portal Snapshot repository. ### Source excerpt In response to Sonatype announcing the end-of-life for OSSRH, we have migrated to their new publishing platform for our open source artifacts. This is otherwise a transparent change for those who consume these artifacts from Maven Central, but there are two related changes which might affect your builds. ## Worth Reading: On Writing DevFeed: [Worth Reading: On Writing]() Original publisher: [Read original article]() Published: 2025-03-26T07:14:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Publishing]() Tags: [links](), [worth-reading](), [writing]() ### AI overview The article recommends a collection by Zvi Mowshowitz covering more than a dozen writing styles, beginning with J.R.R. Tolkien, for engineers seeking to improve their online presence and overcome difficulty starting to write. ### Source excerpt One of the most significant problems engineers face when trying to improve their online presence is the "How do I start writing?" roadblock (hint: publishing bland AI-generated slop won't get you far unless you aim to become a Thought Leader). Zvi Mowshowitz collected links to over a dozen different writing styles, starting with JRR Tolkien. I'm pretty sure you'll find something useful in that vast collection. ## A Blog, If You Can Keep It DevFeed: [A Blog, If You Can Keep It]() Original publisher: [Read original article]() Published: 2025-02-10T00:00:00Z Content type: opinion Language: en Sources: [The Fly Blog]() Topics: [fly.io](), [Publishing](), [Code]() Tags: [blog](), [cdn](), [close-to-users](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [go](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [networking](), [postgresql-clusters](), [servers](), [technical](), [writing]() ### AI overview A Fly.io team member reflects on the company's use of long-form technical EffortPosts to reach Hacker News audiences. The article argues that strict editorial processes, perfectionism, and concern about exhausting the audience have slowed publication, and describes a shift toward publishing more freely. ### Source excerpt A boldfaced lede like this was a sure sign you were reading a carefully choreographed EffortPost from our team at Fly.io. We're going to do less of those. Or the same amount but more of a different kind of post. Either way: launch an app on Fly.io today! Over the last 5 years, we've done pretty well for ourselves writing content for Hacker News. And that's mostly been good for us. We don't do conventional marketing, we don't have a sales team, the rest of social media is atomized over 5 different sites. Writing pieces that HN takes seriously has been our primary outreach tool. There's a recipe (probably several, but I know this one works) for charting a post on HN: Write an EffortPost, which is to say a dense technical piece over 2000 words long; within that rubric there's a bunch of things that are catnip to HN, including runnable code, research surveys, and explainers. (There are also cat-repellants you learn to steer clear of.) Assiduously avoid promotion. You have to write for the audience. We get away with sporadically including a call-to-action block in our posts, but otherwise: the post should make sense even if an unrelated company posted it after you went out of business. Pick topics HN is interested in (it helps if all your topics are au courant for HN, and we've been very lucky in that regard). Like 5-6 more style-guide things that help incrementally. Probably 3 different teams writing for HN will have 3 different style guides with only like ½ overlap. Ours, for instances, instructs writers to swear. I like this kind of writing. It's not even a chore. But it's become an impediment for us, for a couple reasons: the team serializes behind an "editorial" function here, which keeps us from publishing everything we want; worse, caring so much about our track record leaves us noodling on posts interminably (the poor Tigrises have been waiting for months for me to publish the piece I wrote about them and FoundationDB; take heart, this post today means that one i ## 2024 Wrapped: Newsletter, Coaching, Books DevFeed: [2024 Wrapped: Newsletter, Coaching, Books]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2025-01-10T15:58:20Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [engineering-culture](), [CI/CD](), [Microservice](), [Testing](), [Publishing]() Tags: [articles](), [continuous-delivery](), [contribution](), [engineering-culture](), [software-architecture](), [testing]() ### AI overview A 2024 retrospective covering the author's newsletter, coaching, training, video and streaming activity, conference participation, book contribution, and community projects. It reports audience and activity metrics, including 63 Substack posts, 125,000 Substack views, 223 coaching sessions, and increased video watch hours. ### Source excerpt Big wins in 2024: Coaching and Training, Meeting Kent Beck, Dave Farley, Sander Hoogendoorn, Speaking at conferences, Book Contribution, Youtube Channel Success, groCTO ## Release Content Faster DevFeed: [Release Content Faster]() Original publisher: [Read original article]() Published: 2023-08-11T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Firebase](), [Content Management System](), [Publishing](), [Accessibility](), [Developer experience](), [Web Development](), [Website]() Tags: [accessibility](), [astro](), [developer-experience](), [development](), [docs](), [firebase](), [html](), [web]() ### AI overview How Firebase rebuilt its blog with Astro, increasing performance by 71% and reducing publishing time from hours to minutes. The case study describes the limitations of Blogger and how Astro enabled faster publishing, accessible animations, and a better developer experience. ### Source excerpt How Firebase Cut Blog Publishing From Hours to Minutes with Astro ## Trying Substack as a Simpler Blogging Platform DevFeed: [Trying Substack as a Simpler Blogging Platform]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2023-07-06T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Publishing](), [configuration]() Tags: [blog-post](), [blogging](), [simplicity](), [subscriptions]() ### AI overview Bruce Eckel explains why the ceremony of creating blog posts can discourage him from writing and describes trying Substack as a simpler publishing platform. He likes its clean writing workflow, live preview, email delivery, and subscription-based business model, while noting that he is still adjusting to some limitations. ### Source excerpt TLDR: BruceEckel.substack.com I've noticed that I haven't been writing here that much lately, and I began to suspect it is because of the necessary ceremony of creating a blog post. Which, really, isn't that much but I've started to see that even the smallest amount can be an impediment. When I began trying to paint, I discovered these impediments, and they're different for each person. In my case, the stretched canvas was "too important" and I resisted putting paint on it (both parents grew up in the depression, so I am overly careful about wasting things, which makes experimentation hard). ## Simplifying the Plugin-Publish Plugin DevFeed: [Simplifying the Plugin-Publish Plugin]() Original publisher: [Read original article]() Author: Jozsef Bartok Published: 2022-07-18T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Development](), [configuration](), [Maven](), [Publishing]() Tags: [configuration](), [gradle](), [gradle-plugin](), [plugin-development](), [publication]() ### AI overview Gradle Plugin-Publish plugin version 1.0.0 simplifies publishing Gradle plugins by enforcing stronger conventions, reducing duplicate configuration, and clarifying how it integrates with signing and shadowing plugins. ### Source excerpt Configuring the publication of Gradle plugins to the Portal happens with the help of the Plugin-Publish plugin. The recently released version 1.0.0 of the plugin significantly improves the process by having stronger opinions and a more straightforward configuration. Stronger Conventions Gradle plugin development has a long history and has gradually evolved to use helper plugins to aid you with setting up your plugin project. The most important ones: Gradle Plugin Development plugin (java-gradle-plugin) Maven Publish plugin (maven-publish) The Plugin-Publish plugin shares this long history, and it ended up supporting all the various combinations of helper plugins. This results in too many ways of publishing plugins, and too many configuration options, with some having hard-to-understand semantics depending on the exact setup. For example, publication metadata can be generated via the maven-publish plugin or in other, ad-hoc ways. Depending on this, both plugin and marker GAV coordinates can vary, with surprising effects. Version 1.0.0 of the Plugin-Publish plugin addresses these issues by tightening and enforcing the conventions. The main helper plugins are always auto-applied: maven-publish is always used for generating the publication metadata (Maven POM & Gradle Module Metadata). java-gradle-plugin is always applied and used as a base for plugin definitions; as a consequence, the gradlePlugin block is now mandatory and the pluginBundle block has been trimmed down to remove all duplication. Unambiguous configuration When configuring the publication of plugins, each property of the end result should have a single way of being specified. To ensure that's the case, version 1.0.0 of the Plugin-Publish plugin is removing the pluginBundle.plugins block, as it was duplicating gradlePlugin.plugins. Unfortunately, the duplication is not (yet) perfect, so the pluginBundle.pluginTags map needs to be added to be able to define different tags for plugins published together. The [Next page]()