Forum Discussion
Modern Publishing Sites
Hello,
Are there any news regarding the Modern Publishing Sites that should complement the Modern Team Sites?
We're really waiting for those to be released in order to kick-off our new intranet project.
To avoid any misunderstanding I'm talking about this kind of publishing experience:
Thank you in advance,
Ben
- Here in the same situation. I saw this functionality able to a user in a microsoft video https://www.youtube.com/watch?v=x8tgKBXmmPg
here is the frame: http://imgur.com/a/NEIKX See MS comment here https://techcommunity.microsoft.com/t5/SharePoint-Blog/Reach-your-audience-via-SharePoint-communication-sites-in-Office/ba-p/70079 Looks like Q2 for first release and Q3 worldwide
I don't think businesses should be expected to beta test every service and software for another company while paying for the privilege.
The only group that has whole-hearted gotten behind the Office365 platform has been our Project Management team.
Then Microsoft pulled site mailboxes, even from PWA. Oops.
Now, we have a PWA site for a project, a Group for the same project (which our PMA is super thrilled about, let me tell you; he's got so many groups it is utterly ridiculous) so that they have a shared mailbox, and never the twain shall meet. It's pretty awesome, in that not really kind of way, when there are two sites for one function. So, where's all that information? Dunno. I'll need to look in the umpteen different places it might be. Case in point: Teams files. Let's say I have file.doc in a folder in the channel "General". I make a change to it, or want to announce that the file is there. It makes a copy and puts the copy in the root of the General folder. Oh, and different channels cannot see other channel files, because the view is one level back (the only workaround is making a SharePoint Document Library tab. Why even have the Files tab? Who thinks this stuff through? Oh, that's right we do. "Oh, you'll want to waste another X amount of time not doing your job, and doing ours by visiting UserVoice and telling all your friends to vote for your 'well, duh' functionality." Unacceptable in the biggest way possible. Again, we are paying Microsoft. There should be an expectation of enough stability to not be paralysed by tool overload and shifting priorities of a product management team.
Every few months, we have to up-end our processes, reinvent them, and then retrain. That is just not a way to run a business. I get Agile. I get DevOps. But you know who loses out with the Microsoft implementation of those? The customer; the one that was supposed to be front and center.
I know they are in a transnational period. They will forever be in a transnational period. That's fine. The process-breaking changes every few months: not fine, nor will it ever be.
I'll be glad when the Product Management team overseeing the Office 365 platform (if there is such a group, and not little groups that never talk to each other for each bit of the platform) takes a look at the harm they are doing to their clients, the third-parties that have built their businesses around custom solutions and support, and figures out that a more sane cadence is likely the best approach.
Oh, and the Communications site business... still doesn't do anything to answer "What about existing content?"
- Have you seen the new Communications Sites? I think this might be where this went. Looks pretty good. https://www.youtube.com/watch?v=WEnQKzzbvfo Not sure when it will arrive, they say the next couple months. :)
- Correct...the new "goodies" are around Communications Sites :-)
Where does that leave the 'top-level' sites that already exist?
We've got xxxxx.sharepoint.com, which is the top-level site collection in SPO.
It, and all the content below it (and any content that was created before Modern started rolling out) are all in classic. What becomes of all that content? Heck, I created a list a couple of weeks ago; it came out being 'classic'. I created custom collumns, custom content types, set up the list to use everything I had created. Of course, I wanted to make use of SPFx so that I could make a form that didn't require a user to click through four different things just to get to the form. Guess what? Can't use that SPFx 'webpart' on the classic site. So, I get to go back to InfoPath and create forms, then create a new page (and hope like hell it doesn't decide all on its own to be a modern page, since we've had both classic and modern spring up with no rhyme or reason) and add some js to create a couple of buttons to call the appropriate InfoPath form. ARGH!
For that matter, why does the SharePoint 'app' in the App Launcher open the goofy 'almost Delve' page instead of the actual SPO homepage (top-level site in tenant site collection)?
If Microsoft wants the homepage for SPO to be Delve, get rid of the SharePoint 'app' and let it hide behind everything else. From there, admins can create a custom 'app' and then tell all of their users to manually (come on, really) add the app to their App Launcher home.
I'm having a heck of a time getting SPO adoption. Things like this, along with trying to explain the intracacies of the different applications and locations are a nightmare. I get it, but I spend an ENORMOUS amount of time looking this stuff up (when I could actually be getting things done). I get what Groups are, how they are important, how they tie things together. I get Teams. I get OD4B vs SPO vs Groups-based SPO sites vs Teams. Explaining the abstract, sprawling ecosystem to all of these people that are used to there being a company-wide RW share mapped to (InsertLetterHere): is nigh-on impossible. The more I train people, the more things change, the more applications are released, the more confused people get. The level of frustration is through the roof! People that were using personal Dropbox accounts (and sharing them) were told they could no longer do that. Guess what? They are back, and I don't blame them. In the time that we purchased our initial subscription in Spring 2016, to now, there have been three major changes, just in how OD4B works! First, it was "no SharePoint", then it was "SharePoint, if you use this version, and add this registry entry", then it was "Okay, we are letting you use SharePoint, but we are taking away your ability to share OD4B files from Explorer". So I get to retrain everyone every few months. This is completely unsustainable. I have been unable to get buyin for migrating data off of fileshares because no one knows how to use SPO or OneDrive, and they don't trust it, either!
<sigh/>
Was pondering the same question today. Comparing our first release tenant (TEST) to PROD tenant.
Along with when is a modern site REALLY a modern site?? As I can create a new site in PROD (based on the Team site template) and it looks and feels like a classic site but when you create a new page it creates a "modern" page, using the site page content type.
But I still don't have the new look and feel in the site contents, so hence my query is this a pseudo modern site or am I just missing a feature (hidden for now!).
As some of you mentioned hopefully we get some answers in the virtual summit next week.....
- Can we expect a roadmap on this topic at the upcoming SharePoint Virtual Event being held next month?
- I'd expect nothing less :P
Ha! I'd hope so.. From reading Jeff Teper's tweets it sounds like the product teams have been pretty busy in preparation for this event.
- I'm exactly in the same situation with a new customer that want a time estimate with Modern Publishing Pages and it's bit frustrating.
I hope it's coming soon.A couple of hour clients are now also in the same situation. I would be nice to have a more detailed time estimate or some additional info e.g. screenshots of the social integration, publishing site "types"
I'm currently advising my clients to proceed forward with Classic publishing pages for their Intranets based on what I've seen with the Modern Team Pages. The Modern concept is fantastic but what's been released thus far doesn't address common needs and there's a few releases after the initial before some of the bugs are worked out. Without a date for even the first release of Modern Publishing Pages, we are giong full steam ahead with Classic pages.
Greetings all,
I too am wonder what the hold-up is on the New SharePoint Publishing Experience TNSPE) !
What confuses is me is this:
1. there are myriad (Microsoft) videos since May of 2016 which are promoting The (also new) "SharePoint Framework";
2. The SharePoint Framework appears to "need" (or at least benefit from) The New SharePoint Publishing Experience (see Daniel Kogan's very exciting video back in May 2016);
3. The SharePoint Framework itself was announced as "v1.0" just last week; so...
I would think the NSPE would be READY at the same time?
Yet I find myself wandering around all my various Office365 websites, and I see neither hide nor hair of the new experience.
Has anyone tried reaching out directly to Daniel and perhaps the Microsoft Mechanics team?
Pernille-Eskebo Mechanics: guys - any word on the NSPE ?
Cheers,
-Mark
FOLLOW-UP...
ONE DAY after me posting the above message wondering where my company's New SharePoint Publishing Experience was (in our Office 365 environment)...... this morning SUDDENLY we now HAVE the new experience !!!
COINCIDENCE ??
:-OSUGGESTION FOR ALL MEMBERS WHO ARE STILL MISSING THE NEW SP PUB EXPERIENCE:
1. POST a note HERE that you don't have it;
2. WAIT 1 days (for the Office365 NSPE leprechans to secretly visit your website & install NSPE);
3. CHECK your Office365 environment; you WILL have the new experience !;-)
I'm not kidding guys - the NSPE literally just APPEARED TODAY !
Cheers
-MV- Can post some more info of your experience with this as many people are "hoping" it to be true. It's quite odd that MS has not released any information about this being available yet you seem to have it. Normally you would expect quite a fanfare from MS about something like this.
I am waiting for this as well, would like to convert our Intranet to the new publishing layout if possible. Hopefully this will be released soon.
- Mmm...you me re-build / migrate? I'm not sure if we will have the ability to do this layouts conversion you mention :-(
It is more of a re-do of our current intranet using the new publishing templates. We are about do for an updated look and feel anyway. :)
We are in exactly the same situation, waiting on this new experience to be released before we work out what to do with our old 'intranet'. The RoadMap seems to say H1/2017.
- AFAIK, there are not new news about new publishing features in SPO...no ETA or indication about when they will be ready
Thanks Juan.
