- The speaker is updating a webpack project and publishing it to GitHub pages using an example of Reveal.js for the NCA Talent Connector presentation.
- They mention that all the things they do are open source and encourage viewers to check out the Never Code Alone GitHub account.
- The speaker goes through different topics discussed in the presentation, including onboarding, values and goals, and fresher.
- They mention making a mistake in copying something and fixing it in their terminal using git commands.
- The speaker demonstrates making changes to the project and committing them using the Pugitive plugin.
- They mention running an npm run build command and generating files.
- The speaker discusses the topic of commit amendments and their personal preference for having understandable commit history.
- They stage the newly generated file and make a commit with additional information.
- The speaker saves their changes and views the commit history.

- The speaker is discussing the need for more contrast in their YouTube video.
- They mention pushing updates to GitHub and checking the deployment process.
- They encounter a delay in the update but eventually see the changes.
- The speaker asks for opinions on GitHub Hosting and GitHub Actions.
- They mention using GitHub locally and wanting to deepen their knowledge.
- They encourage viewers to follow their channel and provide links to other videos.

In diesem YouTube-Video von "Never Code Alone" lernst du, wie du ein Webpack-Projekt aktualisierst und auf GitHub Pages veröffentlichst. Dieses Tutorial verwendet das Beispielprojekt "Reveal JS" für eine aktuelle Präsentation des "NCA Talent Konnektors". Roland erklärt Schritt für Schritt, wie du dein Projekt verwalten und Git-Commits erstellen kannst, um Änderungen nachzuverfolgen. Wir erklären, warum es wichtig ist, Commits sinnvoll zu organisieren und wie dies die Zusammenarbeit in Teams erleichtern kann. Schließlich führen wir den Build-Prozess durch und zeigen, wie die Änderungen auf unserer Webseite umgesetzt werden.

Wenn du ein Entwickler oder eine Entwicklerin bist und mehr über die Verwaltung von Webpack-Projekten, die Veröffentlichung auf GitHub und effiziente Git-Nutzung erfahren möchtest, dann ist dieses Video genau das Richtige für dich. 

Schließe dich der Community von "Never Code Alone" an, um wertvolle Einblicke in die Welt der Webentwicklung zu erhalten und deine Fähigkeiten zu verbessern. Vergiss nicht, das Video zu liken, zu kommentieren und zu teilen, wenn es dir gefallen hat. Viel Spaß beim Lernen und Entwickeln!

00:00 Update für GitHub Pages als Tutorial auf Deutsch
01:54 ZSH Terminal für Webdevelopment
02:38 Vim Editor für eine Änderung an einem Webpack Javascript Projekt File
03:45 Fugitive Git Commit Tutorial
05:27 NPM Run Build ausführen und Javascript HTML Files mit Webpack neu generieren
06:15 Tig für Git Diff View auf dem Terminal
06:43 Git Commit Ammend mit Vim ausführen
11:10 GitHub Action und Cache Folder für GitHub Pages
12:40 Fazit zu Publishing Updates bei Github Pages

ChatGPT Playlist:
https://www.youtube.com/watch?v=Rfh8DSpRYIM&list=PLKrKzhBjw2Y9WAmajKpaE8mzQ2UpY1UYu

Cypress.IO Live Coding Tutorial Playlist:
https://www.youtube.com/watch?v=mb_PTxDeJKI&list=PLKrKzhBjw2Y9ceCxO3ollOc4eIVPAjiHs 

Vim Playlist:
https://www.youtube.com/playlist?list=PLKrKzhBjw2Y-9sCNpvbg3BY9v4JRc6fgn

Tailwind Playlist: 
https://www.youtube.com/playlist?list=PLKrKzhBjw2Y92eHOPEfwwZmAkxxcGr-yi

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

Hier geht es zu unseren Social-Media-Kanälen: 

► Patreon: https://patreon.com/nevercodealone 
► Twitter: https://twitter.com/nevercodealone 
► Instagram: https://www.instagram.com/nevercodealone/ 
► LinkedIn: https://www.linkedin.com/company/never-code-alone/ 
► Facebook: https://www.facebook.com/nevercodealone

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

