vscode-live-server VS Jekyll

I think your using the VSCode Live Server plugin. I would not use the Live Server plugin to run your app. The plugin does some magic to inject additional HTML into displayed page. Having SVG icons breaks it (not sure if you are using svg icons). I would run a basic app through a Python server by creating pyServer.py file:

Now open the html file using an HTTP server of your choice. I'm using the Live Server VS Code extension. You will see something like this.

More than likely.

This seems like a common issue with the vs code live server extension. You may want to switch to using npm live-server or try setting a proxy: https://github.com/ritwickdey/vscode-live-server/blob/master/docs/settings.md

I was using the VS code live server extension from here https://github.com/ritwickdey/vscode-live-server which exposes port 5500 on my localhost by default.

You need to use a server that establishes a root directory to /build (not fall back to the root of C:). I tried to get LiveServer (VS Code Extension) to function but it too needs the server root set to /build. Just found this which should solve that problem.

After downloading it, I will also recommend downloading an extension called Live Server in VsCode and it will help you to create a local server and view the changes made to the website without refreshing it each time & is super useful, Trust me!

To set the hostname to the desired IP address, use liveServer.settings.host (the default is 127.0.0.1).

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Jekyll

In future, if you want to move from Jekyll to something else, you just have to worry about that `_posts` and `_assets` folder. They may have different naming convention but you can just config-managed it or change it to your choice. This is why I suggested owning that two yourself.

You also may not worry about FrontMatter[3] (meta in the header) and its accompanying jazz by asking Jekyll to use the plugins `jekyll-optional-front-matter` and `jekyll-titles-from-headings`. These comes as part of the officially supported Jekyll plugins[4] by Github. That way, you are just writing a human-readable plain-text spiced up with Markdown and readable by almost every other Static Site Generator.

Now, play with the `_config.yml` that Jekyll generates for you from the theme above to define your post dates, navigation, and others. Jekyll is one of the OGs — the Gandalf of Static Site Generators. If you have a problem, someone somewhere has solved that.

Did I missed something? I was supposed to write a blog article for my website on this one and this comment will serve as my starting bullet points.

1. https://docs.github.com/en/pages/setting-up-a-github-pages-s...

2. https://jekyllrb.com

3. https://frontmatter.codes/docs/markdown

4. https://docs.github.com/en/pages/setting-up-a-github-pages-s...

"Using the Chirpy theme for Jekyll."

I would suggest looking into static site generators. Some popular examples, which are used myself are: - Hugo: https://gohugo.io/ - Jekyll: https://jekyllrb.com

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

I created my blog using Jekyll, a great open-source tool that can transform your markdown content into a simple, old-fashioned-but-trendy, static site. What are the advantages of this approach? The site is super-light, super-fast, super-secure and SEO-friendly. Of course, it’s not always the best solution, but for some use cases, like a simple personal blog, it’s really a good option.

Yes, it's Markdown and I use https://jekyllrb.com with the theme "jekyll-theme-hacker" to generate the site. I quite like how simple it is.