I’m part of the startup YouJustGo and we are currently targeting the Chinese market. Our site is built in Angular 2 and we wanted to have our site in two languages, English and Chinese. I’ve done most of the technical work in this space, to get the site working in both languages, and I would like to share my experience.
When I heard about Microsoft Teams, I was very excited from the start. I’m using Slack a lot for GitHub projects and for some internal projects, as there is no alternative in Microsoft. Teams is positioned as a Slack competitor, and when it was available as public beta, I immediately contacted our Office 365 admin to enable it. I’ve been using it for a couple of weeks now, and I want to share my experience with you!
Update: New post can be found here.
i18n (internationalization) support for Angular 2 is now built-in the framework. Previously we used ng2-translate, but I found it time-consuming to add all translations manually to the .json files. Since a week or so the documentation is also available at Angular.io. While useful, it did not provide information, it involves a lot of manual steps. I’m going to provide a set of Gulp tasks that will automate everything!
Announced at the “Future of SharePoint” event, was the SharePoint Framework. And it is in public beta since this week! I was one of the lucky persons who had access to the internal repository, so I already had a play with it before. Unfortunately I could not blog about it, as it was under NDA. I will talk about how it will fit into the existing SharePoint development infrastructure, and start with some history 🙂
Imagine you want to know the sentiment of an email without reading it. This can be useful if you want to ignore negative emails for certain parts of the day. I have built a solution for that, by integrating Azure Machine Learning in an Office Outlook Add-In. Every time you read an email, it processes the body, sends it to Azure, and displays if it is negative or positive Continue reading
After my blog post yesterday about Flow, I got a request from a user to build a Flow for Salesforce that does something when an Opportunity is closed, and checks if it was won or lost.
I love feedback, so I decided to build that flow. The result? Check out below email:
If you’ve followed my blog, you know I’ve been looking at PowerApps. PowerApps consists of two parts: Flows (formerly Logic Flow App) and just Apps. Flows allowed you to do things like “If someone tweets about my company, send me an email”, or “When a record is added to SalesForce, add an item to a SharePoint List”. Microsoft has now taken out Flows / Logic Flow Apps, and released it as a separate product: Flow. I think this is a good step, PowerApps can then focus on enabling power users to create mobile apps. I will briefly discuss what Flow is, and show an example of an automated tweet translator emailer. Continue reading