Das sind unsere Webseiten:

► Never Code Alone bietet kostenlose und kommerzielle live Coding Events und PHP Kurse für Fortgeschrittene an und unterstützt soziale Projekte https://nevercodealone.de 

► TESTIFY - Agentur für Website Testing mit Cypress.IO und dem Codeception Testing Framework https://testify.team/ 

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

Du möchtest Never Code Alone unterstützen?
Dann lass uns gerne ein Abo da und schreibe deine Fragen und/oder Anregungen in die Kommentare. 

Danke fürs zuschauen!
Ich hoffe das Video hat dir gefallen.

Hello friends of software entertainment and welcome to Never Code Alone.

You want to know how to update a webpack project and publish it to GitHub pages.

I do the whole thing here on an example of Reveal.js for our current presentation of the NCA Talent Connector.

Check out the GitHub account of Never Code Alone.

And here I publish web development tutorial videos twice a week.

After the intro it goes straight to the matrix.

And so we are here directly on the GitHub page, where a very good employer has introduced himself and Benjamin has definitely noted here that it is better to be nice, please also on the last slide should be written differently.

We had the topic of onboarding, a great process.

Definitely watch the video if you want to start very well with a good employer.

Then we had the topics values ​​and goals and here at the end we have fresher, it's nice to stand and he definitely wanted to change that and if we go back to the job offers here I am not so quite sure if I copied it so wrong.

Mea culpa, that's really stupid, but I like to copy that from here, go here directly to my terminal in my project, yes, I implemented the project and then made a corresponding git init and here also this initial branch main configured that is definitely something that should be done, please do that too I have a few more master branches fly around but always rename around and have here accordingly under sources the corresponding html presentation HTML presentation and when I jump to the end with capital G, I basically get directly to the right place.

I can now here also move accordingly forward, say I want to make a DW and that with the dot command repeat twice and now here a dw

and repeat that twice with the dot command and now insert

the text here now he got a big F I don't know exactly where it comes from, but I'll write it for today definitely save it

I like to do that here with the Pugitive plugin.

I also published a video about this here.

Now I can switch to English here, so I know where my equal sign is.

Look what I did exactly, what changes happened here.

Can the with S stage and with cc write a commit.

Can here normal in Wim with I in insert mode go and then say fix company name in say fix company name in russia and here is also the advantage that here practically in the auto completion that is loaded what is in the context here you can see that here that I can do that accordingly and then I can go here and say I have done that and with escape go out again can double point wqr all write and that just stop on everything refer that means I come wqr all write quit and that just refer to everything that means I come directly back in my terminal can run an npm run build here but I can also say build and then go up because it is the last command that I have called up here I work here with oh my ZSH and if you want to learn something about how to deal with such tools, please contact me we can definitely do something for your teams remotely and just shoot off an hour of passion yes that is definitely something that brings me personally and I totally enjoy the work when I do that now then this image is displayed accordingly and here there is an individual CSS that is processed accordingly, but of course also the corresponding presentation here is an image and the files were now generated accordingly here I can also take a quick look at what is currently happening here and here we see that the changes were made accordingly in the index file and they are now minified, so it's not quite as good to read, but we know what happened and if we want to say hey that's not an additional commit now, which would also be an additional contribution at this point, which I personally don't think is so bad.

But the topic of commit amendments, you can tell me what you think of it, because I generally find it quite good as a developer in teams if my history is understandable, I can also save in-between steps and if I now, for example, go to the weekend and don't come back on Monday because I'm sick or something else, someone can of course take over my work a little easier and I believe that if you run a merge, a squash commit is executed, as it happens on github.

I would work like that, but I now also know some teams that always amend their own commits and for me it was very difficult to get used to it.

But in this case I would say that this definitely belongs to the commit and then it's okay if you do it that way.

In this case I can simply stage this newly generated file additionally and can say, so on the 1 hand I could say I'm doing commitment where I adjust the corresponding message again because I want to provide information about it or I make a CE, so commit end and no adjustment is made and that is practically added directly today I do a ca because I want to add additional information here that I do with without new lines on and say here with minus that I am here accordingly edit.html

