- Pharo-dev - lists.pharo.org

question about Zinc ZnUrl or ZnResourceMetaUtils

by StÃ©phane Ducasse

Hi sven Are the dictionaries for the query part conserving the order? Because this would be really nice. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

> > Its intended to work with Pharo 6 and the repo is on sthub. Would it be possible guile to put it on GitHub ? > I cannot access mcz files from smalltalkhub. http://smalltalkhub.com/mc/RMoD/Ecstatic/ConfigurationOfEcstatic-GuillermoP… <http://smalltalkhub.com/mc/RMoD/Ecstatic/ConfigurationOfEcstatic-GuillermoP…> => /mc/RMoD/Ecstatic/ConfigurationOfEcstatic-GuillermoPolito.14.mcz not found Cheers, CÃ©drick

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

I like what I see so far in ecstatic. I just wonder if partials are available ? Its intended to work with Pharo 6 and the repo is on sthub. Would it be possible guile to put it on GitHub ? Cheers, CÃ©drick > Le 28 mai 2020 Ã 10:36, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > >> >> Guile, what is its status ? Can you give some information (the web site is in latin ;) ) > > Ok I didnât see the menu and was hitting (on phone) http://guillep.github.io/ecstatic/getting_started.html <http://guillep.github.io/ecstatic/getting_started.html> (you should remove this link ;-) ). > > > http://guillep.github.io/ecstatic/install.html <http://guillep.github.io/ecstatic/install.html> > http://guillep.github.io/ecstatic/first_site.html <http://guillep.github.io/ecstatic/first_site.html> > > Iâll try soon. Are partials possibles ? I guess I have to look at the code â¦ > > Cheers, > CÃ©drick > >> >> Iâll try it. >> >> Cheers, >> CÃ©drick >> >>> Le 27 mai 2020 Ã 14:00, serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com> a Ã©crit : >>> >>> There is already a static website generator in Pharo: https://github.com/guillep/ecstatic <https://github.com/guillep/ecstatic> >>> Maybe you should start from that? >>> It would be great. >>> Regards >>> >>> Sent from my iPhone >>> >>>> On 27 May 2020, at 19:49, Esteban Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: >>>> >>>> ï»¿On Wed, May 27, 2020 at 3:59 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >>>> >>>>>> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... >>>>>> I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . >>>>> It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... >>>> >>>> I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR >>>> and SPA, I found some of their ideas in how to organize content to be >>>> valuable, but I can't stand the tooling or the feeling of facing an >>>> unneeded accidental complexity. >>>> >>>>>> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. >>>>> Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. >>>> >>>> I spent the last weekend giving a try to that Gatbsy thing (nuxt.js >>>> and vuepress are in the backlog too), and at 10PM on sunday I decided >>>> to start coding something in Smalltalk, because it just feels better >>>> to me. >>>> >>>> I don't know how harder would it be, but that's a tool we currently >>>> lack, the static-site generator. And we have support for different >>>> templating, rendering canvas, and whatnot. >>>> >>>>>> Combine this with the new headless image and it should easily plug into netlify . >>>>> Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. >>>> >>>> When I think about netlify I don't think about an app (as in, an >>>> executable) but as a simple static site, but if it possible to deploy >>>> an app that is distributed and served by their CDN, then better! >>>> >>>>> I also wonder what would be possible with mini-image like Erik did. >>>> >>>> I need to see more! >>>> I don't know how independent a client image can be, how much you can >>>> "pre-deploy" without needed to rehydrate the browser with server >>>> changes, etc. >>>> It's promising. >>>> >>>> Regards! >>>> >> >

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

