Our core goals for IP.Board 3.3 where to clear up the moderator tools, make IP.Board more efficient for larger communities and improve SEO.
We've already blogged twice on our SEO improvements outlining tweaks to improve good keyword density, reduce crawl errors and improve good keyword placement.
Our own company forums are very busy and get a lot of traffic and we monitor the data via Google's…
During each release cycle we often take some time out to assess performance and look at ways to improve in this area. We're also in a unique position to have first hand experience at hosting tens of thousands of IP.Board installations via our own hosting network.
We also work closely with our clients who constantly give us feedback on how IP.Board is performing and let us know about any areas th…
While we have discussed many great things you can expect to see coming in IP.Content 2.3 already, we've got a few miscellaneous changes that we wanted to let you know about, but that weren't necessarily grouped into a single "theme". Still, we felt you would be interested to hear about these changes, so I've taken a moment to compile this blog entry, discussing some of these odds and ends for tho…
Anyone that runs a lively and thriving community knows that now and again you have to make the hard decision to ban a member. IP.Board has a powerful set of tools built in to manage this for you and you can ban a member for a set number of days or permanently with a few clicks via the warning system or the ACP member management system.
Currently, there are two ways to ban a member. One is to fla…
As part of our goal to improve the usability of IP.Content, particularly for non-coder administrators, we've used the 2.3 release to look at ways of reducing or eliminating the amount of code that needs to be written in order to create great websites.
In the current version of IP.Content, blocks require individual templates (entered as part of the wizard process), and the default, unedited HTML …
As part of our continued effort to strengthen existing functionality in IP.Content 2.3, and bring about a more consistent and reliable experience for novice and advanced users alike, we have implemented support for IP.Nexus blocks in IP.Content 2.3. IP.Nexus is our powerful e-commerce application, allowing you to monetize your site through the use of many great features such as a storefront, user…
IP.Content 2.3 development is progressing nicely. We are sticking to the four core points we wanted to address with the release of 2.3, namely: usability, consistency, SEO, and strengthening the existing feature set. All of these points tie in together and compliment each other nicely, and addressing these points together will allow for an easier to use and understand yet even more powerful prod…
IP.Board has featured a reputation system since 3.0, allowing users to give positive or negative reputation to posts, as well as content in other apps in the IPS Community Suite (blog entries, gallery images, etc.) as well as content in third party applications.
In IP.Board 3.2, we enhanced this by adding a new way of viewing the reputation system, in terms of "liking" content as opposed to givin…
With every release of our products, we like to spend some time identifying areas which can be improved slightly, and small feature suggestions we can use. 3.3 is no exception, and I wanted to write a quick blog entry to highlight just some of the smaller enhancements we've made to 3.3 to make the product more powerful and easy to use. Login autosave
In 3.2, we introduced a login popup box whe…
We hope that everyone is enjoying reading about the upcoming changes you will see in IP.Content 2.3. As we outlined originally, our focus is on four primary goals: usability, consistency, SEO and strengthening our existing feature set. One common usability issue our clients have pointed out is that after they create a page, there is not an easy way to link to the page in the primary navigation b…
Tagging is a powerful feature made available through the IP.Board framework that allows you to collect "tags" for submitted data, either through an ad-hoc system whereby the members provide tags at will, or through a closed system where the available tags are pre-defined. Tag support in IP.Content is, arguably, the number one requested feature, and since we try to listen to our customers and deli…
Development of IP.Content 2.3 continues, and while we have many more great things in store for this release, we wanted to take a moment to tell you about two new features you can expect to see in this release. Many of the recent blog entries have described consistency improvements, SEO improvements, and other integration changes, but we wanted to make sure you knew that this release would have a …
.thumb.jpeg.beabd3e950acc9626a39df2efa937da3.jpeg)
