🚀 New Release: API-Doc-Crafter just got sharper. Cleaner. Meaner.
Giving my little OpenAPI merging monster some upgrades.

It all started with a simple idea: merge OpenAPI specs from multiple repos.
Now? It transforms outdated Swagger specs to OpenAPI 3+, generates HTML pages with full navigation, and allows customization via config or env.

✨ SecurityRequirement deduplication - because why merge APIs if you can't also merge logic?

🧠 Custom metadata enrichment - inject your info, license, contact, and docs straight from config. No more excuses.

🔁 Better parser fallback - now tries more ways to read broken specs than your average intern in panic mode.

🎭 Variable substitution in outputs - ${variables} be gone. Use env or config, stay DRY, stay sane.

🧪 Tests expanded. HTML, JSON, YAML outputs covered like a nuclear bunker.

🧰 Powered by GraalVM, no reflection, blazing fast.
🐳 Native Docker builds.
🧼 Reflection config surgically trimmed. Less bloat. More edge.

Project: https://github.com/YunaBraska/api-doc-crafter
Happy crafting. And remember: if your docs aren't automated, they're probably lies.

#OpenAPI #Swagger #APIdocumentation #DevTools #GraalVM #Java21 #Docker #Automation #CleanCode #DevLife #APIDocs #OpenSource #DeveloperTools #coding #programming

GitHub - YunaBraska/api-doc-crafter: Clean, Merge, Group, Remove and generate OpenAPI documentation

Clean, Merge, Group, Remove and generate OpenAPI documentation - YunaBraska/api-doc-crafter

GitHub
Do developers need code samples in API documentation?

Although code samples have long been a staple in API documentation, I’m not sure users need them that much. Many developers now use AI tools that can generate the same basic code samples that are commonly provided in documentation. If these same developers pass in either the source files or reference documentation, AI tools can generate the code samples they need in the language they want, and better yet, tailored to their project and business context.

I’d Rather Be Writing Blog and API doc course

🛠️ Api-Doc-Crafter - Last-minute release before 2025! 🎆

lightweight tool (CLI, Docker, GitHub Action) to merge, sanitize, & generate API docs with ease! Built for Developer Experience, Minimalism, & Compliance.

🧩 Merge OpenAPI/Swagger files effortlessly.
🔒 Exclude sensitive endpoints with patterns.
🌐 Whitelabel HTML output
📁 YAML, JSON, & HTML support.
⚡ Blazing fast & portable.
🖌️ Add your own logo & branding.

https://github.com/YunaBraska/api-doc-crafter

#APIDocs #OpenAPI #DevTools #Automation #Sorting #Branding

GitHub - YunaBraska/api-doc-crafter: Clean, Merge, Group, Remove and generate OpenAPI documentation

Clean, Merge, Group, Remove and generate OpenAPI documentation - YunaBraska/api-doc-crafter

GitHub

Just wrapped up my talk at #APIdays Paris!
🚀 Built a wild GenAI tool that turns messy inputs into killer API docs using @Mistral + @HuggingFace.
Turning raw notes & specs into structured documentation? Yes, please.

🔗Demo: https://apidays-ai-novikova.netlify.app/documentation
🖥️ Slides: https://speakerdeck.com/lananovikova10/beyond-the-spec-bringing-context-to-life-with-genai-for-api-docs
📦 Code: https://github.com/lananovikova10/apidays-ai-poc
#AIDocumentation #APIDocs #generativeAI

API Documentation Generator

Generate API documentation using AI

Hi there.

Any technical writer here?

#technicalwriting #apiDocs

Docs as Code: The Best Guide for Technical Writers

https://dev.to/dumebii/docs-as-code-the-best-guide-for-technical-writers-97c#key-principles-of-docs-as-code

"Docs as Code is a methodology where documentation is treated like code. This means you use the same tools and processes for documentation that you use for code development. By doing this, you integrate documentation into the development process, making it a first-class citizen." -- #DumebiOkolo

#api360 #apiDocs #apiDesign #devRel

Docs as Code: The Best Guide for Technical Writers

Recently, my work has involved writing a lot of documentation and. Doing this has introduced me to...

DEV Community

Let’s Bring Science Into API Documentation

https://blog.jetbrains.com/writerside/2024/06/let-s-bring-science-into-api-documentation/

"Just like the knowledge of wave patterns enhances a surfer’s performance, understanding the principles of pattern recognition and learning styles can transform our approach to API documentation." -- #SvetlanaNovikova

#theMind #api360 #apiDocs

Let’s Bring Science Into API Documentation | The Writerside Blog

In today's fast-paced development environment, effective API documentation is not just a nice-to-have, but a necessity. This blog post explores how understanding pattern recognition and learning styles can revolutionize the way we create API documentation. By examining the different types of knowledge present in API references and recognizing diverse developer learning strategies, we can create documentation that is not only informative but also engaging and intuitive.

The JetBrains Blog

API Documentation Checklist

https://bump.sh/blog/api-documentation-checklist

"This article provides a checklist to help you identify the documentation you will need for launching your API. We will also include some things to consider post-launch as well to help you continue to improve your documentation." -- #JamesHigginbotham

#api360 #apiDocs #apiDesign

API Documentation Checklist · Bump.sh

Your API is nearing completion and it’s time to let the world know about it. This means that it is time to complete your API documentation effort. But, where should you start? How do you know if you covered everything that your decision makers and developers will need to select your API and get started successfully?

Moving API Docs From Human-Readable to Machine-Readable https://buff.ly/3TPK2KV

"I have more faith that we will get humans to adopt or at least auto-generate OpenAPI and APIs.json than I believe we’ll develop AI to unwind this mess." -- #KinLane

#api360 #apiDocs #apisJSON

Moving API Docs From Human-Readable to Machine-Readable

One of the super powers of APIs.json is the ability to evolve the human-readable aspects of API operations into machine-readable ones–as this is how we are going to scale to deliver the API economy all of us API believers envision in our minds eye. I saw what Swagger (now OpenAPI) had done for API documentation back in 2013, and I wanted this for the other essential building blocks of our API operations. A decade later I am still translating our getting started, plans, SDKs, road map, change log, and support into machine-readable artifacts as part of our API Commons work, but I am still working to translate documentation into machine-readable artifacts as well.

API Evangelist

Everyone is looking to me for API doc best practices and process. Validating, but also a little intimidating, like the teacher learning the content the night before to stay ahead of the API doc class while teaching seven other classes at the same time.

I'd appreciate y'all sharing any thoughts & references & resources, from theory to implementation.

#technicalWriting #techWriterLife #writeTheDocs #loneWriter #apiDoc #apiDocs #apiDocumentation