search

quikdraw2700 / ScrumTheBoardGame

Public artifacts for Scrum! The Board Game
3 stars 0 forks source link

Q: Shall we Build PDFs from Text / MarkDown? #19

Open davidakoontz opened 6 years ago

davidakoontz commented 6 years ago

If so... what tooling & process?

Let's run something up the flag pole...

davidakoontz commented 6 years ago

see idea on Pandoc (text to PDF / HTML converter)

http://kieranhealy.org/files/papers/plain-person-text.pdf http://kieranhealy.org/files/papers/workflow-apps.pdf https://github.com/kjhealy/workflow-paper

quikdraw2700 commented 6 years ago

Interesting. I wasn't aware of this.

Are you thinking for all the docs or just for the card decks?

davidakoontz commented 6 years ago

@quikdraw2700 Thanks for the feedback. I was playing around last night ... first path was Docx to LaTeX to Markdown; needless to say LaTeX tools are complex and I did not figure them out - the next attempt was finding that Pandoc now understands Word files.

So the path I'm playing with now is: Word format -> Pandoc -> Markdown format -> Git Repo; and the return route. To work in MS Word and store in Repo in mutable text. Should give fine level of change control with merging of concurrent editors... (a desired feature of workflow).

So now what does that workflow make easier vs the hassle? - This I don't know... but willing to explore.

Moving forward; I see many in the Pandoc community are using Make to automate the build workflow.

Yes, I sense that the card decks would be a great 1st attempt. Is there a reason (I don't know) that the deck is currently a set of unique cards, rather than the actual finished product deck, that could be sent to the printer once? -- I'm guessing to allow figuring out the ration of cards in the deck... via experiment... is that fairly stable now; are we willing to switch to full deck?