After the first article on how to make Segoe UI (pronounced: SEE-Go) in Microsoft Teams, I got an additional question. The question was if this will work with all the required icon font in teams too. For that, we need an extra font to get loaded.
When you write a web part, that don’t use Fluent UI or its predecessor Office UI Fabric, you might have recognised Segoe UI from SharePoint is not loaded there.
This time we take a look at the fundamentals on the page and text layout on modern SharePoint pages in communication sites. The text layout is the essential design element on web sites and the intranet. 95% of a current information system is base on just text.
First, let us define some basics on typography on the web to have a better understanding later on the available layout options we currently have.
While working on a small side project on a Sunday, I asked myself the question. Is it possible to use live-reload when I developed a web part on SharePoint Online? I had to search for an answer for that and guess what? I found a solution.
This solution is not only for development but also for a production compilation of a SharePoint web part or extension.[Read more]
During development or the product design or project, you like to avoid external dependencies as much as possible to keep your code secure, reliant and consistent. With these baselines, I want to cover some aspects of Fluent UI that you should consider before adopting it. To be more specific the reason when considering Fluent UI are related to the web version.
Last week I discovered a leak that effects documents published on Workplace from Facebook. After filing a white hat report, I got a response from Facebook’s security team. It seems that they are not concerned that customer data are exposed publicly by their platform via public content delivery networks. The leak is how this platform treats documents and how sharing works.
“Access for everyone” and “discover the secrets of connected companies” are taken literally.
With Markshell I created a small tool that allows you to output Markdown files directly to the console. Why that? Right now, when you write a CLI or any console application, you like to provide some help for it. On the other hand, you also want to have proper documentation set up on Github pages or only in the Github Repo.
Markshell is precisely for that and helps and provides this opportunity and helps you to avoid writing multiple documentations.
I am currently working on updating my old style guide project and one of the central things there will be that I hide commands like yo, gulp serve, and so on behind a CLI. The fact that I have to write two times the same documentation leads to the idea, inspired by a talk with Waldek Mastykarz, to output Markdown files on the console directly.