You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a template file is loaded in the controller, `Django` scans all template directories starting from the ones defined by the user, and returns the first match or an error in case the template is not found.
155
+
The theme used to style this starter provides the following files:
156
+
157
+
```bash
158
+
< LIBRARY_ROOT ># This exists in ENV: LIB/admin_soft_pro
159
+
|
160
+
|-- templates/ # Root Templates Folder
161
+
||
162
+
||-- accounts/
163
+
|||-- signin/basic.html # Sign IN Page
164
+
|||-- signup/basic.html # Sign UP Page
165
+
||
166
+
||-- includes/
167
+
|||-- footer.html # Footer component
168
+
|||-- sidebar.html # Sidebar component
169
+
|||-- navigation.html # Navigation Bar
170
+
|||-- scripts.html # Scripts Component
171
+
||
172
+
||-- layouts/
173
+
|||-- base.html # Masterpage
174
+
|||-- base-fullscreen.html # Masterpage for Auth Pages
When the project requires customization, we need to copy the original file that needs an update (from the virtual environment) and place it in the template folder using the same path.
185
+
186
+
> For instance, if we want to **customize the footer.html** these are the steps:
187
+
188
+
- ✅ `Step 1`: create the `templates` DIRECTORY inside the `home` app
189
+
- ✅ `Step 2`: configure the project to use this new template directory
190
+
-`core/settings.py` TEMPLATES section
191
+
- ✅ `Step 3`: copy the `footer.html` from the original location (inside your ENV) and save it to the `home/templates` DIR
0 commit comments