static-tweet VS pages-gem

One example I like is this Static Tweet Demo by Vercel. Tweets are dynamic - the number of people commenting/liking/retweeting is constantly changing. But do you always need to show the latest numbers or can you live with slightly stale data?

There is also this alternative solution if you are using react/next

https://static-tweet.vercel.app/

I was writing a blog where I have to curate some tweets. Twitter's embed made the webpage sluggish so I researched a bit and came across this library (ifades' Static Tweet). Currently, the package for this library doesn't exist but has been used by the author for demos. I would like to use this library. If anyone could just show me the way or guide me through as to how can I use this. That'd be amazing.

That sounds a great side project, since some developers might prefer a static svg dynamically created via url like boringavatar.app/[username here].

There's some prior work on this: e.g. https://github.com/lfades/static-tweet and https://github.com/vercel/og-image.

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.