377879
results for ""a""
-
because a lot of this can be automatically checked to see if the right rel values are being used or not
[tantek]
at
2025-05-28 19:29
-
capjamesg, this makes me think we need to start thinking about a rel value validator, perhaps an addition to http://indiewebify.me
[tantek]
at
2025-05-28 19:28
-
hmm, maybe a PDF with a hyperlink to itself in a repo could have rel="repository"?
[tantek]
at
2025-05-28 19:27
-
and in all those cases, since none of those files can have a hyperlink *inside*, the rel value must be conveyed by HTTP LINK header
[tantek]
at
2025-05-28 19:23
-
So you may use rel=repository on its own if a file is say markdown or txt but not code?
capjamesg
at
2025-05-28 19:21
-
quoting from https://microformats.org/wiki/source-code-brainstorming#Alternatives "rel=repository. … for just the (presumably revision control) repository file for the current page, without asserting a 'code' semantic"
[tantek]
at
2025-05-28 19:20
-
re: "differs from a source-code file" – examples of plain "view source code" (not on a repo): wikis that require login to edit instead show a "View source" link/button that when clicked shows you a textarea you can copy out of (but not edit). E.g. http://indieweb.org, http://microformats.org/wiki, http://wiki.mozilla.org
[tantek]
at
2025-05-28 19:19
-
those are all the examples where a page on the web links directly to the file in github
[tantek]
at
2025-05-28 19:17
-
(and how it differs from a source-code file)
capjamesg
at
2025-05-28 19:06
-
nope, if your link means "root" of a repository, then you must use both: rel="repository root"
[tantek]
at
2025-05-28 19:02
Sort by:
Filter results by:
Tag
Query took 0.05s.
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