Nikola Ideas para PyCamp
Si vas a PyCamp (o si no vas también), sos bienvenido a unirte a mí en la implementación de estas cosas en una maratón de programación empezando el viernes y siguiendo todo el fin de semana.
Tengo algunas ideas en la cabeza, pero quiero más. Estas son las que tengo, agreguen en los comentarios:
- Galería de Código
-
Como galerías de imágenes, pero para código. Ponés el código en una carpeta y va a aparecer hermoso. Con la adición de una directiva "listing" de docutil, va a hacer que mostrar código en detalle o en contexto sea simple y poderoso, haciendo a Nikola más atractivo para bloggers-programadores.
- Pulir Galerías
-
Las galerías de imágenes están implementadas y andan, pero necesitan pulido. Se pueden hacer más eficientes en red, ponerles feeds RSS, galerías recursivas, metadata, textos en las imágenes, y mucho más.
- Pipelines
-
¿Querés minimizar to CSS? ¿Emprolijar tu HTML? ¿Achicar las imágenes? ¿Aplicar transformaciones al HTML? ¿Cosas que no me imagino?
Los pipelines traerían el poder del shell unix a un generador de sitios, permitiendote conectar filtros provistos por nikola o por la comunidad como si fueran legos.
- Editor Online (Alva)
-
Si bien los generadores de sitios estáticos tienen muchos beneficios, tienen un lado malo: tenés que editar los archivos en tu propio equipo.
Un editor online para Nikola te permite editarlos via web y publicar desde cualquier lado.
- Nikola Hosting (Shoreham)
-
¿Por qué no crear un servicio en que el usuario alimenta de posts al server y el server publica? La alimentación puede ser vía un DVCS, un servicio de sync de archivos, editor online, o lo que sea, y el resultado se publica inmediatamente o tocando un botón.
- Borradores
-
Yo no hago borradores. Yo escribo y mando. Pero otros prefieren enfoques mas cautelosos y menos dementes. Entonces, ¿Cómo deberían funcionar los borradores? Si bien seguramente es fácil de implementar es una tarea excelente para un principiante, donde hay que pensar más acerca de lo que se quiere lograr y la experiencia que se brinda al usuario que acerca del código en sí.
Entonces, si hay algo que viste en otro generador de blogs estáticos que Nikola no tiene, o tenés una idea y necesitás un framework donde meterla, o tenés una idea loca loca loca que nadie quiere tocar ni con un puntero láser...
CONTAME.
If you do pipelines, I could upstream my optimizations. I am therefore hoping you do that. The Gallery Polishing, I would do my own, but I am not really qualified. I would love if it became network efficient, and it actually matters a lot to me. For bonus points, could you integrate with Digikam tags?
Are digikam tags in the EXIF data?
I believe in settings/metadata you get to specifiy what.
From the gallery, I would hope to be able to export all, then let Nikola work on those in its template I suppose, and remove the rest with jpegoptim and friends.
So then in Digikam, I would tag things to be in a certain album, and then I would want it to appear in Nikola. That would be a great user interface, and would require no copying of files and links at all.
But if you do that as a last step, it would probably be best. But I seem to recall you as a KDE guy, so i kind of expect you to know how to talk with Digikam directly.
Yes, former KDE guy, but have no clue about digikam's inner workings, really.
lol, I will forgive. Enjoy your hackfest... I am currently at Europython, and don't get anything done, just talking to so many people, new and witty people, who have a lot to say. But I rebased to latest Nikola and it was easy to do.
One thing, I believe you ought to not forget, is the pylint cleanliness thing. It would allow you to catch typos and mismerges easier (seen recent commits of such) and it's only practical, if you once make it to 0, so you can then use it easily as a check before push.
And btw, I was considering to package Nikola for Debian, but for that, I need a solution for the "doit/nikola" mix. Did you give an OK for that? I wanted to attack that occasionally. It's can't be that hard. As for the packaging, the lack of a doit Debian package will be hurting though.
I am ok with making the nikola command a doit wrapper. If doit is not packaged, you can bundle the standalone doit script: http://python-doit.sourcefo...
And yes, I need to be more careful with pylint and the rest :-)
Ok, will do that then. As for the packaging for Debian, builtin copies bundled are not very popular, but I can still try.
As for pylint, don't worry, it would just be nice, if you had something like "check-with-pylint". You can steal it from Nuitka and re-license as you see fit. It already has most of the things sorted out.
Git it from here: http://nuitka.net/gitweb/?p...
Just change the path to your script, and adapt the while listing, then adapt the options. I have disabled naming stuff, and useless things already.
As a contributor, I would appreciate a quick way to tell that I don't submit any bad stuff. But now, changing things, it's not really practical. So if you want to go for that, you are welcome. :-)
Yours,
Kay
Es una pavada pero tener como opcional tener un "almanaque" similar al que usa el gran hermano del canal (http://irclogger.com/.pyar/) para asustar menos con el archivo creo que estaria bueno
Exportar a pdf!
Here's my two cents: 1) Add support for predefined page layouts. Most sites/pages have header, footer, content area and optionally a left column and/or right column. That would also allow for more powerful theming. 2) add support for including YAML metadata in file header rather than a separate file, as in Jekyll (see https://github.com/mojombo/....
There is already a way to put the metadata in a comment in the post itself (but it seems to be slightly buggy)
I am not sure I understand about the layouts. Can you point me at docs or examples?