Turn Your WordPress.com Blog into a Podcast with Anchor

Blogging on WordPress.com is all about sharing your unique voice, and starting today, you can extend that to another platform: Anchor. We previously shared some tips and tricks for getting started with a podcast on WordPress.com and are thrilled to share this new option.

Anchor, part of the Spotify family, powers the most podcasts worldwide, with free tools to easily create, distribute, and monetize, no matter how you record — including podcasting with your WordPress.com blog!

Creating an Anchor podcast from your site is free and seamless. After all, you’ve already got a whole blog’s worth of written content to use. With Anchor, all that’s left is converting your words into audio, which can be as easy as using your blog to quickly record a text-to-speech version.

Blog-to-podcast benefits

Making a podcast out of your blog breathes new life into the work you’re already doing — you can make your unique blogging voice actually audible! By converting your blog into a podcast, you’re leveraging the power of audio to grow your brand, audience, and income — without any extra work. Hundreds of millions of listeners (and counting) consume podcasts every day, and they’re constantly looking for fresh voices and perspectives. Whether you have a built-in WordPress.com audience to bring over or not, an audio extension of your blog means another avenue for exposure — to your existing followers and new ones. And then there’s monetization: Anchor Sponsorships lets you read ads in your own voice during a break in your podcast; Anchor’s Listener Support feature, meanwhile, allows your biggest fans to support your work via a recurring monthly donation.

A podcast version of your WordPress.com blog also introduces an entirely different audience to your work, and frees listeners up to do what readers aren’t able to: multitask! There are, of course, many benefits to readers fully immersing themselves in the written content of a blog. But audio enables listeners to consume your work while performing everyday activities, like going for a walk, driving, cooking, or just relaxing. Last but not least, turning your blog into a podcast unlocks it for those who are visually impaired or may otherwise have difficulty accessing the written version.

Let your words do the talking

Connect your site to Anchor and your existing blog posts will import as episode drafts

Your blog can almost literally do the talking for you with direct text-to-speech, similar to an audio transcription of an article. This is a great option for blogs less dependent on top-notch production value and more focused on the content itself — such as well-researched news, sports, essays, and wellness stories. With text-to-speech conversion, your blog can be podcast-ready in a few minutes.

Converting your blog post to podcast-ready audio and distributing your new show takes just a few minutes.

Of course, if you want to create a podcast that highlights your actual speaking voice, you can record it by reading a transcript of your blog post, which will be imported directly into Anchor for easy access.

You can get more creative, too, by using your blog as a jumping-off point to host an audio discussion about the blog topic. Or let your blog serve as inspiration for a more traditional podcast, where you host and interview guests, record scripted segments, and much more, in ways amplified by audio!

Create a podcast today

There are a number of different ways to turn your WordPress.com blog into a podcast. The amount of work it takes can be surprisingly minimal — or more hands-on if you like. Whether you just want to create an audio version of your blog, expand your blog concept to a different platform, or simply try your hand (and voice) at a new medium, there’s a podcast structure for you. Most importantly, your written work means you’re not starting from scratch.

Here’s a step-by-step guide for creating a podcast on Anchor from your existing pages and posts on WordPress.com:

You can also convert all of your newly published pages and posts into podcasts as well.

If you’re looking for inspiration, a perfect example is TheDesignAir, whose blog covers aviation design and product news. Check out their text-to-speech podcast with Anchor:

Ready to turn your blog into an Anchor podcast for free? Get started by creating your Anchor account. Happy podcasting!
Quelle: RedHat Stack

Build a Beautiful Site in the WordPress Mobile Apps with Predesigned Page Layouts

Your WordPress mobile app is a convenient way to create and manage your WordPress site. Now, you can design a new page right from your phone or tablet — and build the site of your dreams — with predesigned page layouts.

Introducing starter page layouts

Not all of us are designers, and building a page on your site with the layout in your mind can be intimidating and time-consuming — but it doesn’t have to be that way! Now when you create a new page on WordPress for iOS or Android, you can choose from premade layouts. You can also customize them to fit your needs, right from the block editor.

Choosing a layout

When you create a new page in the app, you’ll see a list of premade page layouts, including about pages, contact pages, team pages, services pages, and more. Whether you’re the owner of an online shop of sustainably made clothing, the founder of a newly formed digital magazine, or a financial strategist who’s just launched a consulting business, you can use these premade layouts to build the most essential pages on your website.

