From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Moynihan Subject: Hyperlinked Tag table in org-publish HTML export Date: Wed, 30 Jul 2008 15:03:38 +0100 Message-ID: <489074BA.4000806@calicojack.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KOCHW-0005hp-U5 for emacs-orgmode@gnu.org; Wed, 30 Jul 2008 10:03:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KOCHV-0005fs-40 for emacs-orgmode@gnu.org; Wed, 30 Jul 2008 10:03:58 -0400 Received: from [199.232.76.173] (port=60830 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KOCHU-0005ff-R8 for emacs-orgmode@gnu.org; Wed, 30 Jul 2008 10:03:56 -0400 Received: from storm.bpweb.net ([83.223.106.8]:54432) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KOCHU-0003bR-8J for emacs-orgmode@gnu.org; Wed, 30 Jul 2008 10:03:56 -0400 Received: from lechuck.local (host-77-100-223-163.static.telewest.net [77.100.223.163]) (authenticated bits=0) by storm.bpweb.net (8.13.1/8.13.1) with ESMTP id m6UE3hTS000843 for ; Wed, 30 Jul 2008 15:03:48 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Hi all, Well I've been continuing my usage of org-mode, and have been using it for sometime as a lightweight bug tracker for documenting bugs and associated code-snippets/error-reports in small software projects. Recently I wanted to make this document viewable for others, and so published it with org-export-as-html. Anyway, I'm delighted with the output; particularly regarding the fontifying of code-snippets, but there is an improvement I'd like to make in my output: I currently document bugs roughly like this: * ProjectX bugs ** BUG project crashes on network failure :2.0:NETWORK:UI: ** BUGREPORT error thrown on data entry :DB: ** FIXED compiler warnings :1.0:BUILD: * ProjectX Improvements ** FEATUREREQUEST Add a new button to UI :2.1:UI: ** FEATUREREQUEST Add email support :2.3:UI:EMAIL:EXP: ** FEATUREREQUEST Support X,Y,Z :3.0:DB:TRUNK:EXP: You'll notice that I use tags to categorise features/bugs and to prioritise them into versions of the software. I also use these tags to indicate which branch features/bugs might be best put into. Sometimes these changes are required to be deployed into several branches so tagging like this is flexible and works well. However the problem is that, in the exported HTML the tags are not listed in a useful way. It would be great if org could generate a table of contents organised by tag. To allow easier navigation Tags on outlines/headings would then be links back to the tag table, and links in the tag-table would link to the headings like they do already with the TOC. Thinking about it, would org-info.js do this? Thanks again! R.