summaryrefslogtreecommitdiffstats
path: root/2021/talks/tech.md
diff options
context:
space:
mode:
Diffstat (limited to '2021/talks/tech.md')
-rw-r--r--2021/talks/tech.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/2021/talks/tech.md b/2021/talks/tech.md
index 3ec253b7..c327181d 100644
--- a/2021/talks/tech.md
+++ b/2021/talks/tech.md
@@ -8,6 +8,8 @@
# Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide
Jan Ypma
+[[!taglink CategoryOrgMode]]
+
[[!inline pages="internal(2021/info/tech-schedule)" raw="yes"]]
The emacs org-babel package is often mentioned in conjunction with
@@ -26,6 +28,20 @@ org-treeslide to write and present technical documentation with style.
# Discussion
+Pad:
+
+- Q1: Sorry if you already answered this somewhere (but if not, can
+ someone with a reddit account copy this over? thx). Hi, I would love
+ to move my team over to using something org-based, but that'll
+ never happen because, well... (wait for it) Emacs! By the way, I'm
+ currently using heavily customized Sphinx setup, mostly internal,
+ sometimes shared with data partners; lots of schema-gen from message
+ protocols defined in code, etc. Anyhow: questions. Do you work with
+ non-Emacs users? If so, how did you get them to accept this
+ workflow? And if it's just you DJ'ing, how do they weigh in when
+ they want an update, open a formal ticket?
+- <https://github.com/jypma/emacsconf2021/blob/master/presentation.org>
+
BBB:
- Have you encountered any push-back from people requesting the documentation who are of the opinion that only a Word document will do?