Consider to let the user export the graph itself and convert/use it elsewhere.
HN user
xamde
http://xam.de
I think you found a very good prompt/technique to extract mostly the high level stuff without making the diagrams too complicated. And then elk.js seems to do the layout.
Deepwiki.com also has some usable autogenerated architecture diagrams worth a look.
Thanks, it is based on an unreleased 50-page complex syntax speec with over 40 different kind of arrows. Luckily, I simplified BEFORE release :-)
OKF seems OK, but bound to Markdown. A Markdown document can be turned into an OKF document by adding a 'type' to the frontmatter YAML.
What about a knowledge graph language, which can be stated in Markdown prose, in Markdown code blocks, but also everywhere a text field is waiting for you? In the minimalistic language https://ddot.it you can link outside the Markdown world, to files, URLs or even just labels. Like OKF it's just a format.
Disclaimer: I wrote that (short) spec.
I am working on a simplistic syntax for mixing any text with structured knowledge (links, triples, property graph)
Syntax..has name..ddot.it
The spec is ready at https://ddot.it, now working on tool support.
Check out deepwiki.com, which is quite similar and works well
Looks like org mode for the masses
I believe it uses an cross compiled version of dot in js
Reading all these comments, it seems we as a community don't yet have an idea how to write effectively for LLMs. E.g., I guess markdown tables are harder to process, since the row-column-value mapping first needs to be decoded. Or is this irrelevant?
There will be companies founded on executing this idea.
I love how you make sure not to mention the city name, so that not too many people will suddenly show up
it all comes down to whether you view the internet as the greek agora or the roman circus.
The best summary I've ever read about the internet
A shout out to the intellij plugin developer. The Asciidoc plugin has so many nice little Features. E.g. consistent file renames, or paste as screenshot which auto creates a file and embeds it.
Also, Basic statistical reasoning is required. And some core facts about our physical world. What about an open curriculum listing the most important things in a teachable order?
There is also the base band processor, which is completely locked away from user access. Running a wireless network would be much harder, if users could access it. So I guess freedom and working tech are trade-offs in this case.
There is also the "Void" type.
The {@code Void} class is an uninstantiable placeholder class to hold a reference to the {@code Class} object representing the Java keyword void.
When Java introduced Generics they re-used "Void" type. Method calls need to use "null" when "Void" is the type. So in a way, "type of null" is "Void".
Wasm might make that a reality rather soon
From my Analysis, GraphML, although specified in XML, seems to be one of the most widely used exchange formats, especially with the yWorks extensions for yEd.
I am a Netlify Pro customer. I was not aware of this unlimited spending concept. This is simply unacceptable from a risk-perspective.
Unless there is an issue with either the light source or the power source. Muted/unmuted is also a pair where unmuted often does not equal "we can hear you"
The document is primarily intended for the following audiences:
Software developers that want to implement an RDF dataset canonicalization algorithm.
Masochists.
Pick your side.The IntelliJ AsciiDoc plugin is a little juwel with all bells and whistles, Syntax highlight, Preview, structure view, even refactoring of references. We use it together with Antora.
This ist really a succint description: "Sometimes it seems to me that AI people have begun hallucinating as much as the models they’re training."
OK, here is a true code approach to generate wiki pages with embedded Mermaid sequence diagramms. https://github.com/Calpano/featdoc Feedback welcome.
As a counterpoint, our even older Chromecast Audio devices keep on trucking just fine.
The ROK is a nice way to make Espresso. Manual pressure. Try it .
Edit in sublime Text, save, See the browser window on the other monitor (portrait orientation) update, tweak, repeat... That is my workflow for long and short Docs. AsciidoctorJs Chrome Extension is the glue.
Should have been called nutshell
The next step are tools like featdoc which let you define systems and interaction rules which then generate a (mermaid) sequence diagram.
Example at https://dev.azure.com/itmv/Coffee%20Shop/_wiki/wikis/Coffee-...
Project at https://github.com/Calpano/featdoc
Disclosure: I maintain this project
Good link. So cross platform UI as an idea is dead.