@flancian I'll admit that I didn't search maybe the most thoroughly because I was supposed to be doing something else at the time, but do y'all have documentation of the jekyll import into the agora? Code links also fine, I couldn't find what specifying that maps to

Follow

@maya ahoy! thank you for asking :) [[jekyll]] support is basic for now -- are your source files Markdown? if so, filename.md maps to node [[filename]]; filename-with-slugs.md and 'filename with spaces.md' are also supported.

Is your jekyll site on git? If so, I'd be happy to import it into the Agora and work on any support you'd need (dev.anagora.org if you want to take a look at how it'd look before publishing).

Β· Β· 2 Β· 0 Β· 0

@flancian Well, I wanted to look at how it'd import jekyll stuff mostly so I could get a sense of what I have that might be halfway sensible to include; I have a number of things like the file that gets rendered as maya.land/maya-blue/ The .md has liquid nonsense in it `{% sdlfkjsldf %}` for transcluded link previews, and knowing whether those get excluded is relevant.

@flancian I have a private tiddlywiki that I grab some .md files from into my jekyll site repo based on tag, so I'm just kind of poking into what subset of all this might make sense for the agora?

@flancian the site's repo itself is on a private repo on a private gitea instance and honestly is *way* heavier than I'd want you to have to deal with, since there are assets in the source control that Really Shouldn't Be

@maya I think I added a regex to drop liquid templates and other unsupported stuff... But I might have only planned to do so :) in any case, it should be easy. If you have a repo URL I can set up dev.anagora.org with your garden and see what happens (tm), then we can iterate. I've also been meaning to add attribution/links to sites already rendered elsewhere, this could be a good motivation to get that done.

@flancian teapot.systems/maya/mayagora.g I set up to pull things over into this in order for that Seeing What Happens. my notes in TW that haven't been intended for jekyll link to each other [like this](#target page name) which may or may not play nicely with intended linking practices

@flancian this is standard linking within TiddlyWiki markdown, but presents some issues if the .md heads straight into a parser

@maya good to know, thanks! I've been meaning to improve Tiddlywiki support anyway; this seems like it would indeed not work out of the box, but also not be super hard to fix in render.py (where a bunch of rendering hacks currently live).

@maya happy to see [[gitea]] -- we're close to opening our own instance to the public :) the idea being that users that don't have a notes repo can get one served by us, and then claim it / port it elsewhere at their pace.

@flancian my household nearly went with the built in gitea wikis for household stuff instead of another tiddlywiki. it might be interesting to see how well that works for agora citizens :)

@maya nice! I think they render fine, except for the Tiddlywiki convention you mentioned, which shouldn't be hard to fix.

dev.anagora.org/@maya

If you included a README.md, it will be rendered in your user page.

If you like this enough to start with it: do you accept the Agora's contract? anagora.org/CONTRACT

@maya thank you! welcome to the Agora my friend.

anagora.org/@maya is live, updates to your garden should reflect in the Agora within ~30 seconds of pushing, plus sometimes caching delay (when a page is accessed it gets cached for a while)

@flancian thank you! is there anything written about hypothes.is etiquette on the site?

@maya no, it's all emerging :) if you leave hypothesis comments anywhere, they should show up in /latest.

Sign in to participate in the conversation
social.coop

A Fediverse instance for people interested in cooperative and collective projects.