#ssg — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ssg, aggregated by home.social.
-
Folks, I've done it again. I've created a new static-site generator. Actually an #SSG starter that I extracted from my website's SSG so that I can use it to build new blogs for my other projects without being bogged down with the details specific to my website. If any of you fancy writing your own SSG in #Haskell, give it a go: https://abhin4v.github.io/shake-blog
Shake Blog is meant to be forked and extended. It comes with a basic set of features: posts, pages, tags, archive and feed, which may be enough for you. But the main idea is to understand it and extend it for your website according to your requirements and taste.
It uses #Shake, #Pandoc and #Mustache beneath, and comes with dark mode and code highlighting support. It includes a Github Action to build and publish your blog directly on Github pages with zero friction.
Try it out and let me know. Boost to make me famous.
-
Folks, I've done it again. I've created a new static-site generator. Actually an #SSG starter that I extracted from my website's SSG so that I can use it to build new blogs for my other projects without being bogged down with the details specific to my website. If any of you fancy writing your own SSG in #Haskell, give it a go: https://abhin4v.github.io/shake-blog
Shake Blog is meant to be forked and extended. It comes with a basic set of features: posts, pages, tags, archive and feed, which may be enough for you. But the main idea is to understand it and extend it for your website according to your requirements and taste.
It uses #Shake, #Pandoc and #Mustache beneath, and comes with dark mode and code highlighting support. It includes a Github Action to build and publish your blog directly on Github pages with zero friction.
Try it out and let me know. Boost to make me famous.
-
Folks, I've done it again. I've created a new static-site generator. Actually an #SSG starter that I extracted from my website's SSG so that I can use it to build new blogs for my other projects without being bogged down with the details specific to my website. If any of you fancy writing your own SSG in #Haskell, give it a go: https://abhin4v.github.io/shake-blog
Shake Blog is meant to be forked and extended. It comes with a basic set of features: posts, pages, tags, archive and feed, which may be enough for you. But the main idea is to understand it and extend it for your website according to your requirements and taste.
It uses #Shake, #Pandoc and #Mustache beneath, and comes with dark mode and code highlighting support. It includes a Github Action to build and publish your blog directly on Github pages with zero friction.
Try it out and let me know. Boost to make me famous.
-
Folks, I've done it again. I've created a new static-site generator. Actually an #SSG starter that I extracted from my website's SSG so that I can use it to build new blogs for my other projects without being bogged down with the details specific to my website. If any of you fancy writing your own SSG in #Haskell, give it a go: https://abhin4v.github.io/shake-blog
Shake Blog is meant to be forked and extended. It comes with a basic set of features: posts, pages, tags, archive and feed, which may be enough for you. But the main idea is to understand it and extend it for your website according to your requirements and taste.
It uses #Shake, #Pandoc and #Mustache beneath, and comes with dark mode and code highlighting support. It includes a Github Action to build and publish your blog directly on Github pages with zero friction.
Try it out and let me know. Boost to make me famous.
-
Folks, I've done it again. I've created a new static-site generator. Actually an #SSG starter that I extracted from my website's SSG so that I can use it to build new blogs for my other projects without being bogged down with the details specific to my website. If any of you fancy writing your own SSG in #Haskell, give it a go: https://abhin4v.github.io/shake-blog
Shake Blog is meant to be forked and extended. It comes with a basic set of features: posts, pages, tags, archive and feed, which may be enough for you. But the main idea is to understand it and extend it for your website according to your requirements and taste.
It uses #Shake, #Pandoc and #Mustache beneath, and comes with dark mode and code highlighting support. It includes a Github Action to build and publish your blog directly on Github pages with zero friction.
Try it out and let me know. Boost to make me famous.
-
DriftNotes: A lightweight journaling engine for thoughts that drift between tweets and blogs.
-
DriftNotes: A lightweight journaling engine for thoughts that drift between tweets and blogs.
-
DriftNotes: A lightweight journaling engine for thoughts that drift between tweets and blogs.
-
DriftNotes: A lightweight journaling engine for thoughts that drift between tweets and blogs.
-
DriftNotes: A lightweight journaling engine for thoughts that drift between tweets and blogs.
-
The case for #SSG #CMS made from an AI standpoint:
> Authoring shouldn’t be typing into fields, it should be describing changes. “We renamed the Standard plan to Core — update every page that mentions it” is one instruction; the agent finds the mentions — including the ones in comparison tables and old announcements you forgot — and produces a single reviewable change across all of them.
This (well sourced) article is challenging, but I have a lot of time for it.
https://nooneshappy.com/article/how-ai-may-impact-cms-architecture/ -
The case for #SSG #CMS made from an AI standpoint:
> Authoring shouldn’t be typing into fields, it should be describing changes. “We renamed the Standard plan to Core — update every page that mentions it” is one instruction; the agent finds the mentions — including the ones in comparison tables and old announcements you forgot — and produces a single reviewable change across all of them.
This (well sourced) article is challenging, but I have a lot of time for it.
https://nooneshappy.com/article/how-ai-may-impact-cms-architecture/ -
The case for #SSG #CMS made from an AI standpoint:
> Authoring shouldn’t be typing into fields, it should be describing changes. “We renamed the Standard plan to Core — update every page that mentions it” is one instruction; the agent finds the mentions — including the ones in comparison tables and old announcements you forgot — and produces a single reviewable change across all of them.
This (well sourced) article is challenging, but I have a lot of time for it.
https://nooneshappy.com/article/how-ai-may-impact-cms-architecture/ -
The case for #SSG #CMS made from an AI standpoint:
> Authoring shouldn’t be typing into fields, it should be describing changes. “We renamed the Standard plan to Core — update every page that mentions it” is one instruction; the agent finds the mentions — including the ones in comparison tables and old announcements you forgot — and produces a single reviewable change across all of them.
This (well sourced) article is challenging, but I have a lot of time for it.
https://nooneshappy.com/article/how-ai-may-impact-cms-architecture/ -
The case for #SSG #CMS made from an AI standpoint:
> Authoring shouldn’t be typing into fields, it should be describing changes. “We renamed the Standard plan to Core — update every page that mentions it” is one instruction; the agent finds the mentions — including the ones in comparison tables and old announcements you forgot — and produces a single reviewable change across all of them.
This (well sourced) article is challenging, but I have a lot of time for it.
https://nooneshappy.com/article/how-ai-may-impact-cms-architecture/ -
Das ewige und immer weiter zunehmende #KatzUndMausSpiel bei in den letzten 20+ Jahren populären #CMS (#ContenManagementSystemen) aus Updaten und Patchen wegen #Sicherheitslücken, dann wieder höhere Versionen von #PHP und #mySQL / MariaDB bzw. #Postgres wegen Kompatibilität mit den Updates geht mir zunehmend auf den Sack.
Ich will deshalb perspektivisch meine #Joomla #Instanzen zu einer statischen #Webseite umbauen und dazu einen #SSG (#StaticSiteGenerator) nutzen. Eigentlich habe ich mich auch schon für #Hugo entschieden.
Die Daten der kleinsten Webseite habe ich auch bereits mit https://github.com/davetcc/hugojoomla aus der #Datenbank extrahiert.
Nun brauche ich noch ein schickes #Template. Ja, kann man selber bauen. Da würde ich aber durchaus wie schon bei Joomla ein paar Euro dafür in die Hand nehmen.
Da Hugo für mich absolutes Neuland ist, ist die Frage nach einem guten Anbieter für Hugo Templates - idealerweise einer, der auch mit dem Template kompatible Erweiterugen wie (falls das alles überhaupt mit einer statischen Seite möglich ist) #Slider, #Bildergalerie, #Akkordeon, #Kontaktformular, #FontAwesome, #Downloadverwaltung, #Kalender mit #Buchungssystem anbietet und - noch idealer, für gekaufte Produkte auch guten Support / Hilfestellung anbietet.
Zwar bin ich natürlich des Englischen mächtig, doch manches lässt sich in der Muttersprache einfacher klären, das i-Tüpfelchen wäre also deutschsprachiger Support.
Falls also jemand Erfahrungen, Kontakte, Ideen hat, die mir weiter helfen, immer her damit.
Bitte #Boost für mehr Reichweite. -
Das ewige und immer weiter zunehmende #KatzUndMausSpiel bei in den letzten 20+ Jahren populären #CMS (#ContenManagementSystemen) aus Updaten und Patchen wegen #Sicherheitslücken, dann wieder höhere Versionen von #PHP und #mySQL / MariaDB bzw. #Postgres wegen Kompatibilität mit den Updates geht mir zunehmend auf den Sack.
Ich will deshalb perspektivisch meine #Joomla #Instanzen zu einer statischen #Webseite umbauen und dazu einen #SSG (#StaticSiteGenerator) nutzen. Eigentlich habe ich mich auch schon für #Hugo entschieden.
Die Daten der kleinsten Webseite habe ich auch bereits mit https://github.com/davetcc/hugojoomla aus der #Datenbank extrahiert.
Nun brauche ich noch ein schickes #Template. Ja, kann man selber bauen. Da würde ich aber durchaus wie schon bei Joomla ein paar Euro dafür in die Hand nehmen.
Da Hugo für mich absolutes Neuland ist, ist die Frage nach einem guten Anbieter für Hugo Templates - idealerweise einer, der auch mit dem Template kompatible Erweiterugen wie (falls das alles überhaupt mit einer statischen Seite möglich ist) #Slider, #Bildergalerie, #Akkordeon, #Kontaktformular, #FontAwesome, #Downloadverwaltung, #Kalender mit #Buchungssystem anbietet und - noch idealer, für gekaufte Produkte auch guten Support / Hilfestellung anbietet.
Zwar bin ich natürlich des Englischen mächtig, doch manches lässt sich in der Muttersprache einfacher klären, das i-Tüpfelchen wäre also deutschsprachiger Support.
Falls also jemand Erfahrungen, Kontakte, Ideen hat, die mir weiter helfen, immer her damit.
Bitte #Boost für mehr Reichweite. -
Das ewige und immer weiter zunehmende #KatzUndMausSpiel bei in den letzten 20+ Jahren populären #CMS (#ContenManagementSystemen) aus Updaten und Patchen wegen #Sicherheitslücken, dann wieder höhere Versionen von #PHP und #mySQL / MariaDB bzw. #Postgres wegen Kompatibilität mit den Updates geht mir zunehmend auf den Sack.
Ich will deshalb perspektivisch meine #Joomla #Instanzen zu einer statischen #Webseite umbauen und dazu einen #SSG (#StaticSiteGenerator) nutzen. Eigentlich habe ich mich auch schon für #Hugo entschieden.
Die Daten der kleinsten Webseite habe ich auch bereits mit https://github.com/davetcc/hugojoomla aus der #Datenbank extrahiert.
Nun brauche ich noch ein schickes #Template. Ja, kann man selber bauen. Da würde ich aber durchaus wie schon bei Joomla ein paar Euro dafür in die Hand nehmen.
Da Hugo für mich absolutes Neuland ist, ist die Frage nach einem guten Anbieter für Hugo Templates - idealerweise einer, der auch mit dem Template kompatible Erweiterugen wie (falls das alles überhaupt mit einer statischen Seite möglich ist) #Slider, #Bildergalerie, #Akkordeon, #Kontaktformular, #FontAwesome, #Downloadverwaltung, #Kalender mit #Buchungssystem anbietet und - noch idealer, für gekaufte Produkte auch guten Support / Hilfestellung anbietet.
Zwar bin ich natürlich des Englischen mächtig, doch manches lässt sich in der Muttersprache einfacher klären, das i-Tüpfelchen wäre also deutschsprachiger Support.
Falls also jemand Erfahrungen, Kontakte, Ideen hat, die mir weiter helfen, immer her damit.
Bitte #Boost für mehr Reichweite. -
Das ewige und immer weiter zunehmende #KatzUndMausSpiel bei in den letzten 20+ Jahren populären #CMS (#ContenManagementSystemen) aus Updaten und Patchen wegen #Sicherheitslücken, dann wieder höhere Versionen von #PHP und #mySQL / MariaDB bzw. #Postgres wegen Kompatibilität mit den Updates geht mir zunehmend auf den Sack.
Ich will deshalb perspektivisch meine #Joomla #Instanzen zu einer statischen #Webseite umbauen und dazu einen #SSG (#StaticSiteGenerator) nutzen. Eigentlich habe ich mich auch schon für #Hugo entschieden.
Die Daten der kleinsten Webseite habe ich auch bereits mit https://github.com/davetcc/hugojoomla aus der #Datenbank extrahiert.
Nun brauche ich noch ein schickes #Template. Ja, kann man selber bauen. Da würde ich aber durchaus wie schon bei Joomla ein paar Euro dafür in die Hand nehmen.
Da Hugo für mich absolutes Neuland ist, ist die Frage nach einem guten Anbieter für Hugo Templates - idealerweise einer, der auch mit dem Template kompatible Erweiterugen wie (falls das alles überhaupt mit einer statischen Seite möglich ist) #Slider, #Bildergalerie, #Akkordeon, #Kontaktformular, #FontAwesome, #Downloadverwaltung, #Kalender mit #Buchungssystem anbietet und - noch idealer, für gekaufte Produkte auch guten Support / Hilfestellung anbietet.
Zwar bin ich natürlich des Englischen mächtig, doch manches lässt sich in der Muttersprache einfacher klären, das i-Tüpfelchen wäre also deutschsprachiger Support.
Falls also jemand Erfahrungen, Kontakte, Ideen hat, die mir weiter helfen, immer her damit.
Bitte #Boost für mehr Reichweite. -
#Development #Comparisons
Different hydration and rendering strategies · Benefits and tradeoffs of modern rendering approaches https://ilo.im/16e4ph_____
#Rendering #Hydration #JavaScript #SSG #Client #Server #React #TanStack #WebDev #Frontend -
#Development #Comparisons
Different hydration and rendering strategies · Benefits and tradeoffs of modern rendering approaches https://ilo.im/16e4ph_____
#Rendering #Hydration #JavaScript #SSG #Client #Server #React #TanStack #WebDev #Frontend -
#Development #Comparisons
Different hydration and rendering strategies · Benefits and tradeoffs of modern rendering approaches https://ilo.im/16e4ph_____
#Rendering #Hydration #JavaScript #SSG #Client #Server #React #TanStack #WebDev #Frontend -
#Development #Comparisons
Different hydration and rendering strategies · Benefits and tradeoffs of modern rendering approaches https://ilo.im/16e4ph_____
#Rendering #Hydration #JavaScript #SSG #Client #Server #React #TanStack #WebDev #Frontend -
#NotNews24 | #UnbreaklingDiabloIVWorldNotNews; #IT's #DefinitelyNotNews and #SomeWeather...
#IT's a #BitBlustery in #TheOutside; #MostlySunny...
#YouKnow what #PurpleThings #TasteLike...
#Purple... #IT's #NotEasy... #BeingGreen ♻️
#Something for the #RacistHomophobes at #SSG to have a #LittleThink about on "they/them's" #DeadGame on #NonEuropeanServer(s) while #TheGhostOfMisterDen's #VillageSkank pretends #ShitpostingAsAService is a #ViableBusinessModel / #LegitimateBusiness...
#PurpleThings #TasteOfPurple...
With #AllTheWinning... In #UltraHD / #4KFormat for #TheNext20Years; #OrSo...
With #TheRightStaff™️
🧙⚕️🤖:wolfparty:🤖⚕️🧙 | :fediverse:🦹:PirateBadge:🦄:PirateBadge:🦹:fediverse:
#EuropeanServer #BeingEuropean #StayingEuropean #EULaw #BeingLegal #ContainsTracesOfDementedVillageSkank
-
#BusyBusyBusy... #BusyBeingRetired...
[ #NotSuitable for #AngryIncels, #RacistHomophobes, #MiserableMorons or #CrazyStalkers]
#AlwaysReadTheLabel | #TermsAndConditionsApply
#Something for the #RacistHomophobes at #SSG to have a #LittleThink about on "they/them's" #DeadGame on #NonEuropeanServer(s) while #TheGhostOfMisterDen's #DeadInstance #CryAboutNothing to #NoOne...
#TotallySupported by #DolbyDigital; #Because...
#Still: #WorkingAsIntended... | #今すぐ
With #TheRightStaff™️
🧙🛫🤖:wolfparty:🤖🛬🧙 | ☕️️🦹🍩🦄🍩🦹☕️
#PoweredBy #FloofsAndSparkles #WindowsForWerewolves #SonyExclusives #TheInternetIsStillOn #DiscordIsForImbeciles #FancyHats #GroovyMerch #SoldSeparately #TooBusyForALTText #UltraHD #4KFormat #ContainsZeroPercentMastodonSocial #AsIntended
-
Forking the ssg generator I use has been one of the most fun decisions lately. The codebase is so nice to work on, letting me do small changes like image support for rss feeds
https://github.com/CactiChameleon9/gozer/commit/1718c6230ffe8b200baf1e0bd576b254653fd84e
-
Forking the ssg generator I use has been one of the most fun decisions lately. The codebase is so nice to work on, letting me do small changes like image support for rss feeds
https://github.com/CactiChameleon9/gozer/commit/1718c6230ffe8b200baf1e0bd576b254653fd84e
-
Forking the ssg generator I use has been one of the most fun decisions lately. The codebase is so nice to work on, letting me do small changes like image support for rss feeds
https://github.com/CactiChameleon9/gozer/commit/1718c6230ffe8b200baf1e0bd576b254653fd84e
-
Forking the ssg generator I use has been one of the most fun decisions lately. The codebase is so nice to work on, letting me do small changes like image support for rss feeds
https://github.com/CactiChameleon9/gozer/commit/1718c6230ffe8b200baf1e0bd576b254653fd84e
-
Forking the ssg generator I use has been one of the most fun decisions lately. The codebase is so nice to work on, letting me do small changes like image support for rss feeds
https://github.com/CactiChameleon9/gozer/commit/1718c6230ffe8b200baf1e0bd576b254653fd84e
-
For a variety of reasons, I'm considering moving my blog from Hugo to a different static site generator, and also (which I have been planning for longer), moving away from Netlify (to either https://www.statichost.eu or Bunny.net).
This is a big move as my blog has been running for nearly 24 years and building it involves building >1800 pages. I also want to preserve the site and URL structure to avoid too much breakage. Hugo is great, but it moves too fast and is really more complex than I need.
I've shortlisted Zola, 11ty, and I'll maybe look at Zine too which is very interesting but in Beta (https://zine-ssg.io).
Reading the docs for Zola and 11ty, I think the former would be faster and much more familiar for me coming from Hugo, but 11ty would be much more flexible and indieweb-friendly. However, it's Javascript and for some reason I have never got on with Javascript. It would also mean maintaining dependencies which I would prefer to avoid (one of the reasons I originally moved to Hugo).
Anyone using any of the SSGs mentioned, or the hosts and have any advice? Or have I missed a cool SSG that would fit my brief?
Thank you!
-
For a variety of reasons, I'm considering moving my blog from Hugo to a different static site generator, and also (which I have been planning for longer), moving away from Netlify (to either https://www.statichost.eu or Bunny.net).
This is a big move as my blog has been running for nearly 24 years and building it involves building >1800 pages. I also want to preserve the site and URL structure to avoid too much breakage. Hugo is great, but it moves too fast and is really more complex than I need.
I've shortlisted Zola, 11ty, and I'll maybe look at Zine too which is very interesting but in Beta (https://zine-ssg.io).
Reading the docs for Zola and 11ty, I think the former would be faster and much more familiar for me coming from Hugo, but 11ty would be much more flexible and indieweb-friendly. However, it's Javascript and for some reason I have never got on with Javascript. It would also mean maintaining dependencies which I would prefer to avoid (one of the reasons I originally moved to Hugo).
Anyone using any of the SSGs mentioned, or the hosts and have any advice? Or have I missed a cool SSG that would fit my brief?
Thank you!
-
For a variety of reasons, I'm considering moving my blog from Hugo to a different static site generator, and also (which I have been planning for longer), moving away from Netlify (to either https://www.statichost.eu or Bunny.net).
This is a big move as my blog has been running for nearly 24 years and building it involves building >1800 pages. I also want to preserve the site and URL structure to avoid too much breakage. Hugo is great, but it moves too fast and is really more complex than I need.
I've shortlisted Zola, 11ty, and I'll maybe look at Zine too which is very interesting but in Beta (https://zine-ssg.io).
Reading the docs for Zola and 11ty, I think the former would be faster and much more familiar for me coming from Hugo, but 11ty would be much more flexible and indieweb-friendly. However, it's Javascript and for some reason I have never got on with Javascript. It would also mean maintaining dependencies which I would prefer to avoid (one of the reasons I originally moved to Hugo).
Anyone using any of the SSGs mentioned, or the hosts and have any advice? Or have I missed a cool SSG that would fit my brief?
Thank you!
-
For a variety of reasons, I'm considering moving my blog from Hugo to a different static site generator, and also (which I have been planning for longer), moving away from Netlify (to either https://www.statichost.eu or Bunny.net).
This is a big move as my blog has been running for nearly 24 years and building it involves building >1800 pages. I also want to preserve the site and URL structure to avoid too much breakage. Hugo is great, but it moves too fast and is really more complex than I need.
I've shortlisted Zola, 11ty, and I'll maybe look at Zine too which is very interesting but in Beta (https://zine-ssg.io).
Reading the docs for Zola and 11ty, I think the former would be faster and much more familiar for me coming from Hugo, but 11ty would be much more flexible and indieweb-friendly. However, it's Javascript and for some reason I have never got on with Javascript. It would also mean maintaining dependencies which I would prefer to avoid (one of the reasons I originally moved to Hugo).
Anyone using any of the SSGs mentioned, or the hosts and have any advice? Or have I missed a cool SSG that would fit my brief?
Thank you!
-
For a variety of reasons, I'm considering moving my blog from Hugo to a different static site generator, and also (which I have been planning for longer), moving away from Netlify (to either https://www.statichost.eu or Bunny.net).
This is a big move as my blog has been running for nearly 24 years and building it involves building >1800 pages. I also want to preserve the site and URL structure to avoid too much breakage. Hugo is great, but it moves too fast and is really more complex than I need.
I've shortlisted Zola, 11ty, and I'll maybe look at Zine too which is very interesting but in Beta (https://zine-ssg.io).
Reading the docs for Zola and 11ty, I think the former would be faster and much more familiar for me coming from Hugo, but 11ty would be much more flexible and indieweb-friendly. However, it's Javascript and for some reason I have never got on with Javascript. It would also mean maintaining dependencies which I would prefer to avoid (one of the reasons I originally moved to Hugo).
Anyone using any of the SSGs mentioned, or the hosts and have any advice? Or have I missed a cool SSG that would fit my brief?
Thank you!
-
Korea Investment Cuts E-mart Target 15% on Starbucks Losses
Emart CI. Emart E-mart’s earnings are expected to fall short of market expectations due to sluggish Starbucks sales…
#EuropeSays #Korea #KR #Seoul #E-Mart #Homeplus #KoreaInvestment&Securities #Korearetail #SCKCompany #SSG.com #Starbucks #targetpricecut
https://www.europesays.com/korea/80879/ -
Oh and there's one more thing. One of the reasons I build my own #SSG for HyperTexting is because I wanted to be able to generate "incremental builds". In other words, only generate the files needed for a new post. For an "unlisted" post that doesn't appear in any RSS feed that could be a single HTML file. For a post that appears in one or more RSS feeds and the home page, the #SSG should be able to figure that out.
Here's the build & deployment HT performed for the first video in this thread.
-
Oh and there's one more thing. One of the reasons I build my own #SSG for HyperTexting is because I wanted to be able to generate "incremental builds". In other words, only generate the files needed for a new post. For an "unlisted" post that doesn't appear in any RSS feed that could be a single HTML file. For a post that appears in one or more RSS feeds and the home page, the #SSG should be able to figure that out.
Here's the build & deployment HT performed for the first video in this thread.
-
Oh and there's one more thing. One of the reasons I build my own #SSG for HyperTexting is because I wanted to be able to generate "incremental builds". In other words, only generate the files needed for a new post. For an "unlisted" post that doesn't appear in any RSS feed that could be a single HTML file. For a post that appears in one or more RSS feeds and the home page, the #SSG should be able to figure that out.
Here's the build & deployment HT performed for the first video in this thread.
-
Oh and there's one more thing. One of the reasons I build my own #SSG for HyperTexting is because I wanted to be able to generate "incremental builds". In other words, only generate the files needed for a new post. For an "unlisted" post that doesn't appear in any RSS feed that could be a single HTML file. For a post that appears in one or more RSS feeds and the home page, the #SSG should be able to figure that out.
Here's the build & deployment HT performed for the first video in this thread.
-
Oh and there's one more thing. One of the reasons I build my own #SSG for HyperTexting is because I wanted to be able to generate "incremental builds". In other words, only generate the files needed for a new post. For an "unlisted" post that doesn't appear in any RSS feed that could be a single HTML file. For a post that appears in one or more RSS feeds and the home page, the #SSG should be able to figure that out.
Here's the build & deployment HT performed for the first video in this thread.
-
I've started to expose some of the underlying #SSG functionality in HyperTexting for power users. For example, if you have a HyperTexting profile setup for a HyperTemplates website, you can access a "Builds" menu from the #CMS settings and generate a full-site build. Builds are not quite as fast on an iPhone 16 vs a Mac, but still respectable! In this example I performed a full-site build of a website with 86 pages + 42 asset files + 15 feed files in 379ms. That's under 3ms per file generated. ⚡️
-
I've started to expose some of the underlying #SSG functionality in HyperTexting for power users. For example, if you have a HyperTexting profile setup for a HyperTemplates website, you can access a "Builds" menu from the #CMS settings and generate a full-site build. Builds are not quite as fast on an iPhone 16 vs a Mac, but still respectable! In this example I performed a full-site build of a website with 86 pages + 42 asset files + 15 feed files in 379ms. That's under 3ms per file generated. ⚡️
-
I've started to expose some of the underlying #SSG functionality in HyperTexting for power users. For example, if you have a HyperTexting profile setup for a HyperTemplates website, you can access a "Builds" menu from the #CMS settings and generate a full-site build. Builds are not quite as fast on an iPhone 16 vs a Mac, but still respectable! In this example I performed a full-site build of a website with 86 pages + 42 asset files + 15 feed files in 379ms. That's under 3ms per file generated. ⚡️
-
I've started to expose some of the underlying #SSG functionality in HyperTexting for power users. For example, if you have a HyperTexting profile setup for a HyperTemplates website, you can access a "Builds" menu from the #CMS settings and generate a full-site build. Builds are not quite as fast on an iPhone 16 vs a Mac, but still respectable! In this example I performed a full-site build of a website with 86 pages + 42 asset files + 15 feed files in 379ms. That's under 3ms per file generated. ⚡️