Once you find a layout that you’d like to try, tap it to select it. After you’ve selected a layout, you can either preview it or create a new page with the chosen layout.

Ready to try these new Starter Page Layouts? Be sure to update your WordPress app to the latest version. If you don’t have the app yet, download it for free, on both Android and iOS.

We’d love to hear your feedback on these new layouts. Reach out to us from within the app by going to My Site, tapping your photo on the top right, tapping Help & Support,  and then selecting Contact Support.
Quelle: RedHat Stack

Showcase Your Figma Designs on WordPress P2

Figma — one of the most popular and fastest growing digital design tools today — was recently voted “the most exciting design tool of 2021.” 

In many organizations, a smaller group — often the design team — uses Figma on a daily basis. But designers need a seamless way to share their work and gather feedback from other disciplines across the organization. Enter P2. P2 is a product powered by WordPress.com that boosts remote, asynchronous team collaboration. With P2, team members can share ideas, collect feedback, and assign tasks to one another.

You can now embed Figma files on P2 and get contextual feedback from everyone, creating a more inclusive environment, eliminating the need for others to learn and navigate design-specific software. 

Sharing Figma files on P2 allows teams to review designs and comment where everyone collaborates. It integrates all work in a single spot, helping track project progress. P2 is fully searchable for future reference too! As you iterate in Figma, your files will magically sync on P2. No more messy screen grabs or wondering which Figma file is the most up-to-date.

Step 1 : Copy the link to the art board or prototype from Figma

Step 2: Add the Figma block and paste the link into it

Get P2

Want to know more about how P2 can help improve communication and collaboration on your teams? Check out a demo. You can also create your own P2 here and take it for a spin. Any questions? Feel free to comment on the demo P2.
Quelle: RedHat Stack

Building Single-Page Websites on WordPress.com

WordPress.com supports a wide range of features for building your online presence: blogs, online stores, newsletter signup forms, and more. These tools are invaluable for many customers, but they can seem excessive for folks who are just looking to create a straightforward single-page website. If that’s you, read on for examples of how you can also create one-page websites here on WordPress.com. 

Both examples use WordPress.com’s freshly-launched Blank Canvas theme, which is optimized for single-page websites. It comes with no header, navigation menus, or widgets, so the page you design in the WordPress editor is the same page you’ll see on the front end. The theme also comes with a handful of ready-made Block Patterns to help kick start your site. 

About Me

By using the “About Me” block pattern, your website can be a special, concise introduction to who you are and what you do. 

Start with the new Blank Canvas theme. Once that’s installed and activated, open your homepage in the WordPress Editor. If you have homepage content already, feel free to select it all and delete it. 

With a blank slate in place, you’ll want to open the block selector, and switch over to the Patterns tab. By default, this will show you the single-page patterns that are included with the Blank Canvas theme. Selecting the “About Me” pattern will provide you with a beautiful starting point to begin customizing. 

With just a few clicks, you can personalize the images, text, and social media links to make your site your own. 

Collections of Links

Sending your followers to a single link is increasingly important. A handful of social media services only allow you to link to one webpage (I’m looking at you, Instagram). Or maybe you’re a musician, and you want to point folks to your new album on their music service of choice — Spotify, Apple Music, Bandcamp, or Tidal. Having a single page full of links is becoming a necessity — and Block Patterns provide a simple path to creating one on WordPress.com. 

Again, let’s start with the new Blank Canvas theme. Open the homepage, and delete existing homepage content, if you have any. From there, you’ll want to open the Block Patterns panel again, but this time, select the “Links” pattern. 

This will provide you with a template you can use to begin your list of links. Customize or delete the user photo, add your name, links, and a description if you’d like. Each sample button can be customized or removed, and you can add as many links as you’d like. 

Once you have this the way you like it, copy your site’s address and paste it into social media!

If you have an existing site that you’d like to convert into a single-page site, we have you covered too. We’ve added a new setting to 20 of our most popular themes that will let you hide the header and some footer elements on the homepage. This will provide you with a blank slate to build from. 

What other types of websites (single-page or otherwise) would you like to see more resources for? Share in the comments below! 
Quelle: RedHat Stack

Kubernetes Training Webinar Q&A: Running with the Application Essentials

