383524 results for ""a""

  • also, if you *do* have a CMS or some existing automation, you can still send passive webmentions because the GET request is just as automation-friendly as a POST. So in practice there's no real downside that I can think of.
    autumnlilybug at 2025-11-13 20:41
  • anyways, the advantage is that you don't have to mess with curl or any other low-level tooling, and you also don't need a CMS to handle sending the webmention, you can just click that link (or type it into your browser and leave a normal hyperlink in your page)
    autumnlilybug at 2025-11-13 20:40
  • Webmention relies on HTTP POSTs which are non-trivial to automate without using a CMS. I decided to implement a GET handler on my webmention endpoint that uses the search parameters `s`, `t`, and `v` in place of the formdata fields `source`, `target` and `vouch`. If you were to link to, say, `example.com/page1` with a normal webmention, you would use a normal `href` to that URL and then send a POST. With passive webmention
    autumnlilybug at 2025-11-13 20:36
  • [preview] [Katherine Isabella Del Toro] Implementing a Webmention Receiver For The Blog
    Loqi at 2025-11-13 20:32
  • Yeah, we can use #indieweb-dev to chat about the tech details behind a website 😄
    capjamesg at 2025-11-13 20:29
  • Still getting a sense of what technologies are popular on the indieweb
    autumnlilybug at 2025-11-13 20:29
  • hey capjamesg, that's a lot of dev jargon! site generator, static site generator, static generator... can you move to #indieweb-dev?
    Loqi at 2025-11-13 20:29
  • Yeah! I have been using a static generator for several years now.
    capjamesg at 2025-11-13 20:29
  • I write my posts in markdown and use a static site generator to make the HTML.
    capjamesg at 2025-11-13 20:28
  • Accessibility is key to designing web sites in an inclusive manner, lowering barriers to information, interaction, and communication, to make the web accessible to people with disabilities, and sometimes a literal site path (/accessibility) for a website accessibility statement; the IndieWeb community encourages both accessible events & personal sites https://indieweb.org/a11y
    Loqi at 2025-11-13 20:19
Sort by:
Relevance Date


Filter results by:

Tag

Query took 0.03s.

Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23
Powered by phinde, the self-hosted search engine. status