Well since I haven't seen an appropriate solution. Use the HTML widget from the left side of your blog and paste into it the script generated in the GitHub Gists(embed), for the colors simply add the right format to the Gist for instance "example.js" or "example.py" depending on the language that you want to highlight. So you don't need a "dirty solution". While this is not Velo-related companies in the development business for sure needs a solution to share posts. This is a good reliable solution.

Very useful. Some of our clients have required these types of integration in the past. I couldn't find the guide for AWS PostgreSQL which is highly demanded by our clients is that also available?

@alessuae You can use this solution: https://www.wix.com/velo/forum/tips-tutorials-examples/parsing-xml-data-structures-with-velo?appSectionParams=%7B%22origin%22%3A%22member_posts_page%22%7D This solution takes XML structures and transforms them into JSON objects

Well I'd agree about Corvid if you want to but once again Velo proves to be open to its own interpretation as shown now by Tristan

You must store backend functions in collections they clean up each 3 minutes

async await solution: import {fetch} from 'wix-fetch'; $w.onReady(function () { callIP(); }); async function callIP(){ const response = await fetch('https://extreme-ip-lookup.com/json'); const objectIP = await response.json(); console.log(objectIP); } the method by default is always GET, so you don't need to set the method call this kind of function and use DEV tools on your browser to extract from the objectIP whatever you need, since this is an object you can do objectIP.city or any other ...

Still being called Corvid on the CLI yes there is no Velo CLI available

I love Wix and their programming platform :)

Reason why Velo is totally open to interpretation far away from being a meaning that stands for Velocity.

Well, here is the definition of Velo by Wikipedia: https://en.wikipedia.org/wiki/Velo#:~:text=Velo%20or%20V%C3%A9lo%20may%20refer,%2Dwheeled%2C%20single%2Dtrack%20vehicle Urban Dictionary: https://www.urbandictionary.com/define.php?term=velo Merrian Webster Dictionary: https://www.merriam-webster.com/dictionary/velo you name it... it actually refers to velocipede

Thanks for the post, but sorry is not the prettiest or the right name for a development technology honestly Velo feels like old JQuery the brand needs to show case the power of NPM and NodeJS, APIs the website needs to be more technical if you want to attach skilled developers. On the other hand Velo can be anything not only velocity is totally open to human interpretation on the middle of an important meeting there is no time for interpretations it is important a defined name at least on my case when I have to present it to our clients is not going to sound powerful either robust.

Not the prettiest name now I'll have to talk to my clients as hey let's do it with Velo... I don't know it sounds clucky. It doesn't feel robust and the new website feels Nah is not for technical stuff is not for high-performance Corvid had a better brand presence towards the developer world, we developers tend to be more nerdy and more geek ... so yeah once again not the best name. Check it out... React, Angular, Vue, Node, Dino, Jest, Flask, you get the picture... but not Velo...

@Marlowe Shaeffer Hi Marlowe. Happy to help! Would be great to have the properties panel in 2 ways: 1 - outside of the text editor floating (as it has been until now) 2- inside the text editor (the new style) So just an option to choose to attach the properties panel to the text editor or disattach, remove it from it.

@Yisrael (Wix) Thanks a lot for your reply. Where can I give feedback regarding the new properties panel inside the Wix text editor? I was thinking to send feedback through the Editor X The new properties panel inside the text editor: This is not always helpful. In my case, I build the entire UI, set IDs for the elements, and expand to full screen the text editor so is as easy as possible to observe all the functions there. So having the properties panel easy to access without the text editor is helpful to have a full screen of the UI. When assigning IDs to the elements and is not really helpful inside the text editor because I use to program with text editor full screen and not by having visible half of the website. Would be great to have both options available for the properties panel

Hopefully, somebody from Wix read this, the autosave is bugged on Mac. After turning it off opens the terminal this is not weird what is weird to me is that after some minutes on some projects turns on again, some other projects when you get back to work its always on... even if you turned it off before closing the editor. This is happening on all our Mac systems This is on Mac, Chrome Version 85.0.4183.83 (Official Build) (64-bit)

@Vijay If you want to set a mode for all your repeated picture elements simply use global selector $w('#id') select one instance of your picture element which because is a global selector will affect all of your repeated element pictures and set the mode. I use it on repeaters all the time, it doesn't need any special code...

Backend variables expire to keep cleaner and reduce unused memory in the servers. You have to keep this in mind and prevent it saving your important data in a Wix collection. Yes Corvid DB is a Wix collection...

@dimitar You could simply create your own backend with Corvid. That was my recommendation well however an external backend works fine. If you decide to set up a backend with Corvid only keep in mind variables exist for around 204.417 seconds (3.40 minutes) I actually calculated this time expiration, is somewhere in the forum. What I do to overpass this situation is to save all important data in a Corvid database and pull the data from there. If my variables become undefined I just restore the variables by pulling back the data from the database and assigning back the data to the variables. How do I know if the variables come undefined by a try/catch block in the frontend, the catch runs as soon as the variables are undefined.

Good to know this workaround, thanks for sharing it. I'd recommend you to create as first the location object before assigning it to the location property of the Google map. So is something like location = {} location.latitude = currentItem.latitude location.longitude = currentItem.longitude location.description = currentItem.nameEnterprise Then once your new object is ready (the location object) assign it to the Google map property so is: $w("#googleMaps1").location = location;

@Aleks Fylymonchuk Yeah thats what I thought, tho would be something important to have in Corvid if you guys want to create a robust programming platform. Also since the directions link is a setting available in the editor it looks like it should work ... so this is misleading ...