IP.Content 2.3: What To Expect

I'm pretty techie minded and never got used to the damn thing lol.

Since version 2 it's getting better and better. They listened to user input on that much faster than they did with SEO.

Indeed. I hope they implement a kind of frontpage manager, where you can drag and drop blocks similar to vB's grid system. Let's wait and see

Usability is the focus of the next version, actually.

http://community.invisionpower.com/blog/1174/entry-7038-ipcontent-23-what-to-expect/

Slowly but surely it's getting better and user friendlier

IP.Content 2.3 Dev Update: ACP Interface Improvements [Part 1]
IP.Content 2.3 Dev Update: ACP Interface Improvements [Part 2]

We will see. There's a big difference between claiming user friendless and actually implementing it.The users will be the judge of that.

I'm sure you won't like it, no matter what they'll do.

I'm with Azhria, in thinking Content was ultra-powerful and outside the abilities of the average forum admin. Actually, I would have been quite happy to have had a script like GARS, rather than all the abilities Content had. I could install GARS and set up an Articles forum in a matter of minutes.

And then, when it came to styling Content, it was typical of other IPS applications. You could change this in here and then change that over there. But remember, if you want to change this one bit here, you need to find that one obscure template. And then, in order to enable that template, you needed to know the place to change one setting, which was hidden in an obscure location. <looking over my shoulder, wondering when bfarber will be here to tell me I'm wrong, all wrong>

I truly liked the tight integration between IPB and the official applications. I hated the frustration that arose from trying to use them. And when I recall I was primarily trying to use Content to do an article library, I am suddenly reminded I can do all that from within XenForo's core, and no add-on application (and it's associated license renewals) required.

Thankfully, Content is in the past for me. And I really have just one memory of it. Content = Frustration.

If you use the board wrapper it's quite easy to keep the look of your style. Of course, you have to use the same css classes in your blocks and pages.

I really doubt you can do an article library in XenForo's core without any additional programming (I own a license, so please give me a hint where to find this feature) and if you can do that, I can't understand where your problem with IP.Content was.

Misunderstanding on my site. Those are static pages, I thought about an article database with different dates, comments and so on.

Code:

#content {
    padding-right: 300px;
}
 
#ptSidebar {
    float: right;
    margin-right: -290px;
    position: relative;
    width: 280px;
}

This is my only additional CSS to get the layout for my IP.Content page with board wrapper and it works on all areas within IP.Content.

I don't go by words, I go on implementation. And throw in whether IP Content does improve on "User Friendliness" I will wait and see. I remember one of the developers actually implementing a feature I mockuped and promised they would finish it up when they had more time but they screwed that up by introducing more clicks than they had to and also introduced a 1990 popup window.

That to me shows the ear is not listening so again I will give this a thorough test whether it's user friendliness is improved as I go on features and improvements through testing not because a company says it will be friendly. I'm not that easily won over.

We will see on release day.

I wasn't being real clear, myself. No, I wasn't trying to build an article database. I have an automotive forum and occasionally, a user will post a reply or a post showing how to deal with some technical aspect. We always liked to get those set aside, for future reference. Using Content for that purpose was akin to taking an F-117 to a fist-fight.

XenForo's static pages will work just fine for what we're trying to do.

The Wrapper function will pull all IPB Stylesheets and use them for the page, so you can just use CSS classes and the page will inherit the color scheme from the skin.

It will also add the Header, Navigation Breadcrumb, and Footer automatically. So all you need to focus on is the content. Similar to XenForo pages, in that you still have to use HTML and the correct CSS classes and id's in order to fully inherit the skins colors / customizations. And all utility methods will be readily available, so you can build pages with a sidebar or two using the ipsLayout classes.

Interesting.

What?