If you miss it so much we have something much better Github wikis, we never use
Each of our books is hosted in a Github repo and each repo always comes with its own wiki using very simple markdown as everything else in Github You do not have content but only a snippet of code to offer ? No problem we have you covered there too create a gist for it , link it in the wiki and we will add it back to book. Gists even offer their own version control which means you can keep working and improving your code snippet for years to come without braking the workflow. Then its a question of copy pasting the contents to pillar and adding them in our books , or if you do not mind the extra work write it in pillar directly and add it to the relevant book All books can be added to CI and generate automagically html pages for direct access , we do this already with PBE 5. Our Pharo "wiki" is easier to use and far more powerful than anything Squeak ever had, no offence intended of course to the original creators and maintainers of Squeak wiki. Also github offers hosting of static webpages we could have a website hosted as github repo made with pillar that link to all wikis, gists and book artifacts. I can create this in an hour of work its not big deal. I would have done this myself but Stef already has added the books to Pharo.org which I find is more or less the same thing. On Fri, Feb 10, 2017 at 10:15 PM [email protected] < [email protected]> wrote: > I miss the Squeak wiki Pharo style. > > Phil > > Le 10 févr. 2017 19:06, "Esteban A. Maringolo" <[email protected]> a > écrit : > > 2017-02-10 14:59 GMT-03:00 [email protected] <[email protected]>: > > Mass adoption and hyper reduced friction to get people on board. > > > > For me: I have 10+ slack teams in my slack client and there is really no > > point in having more clients on the desktop. > > +1 to this. This is key. > > Maybe what we're missing is a simple wiki to collect the shared > knowledge, recipes, and other stuff. > > > Esteban A. Maringolo > >