I would also make points here and not at the top.

Rebuild docs folder These are the 2 things I did and I would say here I can make a big c here that is a correction until the end that it is now so and have that accordingly now amended here and when I say now I save that again everything wqr then I am here accordingly out and see on tick that I only have 1 commit here and that contains the information accordingly and you can see that here 2 files have been changed.

I have to somehow put a little more contrast in here.

It's hard to read on YouTube and not optimal for me to read.

But when I've done all this, I can push it accordingly.

accordingly directly to the github and I think that it is already updated now it is not yet We have to see how this deployment process works here.

Because the commit has definitely arrived.

That's not so nice, of course, I would have thought that this would work right here.

Under actions, it definitely says exactly what should basically happen.

I don't know if I have to manually empty caches, but there are no caches in here.

Can you use docs for GitHub pages, fix company name, I don't know if I have to do it again here Or that you can do it at all.

Who of you knows you with GitHub Actions and wants to imagine it here on YouTube.

That is of course something we need somehow.

don't see any indication that I would have to update something here again.

Well, I can live with it, if you know it.

Otherwise, the first time you are a bit shocked and I would like to always show you what's going on so on and with that we have definitely made the changes Question to you, what do you think of GitHub Hosting, GitHub Action and how far do you use GitHub directly?

There are often times that you use bitbucket or github in the sas version for your corresponding deployment pipelines i.e.

The cloud service directly and that doesn't host it myself, I personally host github locally and didn't want to do this manual flow that somewhere such a static page with a pull somewhere That was definitely too stupid for me now and I would also like to know about GitHub and GitHub Actions.

I will soon also install a corresponding code analysis and here always further deepen the knowledge and at least make it available

So your opinion is asked and otherwise again the note please follow the channel here, turn on the bell, here is another video that is definitely is meaningful And then again the Tailwind playlist here and the channel link.


Speaker 0: Hello friends of software entertainment and welcome to Never Code Alone. You want to know how to update a webpack project and publish it to GitHub pages. I do the whole thing here on an example of Reveal.js for our current presentation of the NCA Talent Connector. All the things we do are open source. Check out the GitHub account of Never Code Alone.

And here I publish web development tutorial videos twice a week. So please follow and turn on the bell. After the intro it goes straight to the matrix. And so we are here directly on the GitHub page, where a very good employer has introduced himself and Benjamin has definitely noted here that it is better to be nice, please also on the last slide should be written differently. We had the topic of onboarding, a great process.

Definitely watch the video if you want to start very well with a good employer. Then we had the topics values ​​and goals and here at the end we have fresher, it's nice to stand and he definitely wanted to change that and if we go back to the job offers here I am not so quite sure if I copied it so wrong. Yes, I did it wrong. Mea culpa, that's really stupid, but I like to copy that from here, go here directly to my terminal in my project, yes, I implemented the project and then made a corresponding git init and here also this initial branch main configured that is definitely something that should be done, please do that too I have a few more master branches fly around but always rename around and have here accordingly under sources the corresponding html presentation HTML presentation and when I jump to the end with capital G, I basically get directly to the right place. I can now here also move accordingly forward, say I want to make a DW and that with the dot command repeat twice and now here a dw

Speaker 1: and repeat that twice with the dot command and now insert

Speaker 0: the text here now he got a big F I don't know exactly where it comes from, but I'll write it for today definitely save it

Speaker 1: small

Speaker 0: Or I can also commit it directly. I like to do that here with the Pugitive plugin. I also published a video about this here. Now I can switch to English here, so I know where my equal sign is. Look what I did exactly, what changes happened here.

