ranyefet

TV.com was an example. This goes as well for movies site, songs database, books database and more... I want that the core system will have all the common features of this sites like: users generated content, profiles, users lists, permissions.. and the only things that will be different is the content types/fields. What is the different between imdb/tv.com? I'm thinking about running a local site for users in my country for local series. Thanks for all of your comments. I decided to build it my self so i could control every aspect of the application but it's a lot of work. I'm still not sure which framework to use. I'm familiar with CodeIgniter, but I really liked FuelPHP Do you guys have any suggestion on how to structure the database for the different content types & revisions?

Actually I was planing on using CodeIgniter but I want to build this site once and maybe use it for more similar sites (movies db, games db) That's why I was looking for something that will handle the different content types and will allow me to add/edit/remove fields as I like. I also want to have an nice API like PW does. When you combine all that, It's pretty big project for one developer. Basically I need the following: 1. API to handle the database: content types, content relations, custom fields, users, roles, permissions etc.. 2. The same API will be used for the site itself and REST API 3. Content will have revisions 4. Smart caching system I want to build the API so that it will be independent and can be used anywhere with any framework or just including it to simple PHP file and do something like: $app->find('show[id=1]'); Maybe you have few advises for me what is the best way to accomplish that? (And you're welcome to move this topic to different forum) Thanks, Ran.

Hello All, First I like to say to I read the API and I think you did great job with PW! I like to build a website and I'm not sure if PW is the right solution. My site that I'm planing is something similar to: http://www.tv.com My site will have the following content types Generes: - Action - Drama - Comedy Series: - Lost - Prison Break - Friends People (Producers, Actors, Directors): - Wentworth Miller - Ryan - Michael Characters: - Michael Scofield Seasons: - Season 1 - Season 2 Episodes: - Episode 1 - Episode 2 Series is the main content type which will have few genres, seasons, episodes and people. A series will eventually look like: - Prison Break - - Seasons - - - Season 1 - - - - Episode 1 - - Actors - - - Wentworth Miller - - Characters - - - Michael Scofield All the site data will be user generated and the site will act as a Wiki system. Every user will be able to login and edit any data on the site. any changes to data will be needed to be approved by the moderators. The system will need content revision built in for each content type in order to revert changes. Also Users will be able to create their own lists for tv series: plan to watch, watched series. Of course the system will include user profiles, notifications, messaging etc.. I'm plan on using PW only to create the structure of the site and uses PW API for creating the front end. I'm only going to use the admin panel once and i'll create my own admin panel for my users & moderators. Also going to use the API in order to build REST API for my site. Basically I looking for an API that will handle my database and will allow me to create lots of complex content type and relations between them. I really like to create my site in a modular way so that If I want to use the same site to build a Movies database I'll only need to change the some fields. Do you think that PW is the right solution for this task? or I should built something from scratch?