PDA

View Full Version : Block diagram ?BluePrint stack? for vBulletin???


pcaliban
11-15-2010, 03:28 PM
Reading August 24th 604 Page manual (without page numbers in table of contents!..arrrrrg)
:confused:

Is there another shorter non-admin manual or Thread or set of Threads someplace that explains the vBulletin Concept and offers some Tutorials??
I tried the most basic ?make your own page? and that failed! Not a good start!

The Basic Question:
IF I want to create a NEW webpage that appears in the MAIN top bar Menu, which has a defined LOOK and Structure for its content? Like a new CAREERS page/menu pick

What is the process.?? Suggestion for a TUTORIAL or YOUTUBE??
Is there a basic building block diagram ?BluePrint stack? for vBulletin.

HOW?..?
Do I create a Section? Called Careers?
Do I create a Page called Careers?
Do I control the MENU? Via CMS ADMIN? Or STYLE&TEMPLATE ? via CODING?
Do I create the GRID first, then create a LAYOUT. (YEP)
Do I only create Static HTML for the Career Page/Section via Articles?
Do I use Widgets with HTML code, that are placed on the Layout, which is driven by the GRID?!

Is there a basic building block diagram ?BluePrint stack? for vBulletin.
This is not a Portal Framework with Forum, blog, Modules like a DNN, Concrete5, or Liferay?

First 90 Pages about setups A-OK (ton of setup - beads of sweat!)

I was looking for a common APPENDIX to see how Things are Defined in the manual:
I am trying to understand the vBulletin Conceptual Framework and LINGO
Grid, Page, Section, Widget, Layout, Article.


CMS (pg 91)

The WORDS and ADMIN backend seem reminiscent of Joomla feel with same 'LINGO' like 'Article'

For CMS and Style/I see most functions reside on the ADMIN side for ?BULK? stuff, but surprised to see the ability to create a PHP or Static page along with the Combo box value 'create article' on USER side.

Not even sure best practice to include non-vBulletin PHP code in the VB Framework (iFrame, Include, CODE??)

On the user side I guess ?inline content management? like a DNN Portal allow 'an editor' to go to a webpage and 'add articles'.

On the ADMIN Side I see all the control on STYLES & Templates and CMS

? SO ..A GRID is HTML defining how Widgets are placed on a Layout, which some how gets connected to Section,which sounds like a PAGE, but maybe not, cause I see the Non-Admin side allow for PAGE creation. I see no direct OPTION to control MENUS as one might in Joomla or DNN?
o (my 1st read of the manual I thought LAYOUT would be the GRID and LAYOUT would be the TEMPLATE) WRONG!:(

Seems I have been super wrong??..
(I understand WIDGET to be vBulletin code or my snippts of code)
(I understand the GRID is some XML(<DIV> structure/syntax for Layout)
(I understand LAYOUT to be the location for the WIDGETS on the GRID)

? I see a STYLE(not just meaning CSS) as a long list of TEMPLATES and Style variables(CSS Class Tags??) (scary)

So a STYLE is the overall look? driven with TEMPLATES, CSS, STYLE Variables?? Which are driven by a GRID that is part of LAYOUT?

I saw a USER side ability to create a PAGE, but no such option on the ADMIN side?
I do not see an ADMIN Manage PAGE option? And clearly do NOT get how a PAGE or SECTION falls into the Main MENU system without coding?!.
Guess a SECTION is NOT a PAGE; WHEN is see PAGE setup has the YES/NO option for?Full Display in Section Page?

Is there a basic building block diagram ?BluePrint stack? for vBulletin.