I would rate it an eight out of ten.

We're customers and end-users. 

I am not a very extensive Designer since I am managing a team. Most of my team members are experts here. I am mostly trying to manage the development part. I do not know each and every detail, the intricacies of the SharePoint website.

Web development is a very steep learning curve. It takes a lot of time to become a master. Therefore, we use SharePoint to make sure that we could deliver for clients. Being in consulting, you have to deliver the outputs relatively quickly. 

I'd advise users to start exploring it on their own to get to know the menus and different options that they could get. Try different tutorials. There are plenty of tutorials available. That helps in knowing exactly what you have to do. Just start exploring the system.

I'd rate the solution nine out of ten. It's intuitive and customizable. 

It's a very user-friendly solution. 

It makes programming and designing customization easier.

I'd rate the solution nine out of ten. 

It's good. We have everything up there. We don't need to worry, and we can easily work everywhere. We don't need to worry about our physical devices. We can easily log in to any device with it. So, it's something I would recommend.

Overall, I would rate the solution a nine out of ten. 

It's a good solution, even though some users don't seem to actively use it all the time. Maybe it's the organization's fault for not enforcing its usage more. But for what we've used it for, it's been a very good solution.

Overall, I would rate the solution a nine out of ten. I would recommend using this solution for an intranet website. Apart from WordPress, SharePoint is the next point for our internal website.

I rate SharePoint Designer nine out of 10.

We are using the business version of the solution.

I'd rate the solution eight out of ten. We're mostly happy with the solution overall. 

I rate the solution ten out of ten. 

We use Microsoft 365 because it is easy and user-friendly. We don't need to customize it because we use the solution as is. The product works the way we use it. People should not get a solution based on what they see out there. They need to understand their users' needs first, then, based on that, they must select the right system. Overall, I rate the solution a seven out of ten.

The solution's stability has certain shortcomings that need improvement.

To others, I would like to say that they must know what they want to do before they embark on SharePoint.

Overall, I rate the solution a ten out of ten.

I highly recommend SharePoint Designer for those who frequently utilize quick and convenient file-sharing tools and cloud-based licensing tools. Especially if they are already using Microsoft email or other Microsoft services, SharePoint seamlessly integrates with their existing infrastructure. However, if individuals primarily rely on Google apps or related products, I believe there is no obligation for them to adopt SharePoint Designer.

I rate SharePoint Designer an eight out of ten.

I would recommend SharePoint Designer for those building a solution for communication with audiences across the globe because SharePoint Designer will ultimately be a complete one-stop solution for customers. I would give SharePoint Designer a rating of nine out of ten.

I would recommend the solution to other users and companies. 

I'd rate it six out of ten. 

Five people use SharePoint Designer within my company. Currently, there's no plan to increase the usage of the product.

One to two people take care of the deployment and maintenance of SharePoint Designer. Managers can use the product, but the technical staff uses it more.

Based on experience, I would recommend SharePoint Designer to other users because it's a product that's very easy to use, easy to set up, and provides a lot of functionalities in terms of customizing SharePoint.

My rating for SharePoint Designer is eight out of ten.

I would rate the tool a four out of ten. You need to have an idea of how you are going to use the solution before implementing it. Once implemented, you can explore the tool. You can use ChatGPT for some advice. 

My advice for anybody who is considering SharePoint is to first define your needs and then take quite a good look at the market. For tasks including document management, ECM, or a platform content service (PCS), most of the time, you will be better served by a solution other than SharePoint. If, on the other hand, you are looking for team collaboration, then SharePoint may be a good option.

Overall, I am not very satisfied with SharePoint.

I would rate this solution a five out of ten.

We have been using the 2016 version. 

I'd advise others to use SharePoint Designer if they value SharePoint. 

I would rate the solution eight out of ten. It has been very useful as a tool. 

I give SharePoint Designer a nine out of ten. We can create sites without having to code.

I recommend SharePoint Designer to others.

I rate SharePoint Designer a six out of ten.

SharePoint Designer is the best solution we have. We don't see any alternative as of now. For intranet and knowledge management purposes this is the best solution. It has great integration with Office products.

I rate SharePoint Designer a ten out of ten.

I would definitely recommend using this solution, it's useful to store the data and files.

Overall, I would rate the solution a nine out of ten.

I rate the solution an eight out of ten. 

I rate SharePoint Designer a six out of ten. There were some bugs, but when you are working on SharePoint, you have to recommend SharePoint Designer, for sure. 

We use the on-premises deployment model.

A lot of planning is necessary before deciding on a final solution or a final architecture. Planning is very important prior to implementation.

I'd rate the solution seven out of ten.

SharePoint Designer is just a tool. As there are a lot of key factors, I would recommend using SharePoint Designer online for internal collaboration platforms. SharePoint is not only a document management system, but it also handles content management systems, workflow automation, process automation, and more. 