The post Kubernetes Training Webinar Q&A: Running with the Application Essentials appeared first on Mirantis | Ship Code Faster.
Last week we teamed up with our training partner ExitCertified to present our most successful webinar ever, “Running with the Application Essentials,” which attracted nearly 3,000 registrants!  Here we’ve taken the time to answer all the questions we received from the audience, but we’d love for you to view the whole webinar!
Are there any macro services?
Compared to the term “microservices”, the terminology commonly used as a point of comparison is “monolithic application.”
How would a microservice application coalesce information? Is there another layer to this? 
Great question. The short answer is to start looking at the API composition pattern. You will need an API composer than can handle sending queries to the backend services and then performing an in-memory join of the results (for example).
One advantage you forgot to mention is that you have the ability to do a blue-green deployment during business hours while the system is live, saving time and costs.
I hinted at it. But yes blue-green deployments, canary testing, A/B testing, and so forth are great to include in the software lifecycle and can make up for any deficiencies in the rounds of pre-production testing of code changes in cloud-native applications, while at the same time mitigating against downtime with each code release.
Can I think of microservices as decomposing all of the subprocedures and functions in my ASP page into their own microservices?
In a manner of speaking, yes. Conceptually, that is one way of thinking about functional decomposition.
Are there at least two levels of testing with microservices? First, is there more of a unit test that tests all of the possible inputs/outputs expected? And then is there a system test that takes into account multiple miroservices that together perform some business action?
Testing code changes of an application decomposed into microservices is a complex topic that requires specific attention to the strategy for testing. While unit and integration testing are quite a common approach for testing code fixes or minor enhancements for microservices, other testing approaches include a controlled rollout into production (for example, canary testing, A/B testing, and so forth) for code changes where pre-production testing would be considered too costly in terms of time to develop and deliver. The more complex the application, the increased difficulty of testing. A controlled rollout of a code change should allow for a quick rollback if an unintended error is introduced.
Should a development approach be to prototype my concept with the monolithic approach, then thereafter build the final product as a microservice architecture?
That really depends on time to deliver final product and value gained by prototyping monolithic only to deliver in microservices. Both architectures have their benefits and drawbacks. If the the application is small enough to be developed and maintained in a monolithic architecture pattern, then the recommendation is to proceed accordingly. However, when scoping the requirements of the application suggests a level of complexity that will require multiple teams of developers and requires rapid release cycles (continuous delivery / deployment), then microservices seems like the right choice.
On top of the testing question, what is the difference between microservice and monolithic in terms of testing, if unit and system tests are the same. I still would need to do unit tests and a system test in monolithic development.
Testing in a distributed system, as I have described, is quite complex comparatively. As in a monolith, testing is straightforward: either the application features are all available or the application is not available at all. In an application developed in a microservice pattern, software testing methods need to be carefully considered in the design phase of the application. For example, unit and integration testing code changes are specific to the target service, not all services comprising the application. Depending upon the application and business requirements, other types of pre-produciton and production testing may also be considered, such as blue-green deployments, canary testing, and so on.
You mentioned but did not define, Kubelet, Kubelet-Proxy, Master/Worker nodes and Pod
Yes my main point is to provide an introduction to the Kubernetes architecture, and highlight which components (such as kubelet and kube-proxy) provide resiliency with respect to running applications within the cluster. In the complete Mirantis training course, CN 120: Kubernetes Application Essentials, we provide a thorough presentation on the main components that make up the architecture of the Kubernetes platform.
How is state integrity ensured for stateful applications such as databases (MS SQL, My SQL, Maria DB, and so on) running on multi-node Kubernetes? 
Good question! To add to the point of Persistent Volumes and PVCs, the Kubernetes object to consider is the StatefulSet object with the corresponding headless Service object. In your specific example of a database, additional configuration is required to ensure High Availability (HA) across multiple pods within the StatefulSet. The Kubernetes documentation provides a tutorial on configuring HA for MySQL as found here (https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/). While not the only approach, the tutorial should provide you with a good start in such a case. To further add as a point of consideration, the main drivers of using Kubernetes is a cloud-native technology stack specifically meaning datastores that are cloud-native. You may want to consider other cloud-native datastores as a comparison, such as CockroachDB.
How are these pods secured by encryption?
Pods do not offer any kind of native encryption of the data they handle. With some exceptions for Kubernetes components, encrypting application network traffic and data at rest within the cluster is not handled natively. Additional addons and environment configuration are necessary to achieve encryption in both cases.
Does Mirantis run its own datacenters for the Mirantis Cloud Native Platform or 3rd party provider datacenters (AWS, Google, Azure, etc.)?
Mirantis Cloud Native Platform runs on customers’ public or private clouds or on bare metal.
Is there a community edition of Mirantis Kubernetes Engine for self learning?
A trial version is available. If you are interested in downloading and practicing on the Mirantis Kubernetes Engine (MKE) you can do so easily with Mirantis Launchpad. See more information directly on our website: https://www.mirantis.com/software/docker/download/.
Should you have Ops Before Dev? Or can you just jump into Dev Track with developer experience but very little Kubernetes and little to moderate Docker?
In terms of the Mirantis learning track, we recommend the Container Essentials -> Kubernetes Application Essentials -> Kubernetes Native Application Development. Although an option, the Operations course is geared towards Kubernetes operations management.
Is the COA exam is still available?
Yes it is! To get started, have a look here: https://www.openstack.org/coa/. Additionally if you are ready to register, you can take a look at all of the available sessions here: https://coa.arlo.co/w/events/1-coa-certified-openstack-administrator
I’d like some articles about K8s security. Thanks!!
A site that has a great list of articles organized by Kubernetes Security topics can be found here: https://kubernetes-security.info/
Can you please elaborate on service discovery?
Kubernetes provides two primary modes of finding a service within a cluster: environment variables and DNS. If a service exists at time of pod creation, then that service will be made available to the containers within the pod as environment variables. The DNS option allows for applications to contact services by DNS name, assuming the cluster is configured with a DNS service (highly recommended).
Thanks for joining us, and again, check out the full webinar!
Interested in taking a class from Mirantis Training? Check out our course catalog and public class schedule.
The post Kubernetes Training Webinar Q&A: Running with the Application Essentials appeared first on Mirantis | Ship Code Faster.
Quelle: Mirantis

