Reworking @publicspaces Spoelkeuken self-assessment into Limesurvey CE - a self-hosted survey tool.
My experience so far: it's easy to create a simple survey, but it becomes a lot harder to calculate values, hide/show questions and allow respondents to download their answers.
#UX #UI #Design & #Documentation could all use more attention. A bit surprising since this tool is already 23(!) years old.
#OpenSource #Tech #SelfHosting #DigitalAutonomy #DigitalSovereignty
How Modern Medical Practices Are Solving Their Documentation Crisis
#itranscript360 #MedicalPractice #documentation #AIPoweredSolutions
@nicole4fox np.
@pine64 do some nifty stuff, and in terms of #documentation and #support.only have competition from @olimex and @RaspberryPi / @raspberry_pi / #RasberryPi.
dominik kundel (@dkundel)
Codex의 'rules' 기능 관련 공식 문서 링크 안내: developers.openai.com/codex/rules에서 rules 사용법과 샌드박스 기반 자동화 설정 방법, 권한 제한 방식 등을 확인할 수 있다는 공지입니다.
📰 仕様駆動開発(SDD)って、本当に不要なの？ (👍 62)
🇬🇧 Rethinking spec-driven development: examining the trade-off between documentation and code maintenance costs.
🇰🇷 사양 주도 개발은 정말 불필요한가? 문서와 코드 유지보수 비용의 균형 재검토.
In an announcement during #LightningTalks at #FOSSBackstage2026 I just learned that the @sovtechfund is providing grants to #CommunityManager and #TechnicalWriter to sustain #OpenSource projects.
As a researcher of #SoftwareArchitecture I've seen many projects suffering from a lack of #documentation and/or community management work (due to e.g., priorities) and would like to encourage you to take this chance. 😃
Saneject is getting real docs soon.
The README can finally stop moonlighting as a documentation site, because I've been building a proper DocFX docs site for the upcoming Saneject 1.0.0 release with everything there is to know about the framework. It's already a much better way to explore guides, concepts, and API docs without digging through a giant wall of text.
Excited to share it soon.
#Saneject #Unity #Unity3D #GameDev #DI #Tools #Documentation
I've also just created the public task board for Bluebird Documentation (BBD). Link is below!
🕐 2026-03-15 12:00 UTC
📰 最初に伝えるべきは「結論」ではなく「要約」 (👍 70)
🇬🇧 Technical docs should lead with summaries (context+purpose) not just conclusions. Learn why and how to write effective opening summaries.
🇰🇷 기술 문서는 결론만이 아닌 요약(맥락+목적)으로 시작해야 합니다. 효과적인 도입 요약 작성법을 알아보세요.
🕐 2026-03-15 06:00 UTC
📰 最初に伝えるべきは「結論」ではなく「要約」 (👍 66)
🇬🇧 Technical docs should start with a summary including context and purpose, not just a bare conclusion. Explains benefits and writing techniques.
🇰🇷 기술 문서는 단순한 결론이 아닌 맥락과 목적을 포함한 요약으로 시작해야 합니다. 이점과 작성 기법을 설명합니다.
＂… As my boss in my non-coding job says, people don't read. …＂
Too true, for too many readers.
<https://people.freebsd.org/~grahamperrin/style/writing/tips/>
– and then click the word "concise" for a ninety-nine page primer (PDF, A4). That's ninety-one pages longer than a long primer should be.
A good primer should be no longer than four pages – visualise an A3 sheet, duplex, folded – with directions.
Eight pages, max.
Off with my head, et cetera.
Here is also the task board for Bluebird Documentation.
What to share where your at on your personal project with your followers? Try out Bluebird Task Management!
Just like with public documentation, you can now have a public board! Share task information with anyone following your projects! I just made the task board for Bluebird Task Management public. Take a look!
#coding #documentation #tasks #webdev #buildinpublic
tasks.bluebird-documentation.com/public/board/3
The EFF just banned AI-generated documentation from their open source projects. Docs are literally what AI does best — consistent, complete, doesn't skip the "obvious" stuff.
The real problem is drive-by PRs from people who don't understand their code. Gemini Code Assist reviews every PR for free. That's the fix — not banning AI from its strongest area.
#OpenSource #AI #CodeReview #DevTools #Documentation
RE: https://mastox.eu/@FranceskAlbs/116209436941955852
Appel de l'#OHCHR à contributions publique sur le rôle des médias dans le contexte des politiques et pratiques d’Israël à l’égard du peuple palestinien, en particulier après le 7 octobre 2023.
Il y a du boulot avec les médias français !
1/4
#medias #documentation #génocide #lemonde #bfm #cnews #franceinfo #lefigaro ...
"A few months into working with AI agents on a documentation project, I'd noticed some inconsistency in agent behaviors and decided to do some digging. Turns out the AGENTS.md file in our repo — the one telling agents how to behave, where things were, and what to escalate — had grown to over 800 lines, and a few people (or likely their agents) had added rules independently, some subtly contradicting each other.
The agents weren't broken. They were following instructions that didn't serve them well.
In a previous post, I argued that agent configuration files are documentation and that their formats, structures, and purposes map directly to work technical communicators already do. That post covered the what: five doc types (project descriptions, agent definitions, orchestration patterns, skills, and plans/specs) and why writers are well-positioned to create them.
This post goes further. These files are internal documentation, full stop. They encode how your team actually works. And if you don't manage them with the same rigor you'd apply to any internal doc set, they'll degrade in the same ways: outdated content, conflicting guidance, and gaps nobody notices until something breaks."
https://instructionmanuel.com/agentic-docs-are-internal-docs
#TechnicalWriting #AI #AIAgents #AgentConfigs #Documentation #DocsAsCode #LLMs #GenerativeAI #Markdown
"Are we heading toward an AI utopia, an AI dystopia… or something in between?
In this episode of Technical Writing Uncensored, I sit down with technical writer and blogger Fabrizio Ferri-Benedetti to talk about how AI and LLMs are changing technical writing — and what writers should actually be worried about.
Fabri writes the excellent Passo Uno blog, where he explores technical writing, AI, and the future of documentation.
Read his blog here: https://passo.uno
We discuss whether AI will replace writers, how technical writers can stay relevant, and why writers might actually become more important in an AI-driven world.
Fabri also explains why writers should think of AI as “a second language”, not something that replaces human expertise.
We also discuss:
Why AI is more like a tool (a hammer) than an autonomous intelligence
Why good documentation is essential for AI systems
Whether tech writers will become editors and prompt architects
Why writers need a “mental gym” to keep their thinking sharp
This conversation is a thoughtful look at the real impact of AI on technical writing, without the hype.
#TechnicalWritingUncensored #TechnicalWriter #TechnicalWriting #Documentarian #Documentation #WordNerds #TechComm #ContentStrategy #WritingTips #CareerAdvice #UserExperience #DocsLikeCode #TechWritingUncensored #TechCommunity #aiforwriters #ai #llm #artificialintelligence "
Créer un site Web local de documentation pouvant exporter en PDF avec mdBook https://linuxfr.org/news/creer-un-site-web-local-de-documentation-pouvant-exporter-en-pdf-avec-mdbook #documentation #markdown #rust #Doc
Découvre cette vidéo du CRDP Versailles sur Wikipédia au CDI — un guide pratique pour profs, documentalistes et curieux! Clair, concret et parfait pour intégrer Wikipédia en classe. À voir, utiliser et partager! #Wikipédia #CDI #Éducation #Documentation #CRDP #Framasoft #OpenEducation #French
https://peertube.gegeweb.eu/videos/watch/a3461981-d4f5-45ed-9f68-f71caa0891e0
