31
Beta / Re: 2.4 template-making guide
« on: June 17, 2020, 05:49:27 PM »
some sections do not need to be with public attribute because they are already included by a macro call in a public section ~style.css, ~lib.js
[icons.css|public|no log|cache] --> {.$icons.css.}
[normalize.css|public|no log|cache] --> {.$normalize.css.}
[sha256.js|public] --> {.$sha256.js.}
another thing needs probably to be extended
public sections are called mainly with the reference / ~ sectionname, however in a diff template this type of section may have to be completely redefined.
Due to the inheritance principle this section is available from anywhere in the vfs using the macro {.section | sectionname.} But should also be available by adding ~ sectionname to the url of any folder element vfs as example http://127.0.0.1/New%20folder%20(2)/~test
[icons.css|
[normalize.css|
[sha256.js|
another thing needs probably to be extended
public sections are called mainly with the reference / ~ sectionname, however in a diff template this type of section may have to be completely redefined.
Due to the inheritance principle this section is available from anywhere in the vfs using the macro {.section | sectionname.} But should also be available by adding ~ sectionname to the url of any folder element vfs as example http://127.0.0.1/New%20folder%20(2)/~test