Working with multiple Kubernetes clusters in Mirantis Container Cloud and Lens

The post Working with multiple Kubernetes clusters in Mirantis Container Cloud and Lens appeared first on Mirantis | Ship Code Faster.
One of the advantages both Mirantis Container Cloud and the Lens IDE share is that both enable you to easily work with multiple Kubernetes clusters. What’s more, the Mirantis Container Cloud Lens extension ties the two together, making it simple to connect some or all of the clouds in your Mirantis Container Cloud to your Lens install.
In this tutorial, we will look at adding Kubernetes clusters to Lens, Installing the Mirantis Container Cloud Lens extension, and using the extension to add existing clusters from a Mirantis Container Cloud instance. We’ll look at both clusters and workspaces, and when we’re done, we’ll clean everything up.
Setting up
The first thing we’ll do is make sure everything is working properly by accessing a single cluster.  The easiest way to do this is to follow these steps:

Make sure you have Lens installed.  You can find instructions in the Getting Started with Lens blog.
Make sure you have a Kubernetes cluster running. You can create one easily using K0s. For instructions, see How to create a Kubernetes cluster with K0s: A quick and dirty guide.
Make sure that you have a copy of your KUBECONFIG file.  (If you created a K0s cluster on an external server, make sure to edit the KUBECONFIG file to point to the appropriate IP address. You can see those instructions in the guide.)

Now you’re ready to add the cluster to Lens.
When you start Lens for the first time, you’ll be presented with the quick launch menu, which enables you to add a cluster.

Follow these steps to add the cluster:

Click the Add Cluster button (+) in the upper left.
Lens allows you to choose between adding an actual KUBECONFIG file and copying and pasting the kubeconfig information.
Add the kubeconfig file and select the appropriate context, then click Add Cluster.  At that point you can navigate through the objects in your cluster.
At this point, you can add additional clusters and they will appear as an icon on the left-hand side.  You can change the icon representing the cluster by choosing File->Cluster Settings and scrolling down to the General section.
You can then browse your local system for an image to use for the new cluster.  For best results, use a square image, but all the common image formats such as jpg, png, and gif will work.

If you have multiple clusters you can also organize them into Workspaces.
Using Workspaces
Workspaces are a way to organize clusters to make them easier to find when you have dozens, hundreds, or thousands to deal with.  To see the existing Workspaces, click the lower left-corner of the Lens interface.

In this case, we only have the original Workspace, default.  To add more, click Workspaces->Add Workspace.

From there you can specify the new name and click the square disk icon to save.  Once you’ve done that you will see the new workspace in the lower-left list.

