프로그래밍/Architect

2023년 개발자를 위한 35가지 기술 자료 도구

홍반장水_ 2023. 5. 18. 09:47
반응형

35 Knowledge base tools for developers in 2023

https://medium.com/promyze/35-knowledge-base-tools-for-developers-in-2023-2584d1ea6bbb

 

35 Knowledge base tools for developers in 2023

In 2023, there should be no debate about the added value of great documentation in software projects. Software engineers should have access…

medium.com

 

  • 엔지니어가 도구의 UI에서 문서를 작성하는 Wiki와 유사한 도구 (예: Notion, Confluence, …)
  • 예 를 들어 코드 분석 및 온보딩 세션(예:프로미즈);
  • 질문/답변 플랫폼과 같은 커뮤니케이션 도구(예: Teams용 StackOverflow, …)
  • 개발자가 일반적으로 마크다운으로 문서를 작성하면 모든 마법이 일어나는 생성된 위키 도구(예: ReadTheDocs, …)

Acreom

Capture notes, break down issues, track your progress, create a knowledge base.

AnswerHub

Empowering developers and teams to learn, share, and succeed through online communities and knowledge sharing.

AppFlowy

Open Source Notion Alternative

Archbee

Build better product documentation — faster

Bit.ai

Next-Gen Document Collaboration Platform for Teams!

BookStack

(Open Source) BookStack is a simple, self-hosted, easy-to-use platform for organizing and storing information.

ClickUp

Save time with the all-in-one productivity platform that brings teams, tasks, and tools together in one place.

Coda

The all-in-one doc for teams.

CodeStream

New Relic CodeStream is a free open-source extension for VS Code, Visual Studio, and JetBrains.

Confluence

Confluence is your remote-friendly team workspace where knowledge and collaboration meet.

Daux.io

(OpenSource) The Easiest Way To Document Your Project.

Developerhub.io

All-in-One Platform for Online Documentation.

Docusaurus

(OpenSource) Build optimized websites quickly, focus on your content.

Flarum

(Open Source) Forums made simple. Modern, fast, and free!

Forem

(Open Source) Forem is an open source platform for building modern, independent, and safe communities.

GitBook

Where software teams break knowledge silos. (We use it at Promyze for our public documentation)

GitHub Pages

Websites for you and your projects.

Hugo

(OpenSource) The world’s fastest framework for building websites.

Jekyll

Transform your plain text into static websites and blogs.

mdBook

Static site generator from Markdown files.

MkDocs

(Open Source) Project documentation with Markdown.

Notion

The all-in-one workspace — for your tasks, notes, wikis, and calendar.

Notaku

Build a full-featured Docs website in minutes, using Notion as CM

Nuclino

A modern, simple, and blazingly fast way to collaborate — bring knowledge, docs, and projects together in one place.

Papyrs

The easiest way to create an online for your company.

Read The Docs

(Open Source) Read the Docs simplifies software documentation by automating building, versioning, and hosting of your docs for you.

SkyDocs

(OpenSource) SkyDocs is a lightweight static documentation builder with MarkDown.

Slab

Build a culture of knowledge-sharing today.

Sphinx

(OpenSource) Sphinx makes it easy to create intelligent and beautiful documentation.

Stack Overflow For Teams

Knowledge sharing and collaboration without distractions.

Swimm

Documentation Platform Built for Engineers.

TechDocs

Spotify’s docs-like-code plugin for Backstage.

Tettra

The best way to organize and share knowledge with your teammates.

Wiki.js

(OpenSource) The most powerful and extensible open source Wiki software

Promyze

Connect Developers’ Knowledge and share best coding practices, fully integrated in developers tools.

That’s all, folks; we hope that post gave you an overview of the current landscape of the knowledge base tools for software developers.

Among the ones quoted above, at Promyze, we use Notion to gather material such as procedures to create new releases of our IDE extensions. We use GitBook to publish the user documentation of our platform. Finally, we use our tool Promyze internally to raise new coding standards continuously. We bring these standards directly in IDEs & during code reviews since we consider this is the moment developers need this knowledge. You don’t code with a Wiki opened in a tab.

For each kind of documentation, you must define who should update it, when, and how other engineers will be notified of this change.

 

반응형