emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: any org[/beamer] experts in the ottawa area available for consulting?
Date: Mon, 10 Sep 2012 05:56:50 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1209100537280.16640@oneiric> (raw)
In-Reply-To: <CA+M2ft-t+zFWiFXPJ6it5ojHc5x4fVEo+zzGGg8D=EnUhLCjBQ@mail.gmail.com>

On Sun, 9 Sep 2012, John Hendy wrote:

> On Sun, Sep 9, 2012 at 4:47 PM, Rasmus <rasmus@gmx.us> wrote:
> > "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
> >
> >> p.s.  i asked this on the org list hoping for someone who also knows
> >> beamer, of course.  if that doesn't work, i can ask on the beamer
> >> list, looking for someone who also knows org. :-)
> >
> > I don't get the question, I'm afraid.  Could you reiterate questions
> > more concretely?
> <snip>
> I *think* I get the question, but to Rasmus' point, could you provide
> some examples of what an end product might look like? This would be a
> tangible way for you to make the details of your request known. Rather
> than base the request in reference to the site link you provided,
> something more like:
> - We have x number of courses, and each one has y article-style and z
> presentation style teaching documents (manuals, tutorials, class
> guides, etc.)
> - An example of a representative manual is here: url
> - An example of a representative presentation is here: url
> - Repeat for any other documents you're looking to redo
> Then provide a ballpark example of what you're looking to transform
> the above into. Perhaps link to a manual/presentation you've found
> that you would like to emulate certain characteristics of?
> Lastly, a list of deliverables would be nice. For example, "I would like:
> - A .emacs that could be shared among all documentation users
> - A custom beamer template
> - A custom LaTeX article class designed to produce the format above
> - etc."
> Just some thoughts to help others respond to something more concrete.
> I looked around the site at the courseware section as you pointed out.
> I think I get what you want, but it would still be helpful to have at
> least some of the above for others in order to know what they are
> being asked to do. It also helps some of us know what level of
> org-mode knowledge would be required to help you. Lastly, what, if
> any, compensation is involved.

  ok, i'll try to be as detailed as i can, even though i'm still
trying to wrap my head around all of the features org-mode and beamer
give me.  (aside: while having someone do this for me remotely might
work out, i'd still prefer to find someone local here in ottawa to sit
down with since i'm not even going to *know* all the questions i want
to ask until i see things happening.)

  my colleague and i are looking to both convert existing courseware
manuals and write new manuals in beamer format.  representative
manuals can be seen here in both ODP and PDF format (my specialty will
be the linux content manuals):


  as you can see, the emphasis will be on the typical bulleted list
format, while i personally will want to include *copious* amounts of
source code snippets while writing about the linux kernel and device

  i am not an accomplished user of *any* of the technologies in the
toolchain -- org-mode, emacs, latex or beamer.  i have used emacs in
outline mode for quite some time for *designing* new manuals and, for
me, the whole outline mode feature of org-mode is essential; that's
how i want to lay out and start writing new manuals.

  what i'm after is as much infrastructure as i need to get started
writing one or more manuals.  by infrastructure, i mean setting up a
working directory on my ubuntu system which will support not just
writing individual manuals, but factoring out common content
(copyrights, etc) and being able to include it in all manuals
arbitrarily.  so, in the end, i'm after a fairly complete publishing
and processing toolchain that will take me from writing .org files to
the final beamer files for each manual.

  a recent example on this list shows why i'd like to hire someone to
help, to save me time.  i asked why a simple "H:3" option didn't
give me three levels of headings, even though the org-mode user manual
*clearly* suggested that's how to do it.  a couple people responded,
describing a need to use "require" and "org-e-beamer" and
"org-export-dispatch".  but while i'm sure that's the solution, i
would *never* figured that out on my own since i would have had no
idea where to look.

  what i'm after right now is a starting infrastructure so i can start
cramming content into manuals, and i can tweak over time as i learn
what else i can do.  as for compensation, if you can help, let me know
your rate and we can chat.



Robert P. J. Day                                 Ottawa, Ontario, CANADA

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday

  reply	other threads:[~2012-09-10  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09  9:54 any org[/beamer] experts in the ottawa area available for consulting? Robert P. J. Day
2012-09-09 21:47 ` Rasmus
2012-09-10  0:55   ` John Hendy
2012-09-10  9:56     ` Robert P. J. Day [this message]
2012-09-13 17:45       ` Manish
2012-09-13 17:56         ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1209100537280.16640@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \
    --cc=rasmus@gmx.us \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).