Now we’re ready to go ahead and add in our Mirantis Container Cloud clusters.
Adding Mirantis Container Cloud
Mirantis Container Cloud is a convenient way for you to get control over multiple Kubernetes environments.  
Let’s start by taking a quick tour of some relevant parts of Mirantis Container Cloud.  (if you need to install Container Cloud, you can find information here.)
First sign with the username and password you specified at install, or that was given to you by your administrator.
From here, you can see a list of the main clusters.  In this example, that means just the main management cluster:

Notice that I said “main clusters”.  If you click Projects, you will see that you can also add individual projects.

Obviously default is the project we’re looking at to start with, and that’s where the kaas-mgmt cluster lives.  In this case, however, we have a second project called demo, which we can access by clicking the icon next to the project name and choosing demo->Save.

As you can see, in this case we have two clusters that are part of the demo project:

And of course anything we do in this context will apply to the demo project.
So how do we get these clusters into Lens?
Adding the Mirantis Container Cloud extension to Lens
It would be simple for us to add each individual cluster to Lens as we added our original k0s cluster, but there’s also an easier way that takes advantage of the Lens Extensions API.
Mirantis has create a Mirantis Container Cloud Lens Extension that will enable you to easily import some or all of your Mirantis Container Cloud clusters.  To take advantage of it, follow these steps:

Download the extension from Github. Don’t extract the archive, just make note of where you’ve saved it.
Open the Extensions view by choosing Lens->Extensions.
Under Install Extension, click the file folder icon and navigate to the archive you downloaded. The extension will likely install immediately, or click the Install button.
You should see the new extension listed under Installed Extensions.

If you need to disable or uninstall the extension, you can do it from this page.
Adding clusters to Lens with the Mirantis Container Cloud extension
Now we’re ready to go ahead and add our clusters to Lens so we can work with them more easily. Follow these steps:

We have a couple of ways to start this process.  One would be to go to File->Add Cloud Clusters. The other is to click the Container Cloud icon at the bottom right of the window. or
From here, you can add the actual clusters by adding the Mirantis Container Cloud URL, username, and password.  

On the right-hand side you have the option to make two decisions.  The first is whether you want to add these clusters to new workspaces.  These workspaces will be based on Container Cloud projects.  For now, leave this option checked.
The other option is to decide whether to generate an offline token for access to the clusters.  Note that once you generate a token, this token cannot be revoked, so only do this if absolutely necessary.

Choose which clusters you want to add and click Add selected clusters.
Open the Workspaces menu on the lower left-hand corner and you will see that we have two new namespaces, mcc_default and mcc_demo, corresponding to the Mirantis Container Cloud default and demo projects, respectively. Change to the mcc_default workspace.

Notice that there’s just one cluster, kaas-mgmt, in this namespace.  You can see the user and the cluster name by hovering over the cluster icon.
 Change to the mcc_demo workspace.  Notice that you now see the demo-1 and demo-2 clusters that were part of the Mirantis Container Cloud demo project.

Now you have the ability to poke around the cluster just as you would with any other Kubernetes cluster linked to Lens.

Cleaning up
Of course, we can’t talk about how to add clusters and extensions to Lens without talking about how to clean them up again.
Removing a cluster
To remove a single cluster from Lens, follow these steps:

In the left-hand panel, click the cluster you want to delete. 
Choose File->Cluster Settings.
This option brings up a page that shows you information about the cluster such as the Kubernetes version and distribution, status, API address, and so on.  It also gives you the option to change parameters such as the cluster’s name and workspace, and to enable metrics or set the default namespace.

Scroll down to the bottom of the page and click the red Remove Cluster button.

Note that you’re not doing anything to the cluster itself, you’re just removing it from Lens.
Removing a workspace
One of the advantages of workspaces is that it gives you the ability to remove an entire group of clusters at once by removing the workspace.  In this example we’ve added two new workspaces, so we can go ahead and remove them.

 In the Workspaces menu at the bottom of the page, click the Workspaces link,

You will be presented with a list of existing workspaces.  You can change the name by clicking the pencil icon.  To delete the workspace, click the trash can icon.

 Confirm the deletion by clicking Remove Workspace.

From here you can repeat the process for any additional workspaces that you want to delete.
Where to go from here
Many companies are working on extensions to Lens, and in the near future there will be some fun new extensions for you to play with.  In the meantime, if you’re just starting out with Lens, we strongly recommend you check out the Getting Started with Lens tutorial, and join the Lens community. 
The post Working with multiple Kubernetes clusters in Mirantis Container Cloud and Lens appeared first on Mirantis | Ship Code Faster.
Quelle: Mirantis

