folder_structure
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
folder_structure [2019/08/03 16:10] – witsec | folder_structure [2024/09/01 14:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Folder Structure ====== | ====== Folder Structure ====== | ||
- | There are [[types_of_extensions|two types of extensions]]. Depending on what of extension you're creating, the folder structure may differ. The following files are always present, regardless of what type of extension you're creating: | + | There are different |
===== Base Structure ===== | ===== Base Structure ===== | ||
- | * params.json | + | * [[params.json]] |
* splash.html | * splash.html | ||
* splash.jpg | * splash.jpg | ||
* thumbnail.jpg | * thumbnail.jpg | ||
+ | * translations/ | ||
==== params.json ==== | ==== params.json ==== | ||
Line 25: | Line 26: | ||
Just like the '' | Just like the '' | ||
+ | |||
+ | ==== translations ==== | ||
+ | |||
+ | Any extension can come with its own translations. Translations are not required, but are very user friendly if you incorporate them into your extensions. Each language can have its own language file that contains all phrases and their translations. | ||
===== App Extensions ===== | ===== App Extensions ===== | ||
- | An App Extension has all the files as described above, plus an additional | + | An App Extension has all the files as described above, plus: |
+ | |||
+ | * [[app.js]] | ||
+ | * [[core.js]] | ||
+ | |||
+ | ==== app.js ==== | ||
+ | |||
+ | The [[app.js]] | ||
+ | |||
+ | ==== core.js ==== | ||
+ | |||
+ | An App Extension sometimes come with a [[core.js]] file. It's unclear when you would need a core.js file. | ||
===== Component Extensions ===== | ===== Component Extensions ===== | ||
Line 34: | Line 50: | ||
A Componend Extension comes with one or more components. In most cases these are additional blocks a user can drag onto his website. The file and folder structure looks like this: | A Componend Extension comes with one or more components. In most cases these are additional blocks a user can drag onto his website. The file and folder structure looks like this: | ||
- | * component_directory | + | * primary |
* [[component.js]] | * [[component.js]] | ||
* [[template.html]] | * [[template.html]] | ||
Line 50: | Line 66: | ||
The [[template.html]] file contains all the HTML to display the block inside Mobirise, but also when the website is previewed/ | The [[template.html]] file contains all the HTML to display the block inside Mobirise, but also when the website is previewed/ | ||
+ | |||
+ | ==== thumb.png ==== | ||
+ | |||
+ | The '' | ||
+ | |||
+ | ===== Themes ===== | ||
+ | |||
+ | Themes are a different kind of extension. They provide an entire theme on which you can base your website and offer several blocks to get you started. Older M3 themes came with Component Extensions in them, but nowadays that isn't the case anymore. Themes often come with: | ||
+ | |||
+ | * fonts/ | ||
+ | * components/ | ||
+ | * plugins/ | ||
+ | |||
+ | ==== fonts ==== | ||
+ | |||
+ | Most themes come with their own fonts to give them that more unique look and feel. Fonts are stored inside this directory. | ||
+ | |||
+ | ==== components ==== | ||
+ | |||
+ | This directory contains all the blocks of said theme. These are the blocks that get displayed on the sidebar which ou can drag onto your website. | ||
+ | |||
+ | ==== plugins ==== | ||
+ | |||
+ | All plugins and (Javascript) libraries a theme uses are stored in this directory. |
folder_structure.1564841404.txt.gz · Last modified: 2024/09/01 14:30 (external edit)