> > Guile, what is its status ? Can you give some information (the web site is in latin ;) ) Ok I didnât see the menu and was hitting (on phone) http://guillep.github.io/ecstatic/getting_started.html <http://guillep.github.io/ecstatic/getting_started.html> (you should remove this link ;-) ). http://guillep.github.io/ecstatic/install.html <http://guillep.github.io/ecstatic/install.html> http://guillep.github.io/ecstatic/first_site.html <http://guillep.github.io/ecstatic/first_site.html> Iâll try soon. Are partials possibles ? I guess I have to look at the code â¦ Cheers, CÃ©drick > > Iâll try it. > > Cheers, > CÃ©drick > >> Le 27 mai 2020 Ã 14:00, serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com> a Ã©crit : >> >> There is already a static website generator in Pharo: https://github.com/guillep/ecstatic <https://github.com/guillep/ecstatic> >> Maybe you should start from that? >> It would be great. >> Regards >> >> Sent from my iPhone >> >>> On 27 May 2020, at 19:49, Esteban Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: >>> >>> ï»¿On Wed, May 27, 2020 at 3:59 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >>> >>>>> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... >>>>> I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . >>>> It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... >>> >>> I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR >>> and SPA, I found some of their ideas in how to organize content to be >>> valuable, but I can't stand the tooling or the feeling of facing an >>> unneeded accidental complexity. >>> >>>>> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. >>>> Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. >>> >>> I spent the last weekend giving a try to that Gatbsy thing (nuxt.js >>> and vuepress are in the backlog too), and at 10PM on sunday I decided >>> to start coding something in Smalltalk, because it just feels better >>> to me. >>> >>> I don't know how harder would it be, but that's a tool we currently >>> lack, the static-site generator. And we have support for different >>> templating, rendering canvas, and whatnot. >>> >>>>> Combine this with the new headless image and it should easily plug into netlify . >>>> Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. >>> >>> When I think about netlify I don't think about an app (as in, an >>> executable) but as a simple static site, but if it possible to deploy >>> an app that is distributed and served by their CDN, then better! >>> >>>> I also wonder what would be possible with mini-image like Erik did. >>> >>> I need to see more! >>> I don't know how independent a client image can be, how much you can >>> "pre-deploy" without needed to rehydrate the browser with server >>> changes, etc. >>> It's promising. >>> >>> Regards! >>> >

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

Cool :) I forgot this one ! Guile, what is its status ? Can you give some information (the web site is in latin ;) ) Iâll try it. Cheers, CÃ©drick > Le 27 mai 2020 Ã 14:00, serge.stinckwich(a)gmail.com a Ã©crit : > > There is already a static website generator in Pharo: https://github.com/guillep/ecstatic <https://github.com/guillep/ecstatic> > Maybe you should start from that? > It would be great. > Regards > > Sent from my iPhone > >> On 27 May 2020, at 19:49, Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> ï»¿On Wed, May 27, 2020 at 3:59 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >>>> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... >>>> I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . >>> It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... >> >> I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR >> and SPA, I found some of their ideas in how to organize content to be >> valuable, but I can't stand the tooling or the feeling of facing an >> unneeded accidental complexity. >> >>>> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. >>> Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. >> >> I spent the last weekend giving a try to that Gatbsy thing (nuxt.js >> and vuepress are in the backlog too), and at 10PM on sunday I decided >> to start coding something in Smalltalk, because it just feels better >> to me. >> >> I don't know how harder would it be, but that's a tool we currently >> lack, the static-site generator. And we have support for different >> templating, rendering canvas, and whatnot. >> >>>> Combine this with the new headless image and it should easily plug into netlify . >>> Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. >> >> When I think about netlify I don't think about an app (as in, an >> executable) but as a simple static site, but if it possible to deploy >> an app that is distributed and served by their CDN, then better! >> >>> I also wonder what would be possible with mini-image like Erik did. >> >> I need to see more! >> I don't know how independent a client image can be, how much you can >> "pre-deploy" without needed to rehydrate the browser with server >> changes, etc. >> It's promising. >> >> Regards! >>

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

