From Phil Pennock to ~ancarda/vcs-autodiscovery
On 2022-02-20 at 20:06 +0000, Mark Dain wrote: > I've been thinking about this for a little bit. Have you heard > of IndieWeb? Vaguely. > They markup pages with Microformats, like so: > https://microformats.org/wiki/h-entry#Example There's not really enough there to see how this contrasts with schema.org itemscope/itemprop stuff, besides being simpler because it's less rigorously defined. If you check the individual projects linked from the index, where I
From Phil Pennock to ~ancarda/vcs-autodiscovery
On 2022-02-16 at 19:15 +0000, Mark Dain wrote: > I'd be happy to take a look if you want to send me a link. Sure, thanks. Go vanity domain: <https://go.pennock.tech/> > That sounds interesting. I like `rel="vcs-repo"' for this > purpose. It could go nicely on <https://git.sr.ht/~user/>. > > I don't have any objections. Let me look a bit closer at the rel > attribute, this can probably be added to the RFC. I've added this to the links on the above index page. I'm happy to change to something else. I just want to make life easier for others with a little semantic structure, while not requiring large amounts of
From Phil Pennock to ~ancarda/vcs-autodiscovery
Folks, I have a vanity domain for Go imports maintained with some rather hacky shell (so not worth listing as an implementation), and I think I have it working. side-question: is there a validator for the tags found? I also have a top-level page, with links to the various projects as direct children; each of those projects now has the vcs-autodiscovery meta elements, but nothing in the top-level page helps a semantic parser distinguish which links are for VCS projects vs just being links to somewhere else.
From Phil Pennock to ~sircmpwn/hare-dev
--- Alexey Yerin caught that the match block was also using println instead of printfln. Adjusted patch for that. Sorry for the bad first attempt at a v2, it's been too many years since I last used a pure git-send-email flow. I forgot what's what. content/tutorials/introduction.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index 61ec5fc..bb0bdd4 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md [message trimmed]
From Phil Pennock to ~sircmpwn/hare-dev
Alexey Yerin caught that the match block was also using println instead of printfln. Adjusted patch for that. --- content/tutorials/introduction.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index 61ec5fc..bb0bdd4 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md @@ -765,10 +765,10 @@ # TODO: We're going to expand the syntax for tuples later let x: (str | int | example | void) = "Hello!"; match (x) { [message trimmed]
From Phil Pennock to ~sircmpwn/hare-dev
--- content/tutorials/introduction.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index 61ec5fc..589d8fe 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md @@ -765,8 +765,8 @@ # TODO: We're going to expand the syntax for tuples later let x: (str | int | example | void) = "Hello!"; match (x) { s: str => fmt::println("x is a str: {}", s); i: int => fmt::println("x is an int: {}", i);[message trimmed]