Now you can make your templates public by publishing them to the Flayyer Marketplace.
It is super easy, just set on your flayyer.config.js the marketplace flag to true.
We are glad to announce we added the long awaited Variables UI support on the Flayyer.com dashboard.
This allows users to know what variables are required and optional in each template.
Now an UI Widget will be displayed based on the type of the variable. We support a hint, a default value and even an array of examples! 🤯
You can start using it by upgrading @flayyer/cli to ^1.17.0 and installing @flayyer/variables:
We added a new section about Cache invalidation to our docs page so you can check it out 👀
This section explains the __v parameter that usually pops up in Flayyer URLs.
This is a random value (not so random, it is just a timestamp) to trigger cache invalidation on social networks crawlers.
You can always toggle off this feature by setting to a nullish value the meta.v parameter when using our libraries.
Previously emojis were not rendered, until now 🚀
We just released @flayyer/cli@1.11.0 which adds an additional post-procesisng step to add Emojis via twemoji, an amazing open-source library from Twitter.
Here is an example:
Are we missing a feature? Have you found a bug? Let us know via Github: github.com/flayyer/flayyer-cli.
We just released @flayyer/cli@1.10.1 which included additional CLI flags to allow developers specify their own directories and different deploy configurations.
Here is an example:
Are we missing a feature? Have you found a bug? Let us know via Github: github.com/flayyer/flayyer-cli.
We just added Algolia integration to our documentation site (yes, this site!). Give it a try and let us know what you think 😃 It is on the top right corner of your screen, or just press CMD + K.
Flayyer is a developer-first company and we are really committed to Developer Experience. The integration was very straightforward thanks to the Docusaurus presets we are using.
We have amazing things on our pipeline, stay tuned!
We are saying goodbye to flayyer.io/v1 in favor of flayyer.io/v2 which has:
No worries for you, the legacy version was just being used by our early-early adopters and all them have migrated to v2.
Happy to announce we have moved our old documentation to Docusaurus 2 🦖🎉
Previously we were writing React and HTML for our information pages but that became very hard to maintain. We adopted this open-source platform and in less than 2 days we were live again.
Because we, Flayyer.com, love open-source, all of this guides and docs and changelogs are open to the public via our GitHub repository: https://github.com/flayyer/flayyer-docs.
Feel free to contribute 😃
