Hi I prefer to clone every repo I use locally. I just did this with Seaside and then used Iceberg to load it into a new Pharo8 image and it worked. Vince From: Pharo-users <pharo-users-bounces@lists.pharo.org> On Behalf Of Vitor Medina Cruz Sent: Wednesday, 20 May 2020 12:27 PM To: Any question about pharo is welcome <pharo-users@lists.pharo.org> Subject: Re: [Pharo-users] New user EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hello, I feel your pain. Updated, consistent and centralized documentation is not strong in Pharo. Things are changing fast and docs don't catch up, also there is an effort to move projects to github, so usually updated stuff are there. I never use Catalog anymore because often things goes wrong. Books are only good to explain major concepts that are less likely to change over time, in order to getting started I would recommend: 1- Seaside github project: https://github.com/SeasideSt/Seaside<https://urldefense.com/v3/__https:/github.com/SeasideSt/Seaside__;!!I_DbfM1H!WXIAvRagwWuej-uZGIn76FNtm7UEPiWg9wPBC5MRYwKLEr7jdo-ZacFmHF-6nRUHMeHpCFNciw$>. Their readme and wiki page seems to be very good and updated, I just evaluated this on playground and it worked as expected: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:v3.4.1/repository'; load I avoid using master tag as it is usually development branch or frequently has some commit that breaks everything up and and what I want is something reliable, so I always use version tags (when the projects provides one). After that, I think using the wiki (https://github.com/SeasideSt/Seaside/wiki<https://urldefense.com/v3/__https:/github.com/SeasideSt/Seaside/wiki__;!!I_DbfM1H!WXIAvRagwWuej-uZGIn76FNtm7UEPiWg9wPBC5MRYwKLEr7jdo-ZacFmHF-6nRUHMeFqPDipfw$>) or seaside web book (http://book.seaside.st/book<https://urldefense.com/v3/__http:/book.seaside.st/book__;!!I_DbfM1H!WXIAvRagwWuej-uZGIn76FNtm7UEPiWg9wPBC5MRYwKLEr7jdo-ZacFmHF-6nRUHMeG9o4S-wQ$>) can get you through all you need to know. 2- Pharo open documentation is a much better place to be getting started with Pharo: https://github.com/pharo-open-documentation/pharo-wiki<https://urldefense.com/v3/__https:/github.com/pharo-open-documentation/pharo-wiki__;!!I_DbfM1H!WXIAvRagwWuej-uZGIn76FNtm7UEPiWg9wPBC5MRYwKLEr7jdo-ZacFmHF-6nRUHMeEp0Lx6gg$> 3- Then you can go and read Pharo by Example and Deep in Pharo books in order to get more information after you can get started, if you are interest, but by now you must be able to do most basic stuff with the system.. Hope that helps you getting by and fuel you interest in Smalltalk and Pharo. Regars, Vitor On Tue, May 19, 2020 at 7:38 PM G B via Pharo-users <pharo-users@lists.pharo.org<mailto:pharo-users@lists.pharo.org>> wrote: I am new to Pharo and liked that it is a cleaned up and modern Smalltalk, but I think I'm done before I ever started. My biggest interest was in Seaside, yet trying to install it from instructions on the Seaside GitHub fails: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load Trying to load packages from the catalog browser like Magritte fails. Some packages aren't updated for 8.0 and are only available for 7.0. Some are only available for 4.0. Trying to follow the book for creating a blog has ha me spend time trying to get something going to no avail. I'm not an expert programmer, but I've been in IT for 25 years and can do some C, Racket, Pascal, shell languages, awk, Perl, but I am stymied at every turn with Pharo.