norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.4K
active users

#githubpages

1 post1 participant0 posts today

With the help of AI, I have set up my personal blog using GitHub Pages.
yongzs1218.github.io
Welcome to visit. You are also welcome to subscribe via RSS to get the latest posts: yongzs1218.github.io/feed.xml

在AI的幫助下,我用GitHub Pages架設了個人網誌(部落格),歡迎諸位瀏覽。
yongzs1218.github.io
也歡迎諸位通過RSS訂閱,獲取最新貼文:yongzs1218.github.io/feed.xml

Mit Hilfe von KI habe ich meinen persönlichen Blog mit GitHub Pages eingerichtet. Herzlich willkommen zum Stöbern.
yongzs1218.github.io
Sie sind auch herzlich eingeladen, über RSS zu abonnieren, um die neuesten Beiträge zu erhalten: yongzs1218.github.io/feed.xml

AIの助けを借りて、GitHub Pagesを使って個人のブログを立ち上げました。ぜひご覧ください。
yongzs1218.github.io
また、RSSを通じて購読して最新の投稿を入手することも歓迎します:yongzs1218.github.io/feed.xml

Với sự trợ giúp của AI, tôi đã thiết lập blog cá nhân của mình bằng GitHub Pages. Chào mừng các bạn ghé thăm.
yongzs1218.github.io
Các bạn cũng được chào đón để đăng ký qua RSS để nhận các bài viết mới nhất: yongzs1218.github.io/feed.xml

С помощью ИИ я создал свой личный блог с использованием GitHub Pages. Приглашаю вас посетить его.
yongzs1218.github.io
Также вы можете подписаться через RSS, чтобы получать последние записи: yongzs1218.github.io/feed.xml

AI ཡི་རོགས་རམ་གྱིས་ GitHub Pages བེད་སྤྱོད་ནས་རང་གི་རྩོམ་ཡིག་གསར་པ་བཟོས་པ་ཡིན། ཁྱེད་ཚོས་ལྟ་སྤྱོད་གནང་བར་དགའ་བསུ་ཞུ།
yongzs1218.github.io
ཡང་ན RSS ཡིས་བསྟར་ཞུས་ནས་གསར་པའི་རྩོམ་ཡིག་ཐོབ་པར་དགའ་བསུ་ཞུ། yongzs1218.github.io/feed.xml

YongZS永值生’s Personal WeblogHome主頁Music production enthusiast, travelling & photography lover, I’ll post my daily life here. 音樂製作愛好者,旅行與攝影愛好者,我會將我的日常生活發布至此。

I'm having one of those mornings where I really want to scrap my entire site and re-write it completely. Hypothetically, if I somehow had so much free time that I could do this, who's got suggestions for what static site generator I should go with, and where I should host said site? Right now I use #jekyll and #githubpages, both with limitations I don't much like so would be looking to try something new.

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
E.g. https://indieweb.org/werd.io
https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

tantek.com⚠️ .io domain^1 likely being phased-out^2 — seven suggested steps Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you: * https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did^3), so here are my suggested steps to take depending on your usage of .io domains: 1. Avoid buying new .io domains (or making plans with existing ones; sell if you can) 2. If you currently run a .io service^4 (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects) 3. If you have a personal site on a .io domain^5 or subdomain, make your own transition plan, and perhaps post about how others should link to your posts 4. If you are using someone else’s .io domain to publish (like #GitHubPages^6), make a transition plan to publish elsewhere and leave a forwarding note and link behind 5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain 6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5 7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive) And of course, post about your #dotIO plans. Glossary Domain https://indieweb.org/domain IndieAuth https://indieweb.org/IndieAuth Internet Archive https://web.archive.org/ OpenID https://indieweb.org/OpenID Redirect https://indieweb.org/redirect RelMeAuth https://indieweb.org/RelMeAuth Web sign-in https://indieweb.org/Web_sign-in References: ^1 https://indieweb.org/.io ^2 https://en.wikipedia.org/wiki/.io#Phasing_Out ^3 https://en.wikipedia.org/wiki/.cs ^4 E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io ^5 E.g. https://indieweb.org/werd.io ^6 https://indieweb.org/github.io This is post 25 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful → https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug - Tantek

Yesterday, I started to look into the steps needed to replace my #WordPress based blog with something more lightweight. Of course, I found #GithubPages. After preparing my #Mac for #Jekyll, I played a bit around with it. Today, I started to get serious (as you can see in the screenshot). I am already in the phase of fine-tuning the blog posts locally. After that, I will commit my posts for the first time. Already curious about the #build duration of my 200+ posts. #devlife

Replied in thread

@Ariri unless you want custom-engineer your own #Markdown -> #LaTeX -> #Ghostscript pipeline like @fuchsiii did, consider #MkDocs as an easy solution to turn Markdown files into sleek #documentation with minimal configuration needed.

That should provide you with an easy way to present stuff in an intuitive way...

I myself can't he assed writing #HTML5 / #CSS3 / #JS6 or wahtever #cursed #WebApp #TechStack is trendy tthese days so I use #MkDocs all the time...

www.mkdocs.orgMkDocsProject documentation with Markdown.

@drewdevault Using #Discord for any serious communication should disqalify the projects and those using it from being taken serious in #FLOSS development at all.

At least with #Mailinglists and #IRC we had the latter problem solved, and whilst a lot of people criticize #GitHub for all the valid reasons, one does not need to have a GitHub account to merely read issues and access documentation published there.

Not to mention Discord has a shitload ob absurd and archaic limitations that have no reason to exist, so even if one were okay with using that garbage #SaaS they'd inevitably run into the limit of "#Servers" [or rather #Instances] they can actually access at the same time VERY QUICKLY...