From: Rainer M Krug <r.m.krug@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Publishing: building navigation menus and lists of files
Date: Fri, 10 Jul 2015 14:58:44 +0200 [thread overview]
Message-ID: <95A8FC33-6289-4C4B-A0E5-92311FC58D24@gmail.com> (raw)
In-Reply-To: <CAN_Dec8MAVHnFJe7Koai7eyPsa8iT-6+56EYjn=5di2+wjQhyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Envoyé de mon iPhone
> Le 10 juil. 2015 à 14:16, Matt Price <moptop99@gmail.com> a écrit :
>
> I am hoping to finally transition some of my websites to static sites published directly from org finally!). one thing I would really like is to automatically build menus and perhaps index files based on the directory structure I'm exporting from. So, if I have:
>
> RLG231
> |
> |--Assignments
> | |
> | |-- Assignment1.org
> |
> |--Lectures
> |
> |-- etc
>
> I would like to have a navigation bar with links to "Assignments" and "Lectures" , and possibly dropdown menus for "Assignment1.html", etc.
>
> What do other people do with their websites?
>
> I have the idea, also, that within the directories I might like to have an "index.org" that looks like this:
>
> * Lectures
> This class has lectures. They are really interesting. Here is a list:
> #+BEGIN_SRC
> this block will output a nicely formatted html list of all the lectures in this directory,
> #+END_SRC
>
> I imagine other people have figured this out so I would love to learn from you all...
Have you seen org-html-themes https://github.com/fniessen/org-html-themes ? You might get some ideas from there?
Cheers,
Rainer
[-- Attachment #2: Type: text/html, Size: 1945 bytes --]
next prev parent reply other threads:[~2015-07-10 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 12:16 Publishing: building navigation menus and lists of files Matt Price
2015-07-10 12:58 ` Rainer M Krug [this message]
2015-07-10 18:37 ` Matt Price
2015-07-13 11:13 ` giles
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95A8FC33-6289-4C4B-A0E5-92311FC58D24@gmail.com \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.