> I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR > and SPA, I found some of their ideas in how to organize content to be > valuable, but I can't stand the tooling or the feeling of facing an > unneeded accidental complexity. A bit the same feeling. All node lib in general, easy to load and play with, but when bad things happen, Iâm lost missing debugging facilities, etc... > >>> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. >> Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. > > I spent the last weekend giving a try to that Gatbsy thing (nuxt.js > and vuepress are in the backlog too), and at 10PM on sunday I decided > to start coding something in Smalltalk, because it just feels better > to me. Yes :) Same, Iâve been trying Hugo and Jekyll. Jekyll was cool for the integration in GitHub. But I donât like the non immediate propagation of changes. So I ended up using Hugo (+ I like that Hugo has lots of templates). Still I was wondering, that if using Hugo and not have the full GitHub integration, then why not having something in pharo :) You know I always try to refrain that Â« do not reinvent the wheel Â»â¦. But thatâs so hard sometimes. (Side note: I use netlogo now to do some simulation - itâs a really cool softwareâ¦ reallyâ¦ still, when I really miss st environnement, is when you model become complexâ¦ and when it comes to debugâ¦. Iâve just spent two weeks debugging thingsâ¦ so frustratingâ¦ frankly with the exploration natively possible n smalltalk, I really think this would have been two daysâ¦)... => so cool you start to write something in st :) > > I don't know how harder would it be, but that's a tool we currently > lack, the static-site generator. And we have support for different > templating, rendering canvas, and whatnot. I agree. :). I loved and still love seaside but my needs are really simple to host website that do not take much processing to host. I want to have 1000 web site of my ridiculous boxâ¦ Most of the need are very low audience web site called Â« vitrine Â» in France. I really hate that company sell such products thousands of eurosâ¦ (not kidding - a friend scam of mine is selling monthly fee like 140â¬ on a period up to 4 years !!!). So maybe we need to discuss requirements. 1- generator based on template (mustache is cool) and partials 2- deal with comments, for submission in general, and maybe all info exchange through PR in git. 3- easy graphical template integration (so you can choose free or small fee templates for your site- say 10/20 bucks) ==> lots are just free for Hugo https://themes.gohugo.io <https://themes.gohugo.io/> 4- having some components that will give some live features whereas itâs static â this can come later this one. ââFor instance, I want to provide a way to choose appointments, in a very smart way ââIâd like also to provide a stupid and simple little IoT that when a shop is open, it relates on the website, and vice-versa. Etc... I think 1 and 2 (and 3) are whatâs needed by all web site generator. 2 is debatable (a must to me), but I find it clever. So you moderate comments through githubs tools (and eventually in conjunction with Iceberg). 3 is really important too. Again, easy at first but can become complex (depend on how many js plugins there are). I know at least two companies thatâd be interested in developing graphic theme. The guy behind jekylltheme coud be interested too. Generally a theme cost around 3000â¬ for a full personalized and unlimited one. Then for individual use, the cost is around 10/20â¬. Lots are free too but of course less advanced. > >>> Combine this with the new headless image and it should easily plug into netlify . >> Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. > > When I think about netlify I don't think about an app (as in, an > executable) but as a simple static site, but if it possible to deploy > an app that is distributed and served by their CDN, then better! Same. This is more an option to me. But I guess this is a vey nice feature to have. > >> I also wonder what would be possible with mini-image like Erik did. > > I need to see more! > I don't know how independent a client image can be, how much you can > "pre-deploy" without needed to rehydrate the browser with server > changes, etc. > It's promising. This is cherry on the cake but what a delicious one :) Cheers, CÃ©drick > > Regards! >

May 28, 2020

[Pharo 9.0] Build #313: Create a common superclass for PDF and SVG surfaces and fix extent

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #313 was: FAILURE. The Pull Request #6399 was integrated: "Create a common superclass for PDF and SVG surfaces and fix extent" Pull request url: https://github.com/pharo-project/pharo/pull/6399 Issue Url: https://github.com/pharo-project/pharo/issues/6398 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 28, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by serge.stinckwich＠gmail.com

