SharePoint: From Concept to Creation to Impact + Live AMA
NOW ON DEMAND SharePoint is the world's most flexible content platform, with over 2 billion files added daily and more than 2 million sites created each day. It's the only content platform that spans the entirety of your diverse content management needs - from engaging pages and branded site building to powerful workflow, document library, automation and collaboration needs. At this event, we shined a light on the latest SharePoint capabilities and share glimpses of what some of our customers are doing with it. Get clarity on what's available, tips and tricks, and the boundaries you can now push with the latest. If you use SharePoint to create sites, publish news, manage workflows, collaborate with peers – or are simply curious about how agents can transform your intranet – this event is for you! Skill up your SharePoint IQ with the latest on: Simpler authoring & more compelling content – Lower barriers to create professional-looking content and ensure you can harness the best of what the web has to offer for your intranet Greater engagement & reach – Scale your message to meet people where they work. Powerful workflow, automations and agents – Build automated subject matter experts and save your team time while managing and automating content workflows. We also held a dedicated time during the event for live Q&A where you will get to interact with multiple product makers – bring your questions and feedback. Be inspired! We can’t wait to hear what you think and how you plan to get even more out of your beautiful, smart, high-impact intranet and content management solution. Read Jeff Teper's new blog post, "SharePoint: Using agents, AI-powered authoring, and automation, for high impact content management" | This provides more depth and detail about all highlighted intranet and AI innovation and new assets generated for the January 29th, 2025, SharePoint event "SharePoint: From Concept, to Creation, to Impact + Live AMA": https://aka.ms/SharePointEvent/blog Visit this event's new microsite to access all new videos, adoption resources, hackathon details, and more: https://aka.ms/SharePointEvent/Adoption. And make a plan to join in the SharePoint Hackathon - A DIY event to see what you do with SharePoint pages, portals, and more - with the potential to get your work featured: https://aka.ms/SharePointHackathon Related resources "Ignite 2024: Agents in SharePoint now in general availability” by Adam Harmetz. Microsoft Ignite 2024 breakout session: Reimagine content management with agents in SharePoint. Subscribe to the SharePoint blog. Follow us on social. Learn more about SharePoint.
Multi language support for "News recommended for current user"
Hi guys, recently we launched our new intranet based on SharePoint Online. To provide a good overview we added the news webpart using the news source "News recommended for current user" to our landingpage. Most of our news are posted in two languages. The news source "This site" can differ between the languages and only shows one instance of every post. The news source "News recommended for current user" is not differing here. Every user sees posts twice in the webpart, which is not really helpful. Does anyone know if we can improve the situation here? The webpart on our landingpage only shows four posts which gets reduced to two posts since every post is shown twice. Thanks in advance!Global Navigation not visible for everyone
Hi all, we are currently setting up our Intranet with the modern experience. Therefore we enabled Global Navigation which is supposed to show the same navigation items as the home site. This worked good until I started to do some testing with the permissions of a user - Lets call him Paul. I created a security group with dynamic rule. Paul is member. This security group is managing the access to my home site. Paul can access the home site and see the site navigation. He also sees the Icon which I have set for Global Navigation but if he clicks on the icon an empty pop up appears. It seems like he ca access Global Navigation but is unable to see the navigation items. Does anyone else have had this problem? Thanks in advance!
Sticky, full size top-nav for SharePoint intranet.
So we're trying to build a corporate intranet which gives a web-like user experience using a SharePoint Homesite as the hub. We're pretty happy with the results so far, but there is one thing that is getting on my nerves... You are able to set a cross-site hub navigation with nice dropdowns, but when you scroll down the page a little, the nav/banner collapses leaving only a small bar with a logo and no links. Users must then scroll back to the top to see the links. I'm sure this is a helpful feature for some (?!) but if we could turn this off, and be able to control whether it happens, that would be great. And easy to implement I would imagine?
Intranet Portal based on SharePoint
Ever since we started looking for a board management portal that is based on SharePoint, and kind of in the process of adopting one. We started to think, why not an intranet portal software that is based SharePoint, that way we could integrate with intranet portal all the other solutions that we have already built on our SharePoint intranet. With this SharePoint we are aiming for some changes in the organization. First of all integrating all internal communication under one software, we already use SharePoint so all our documents are already here, if our intranet is based here, then document sharing and access could be more easy right. Also we have offices around multiple locations, an intranet will also help connect all these offices. Another common problem that our employees face now is finding the document they need to work on, we found out that a SharePoint intranet portal software with unique department portals could solve that issue. Also we are aiming that this intranet portal will reinforce our brand identity with our employees. I was amazed at the response you guys gave on my last query. Hoping you guys could help me with this one also. Thanks in Advance.
Intranet Site Structure with Hub Sites
Hi, all. I have a project currently where I am to build out a sample of our existing Intranet using modern sites, so that we can show leadership not only how much we will benefit from the transition (new technologies that become available to us, etc), but also how the transition will look. IN this new "hub site - associated site" structure, however, I'm a little confused about the layout. In the end, I want our new Intranet to be structured in a way that will allow us to not only take full advantage of all of the most current technologies, but also future-proof it as much as possible. Therefore, I am seeking advice on how to accomplish this. Currently, the section I am building in my sample currently exists in our Classic Intranet, as: Intranet > Product Org > Products and Services > ProdOps 1. The first question I have is a bit of a clarification: in this new "hub sites" and "associated sites" world, is it semantically correct to create sub-sites anymore? Or do we just make sites and associate them to each other? 2. Secondly, I understand that we create Communication sites and convert them to the hub Sites. In my structure, I would probably want to originally make the Intranet and Product Org sites as Communication sites, convert them to Hub sites, and then associate them all with each other, correct? 3. For a site like Products and Services (which currently has sub-sites), what types of Modern site is recommended? It's not just a single team, and will either need to link to (or house directly) document and asset libraries. Originally, I thought a Communication site, but then I read that those cannot have sub-sites, and that if I want those, I should consider Publishing sites instead. But THEN, I read that publishing sites are not available as modern sites, and that doesn't work for us. 4. One part I am trying to incorporate in this new structure is our wiki. I think it would work great to have each component of the wiki to be in each department's own site as wiki page libraries. HOWEVER, I read that with wiki page libraries, we cannot control the entire layout of the page, only the content. We will want to design it all out, with full control of the pages with SPFx, Office Fabric UI, Fabric React, and other technologies. Therefore: Would an Enterprise wiki be a better idea? Is the Enterprise wiki a modern site? Would I built it as a separate site and just associate it to each and every other site? 5. Associating sites: Currently the job of associating sites seems extremely manual and tedious and error-prone (leaving out a site that should be associated to one of the millions of others, seems inevitable), so what is the best practice to automatically ensure sites re associated with each other? Is there a way to do this? Thanks, guys! The answers to these questions will help me get started! Thanks, in advance! ~Charisma
