Things are getting serious with AnalogJS (Angular SSG) 

That was a great improvement, but Angular still doesn't have built-in markdown support. So you'd have to set all that up yourself (which isn't terribly difficult), but Analog has it out of the box

@@kylerjohnson988 Idk, switching to FRAMEWORK for just single feature seems to me little overkill

​@@kylerjohnson988 thay's true, but if you use something like Scully for doing the static files rendering and consume markdown files, you can still use most of the classic Angular stuff and is just adding an extra step to your build process without having to fall into learning a new framework on top of Angular, don't you? At least that's what I did recently for a project at work to build some static blog-like sites.

Not sure what you mean - as in you want me to cover those, or why not use those here? AnalogJS doesn't really stand in opposition to Angular features, it adds things on top (specifically things like file based routing/markdown support/server routes)

@@JoshuaMorony Kevin was showcasing it in live stream: ru-vid.comVf5Hz9pvUv4?si=MQKj8jYGxSYAXCcU and ru-vid.comkUlw-a_fEsc?si=DP8YHtygvtWN1qPR Also when first commented, my comment didn't show up, so commented twice. Sorry for that.

@@adrian333dev I also thought their new SSR and SSG feature was in opposition to analogJs, haven't checked it out though, could be wrong but I was under the impression they did the same thing!?

I tried it. It still sucks! It seemed to me that they just incorporate Angular Universal inside Angular.

Also if Angular keeps adding features, wouldn't Analog be unnecessary in near future?

There is a simplistic version of this already - if you are logged in there will be a banner at the top that has a "Continue" button that will take you to whatever lesson you last viewed, but I would also like to implement more thorough completion tracking

It's subjective, but to me local markdown files built into a static site that can be deployed as just HTML/CSS/JS strikes me as being simpler than needing to run a separate Node server/db to serve content to the frontend through an API

I haven't dealt with the SEO side yet but it should be the same as other SSG/SSR approaches, content is pre-rendered on the server or at build time so you get whatever SEO benefit that is going to provide

It's defining the content not the template - e.g. I might have 100 markdown files representing blog posts/lessons/whatever that defines the content for some component to display - markdown files essentially act as the database for content here

Markdown is simpler, more human-readable, and easier for basic formatting needs, while HTML offers greater control, complexity, and precision for creating web content with specific design, functionality, and interactivity. Often, Markdown can be converted into HTML to take advantage of both formats' strengths(from GPT). But as web developer which already know HTML I don't understand why I whould write content in MD which gives less control. It looks like there is a trend and if other frameworks can render MD why angular wouldn't. As a database I would rather use json files.

My life got so much easier once I started using Nx

@@JoshuaMorony 💙 that's nice to hear 😊

It does sound kind of funny but I don't see a problem with it - I have SSG sites and I used tools I think are good for SSG to build them. My course is not about building SSG/markdown sites with Angular

Great!

I'm not sure what type of content you expect to see, but this video isn't supposed to be a guide for beginners on how to build websites with Angular and I don't think I ever presented it that way. I introduce it as a specific problem I am facing and that the challenges/goals I am solving for are out of the ordinary for a typical blog website which is what makes it a particularly interesting challenge for Analog (specifically because I am doing some weird). The "why" of why I went with this particular architecture isn't on topic for the video, but perhaps could be interesting to explore - in brief though, it allows me to deploy a completely SSG site, I can manage all content locally with just markdown files, and paid content can be protected with no need for any kind of actual user registration/auth. Effectively I have the maintenance/deploy process of a simple static blog, but with power similar to that of a CMS with auth features. I don't really agree with the "this is not the way to do it" statement either - there are many "its" and many ways to do them, I'm willing to be convinced otherwise but this particular solution to this particular problem is a good way to do it.