3 ms·
One of the reasons we built https://ftd.dev https://ftd.dev is this. Check out this example: https://fifthtry.github.io/bling/chat/ https://fifthtry.github.io/b
by amitu 4y ago
One of the reasons we built https://ftd.dev https://ftd.dev is this. Check out this example: https://fifthtry.github.io/bling/chat/ https://fifthtry.github.io/bling/chat/
Unlike what you did, here you can create new component in ftd itself, so there is no limit to how many such components you can create while authoring content.
Maybe you are tired of single quote block: https://fifthtry.github.io/bling/quote/ https://fifthtry.github.io/bling/quote/
- boundlessdreamz 4y agoThis looks great. This is the first I have heard of ftd. It wasn't clear how to use it though. https://ftd.dev/docs/ https://ftd.dev/docs/ doesn't link to the Installation, Getting started and Tutorial
- amitu 4y agoYeah, docs are pretty lacking. The language is in very early stage and has gone through some changes rendering existing docs out of date. Jan we created a 0.3 version of our syntax after 2 years or so of development and we feel good about it and have started updating the docs now. You can checkout a video course: https://ftd.dev/expander/ https://ftd.dev/expander/. And maybe join us on our Discord.
- boundlessdreamz 4y agoThis seems to be part of an ecosystem. But I'm not sure what are the advantages. What does ftd do better than markdoc and what can it do that markdoc can't?
- amitu 4y agoThe key difference is that ftd is a single full stack language. You can make api calls, write custom functions, build components, use components etc etc. A language designed for authoring. But still powerful enough (one day, it’s work in progress) that you can build most UI in it.