Eating your own dog food (Site/Blog)

Hi,

if I want to create a site/blog in pharo… What do I use? I know that there is Pier, but when you check its webpage, the last update is in 2011. Pharo website is built with Marina, but when I check the repo, the last commit was done by me and it was 2 month ago. Will Marina continue to evolve? And is anyone else using Marina?

Uko

Yuriy Tymchuk <[hidden email]> writes:

> if I want to create a site/blog in pharo… What do I use? I know that
> there is Pier, but when you check its webpage, the last update is in
> 2011. Pharo website is built with Marina, but when I check the repo,
> the last commit was done by me and it was 2 month ago. Will Marina
> continue to evolve? And is anyone else using Marina?


http://forum.world.st/Any-framework-to-create-a-blog-over-seaside-td4810615.html
--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Oh, I knew that there was a discussion about that, but couldn’t find where.

Still, is anybody else using Marina except for Pharo website?

Uko

On 07/04/15 10:28, Yuriy Tymchuk wrote:
> if I want to create a site/blog in pharo… What do I use? I know that there is Pier,
>but when you check its webpage, the last update is in 2011.
 >Pharo website is built with Marina, but when I check the repo,
 >the last commit was done by me and it was 2 month ago.
 >Will Marina continue to evolve? And is anyone else using Marina?

Pier is on CI, and just works. Once in a while something breaks
and then we fix it. The PierAddons are also on ci, but are less
used. Diego published how to use Bootstrap with Pier on the
mailing list. That post might be hard to understand, Pier is
very elegant but complex.

Stephan

philippeback wrote

On Tue, Apr 7, 2015 at 9:28 AM, Yuriy Tymchuk <[hidden email]> wrote:

I think http://www.samadhiweb.com/blog/ is using a Smalltalk engine. But I
do not know if it is public.

Phil

> Uko
>

Good catch!

From the about page: This blog began life as a set of static pages, generated by a home-grown content management system written in Smalltalk, imaginatively called SmallCMS1. Since April 2012, SmallCMS1 has evolved into serving content dynamically, to support tag linking like this: sqlite.

Is SmallCMS1 published somewhere?

I started to work on using pillar to do that but nothing ready for
people to use.
I will work on it at Lviv or during my vacations just after.
I want to use it for my website. Right now parts of it are automatically
generated from Pharo.

Stef

Le 7/4/15 10:56, Yuriy Tymchuk a écrit :

What you are after? A static site generator or a dynamic engine? Btw. what do you use to render pillar inside the image to something readable?

Norbert

There is a plan to have pillar rendering with TextModel. I don't think it will support the full pillar syntax.

Le 8 avr. 2015 à 11:16, Norbert Hartl a écrit :

When are you going to be in Lviv?

19 to 23 rd of April.

Stef


Le 8/4/15 11:23, Yuriy Tymchuk a écrit :

Le 8/4/15 11:16, Norbert Hartl a écrit :
> What you are after? A static site generator or a dynamic engine?

A mix between the two.
I want simple static contents + logic generated :)

> Am 09.04.2015 um 15:54 schrieb stepharo <[hidden email]>:
>
>
>
> Le 8/4/15 11:16, Norbert Hartl a écrit :
>> What you are after? A static site generator or a dynamic engine?
>
> A mix between the two.
> I want simple static contents + logic generated :)

Haha, some goes for me. Just didn't find time so far to make that wish a bit more concrete.

Norbert

On Tue, Apr 07, 2015 at 09:38:37AM -0700, garduino wrote:
> Is SmallCMS1 published somewhere?

I'll share some SmallCMS1's inner workings here:

- Content is in plain text file, written in Markdown. Metadata is in JSON at
the start of the content file.

- I use Seaside's HTML rendition engine. Entire site is rendered in
Smalltalk code, like how a Seaside application does. Currently calls out to
the Discount C library's executable through PipeableOSProcess to get HTML from
the Markdown content. I seem to recall that Petit Markdown exists, but haven't
tried it.

- I found Seaside's HTML-in-code style not so convenient when trying to
implement one particular fine looking open source Bootstrap skin. Maybe using
a templating mechanism like Mustache will make it easier.

- Because my site is small, SmallCMS1 reads the entire content directory
tree into a tree-like (duh) structure. URLs are matched by walking the
in-memory tree using simple string matching. I was going to say this prevents
the dot dot trick, but I thought I'd verify. Putting a halt in my code, I
now notice that Firefox processes ".." before it sends the request, so
SmallCMS1 doesn't see the ".." at all, at least when using Firefox.

- Comment system is outsourced to Disqus.

- I VNC into the image and use inspectors, workspaces, and browsers as
SmallCMS1's admin interface. I run my own VPS so I have Unix command line
access to the content directory.

SmallCMS1 is thus quite tied to the way I work.

I have not published SmallCMS1. Maybe SmallCMS2, if it ever happens... :-)

Pierce

Thanks for the detailed explanation Pierce!

And I understand perfectly, I have some internal stuff of my company that I work with the same style, and hard to publish.

Regards!