MAIN Topic: Special Website Transition Working Session Presenter: Sean Twiehaus ************************************************************************ Live code combination, procedures, transition, and work flow instruction on the transition to the new SLUUG website developed by Sean Twiehaus. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ As demonstrated: https://site.sluug.org ONLINE session will use ZOOM remote video service 27 March 2025. Read and view ahead information will soon follow separately. Check the home page for further information and updates. It would be a big help if the people who plan on attending the Thursday meeting could pre-read what I have below. This is the repo for the site: https://git.sluug.org/git/sluug_stllug_site **Login credentials required. To be issued Thusday.** This repo will have updates several times a month as new content is added for the new meetings. If you look in the README.md file it describes the commands that are available for developing the site, building the site, previewing the site, etc. The build command will create a ./dist directory. That directory contains the content that needs to be copied to the web server. This is the repo for the AI Content Generation: https://git.sluug.org/git/sluug_stllug_generation **Login credentials required. To be issued Thursday.** This repo contains a script to generate AI content to supplement what the presenter provided. This repo should change very infrequently. The idea is, you take what the presenter sends to steercom, you format that information into JSON and put it in the correct location, then you run this script. It will add more content. You copy the content to the site repo. You build, preview, and commit the content to the site repo. You should not actually commit any content to this script repo. The README.md file explains how to set up a dev system and the initial json files to run the script. As of right now the README files are the same on Github and Bock. They haven't diverged yet. So the people attending the Thursday meeting could read the READMEs here: https://github.com/seantwie03/sluug_stllug_generation https://github.com/seantwie03/sluug_stllug_site Looking at the site, it looks like the last update I did was December. NOTE: December SLUUG was done. December STLLUG was NOT done. So during the meeting I can show the process by adding January SLUUG and STLLUG. Then we can divide the other months up amongst meeting participants. Maybe Stan can do Feb SLUUG, someone else can do Feb STLLUG, someone else can do March SLUUG, someone else can do March STLLUG, etc. The more people that can get hands-on experience with the process the better! -- -- stan r. -- newlinux.org For anyone new to Linux, the newcomers. -- I know about TCP/IP; but, understand less of it each day. -- Save the earth..... It's the only planet with dark chocolate!