<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hi-Sen on Vue Templates</title><link>https://www.vuejstemplates.com/author/hi-sen/</link><description>Recent content in Hi-Sen on Vue Templates</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.vuejstemplates.com/author/hi-sen/index.xml" rel="self" type="application/rss+xml"/><item><title>Vue Basics Example</title><link>https://www.vuejstemplates.com/theme/hi-sen-vue-basics-example/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.vuejstemplates.com/theme/hi-sen-vue-basics-example/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>In recent years, Vue.js has emerged as a popular choice among developers for building user interfaces and single-page applications. My experience delving into the Vue technology stack has been nothing short of enlightening, particularly as I&amp;rsquo;ve had the opportunity to share my insights with colleagues preparing to adopt this framework. The intention was to facilitate a smoother transformation of our product technology stack towards Vue, allowing team members to rapidly get up to speed and engage with the framework effectively.&lt;/p></description></item></channel></rss>