Can the with S stage and with cc write a commit. Can here normal in Wim with I in insert mode go and then say fix company name in say fix company name in russia and here is also the advantage that here practically in the auto completion that is loaded what is in the context here you can see that here that I can do that accordingly and then I can go here and say I have done that and with escape go out again can double point wqr all write and that just stop on everything refer that means I come wqr all write quit and that just refer to everything that means I come directly back in my terminal can run an npm run build here but I can also say build and then go up because it is the last command that I have called up here I work here with oh my ZSH and if you want to learn something about how to deal with such tools, please contact me we can definitely do something for your teams remotely and just shoot off an hour of passion yes that is definitely something that brings me personally and I totally enjoy the work when I do that now then this image is displayed accordingly and here there is an individual CSS that is processed accordingly, but of course also the corresponding presentation here is an image and the files were now generated accordingly here I can also take a quick look at what is currently happening here and here we see that the changes were made accordingly in the index file and they are now minified, so it's not quite as good to read, but we know what happened and if we want to say hey that's not an additional commit now, which would also be an additional contribution at this point, which I personally don't think is so bad.

But the topic of commit amendments, you can tell me what you think of it, because I generally find it quite good as a developer in teams if my history is understandable, I can also save in-between steps and if I now, for example, go to the weekend and don't come back on Monday because I'm sick or something else, someone can of course take over my work a little easier and I believe that if you run a merge, a squash commit is executed, as it happens on github. I would work like that, but I now also know some teams that always amend their own commits and for me it was very difficult to get used to it. But in this case I would say that this definitely belongs to the commit and then it's okay if you do it that way. In this case I can simply stage this newly generated file additionally and can say, so on the 1 hand I could say I'm doing commitment where I adjust the corresponding message again because I want to provide information about it or I make a CE, so commit end and no adjustment is made and that is practically added directly today I do a ca because I want to add additional information here that I do with without new lines on and say here with minus that I am here accordingly edit.html

Speaker 1: I

Speaker 0: have to adjust that again at the top. I would also make points here and not at the top. Rebuild docs folder These are the 2 things I did and I would say here I can make a big c here that is a correction until the end that it is now so and have that accordingly now amended here and when I say now I save that again everything wqr then I am here accordingly out and see on tick that I only have 1 commit here and that contains the information accordingly and you can see that here 2 files have been changed. I have to somehow put a little more contrast in here. It's hard to read on YouTube and not optimal for me to read.

But when I've done all this, I can push it accordingly. That goes directly

Speaker 1: to GitHub. Push that goes then just stop

Speaker 0: accordingly directly to the github and I think that it is already updated now it is not yet We have to see how this deployment process works here. Because the commit has definitely arrived. Hard reload. That has not yet been updated. That's not so nice, of course, I would have thought that this would work right here.

I'll find out what it's all about. I clicked a little bit here. Under actions, it definitely says exactly what should basically happen. There are still caches here. I don't know if I have to manually empty caches, but there are no caches in here.

Deployments that have happened. Can you use docs for GitHub pages, fix company name, I don't know if I have to do it again here Or that you can do it at all. Who of you knows you with GitHub Actions and wants to imagine it here on YouTube. That is of course something we need somehow.

Speaker 1: I

Speaker 0: don't see any indication that I would have to update something here again. I'll reload here again. And now it works. So it's a slight time delay. Well, I can live with it, if you know it.

Otherwise, the first time you are a bit shocked and I would like to always show you what's going on so on and with that we have definitely made the changes Question to you, what do you think of GitHub Hosting, GitHub Action and how far do you use GitHub directly? There are often times that you use bitbucket or github in the sas version for your corresponding deployment pipelines i.e. The cloud service directly and that doesn't host it myself, I personally host github locally and didn't want to do this manual flow that somewhere such a static page with a pull somewhere That was definitely too stupid for me now and I would also like to know about GitHub and GitHub Actions. I will soon also install a corresponding code analysis and here always further deepen the knowledge and at least make it available

Speaker 1: to you

Speaker 0: here. So your opinion is asked and otherwise again the note please follow the channel here, turn on the bell, here is another video that is definitely is meaningful And then again the Tailwind playlist here and the channel link. Until then. Bye.

Speaker 1: You

See all Never Code Alone transcripts on Youtube

Publishing GitHub Pages mit einem Update für Webpack Files