With an experience and expertise of standing hundreds of SharePoint Implementations and custom business solutions, we have had the opportunity to dive deep into the platform as a technology and understand its architecture to the core. We have successfully built frameworks that extend the architecture to build custom solutions and delivered many packaged products. We exactly know where it rocks and where it lacks.
SharePoint is one of the products that vary quite a lot compared to other products that developers has to engage with. If we look at what SharePoint had in 2007 the improvements in 2010, it has built up lot of potentials to it. Comparing 2010 with 2013 version is another big ask. So will these customization we make will affect a migration and performance after migration? The answer is YES. But this does not mean we should not customize SharePoint.
As I posted few days ago, here Cool usability enhancements in SharePoint 2010 using JQuery, there are number of ways you can make user interface of your sites more usable and personal.
The next step to those usability enhancements is saving user preferences, and what better way to do it than using User Profile service; well turns out there might be a better way.
SharePoint enables developers to quickly deliver prototypes and solutions to users. However, just as quickly, users respond with enhancement requests and new requirements, often overwhelming the development team. This white paper explores the challenges that SharePoint developers face and details a set of best practices for responding to those challenges, so that you can make the most of your SharePoint investment.