Introduction
Sngine is a powerful and flexible social network platform designed to help webmasters build vibrant online communities. To make the most of it, understanding its file and folder structure is crucial. Familiarity with the architecture enables effective customizations, efficient troubleshooting, and seamless integration of new features. In this detailed guide, we will explore the core components of Sngine’s file and folder structure, explaining the role of each folder and file in the system’s overall functionality.

Why It’s Important to Understand Sngine’s File Structure

• Customization: Enables developers to modify or extend the platform to suit unique requirements.
• Troubleshooting: Speeds up debugging by identifying the exact location of problematic files.
• Security: Helps secure sensitive files and data by understanding their hierarchy and access points.
• Optimization: Identifies opportunities for performance tuning, such as caching or file minification.

Overview of Sngine’s File Structure

Upon downloading and extracting Sngine, you’ll find the following core directories and files in the root folder:

1. content

   • Purpose: Stores assets like themes, plugins, images, and language files.
   • Key Subfolders:
     • themes: Contains the default and custom themes. You can customize styles and layouts here.
     • plugins: ( custom made )You can create one such folder to Houses third-party plugins to extend Sngine’s functionality.
     • uploads: Includes user-uploaded files, such as profile pictures and group images.

2. includes

   • Purpose: Contains the backbone of Sngine, including core PHP classes, functions, and database interaction files.
   • Key Subfolders:
     • functions.php: Hosts the main classes such as user authentication, session handling, and APIs.
     • class-user.php: Handles server-side logic, processing user requests and directing data flow.
     • class-pager.php: contains pagination logic
     • class-image.php: contains logic for upload and processing images as routed from upload.php in ajax - daat/uploads.php

3. templates

   • Purpose: Stores the Smarty templates used for rendering the front end of Sngine.
   • Key Subfolders:
     • widgets: ( Create Custom)  Contains reusable UI components like sidebars and feeds.
     • themes/templates: Includes layout files for user-facing pages, such as the homepage and login page. Houses templates for the admin panel interface and front end interface.

4. vendor

   • Purpose: Includes composer dependencies and third-party packages required for Sngine to run.
   • Note: Avoid modifying this folder directly, as updates might overwrite changes.

5. content/languages

   • Purpose: Manages localization and language support.
   • Key Files:
     • .po and .mo files for each supported language.
     • Default language settings are managed here.

6. .htaccess

   • Purpose: Contains Apache configurations for URL rewriting, caching, and security rules.

7. config.php

   • Purpose: The central configuration file for database connections and system settings.

8. index.php

   • Purpose: Acts as the entry point for the application, initializing the system and handling routing.

Deep Dive: Understanding Key Components

1. content/themes

This folder is where you’ll spend a lot of time customizing your Sngine site’s look and feel. Each theme folder contains:

• css: All the stylesheets used by the theme.
• images: Theme-specific images.
• templates: Contains the Smarty templates for layouts and UI components.

2. includes/core

This folder hosts the essential PHP classes that drive the system. Key files include:

• class-user.php: Handles user-related functionalities like registration, login, and profile management.
• class-db.php: Manages database interactions using prepared statements for security.

3. templates/widgets ( MOT IN ORIGINAL CODE, BUT OUR STRUCTURE AT MAKEMYTHEME PREFERS SO)

Reusable components like sidebars, footers, and notification popups reside here. For example, the pro-members.tpl file displays a list of premium members in the sidebar.

Modifying Sngine’s Structure

Example 1: Adding a New Widget

1. Step 1: Create a new .tpl file in the widgets folder, such as custom-widget.tpl.
2. Step 2: Include this widget in your desired page template using:
   smarty

   Copy code

   {include file='widgets/custom-widget.tpl'}
3. Step 3: Style the widget by adding relevant CSS in the theme’s css folder.

Example 2: Adding a Custom Theme

1. Step 1: Duplicate an existing theme folder inside content/themes.
2. Step 2: Rename the folder and modify the style.css file to give your theme a new look.
3. Step 3: Activate your theme from the admin panel.

Security Considerations

1. Protect the config.php File: Ensure it is not accessible from the browser by restricting permissions.
2. Restrict Access to Sensitive Folders: Use .htaccess rules to prevent access to includes and vendor.
3. Enable HTTPS: Secure user data and transactions by enforcing SSL.

Best Practices for Managing Sngine’s Structure

1. Backup Regularly: Use automated scripts to back up files and databases periodically.
2. Document Changes: Maintain a changelog for modifications, especially for includes and templates.
3. Use a Version Control System: Track changes and collaborate using Git.
4. Avoid Core Modifications: Whenever possible, use plugins or theme customizations instead of altering core files.

Conclusion

Understanding the file and folder structure of Sngine is a foundational step for webmasters aiming to customize or extend the platform. By familiarizing yourself with the purpose of each directory and its contents, you can streamline your workflow, enhance security, and create a truly unique community experience. Whether you’re adding a new widget, modifying themes, or integrating plugins, this knowledge will empower you to harness the full potential of Sngine.