Sort Marco, for some reason your emails in particular make google think you
are phishing me.. :)
On Thu, Aug 20, 2015 at 3:02 AM Marco Ciampa wrote:
>
> My only concern is about using markdown (see my other post and my little
> research:
> https://github.com/ciampix/kicad-doc/tree/master/doc_al
On Wed, Aug 19, 2015 at 07:15:58PM +, Pat David wrote:
> Michael made a comment on the previous thread about the dev update posts
> from Karine. I _think_ he meant gimp-dev vs. gimp-web, but I'm going to
> update everyone anyway.
[...]
> On that note, is there any thought/problems/advice on
Ok now I see the logic in this approach. This is just entirely new to me so I'm
kind of lost. I guess I'll be able to help more once I look through how Pelican
works and how the site is laid out a little more.
Kasim Ahmić
Sent from my iPhone
> On Aug 19, 2015, at 10:40 PM, Pat David wrote:
>
To minimize attack vectors and server resource requirements. We literally
have zero requirements for any server-side scripting, particularly during
client requests.
More to the point - what benefit does any CMS/blog system provide for us
over what we're doing here?
The benefit of using a static-
On 08/19/2015 10:06 PM, Kasim Ahmic wrote:
> you could get a simple, lightweight blogging engine like Chyrp
Written in PHP. And probably doesn't create a fully static site.
We already have Python running on the server, we want a static site, and
we want the site content in a version control s
I really only have one question about this whole thing: why go through the
trouble of hacking together a Pelican based website when you could get a
simple, lightweight blogging engine like Chyrp to handle all the blog functions
while every other page is hard coded. I may be missing something her
