mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#readme

0 Beiträge0 Beteiligte0 Beiträge heute

I had a moment of inspiration and created #ggg take a look (still #experimental #foss software)

ggg: #guile #scheme #glyph #generator

codeberg.org/jjba23/ggg

Through #svg generation from #lisp we leverage a (wip) #dsl and apply some #math knowledge to build pixel perfect project #markdown / #org badges.

It also scripts #imagemagick to export to #png or #webp .

You can then use the svgs in your #codeberg (or #github) repository #readme for example.

I provide a #guix manifest in the repo

Am I the only one who gets annoyed when when a project's README looks like this? No example code. No CLI synopsis. No in-depth description or explaination. No screenshots or videos/gifs. Just a short summary and a link to the website or maybe the API documentation. Please don't force me to dig deeper just to figure out what your project does or how to use it.
github.com/inertiajs/inertia#r

GitHubGitHub - inertiajs/inertia: Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers. - inertiajs/inertia

#libobscura is going through the final crunch... I mean, touches, before release.

I just realized the project page and the #readme are like continuous announcement posts. For some people, it's going to be the first contact with your work, so tell them;

- are they the intended audience?
- how do they benefit from this?
- where is the project going?
- how far along is it?
- how to try it out?

/me goes back to rewriting