SharePoint Online is a product that is included in the Microsoft Office 365 package, it is not part of Microsoft Azure. Office 365 and Microsoft 365 is a separate product altogether. People do use SharePoint Designer within the SharePoint 2016 and 2019 on-premise versions, but I see a lot of customers moving to the cloud, so they use SharePoint Online. 

I would rate it a nine out of ten.

We use the on-premises deployment solution.

I'd rate the solution eight out of ten.

I would rate the solution an eight out of ten. You can go ahead if you look to use 2010 or 2013 on-premises versions of the solution. However, it doesn't support the latest versions. 

 I recommend this product to any organization who wants to have a nice framework for building their apps.

I would rate this solution a seven out of ten.

On a scale of one to ten, I rate this a five because it could be more flexible.

I would rate this solution an eight out of ten.

If you are implementing SharePoint Designer in your organization, I would recommend that you use the best practices given by Microsoft, specifically in implementation.

I would rate SharePoint an 8 out of 10.

I will rate this program a five out of ten. The reason for this is that I would like to be able to use SharePoint Designer without having to buy other third party programs. At this stage, I still have to use other designing webpages because SharePoint Designer doesn't offer all the features I need. You can create beautiful pages, add the list and add a document library, but the solution doesn't offer any complicated designing features. One can only do a few simple designs. Everything has to be coded through either Visual Studio or some other solution. So I hope to see an improvement in the new version of this program. Perhaps they can add different templates where one can add banners, tabs, and lists. And even drag and drop features where one can add permissions. That would be great. 

I would highly recommend this solution. 

On a scale from one to ten, I would give SharePoint Designer a rating of nine. If they included some training modules, I would give them a ten, because that would make it even more user-friendly.

We do not need anyone to maintain the solution, we contact our consultant company if we need to.

My advice to others is to use a good consulting company to assist them with the implementation of the solution.

I rate SharePoint Designer an eight out of ten.

We're using the 2013 version of the solution.

The solution has a lot of complexity. That might work for some people, depending on the use case, but for others, that may be a turn-off.

I would rate the solution seven out of ten. I'd rate it higher, but there are other solutions that are able to better cover my needs.

This solution started as Microsoft FrontPage and was renamed at some time.

My advice for anybody who is implementing this tool is to make sure that you understand it. This tool can damage a lot if you don't know what you are doing. If you are only editing your own sites then there is not much damage you can do. However, if you have elevated access then you have to be careful. It is similar in this regard to a registry editor, where if you edit keys outside of your own personal scope then it can cause problems. You can do a lot of damage to your machine.

The biggest lesson that I learned when using this solution has to do with planning. When it comes to using this solution, it is much better to plan what you are doing in advance. Just clicking around trying to get things done is inefficient, and you will spend a lot more time than necessary.

I would rate this solution a nine out of ten.

I give the solution eight out of ten.

I usually recommend this solution to clients before any others.

I've been working with SharePoint version 2013. I would rate it as 7.5 out of ten.

I would rate this solution a nine out of ten.

We're using the SharePoint 2000 version.

The solution makes the work of estimating the requirements pretty difficult. Mainly, it is a very useful tool I can use for small to medium requirements.

If you're new to the solution, be aware that Sharepoint can be challenging, so you need to be ready to learn the solution in order to fully use it. Sharepoint involves coding; it's not like other solutions that offer zero coding. Organizations considering implementing it should be made aware of this.

If you are considering implementing it, I'd take the time to compare it to what you already have and any other options you are considering so that you are able to choose the solution that will work best for you. There are a lot of features now that are actually offered by competitors.

I'd rate the solution seven out of ten. If you were talking about the 2016 version, I'd give it a seven out of ten, but the 2013 version I would rate a six.

I'd rate the solution eight out of ten.

There are other solutions on the market. Some are more usable than Sharepoint.

SharePoint Online has been retired and we now use SharePoint Online.

I strongly recommend this solution. If you have a Microsoft account or Office 365 account, many of the customers don't know that it has a SharePoint within. If they know it, they can manage most of their internal work through it. Having the portal allows the user to manage everything. If they have Office 365 subscription, they should invest in SharePoint because it is available for them free of cost if they have their own subscription to Office 365. However, it is now hidden in the application.

Sharepoint is a good solution and they are working towards more integration with other solutions and tools that can enable developers.

I rate SharePoint Online an eight out of ten.

I rate SharePoint Designer an eight out of ten.

We use the on-premises deployment model.

I'd rate the solution three out of ten.

This product basically has all of the features that I need, but there is no such thing as a perfect solution.

I would rate this solution a seven out of ten.

In terms of advice I would give to others considering implementing the solution, I would say they should adopt the SharePoint Framework and do it with Visual Studio.

I'd rate the solution three out of ten.

In summary, this product allows our developers to do what they want to do.

I would rate this solution an eight out of ten.

On a scale from one to ten, I rate this solution a seven. I like the user experience level and there were some small issues, but I can't remember what they were. It was a long time ago. If Microsoft will keep on supporting the program, they should fix those small issues.