Getting pretty darn close in spite of distraction. A few obvious things to note:

I'm focusing on loading pages via #Logseq HTTP API and processing those pages' contents. Not thinking much about style. Stuffing everything into the #Nanoc tutorial starter site for a moment.

I'm on the Linux machine now, and Logseq's reading of events is everything started with the timestamps of the files on disk rather than Git history. *(sigh)*

That number next to the title is Logseq's row ID for the page.

Meanwhile, figuring out how I can convert a Hugo shortcode to an ERB partial to a #Nanoc helper method.

Pretty funky at this point, but later I can put most of the logic into my helper method.

Between improvements to #Ruby and whatever @denis has been doing, #Nanoc is officially in my "fast enough" category. Four seconds on my machine for the first build of roughly 700 pages, .5s or less for rebuilds. About twice the speed of the Astro iteration. Yeah doing less/different than Astro but that's part of the appeal.

Anything less than ten seconds (on my machine) is fast enough. Hugo, Eleventy, Zola, Astro (barely), and now Nanoc.

Cool. I'll keep at it.

https://nanoc.app

@mudge Still pretty happy with nanoc for the one internal static site I maintain.

#nanoc https://nanoc.app/

Nanoc: a static-site generator written in Ruby » home

Struck this morning by an absolutely terrible idea for building a static(ish) site from my notes. Several terrible ideas wrapped into one, actually.

The sort of collection of terrible ideas that I'm relieved to see there's already a gem integrating #Nanoc with RSpec.

https://rubygems.org/gems/nanoc-spec

nanoc-spec | RubyGems.org | your community gem host

Hey wanna see a stupid #Nushell trick?

Making markdown sections and tables for the schema of a SQLite database (which I then paste into #TangentNotes to be published with #Nanoc)

```
(
open markdown.db
| schema
| get tables
| transpose name info
| each { |t| $"#### ($t.name)\n\n($t.info.columns | to md)\n" }
| to text
)
```

EDIT: removed a couple unnecessary steps in my pipe.

@0x1eef I know about #Jekyll, as that's the one #GitHub recommend, but what is #Nanoc like? That's one I haven't heard of before!

KEY STUDIOでは
アイドル楽曲
バンド楽曲
など

オリジナル楽曲制作
カバー楽曲制作
アレンジ制作
など各種制作依頼を
随時承っております。

(関わらせていただいているグループ)
SPADES
鎌田琥珀
17にしかできないこと
リュミエールONE+
Sub6classical
NanoC
BSJ PROJECT
応援⭐︎少女
などなど

事務所所属のグループでも
個人アイドルの方でも
お気軽にメッセージください。

KEY STUDIO
古橋 崇

#BSJPROJECT
#SPADES
#sub6classical
#鎌田琥珀
#nanoc
#楽曲提供
#楽曲提供します
#アイドル楽曲提供
#楽曲制作

Even though I love Nanoc, I continue my forced conversion to Python and am looking for something as nice and simple as Nanoc. Let's see! #static-site-generator #nanoc #blog #wordpress #python : "Static Site Generators"(https://www.fullstackpython.com/static-site-generator.html)
Static Site Generators

A static site generator combines a markup language with a templating engine to produce HTML files. Learn more on Full Stack Python.

Kennt sich jemand mit #nanoc aus? Meine Seite #githubpages wird nicht mit der richtigen base URL gebaut und ich verstehe nicht warum.