File Structure

• via_CMS

  • /admin/

  • /css/

  • /filemanager/

  • /images/

  • /includes/

  • /js/

  • /source/

  • /thumbs/

  • /vendor/

  • .htaccess

  • gallery.php

  • index.php

  • page.php

  • posts.php

This is the public_html content that goes onto the host server. Other than the admin folder (CMS), the /includes/, .htaccess, index.php, and page.php stand out as most important for development / launch.

We'll review /includes/ in the next page.

We'll review /admin/ in page after.

• /css/
  
  • Front-end site styling.
    
    
• /filemanager/
  • Plugin used by CMS to upload & download files using the Media Library directory / tinyMCE media picker
    
    
• /images/
  • Any images fundamental to the site, such as the logo or misc icons, usually the index hero image as well
    
    
• /js/
  • Misc JavaScript plugins & code. Probably should move the plugins to vendor...
    
    
• /source/, /thumbs/
  • Where the filemanager plugin puts user uploaded files & thumbnails
    
    
• /vendor/
  • Misc plugins, plus composer config
    
    
• .htaccess
  • reGex for standard page vanity URL

    • RewriteRule ^([a-zA-Z0-9]+)/?$ page.php?url=$1 [L]
      RewriteRule ^([a-zA-Z0-9-]+)/?$ page.php?url=$1 [L]
      
      

• index.php
  • Landing content goes here. Usually styled uniquely compared to interior pages. Hard coded to display the Home page's content in the Pages directory
    
    
• page.php, gallery.php, posts.php
  • Each correspond to an installed directory. Specifically Pages, Gallery, and Blog respectively.
    
    
  • I considered writing a routing strategy to keep the root directory clean, but until more than six or so directories are installed, navigating to a views folder for minor template variations seems unnecessary.