Re: merging subtrees (in a syllabus)

[Kaushal Modi <kaushal.modi@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3676 bytes --]

On Tue, Aug 22, 2017 at 4:10 PM Matt Price <moptop99@gmail.com> wrote:

> And then I'd run some elisp that mashes them all up together, and give
> that to the students, since I think that'll make it easier for them to read.
>
> Anyone on the list have any ideas?
>

How about using plain old #+INCLUDE:

Example made up from your examples:

===== a.org (for exporting) =====
* Outline
** <2017-09-12 Tue> (Week {{{n}}}) Hacking History in the Himalaya
#+INCLUDE: "b.org::#hacking-history-in-the-himalaya-intro" :only-contents t
#+INCLUDE: "b.org::#hacking-history-in-the-himalaya-background"
*** Lab 01: Getting Started
#+INCLUDE: "b.org::#lab-getting-started" :only-contents t
** <2017-09-19 Tue> (Week {{{n}}}) Language of the Web
#+INCLUDE: "b.org::#the-language-of-the-web-intro" :only-contents t
#+INCLUDE: "b.org::#the-language-of-the-web-readings"
*** Lab 02: Understanding HTML
#+INCLUDE: "b.org::#lab-understanding-html" :only-contents t
=====

===== b.org (for your content development) =====
* Discussion Topics
** Hacking History in the Himalaya
*** Intro
:PROPERTIES:
:CUSTOM_ID: hacking-history-in-the-himalaya-intro
:END:
Why we should write history, why everyone should do it, and why that means
we
need the Web.  Hacker cultures, collaborative learning, knowledge sharing,
non-expert culture. And a few words about the world's third-tallest
mountain.
*** Background
:PROPERTIES:
:CUSTOM_ID: hacking-history-in-the-himalaya-background
:END:
- [[
http://www.journalofamericanhistory.org/issues/952/interchange/index.html][JAH
- The Promise of Digital History]]
- [[
http://writinghistory.trincoll.edu/revisioning/tanaka-2012-spring/][Pasts
in a Digital Age]]
** The Language of the Web
*** Intro
:PROPERTIES:
:CUSTOM_ID: the-language-of-the-web-intro
:END:
The Web is written in a language called HTML, with some help from other
lanugages called CSS and Javascript. The nonlinear and interactive
properties of
these languages afford new possibilities for storytelling. We explore how
the
Internet works, and what that means for historical narrative.
*** Readings
:PROPERTIES:
:CUSTOM_ID: the-language-of-the-web-readings
:END:
- Vannevar Bush, "[[
http://www.theatlantic.com/magazine/archive/1969/12/as-we-may-think/3881/][As
We May Think]]"
- Tim Berners-Lee, /Weaving the Web/
[[file:readings/berners-lee-weaving-web.pdf][Ch. 2,4]].
- Edward L. Ayers, "[[http://www.vcdh.virginia.edu/Ayers.OAH.html][History
in Hypertext]]"
- Rus Shuler, "[[
http://www.theshulers.com/whitepapers/internet_whitepaper/index.html][How
Does the Internet Work?]]"
* Labs
** Getting Started
:PROPERTIES:
:CUSTOM_ID: lab-getting-started
:END:
- HTML and Markdown
- Some Tools: Github, Dropbox, Atom Text Editor
- About Our Partners
** Understanding HTML
:PROPERTIES:
:CUSTOM_ID: lab-understanding-html
:END:
*Resources:* [[http://jsbin.com/#html,live][JSBin online HTML/Javascript
editor]]; [[http://codeacademy.net][codeacademy courses]]; [[
http://en.wikipedia.org/wiki/HTML][on
Wikipedia]]; [[http://www.w3.org/MarkUp/Guide/][w3 guide]]; also cf. Zotero
Bibliography

----------------------

Because the course readings and hte lab are often separate, it can be
difficult
and confusing to maintain the course outline in its final form. Id like to
be
able, instead, to maintain the labs and readings separately, and /merge/
them to
produce the final document.  So I'd start with something like this:
=====



If it also comes with a thought about how to generate an org date objet
> form an initial seed and a session number, that's be fabulous too.
>

I don't have a good idea on how to implement the date thing, but I see that
others have provided some input.
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 5918 bytes --]