da Agency

A Look at How We Updated Fonts on WordPress.com

We recently updated WordPress.com’s fonts and wanted to give you a behind-the-scenes look at how we chose the list. Here’s an example of a few of them in use.

We looked at several criteria when curating our selections to give your site’s visitors the best experience.

First, we looked at the overall popularity and quality of each font, paying close attention to the letterforms of the most common and most quirky characters.  We made sure that these worked well in specific layouts, at different scales, and as part of the entire collection.

To make the cut, fonts had to contain a breadth of styles and weights, including true italics.

It was important to select fonts with broad character and language support beyond basic Latin. We also looked to showcase a diversity of type designers and open source fonts.

Careful consideration of all the criteria mentioned above allowed us to end up with a list that facilitates attractive font pairings for headings and body text.

Here’s a closer look at a few patterns you can create with a keen typographic eye.

For an even closer, hands-on look, you can check them out in Global Styles and the Customizer today. We’re looking forward to seeing how you use custom fonts on WordPress.com! Your feedback will help us continue to grow, refine, and improve the font choices we offer.
Quelle: RedHat Stack

da Agency

Introducing HTTP/gRPC server streaming for Cloud Run

We are excited to announce the availability of server-side HTTP streaming for your serverless applications running on Cloud Run (fully managed). With this enhanced networking capability,  your Cloud Run services can serve larger responses or stream partial responses to clients during the span of a single request, enabling quicker server response times for your applications.With this addition, Cloud Run can now:Send responses larger than the previous 32 MB limit.Run gRPC services with server-streaming RPCs and send partial responses in a single request—in addition to existing support for unary (non-streaming) RPCs.Respond with server-sent events (SSE), which you can consume from your frontend using the HTML5 EventSource API.Streaming responses help you develop applications that send partial responses to clients as the responses become available, so that your applications and websites can be more responsive. Without streaming support, all the responses must be computed in full before they can be sent to the client; this delays time to first byte (TTFB) performance of your applications. In the diagram below, three partial responses are incrementally sent to the gRPC client.Here are some example use cases for server-side HTTP streaming:Streaming large files (such as videos) from your serverless applicationsLong-running calculations that can report using a progress indicatorBatch jobs that can return intermediate or batched responsesLet’s try it: Serverless gRPC streamingStreaming support in Cloud Run brings significant performance improvements to a certain class of applications, and this is just the beginning—stay tuned as we work hard to enable more features in Cloud Run.We’ve developed a sample gRPC server application that you can deploy to your Google Cloud account in a single click and run a client to stream responses from the Cloud Run-based serverless application.Try out streaming support in Cloud Run and let us know what you think on Stack Overflow or on our issue tracker.
Quelle: Google Cloud Platform

da Agency

New Vulnerability Scanning, Collab and Support Enhance Docker Pro and Team Subscriptions

Last March, we laid out our commitment to focus on developer experiences to help build, share, and run applications with confidence and efficiency. In the past few months we have delivered new features for the entire Docker platform that have built on the tooling and collaboration experiences to improve the development and app delivery process.

During this time, we have also learned a lot from our users about ways Docker can help improve developer confidence in delivering apps for more complicated use cases and how we can help   larger teams improve their ability to deliver apps in a secure and repeatable manner. Over the next few weeks, you will see a number of new features delivered to Docker subscribers at the free, Pro and Team level that deliver on that vision for our customers. 

Today, I’m excited to announce the first set of features: vulnerability scanning in Docker Hub for Pro and Team subscribers. This new release enables individual and team users to automatically monitor, identify and ultimately resolve security issues in their applications. We will also preview Desktop features that will rollout over the next several months.   

We’ve heard in numerous interviews with team managers that developer velocity is critical, that automation enables this and that images going into production have to be secure. Last month we launched Docker local image scans as preview in Desktop Edge and today we are releasing vulnerability scanning in Docker Hub. Starting now each time that you push images into Docker Hub, a vulnerability scan will run automatically using the same underlying tooling as our Docker Scan CLI. Once the scan is complete, you can review the scan results in your Docker Hub dashboard. Look out for a deeper dive into the Hub image scanning in the coming days.  

Improved Collaboration and Control

We are also thrilled to start talking to you about Docker’s plans for Docker Desktop and how we are going to add unique improvements for Desktop for Pro and Team users. Starting in November Pro and Team users of Desktop will get additional features and benefits designed to meet the unique needs of teams and of complex use cases, on top of the core features in the free edition. The first feature will provide visibility of Docker Hub scan results directly within the Docker Dashboard for all of your Hub images. In the coming months we will enable users of Docker Context to store and share your contexts with your team from the Desktop via Docker Hub, allowing development teams to collaborate with the same set of contextual details for shared remoted instances. 

For enterprises who want more control over their version of Desktop and don’t want to keep dismissing updates, we will be providing the ability to ‘ignore’ updates in Desktop until you choose to install the new version. Additionally, we allow for centralized deployment and management of Docker Desktop teams at scale through revised licensing terms for Docker Teams. This will allow larger deployments of Docker Desktop to be rolled out automatically rather than relying on individuals to install it on their own.

Finally, we will also extend the Docker enhanced customer support to include Docker Desktop as well as Docker Hub. Docker Pro and Team subscribers will be assured of consistent support from Docker across all offerings in their subscriptions as they build, share and run their containerized applications. 

We will continue to add more Pro and Team features across the entire Docker platform to make developers’ and teams’ lives easier over the coming months.  And of course, we will continue to improve and enhance our core, free offerings. 

 To test Hub scanning today, sign up for a Pro Docker account.   Or,  try the experience locally and run docker scan on your Desktop CLI. If you are interested in Docker Desktop, and what the future holds, then keep an eye on our product roadmap.  If you have questions about deployment licensing or support, please reach out to us.

CTA: 

Sign up for Docker HubRegister for the Webinar: Adding Container Security to Docker Hub with Snyk on October 15th at 10AM PT Join our YouTube Live: Synk Image Scanning on Oct. 8th at 10AM PT

More info on Docker Subscriptions for Pros and Teams
The post New Vulnerability Scanning, Collab and Support Enhance Docker Pro and Team Subscriptions appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/