The easy part is now out of the way. I have installed IP.Board and IP.Content. For testing and initial purposes this is considered a testing license. There is an Admin and Guest account which people can use to post comments and access the site. No one will be able to register. Once I'm done with this project I'll transfer the active IP license over to it and go live with the site.
URL: http://www.pdxgaming.net/forums
Guest Username: Guest
Guest Password: test
At this point we have the base IP.Board and IP.Content with the demo article system. Now originally when I started using IP.Content when it first came out, that was not available. I do have to say it was definitely something that was missing from a base install of IPC. With it in there, just by itself the article system does have the makings of having the base operations of something like Wordpress. You have an article (blog) system with comments, categories and an interface on the front-end instead of having to do everything within the ACP (Admin Control Panel) which I initially did the first time I used IPC.
IPB Wrapper or to Not IPB Wrapper, That is the Question...
The main decision at this point is to decide whether to use the IPBWrapper or not for the IP.Content. I've played with an used both of them previously. The advantage of the IPB Wrapper is that I can offer multiple skin/theme options to users. That will carry over to IP.Content. Without using the wrapper I can't really do that easily. That kind of defeats the whole purpose of having a seamless, integrated site if they look different.
Not using the IPB Wrapper I have found it easier in my opinion to make adjustments to IP.Content pages. In the past I've had issues with settings on the IP.Board side effecting certain id/classes on the IP.Content side. That can be over-ridden but it does make skinning in my opinion sometimes cumbersome.
Since this is going to be initially for game site, mainly Trading Card Games and some miniatures. I do have the advantage of knowing the client base. Gamers like to personalize and customize. Without using the IPB Wrapper I won't have that as an easy option.
For now I'll use the IPB Wrapper. At least for now.
URL: http://www.pdxgaming.net/forums
Guest Username: Guest
Guest Password: test
At this point we have the base IP.Board and IP.Content with the demo article system. Now originally when I started using IP.Content when it first came out, that was not available. I do have to say it was definitely something that was missing from a base install of IPC. With it in there, just by itself the article system does have the makings of having the base operations of something like Wordpress. You have an article (blog) system with comments, categories and an interface on the front-end instead of having to do everything within the ACP (Admin Control Panel) which I initially did the first time I used IPC.
IPB Wrapper or to Not IPB Wrapper, That is the Question...
The main decision at this point is to decide whether to use the IPBWrapper or not for the IP.Content. I've played with an used both of them previously. The advantage of the IPB Wrapper is that I can offer multiple skin/theme options to users. That will carry over to IP.Content. Without using the wrapper I can't really do that easily. That kind of defeats the whole purpose of having a seamless, integrated site if they look different.
Not using the IPB Wrapper I have found it easier in my opinion to make adjustments to IP.Content pages. In the past I've had issues with settings on the IP.Board side effecting certain id/classes on the IP.Content side. That can be over-ridden but it does make skinning in my opinion sometimes cumbersome.
Since this is going to be initially for game site, mainly Trading Card Games and some miniatures. I do have the advantage of knowing the client base. Gamers like to personalize and customize. Without using the IPB Wrapper I won't have that as an easy option.
For now I'll use the IPB Wrapper. At least for now.


Create a custom theme