There is already a static website generator in Pharo: https://github.com/guillep/ecstatic Maybe you should start from that? It would be great. Regards Sent from my iPhone > On 27 May 2020, at 19:49, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > ï»¿On Wed, May 27, 2020 at 3:59 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > >>> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... >>> I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . >> It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... > > I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR > and SPA, I found some of their ideas in how to organize content to be > valuable, but I can't stand the tooling or the feeling of facing an > unneeded accidental complexity. > >>> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. >> Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. > > I spent the last weekend giving a try to that Gatbsy thing (nuxt.js > and vuepress are in the backlog too), and at 10PM on sunday I decided > to start coding something in Smalltalk, because it just feels better > to me. > > I don't know how harder would it be, but that's a tool we currently > lack, the static-site generator. And we have support for different > templating, rendering canvas, and whatnot. > >>> Combine this with the new headless image and it should easily plug into netlify . >> Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. > > When I think about netlify I don't think about an app (as in, an > executable) but as a simple static site, but if it possible to deploy > an app that is distributed and served by their CDN, then better! > >> I also wonder what would be possible with mini-image like Erik did. > > I need to see more! > I don't know how independent a client image can be, how much you can > "pre-deploy" without needed to rehydrate the browser with server > changes, etc. > It's promising. > > Regards! >

May 27, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by Esteban Maringolo

On Wed, May 27, 2020 at 3:59 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... >> I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . > It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR and SPA, I found some of their ideas in how to organize content to be valuable, but I can't stand the tooling or the feeling of facing an unneeded accidental complexity. >> Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. > Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. I spent the last weekend giving a try to that Gatbsy thing (nuxt.js and vuepress are in the backlog too), and at 10PM on sunday I decided to start coding something in Smalltalk, because it just feels better to me. I don't know how harder would it be, but that's a tool we currently lack, the static-site generator. And we have support for different templating, rendering canvas, and whatnot. >> Combine this with the new headless image and it should easily plug into netlify . > Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. When I think about netlify I don't think about an app (as in, an executable) but as a simple static site, but if it possible to deploy an app that is distributed and served by their CDN, then better! > I also wonder what would be possible with mini-image like Erik did. I need to see more! I don't know how independent a client image can be, how much you can "pre-deploy" without needed to rehydrate the browser with server changes, etc. It's promising. Regards!

May 27, 2020

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by CÃ©drick BÃ©ler