New Theme: Twenty Twenty One

Twenty Twenty One is the latest WordPress default theme, which is now available to all WordPress.com sites. Designed by Mel Choyce-Dwan, the muted tones and timeless design will let your work shine.

Twenty Twenty One takes advantage of all the latest features of the Block Editor — the new block patterns allow you to create a beautiful layout in seconds.

Learn more about TwentyTwentyOne, or check out the demo site!
Quelle: RedHat Stack

RDO plans to move to CentOS Stream

What changed with CentOS?
CentOS announced recently that they will focus on CentOS Stream and CentOS Linux 8 will be EOL at the end of 2021.

While CentOS Linux 8 (C8) is a pure rebuild of Red Hat Enterprise Linux (RHEL), CentOS Stream 8 (C8S) tracks just ahead of the current RHEL release. This means that we will have a continuous flow of new packages available before they are included in the next RHEL minor release.

What’s the current situation in RDO?
RDO has been using the latest CentOS Linux 8 to build both the OpenStack packages and the required dependencies since the Train release for both for the official CloudSIG repos and the RDO Trunk (aka DLRN) repos.

In the last few months, we have been running periodic CI jobs to validate RDO Trunk repos built on CentOS Linux 8 along with CentOS Stream 8 to find any potential issues created by OS package updates before they are shipped in CentOS Linux 8. As expected, during these tests we have not found any issue related to the buildroot environment, packages can be used for both C8 and C8S. We did find a few issues related to package updates which allowed us to propose the required fixes upstream.

What’s our plan for RDO roadmap?

RDO Wallaby (ETA is end of April 2021) will be built, tested and released only on CentOS 8 Stream.
RDO CloudSIG repos for Victoria and Ussuri will be updated and tested for both CentOS Stream and CentOS Linux 8 until end of 2021 and then continue on CentOS Stream.
We will create and test new RDO CloudSIG repos for Victoria and Ussuri on CentOS Stream 8.
The RDO Trunk repositories (aka DLRN repos) will be built and tested using CentOS 8 Stream buildroot for all releases currently using CentOS Linux 8 (since Train on)

How do we plan to implement these changes?
Some implementation details that may be of interest:

We will keep building packages just once. We will move buildroots for both DLRN and CloudSIG to use CentOS Stream 8 in the near future.
For Ussuri and Victoria CloudSIG repos, while we are supporting both C8 and C8S, we will be utilizing separated CBS Tags. This will allow us to have separated repositories, promotion jobs and package versions for each OS.
In order to reduce the impact of potential issues and discover issues related to C8S as soon as possible, we will put more focus on periodic jobs on C8S.
At a later stage, we will move the CI jobs used to gate changes in distgits to use C8S instead of C8 for all RDO releases where we use CentOS 8.
The CentOS/RHEL team has made public their interest in applying Continuous Delivery approach to CentOS Stream to provide a stable CentOS Stream using gating integration jobs. Our intent is to collaborate with the CentOS team on any initiatives that will help to validate RDO as early in the delivery pipeline as possible and reduce the impact on potential issues.

What’s next?
We plan to start the activities needed to carry out this plan in the next weeks.

We will continue discussing and sharing the progress during the RDO weekly meetings, feel free to join us if you are interested.

Also, If you have any question or suggestion related to these changes, don’t hesitate to contact us in the #rdo freenode channel or using the RDO mailing lists.

Quelle: RDO

Let Our Experts Build Your Dream Website

If one of your 2021 resolutions is to launch a business or move an existing one fully online, our WordPress.com experts can help you make it happen.

Launched in beta in the fall of 2020, our premium website building service was developed with your needs in mind. Whether you need a fast and performant eCommerce store for your products and/or services, a polished website for your professional services firm, or an educational website for your online courses, our experts can build it for you on WordPress.com, the most powerful platform for businesses and enterprises large and small.

You’ll work with a dedicated engagement manager throughout the entire project, ensuring that your vision is carried through from start to finish — freeing you to focus on the other critical parts of your business.

Interested in learning more? Fill out the brief questionnaire below, and we’ll respond within two-three business days. The questionnaire helps us learn more about your project. It doesn’t commit you to anything, but the detail you provide helps us evaluate whether the service is the right fit for your needs.

We look forward to working with you!

Take Our Survey
Quelle: RedHat Stack