[pollen] A few questions about pollen capabilities

2019-05-09 Thread Joel McCracken
One of the things that has held me back from using Pollen is what I 
perceive as potential limitations. I'm not sure if I want to use pollen, or 
use XML and write my own processor, and I am trying to make a decision.

I had a number of questions when I started this post, but I decided to look 
at some of the sites I know of that use pollen, and many of them are 
answered. There are still a few though:

I want to be able to define aliases for pages, and be able to do like 
`@link[the-alias]`. I noticed that i could use metas to implement this, so 
that's fine.

I want to have  a CLI command that outputs all the aliases and the files 
they refer to, as a way to remember the aliases. Ideally, I will eventually 
have emacs run this command to get suggestions while I program. 

In general, I know I will want to implement new CLI commands of varous 
kinds, especially where I output information based upon post metadata. Is 
that something I could do without much difficulty?

Not necessary, but another thing I was thinking about doing is implementing 
bi-directional links, that is, adding a section on some pages that says 
"what links here". Is this doable?

When I write something, sometimes I want to declare the file to be a draft, 
and not have it appear in the final output, and/or have "published on" data 
available. I was thinking it would be handy if I could do something like:

◊(define-publish-status 'draft)

and only have draft posts be rendered in development.

Is it possible to read a pollen file and get the sexpr representation, or 
something like it?

So, really, my questions all revolve around controlling the output process. 
I think what worries me is that output works all by itself without any 
control. I also don't know how to add new CLI tasks.

I would be willing to fork Pollen if necessary to do some of these things 
for myself, but if Pollen is designed in such a way that I would be 
fighting a lot, it might be a fool's errand.

Thank you for your work on Pollen. Its super cool, and I really hope I get 
to use it!

-- 
You received this message because you are subscribed to the Google Groups 
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pollenpub+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pollenpub/f2d47937-bab1-4180-a3ff-3a66c3caaef9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[pollen] render and render -p different behaviour

2019-05-09 Thread Evžen Wybitul
Hey, I have recently added a .poly file. It had worked for a little while, 
but lately I'm encountering this error: [...] notes.poly.pm.rktd::15: read: 
bad syntax `#<'. Acutally, the notes.poly.pm.rktd has # in place 
where the document content should be. When I run render -p instead, I don't 
see any such error, but one of the poly-export formats is missing (Markdown 
specifically). Do you know what could cause the doc to not appear at all 
and be #?

-- 
You received this message because you are subscribed to the Google Groups 
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pollenpub+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pollenpub/ad14a1c7-db23-451a-9fdd-485456d5a534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.