Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update README.#43

Merged
tesar-tech merged 1 commit into
BlazorStatic:masterfrom
patricktcoakley:master
Oct 25, 2024
Merged

Update README.#43
tesar-tech merged 1 commit into
BlazorStatic:masterfrom
patricktcoakley:master

Conversation

@patricktcoakley

Copy link
Copy Markdown
Contributor

#42

Only an owner can change the GitHub repo description, which still says:

Embrace the capabilities of Blazor on .NET 8 to craft static websites.

I did a few minor edits to the README, let me know if you want to change anything but it was mostly just small things.

@netlify

netlify Bot commented Oct 23, 2024

Copy link
Copy Markdown

Deploy Preview for blazorstatic ready!

Name Link
🔨 Latest commit a0b52e6
🔍 Latest deploy log https://app.netlify.com/sites/blazorstatic/deploys/671b90f6ff7884000892d6bd
😎 Deploy Preview https://deploy-preview-43--blazorstatic.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@tesar-tech tesar-tech left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few issue. I am just trying to make it shorter and more condense. But I admit it's rather my personal preference and I am not native English speaker, so I might be wrong on some places.

Comment thread README.md
Comment thread README.md Outdated
> The site for BlazorStatic is a feature-rich example of the library. Check the [source code](https://github.com/tesar-tech/BlazorStatic/tree/master/BlazorStaticWebsite).

Upon running your app, **BlazorStatic** fetches the pages' HTML with `HttpClient`, outputs HTML files and assets to the `output` folder, which you can deploy to any static hosting service.
Upon running your app, **BlazorStatic** fetches the pages' HTML with `HttpClient`, outputs HTML files and assets to the `output` folder, and from there you can deploy to any standard HTTP server or static site hosting service.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about: "to any server or hosting"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's nice to make it clear that it's just a bundle of files that an HTTP server could host, but I don't really have a strong opinion either way.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for me it's hard to figure out what "standart HTTP server" means. It is probably technically correct, but doesn't imply the solution is easy..

Upon running your app, **BlazorStatic** fetches the pages' HTML with `HttpClient`, outputs HTML files and assets to the `output` folder, ready to be [deployed almost anywhere](https://tesar-tech.github.io/BlazorStatic/docs/deployment), often for free.

@patricktcoakley patricktcoakley Oct 25, 2024

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any HTTP server (nginx, caddy, Apache) can host your files. You are not limited to a hosting service, which is part of why SSG is so popular: it's simple. The current documentation implies that you need to "deploy" it somewhere particular, like the cloud, which is not the case - I could host my files locally at home, on a VPS, on a VM, or anywhere.

Comment thread README.md Outdated
Comment thread .DS_Store Outdated
@tesar-tech tesar-tech merged commit ccafd5e into BlazorStatic:master Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants