home.social

#diataxis — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #diataxis, aggregated by home.social.

fetched live
  1. Started to learn #diataxis. It's refreshing way of how to navigate documentation.

    Take the difference of what a tutorial versus how to. May seem obvious, but really isn't. Already started using and I'm like never going back to my prior mess of no "compass." 😅

    diataxis.fr/tutorials-how-to/#

  2. Started to learn . It's refreshing way of how to navigate documentation.

    Take the difference of what a tutorial versus how to. May seem obvious, but really isn't. Already started using and I'm like never going back to my prior mess of no "compass." 😅

    diataxis.fr/tutorials-how-to/#

  3. Started to learn #diataxis. It's refreshing way of how to navigate documentation.

    Take the difference of what a tutorial versus how to. May seem obvious, but really isn't. Already started using and I'm like never going back to my prior mess of no "compass." 😅

    diataxis.fr/tutorials-how-to/#

  4. Started to learn #diataxis. It's refreshing way of how to navigate documentation.

    Take the difference of what a tutorial versus how to. May seem obvious, but really isn't. Already started using and I'm like never going back to my prior mess of no "compass." 😅

    diataxis.fr/tutorials-how-to/#

  5. Started to learn #diataxis. It's refreshing way of how to navigate documentation.

    Take the difference of what a tutorial versus how to. May seem obvious, but really isn't. Already started using and I'm like never going back to my prior mess of no "compass." 😅

    diataxis.fr/tutorials-how-to/#

  6. KI generierte Dokumentation ist eine Zumutung

    Ich hatte heute die Zeit mich tiefer mit zwei Projekte zu beschäftigen. Beide sind in der frühen Entstehungsphase, haben aber schon viel Dokumentation, weil es sich primär um Protokollstandards handelt. Leider ist die Dokumentation zu 99% KI generiert. Im Gegensatz zu menschlicher Dokumentation ist alles sehr redundant, sehr luftig ausgeschrieben und so, dass es gut für KI Systeme zu verdauen ist, aber nicht für Menschen. Mal geht es plötzlich sehr tief ins Detail, dann wieder nicht. […]

    mukis.de/2026/06/03/ki-generie

  7. KI generierte Dokumentation ist eine Zumutung

    Ich hatte heute die Zeit mich tiefer mit zwei Projekte zu beschäftigen. Beide sind in der frühen Entstehungsphase, haben aber schon viel Dokumentation, weil es sich primär um Protokollstandards handelt. Leider ist die Dokumentation zu 99% KI generiert. Im Gegensatz zu menschlicher Dokumentation ist alles sehr redundant, sehr luftig ausgeschrieben und so, dass es gut für KI Systeme zu verdauen ist, aber nicht für Menschen. Mal geht es plötzlich sehr tief ins Detail, dann wieder nicht. […]

    mukis.de/2026/06/03/ki-generie

  8. Random plug for a documentation system I really enjoy and got to talk about with someone today.

    If you struggle to write (or think about) good technical documentation like I do, you might benefit from learning about Diátaxis. https://diataxis.fr/

    It breaks down the different reasons people go to learn and acquire information and it really helped me think about how I want to present information.

    #diataxis #documentation #technicalwriting

  9. Random plug for a documentation system I really enjoy and got to talk about with someone today.

    If you struggle to write (or think about) good technical documentation like I do, you might benefit from learning about Diátaxis. https://diataxis.fr/

    It breaks down the different reasons people go to learn and acquire information and it really helped me think about how I want to present information.

    #diataxis #documentation #technicalwriting

  10. Random plug for a documentation system I really enjoy and got to talk about with someone today.

    If you struggle to write (or think about) good technical documentation like I do, you might benefit from learning about Diátaxis. https://diataxis.fr/

    It breaks down the different reasons people go to learn and acquire information and it really helped me think about how I want to present information.

    #diataxis #documentation #technicalwriting

  11. Random plug for a documentation system I really enjoy and got to talk about with someone today.

    If you struggle to write (or think about) good technical documentation like I do, you might benefit from learning about Diátaxis. https://diataxis.fr/

    It breaks down the different reasons people go to learn and acquire information and it really helped me think about how I want to present information.

    #diataxis #documentation #technicalwriting

  12. #EmailMarketers spend too much time debating what to send, but from the sender’s needs, not the reader’s.
    Enter #Diataxis.
    Diátaxis organises content around user intent, not format or channel. Once you look at email marketing through that lens, you realise that many email programmes fail because they deliver the wrong type of message at the wrong cognitive moment.
    mailreach.eu/email-marketing-b
    #EmailMarketing
    #ContentStrategy
    #ContentMarketing
    #MarketingStrategy
    #Marketing
    #ReachRascals

  13. #EmailMarketers spend too much time debating what to send, but from the sender’s needs, not the reader’s.
    Enter #Diataxis.
    Diátaxis organises content around user intent, not format or channel. Once you look at email marketing through that lens, you realise that many email programmes fail because they deliver the wrong type of message at the wrong cognitive moment.
    mailreach.eu/email-marketing-b
    #EmailMarketing
    #ContentStrategy
    #ContentMarketing
    #MarketingStrategy
    #Marketing
    #ReachRascals

  14. #EmailMarketers spend too much time debating what to send, but from the sender’s needs, not the reader’s.
    Enter #Diataxis.
    Diátaxis organises content around user intent, not format or channel. Once you look at email marketing through that lens, you realise that many email programmes fail because they deliver the wrong type of message at the wrong cognitive moment.
    mailreach.eu/email-marketing-b
    #EmailMarketing
    #ContentStrategy
    #ContentMarketing
    #MarketingStrategy
    #Marketing
    #ReachRascals

  15. #EmailMarketers spend too much time debating what to send, but from the sender’s needs, not the reader’s.
    Enter #Diataxis.
    Diátaxis organises content around user intent, not format or channel. Once you look at email marketing through that lens, you realise that many email programmes fail because they deliver the wrong type of message at the wrong cognitive moment.
    mailreach.eu/email-marketing-b
    #EmailMarketing
    #ContentStrategy
    #ContentMarketing
    #MarketingStrategy
    #Marketing
    #ReachRascals

  16. Les Cast Codeurs en 2024 parlent du framework Diataxis et de ranger la documetnation

    (Si vous préférez les formats audio)
    lescastcodeurs.com/2024/12/21/

    #documentation #diataxis

  17. Les Cast Codeurs en 2024 parlent du framework Diataxis et de ranger la documetnation

    (Si vous préférez les formats audio)
    lescastcodeurs.com/2024/12/21/

    #documentation #diataxis

  18. Les Cast Codeurs en 2024 parlent du framework Diataxis et de ranger la documetnation

    (Si vous préférez les formats audio)
    lescastcodeurs.com/2024/12/21/

    #documentation #diataxis

  19. Les Cast Codeurs en 2024 parlent du framework Diataxis et de ranger la documetnation

    (Si vous préférez les formats audio)
    lescastcodeurs.com/2024/12/21/

    #documentation #diataxis

  20. Les Cast Codeurs en 2024 parlent du framework Diataxis et de ranger la documetnation

    (Si vous préférez les formats audio)
    lescastcodeurs.com/2024/12/21/

    #documentation #diataxis

  21. ¿Necesitas crear o racionalizar documentación en tu empresa? Hardware, software, sistemas, procedimientos... No lo hagas a ciegas. Ayúdate de un framework adecuado y alíate con los mejores. Te contamos cómo hacerlo en nuestro último artículo del blog.
    tarsis.net/blog/importancia-pa
    #Diátaxis #documentación #documentation #tutorials #tutoriales #howto #howtos #docs

  22. @kevinbowen Oh this is interesting. I've kept this (ish) as one of my personal principles for writing documentation, that there need to be different kinds of documentation to serve different audiences (especially: tutorial and reference docs), but I never knew there was a formal system for it.

    #documentation #Python #Diataxis

  23. @kevinbowen Oh this is interesting. I've kept this (ish) as one of my personal principles for writing documentation, that there need to be different kinds of documentation to serve different audiences (especially: tutorial and reference docs), but I never knew there was a formal system for it.

    #documentation #Python #Diataxis

  24. @kevinbowen Oh this is interesting. I've kept this (ish) as one of my personal principles for writing documentation, that there need to be different kinds of documentation to serve different audiences (especially: tutorial and reference docs), but I never knew there was a formal system for it.

    #documentation #Python #Diataxis

  25. @kevinbowen Oh this is interesting. I've kept this (ish) as one of my personal principles for writing documentation, that there need to be different kinds of documentation to serve different audiences (especially: tutorial and reference docs), but I never knew there was a formal system for it.

    #documentation #Python #Diataxis

  26. @kevinbowen Oh this is interesting. I've kept this (ish) as one of my personal principles for writing documentation, that there need to be different kinds of documentation to serve different audiences (especially: tutorial and reference docs), but I never knew there was a formal system for it.

  27. While I haven't necessarily drank the #Diataxis #documentation kool-aid 😄 , I do think that what is going on with the #Python documentation is interesting and it is a conversation and a mind-set that it worthy of consideration & attention. YMMV

    discuss.python.org/t/diataxis-

  28. While I haven't necessarily drank the kool-aid 😄 , I do think that what is going on with the documentation is interesting and it is a conversation and a mind-set that it worthy of consideration & attention. YMMV

    discuss.python.org/t/diataxis-

  29. While I haven't necessarily drank the #Diataxis #documentation kool-aid 😄 , I do think that what is going on with the #Python documentation is interesting and it is a conversation and a mind-set that it worthy of consideration & attention. YMMV

    discuss.python.org/t/diataxis-

  30. While I haven't necessarily drank the #Diataxis #documentation kool-aid 😄 , I do think that what is going on with the #Python documentation is interesting and it is a conversation and a mind-set that it worthy of consideration & attention. YMMV

    discuss.python.org/t/diataxis-

  31. While I haven't necessarily drank the #Diataxis #documentation kool-aid 😄 , I do think that what is going on with the #Python documentation is interesting and it is a conversation and a mind-set that it worthy of consideration & attention. YMMV

    discuss.python.org/t/diataxis-

  32. diataxis.fr/tutorials-how-to/ #diátaxis on #tutorials vs. #HowToS

    «Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.

    Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.

    A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»

  33. diataxis.fr/tutorials-how-to/ #diátaxis on #tutorials vs. #HowToS

    «Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.

    Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.

    A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»

  34. diataxis.fr/tutorials-how-to/ #diátaxis on #tutorials vs. #HowToS

    «Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.

    Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.

    A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»

  35. diataxis.fr/tutorials-how-to/ #diátaxis on #tutorials vs. #HowToS

    «Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.

    Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.

    A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»

  36. diataxis.fr/tutorials-how-to/ #diátaxis on #tutorials vs. #HowToS

    «Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.

    Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.

    A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»

  37. #TechnicalWriting #SoftwareDocumentation #Documentation #4doc #Diataxis: "4doc is much better than 5para: I’ve never read a halfway-decent 5-paragraph essay but I’ve read plenty of good 4doc pages. Even so, it still leads to the same kind of “this is the only way” thinking. People use the model even when it’s not the right choice and they don’t vary up the format even when they should.

    My specific issue is that the model is not universal and it’s not comprehensive."

    hillelwayne.com/post/problems-

  38. #TechnicalWriting #SoftwareDocumentation #Documentation #4doc #Diataxis: "4doc is much better than 5para: I’ve never read a halfway-decent 5-paragraph essay but I’ve read plenty of good 4doc pages. Even so, it still leads to the same kind of “this is the only way” thinking. People use the model even when it’s not the right choice and they don’t vary up the format even when they should.

    My specific issue is that the model is not universal and it’s not comprehensive."

    hillelwayne.com/post/problems-

  39. #TechnicalWriting #SoftwareDocumentation #Documentation #4doc #Diataxis: "4doc is much better than 5para: I’ve never read a halfway-decent 5-paragraph essay but I’ve read plenty of good 4doc pages. Even so, it still leads to the same kind of “this is the only way” thinking. People use the model even when it’s not the right choice and they don’t vary up the format even when they should.

    My specific issue is that the model is not universal and it’s not comprehensive."

    hillelwayne.com/post/problems-

  40. #TechnicalWriting #SoftwareDocumentation #Documentation #4doc #Diataxis: "4doc is much better than 5para: I’ve never read a halfway-decent 5-paragraph essay but I’ve read plenty of good 4doc pages. Even so, it still leads to the same kind of “this is the only way” thinking. People use the model even when it’s not the right choice and they don’t vary up the format even when they should.

    My specific issue is that the model is not universal and it’s not comprehensive."

    hillelwayne.com/post/problems-

  41. #TechnicalWriting #SoftwareDocumentation #Documentation #4doc #Diataxis: "4doc is much better than 5para: I’ve never read a halfway-decent 5-paragraph essay but I’ve read plenty of good 4doc pages. Even so, it still leads to the same kind of “this is the only way” thinking. People use the model even when it’s not the right choice and they don’t vary up the format even when they should.

    My specific issue is that the model is not universal and it’s not comprehensive."

    hillelwayne.com/post/problems-

  42. Sarah Haïm-Lubczanski: Présentation:
    Améliorons ensemble la documentation de #PostgreSQL ! avec Sarah Haïm-Lubczanski

    #postgres #diataxis #postgresqlfr #pgdayfr

  43. Sarah Haïm-Lubczanski: Présentation:
    Améliorons ensemble la documentation de #PostgreSQL ! avec Sarah Haïm-Lubczanski

    #postgres #diataxis #postgresqlfr #pgdayfr

  44. Sarah Haïm-Lubczanski: Présentation:
    Améliorons ensemble la documentation de #PostgreSQL ! avec Sarah Haïm-Lubczanski

    #postgres #diataxis #postgresqlfr #pgdayfr

  45. Sarah Haïm-Lubczanski: Présentation:
    Améliorons ensemble la documentation de #PostgreSQL ! avec Sarah Haïm-Lubczanski

    #postgres #diataxis #postgresqlfr #pgdayfr

  46. Sarah Haïm-Lubczanski: Présentation:
    Améliorons ensemble la documentation de #PostgreSQL ! avec Sarah Haïm-Lubczanski

    #postgres #diataxis #postgresqlfr #pgdayfr

  47. Discovered @EvilDMP's Diátaxis documentation framework this morning, as I plan a migration of my #DTAT 'lay outreach' blog from #WordPress to #Quarto. It shows me how little my previous #SciComm efforts have ventured outside the #explanation quadrant! Has anyone else on here adopted #diataxis for #SciComm around a #methodology?
    diataxis.fr/

  48. Discovered @EvilDMP's Diátaxis documentation framework this morning, as I plan a migration of my #DTAT 'lay outreach' blog from #WordPress to #Quarto. It shows me how little my previous #SciComm efforts have ventured outside the #explanation quadrant! Has anyone else on here adopted #diataxis for #SciComm around a #methodology?
    diataxis.fr/

  49. Discovered @EvilDMP's Diátaxis documentation framework this morning, as I plan a migration of my #DTAT 'lay outreach' blog from #WordPress to #Quarto. It shows me how little my previous #SciComm efforts have ventured outside the #explanation quadrant! Has anyone else on here adopted #diataxis for #SciComm around a #methodology?
    diataxis.fr/

  50. Discovered @EvilDMP's Diátaxis documentation framework this morning, as I plan a migration of my #DTAT 'lay outreach' blog from #WordPress to #Quarto. It shows me how little my previous #SciComm efforts have ventured outside the #explanation quadrant! Has anyone else on here adopted #diataxis for #SciComm around a #methodology?
    diataxis.fr/