Let's find out just what happens when we make something different. My goal is to use Drummer to manage an outline of projects. For example, I just got a new electronic goban and it deserves its own page. But it also deserves a blogpost. Maybe everything should be a dated blog post. But it would be nice to be able to use the default blog renderer (Old School) to render things that aren't blog.opml or about.opml.#
I made a public outline called Things.opml, which sometimes you can see included above and sometimes you can't. I haven't yet figured out what causes it to render fully or just be the title yet, I think it depends on its expansion state when I build the blog maybe?#
Update: I have removed the inclusion of Things.opml above, because I did a bad thing and accidentally turned it into a copy of the DW menu. I don't think this is a good thing to include in a blog post. Also, the things list is going to be too long to include inline, and I still don't have a good grasp of when included outlines get expanded when it goes through Old School.#
The Things.opml outline is still public, but I do not recommend opening it. I think I ripped a hole in the universe. For now, Things2.opml is the new Things.opml.#
I don't know if there's a way to get Old School to render/handle a request that says "render this file as a page", but basically that's what I'd like to be able to do. If I can't get Old School to do it directly I can write some Drumkit to do what I need. I think my final goal is to have something that renders my Drummer outlines into static html files that I can just host somewhere. For now I've set Things.opml as the about page for the blog part.#
Each of the nodes in the outline might be a reference to a separate opml file, and nodes might get moved into their own files as they get bigger, maybe. Not sure where the boundary between page and node is. Probably simplest to just let you navigate the entire hierarchy by clicking around, collapsing and zooming, but it'd be nice to make it simple to link to a page of just the electronic gobans, or a page just for the National TQ-1500.#
(Which, by the way, is basically the only electronic goban, ever. One of my projects is to build a new one, using LEDs for indicators and sensors.)#
Let's find out just what happens when we make something different. My goal is to use Drummer to manage an outline of projects. For example, I just got a new electronic goban and it deserves its own page. But it also deserves a blogpost. Maybe everything should be a dated blog post. But it would be nice to be able to use the default blog renderer (Old School) to render things that aren't blog.opml or about.opml.#
I made a public outline called Things.opml, which sometimes you can see included above and sometimes you can't. I haven't yet figured out what causes it to render fully or just be the title yet, I think it depends on its expansion state when I build the blog maybe?#
Update: I have removed the inclusion of Things.opml above, because I did a bad thing and accidentally turned it into a copy of the DW menu. I don't think this is a good thing to include in a blog post. Also, the things list is going to be too long to include inline, and I still don't have a good grasp of when included outlines get expanded when it goes through Old School.#
The Things.opml outline is still public, but I do not recommend opening it. I think I ripped a hole in the universe. For now, Things2.opml is the new Things.opml.#
I don't know if there's a way to get Old School to render/handle a request that says "render this file as a page", but basically that's what I'd like to be able to do. If I can't get Old School to do it directly I can write some Drumkit to do what I need. I think my final goal is to have something that renders my Drummer outlines into static html files that I can just host somewhere. For now I've set Things.opml as the about page for the blog part.#
Each of the nodes in the outline might be a reference to a separate opml file, and nodes might get moved into their own files as they get bigger, maybe. Not sure where the boundary between page and node is. Probably simplest to just let you navigate the entire hierarchy by clicking around, collapsing and zooming, but it'd be nice to make it simple to link to a page of just the electronic gobans, or a page just for the National TQ-1500.#
(Which, by the way, is basically the only electronic goban, ever. One of my projects is to build a new one, using LEDs for indicators and sensors.)#