Hi Tim, > ï»¿ > Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... > > I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . Thanks for the feedback. It seems indeed that Jekyll can become frustrating. Iâm using Hugo right now. I didnât know metalsmith... > > Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. Iâve tried to restrain myself not to redo it in smalltalk but that would be great option. I donât know the required effort though but Iâll be glad to be part of such project. Are you still interested in such project Tim ? > > Combine this with the new headless image and it should easily plug into netlify . Plus to netlify but also class export to servers. I thing Git(hubs) Pages are a nice option. In any cas, one nice pattern is to use git to store pages versions, and then you can replay on Pages / or on your own server / or on netlify. I also wonder what would be possible with mini-image like Erik did. Cheers, CÃ©drick > > Tim > >> On 23 May 2020, at 21:41, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >> ï»¿ >> Hi Esteban, >> >>> This comes really on time for me, I decided to rewrite to small sites I have using Jekyll, and as read all their tutorials I thought even of having a Jekyllst variation, that uses the Jekyll directories and other conventions, but uses Smalltalk as its engine. Of course this is far reached given my real availability these days, that's lower than usual. >> >> Cool anyway if thatâs something that interest you too. What do you think of https://gohugo.io <https://gohugo.io/> ? >> >> Themes are pretty cool https://themes.gohugo.io <https://themes.gohugo.io/> >> >>> >>> However I'd like to be part of conversations around this, and eventually contribute to it, because I already started playing with Jekyll (and Gatsby as well). >> >> Perfect :) >> >> This is not urgent but I need to put 2 websites online for September (simple ones). For now, Iâm trying around. Summer will be perfect for me to work on such project. >> >> Cheers, >> >> CÃ©drick >> >>> >>> Regards, >>> >>> >>> Esteban A. Maringolo >>> >>> >>> On Sat, May 23, 2020 at 10:15 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >>> Hi there, >>> >>> This post is just to talk about one side project Iâm exploring and interested in from a long time. I think it may interest other people here. >>> >>> Iâd like to have powerful (static based) web site so hosting is really cheap (even free) and hassle free. Iâve my own server for years, it is cheap and simple but, of course, it needs some maintenance (linux update, nginx scripts, â¦) even if tools are the simplest Iâve found. >>> >>> Recently thanks to student projects ;-), I found some time to learn what I find is a wonderful solution. This solution is to use GitHub DSCM, GitHub Pages and Jekyll (a ruby static site generator that is natively integrated) all together. >>> https://jekyllrb.com <https://jekyllrb.com/> >>> >>> The beauty is that you can edit the site straight on GitHub. We get the power of version system and hosting for freeâ¦ >>> It literally is a CMS and the cheapest and reliable that I know of (grav might be another option). >>> >>> Of course, there are some Â« dynamic Â» content possibilities too (otherwise GitHub Pages is enough) >>> - blog posts are natively generated through new files according to a name convention. >>> - there are plugins too (but you have to watch for compatibility in GitHub). >>> >>> Dealing with forms and comments is possible >>> - solutions that are hosted on a third-party. Solution like Discus or formspree, â¦ (thatâs a NO GO to me) >>> - web service integration that you can host (note that form spree is on GitHub too https://github.com/formspree/formspree <https://github.com/formspree/formspree>) >>> >>> This last point is where Iâd like Pharo (Zinc, Iceberg) to be integrated. Again we could imagine a web service system based on Zinc. I could manage form submissions that way and everything Iâd like but it may end up complex. Do I need a database ? Do I need to store information and therefore manage the underlying architecture. If it crash, I want only the endpoint to be not available but the whole site still working. >>> >>> An in between elegant solution os to use git for what itâs good at (versioning collaboratively through PR, and also reliable hosting in classic platforms). >>> >>> The idea is to use the PR mechanisms to submit stuff like blog comments (note that you have a free moderation system). >>> This is actually not limited to comments but all kinds of possible interactionâ¦ >>> >>> This way is (to me) better in terms of infrastructure management. Such a service also needs to be available (and maintained) but this is a very minimalist machinery (hanling POST request service only - no real content management as deferred to github). And again, a fail safe version (for the last version of the generated pages). >>> >>> Staticman (https://staticman.net <https://staticman.net/>) is a nice node application that allows to do this. Itâs possible to host the service too. >>> <GraphiqueCollÃ©-1.png> >>> >>> I can use this node app of course, but I believe we could have quite easily such an application in Pharo with Zinc. >>> I also wonder if we could use Iceberg to deal with this information straight in a pharo image (thatâd be cherry on the cake). >>> The super cherry of the cake would be pharo core and lib documentation, demos (you can have one gihub page by organization and/or users - in paid plans, you can have more for private stuff)â¦ One place, one process to contribute, either for code or documentation. >>> >>> Anyway, I have no real question except than asking for feedback and also to know if some people are interested in such project. >>> >>> Cheers, >>> >>> CÃ©drick >>> >>> nb: my hidden goal is to provide web site for people, unipersonal and small organizations. So you know, they pay for the service of creation, but then they own it and can do whatever they like. Of course we can also offer paid services like managing dynamic information content. More than comments, Iâd like to be able to deal with stuff like orders, facturation, even meeting planning through ics versioned files, etc. >>> This really is something Iâd like to be able to provide soon (less than 1 yr time - simplest web site with contact form and comments at least). It might become something more serious the future... >>> >>> >>

May 27, 2020