-
Get Started
-
CSS
-
JS - Node
-
Components
-
Images
-
Routing
-
Servers
-
Spec files
-
Configuration
-
Docmap
-
CLI
-
Recipes
-
Contribute
-
Dependencies
Packages
-
cli
-
s-activate-feature
-
s-bench
-
s-builder
-
s-carpenter
-
s-class
-
s-clipboard-copy-component
-
s-code-example-component
-
s-color
-
s-color-picker-component
-
s-component-utils
-
s-conductor
-
s-config
-
s-dashboard
-
s-datetime-picker-component
-
s-docblock
-
s-docmap
-
s-duration
-
s-env
-
s-event-emitter
-
s-favicon-builder
-
s-feature
-
s-file
-
s-filtrable-input-component
-
s-form-validate-feature
-
s-front
-
s-frontend-server
-
s-frontspec
-
s-glob
-
s-google-map-component
-
s-images-builder
-
s-interface
-
s-kitchen
-
s-log
-
s-markdown-builder
-
s-pack-essentials
-
s-panel-component
-
s-postcss-sugar-plugin
-
s-process
-
s-promise
-
s-range-component
-
s-rating-component
-
s-refocus-feature
-
s-request
-
s-scroll-component
-
s-sitemap-builder
-
s-slider-component
-
s-static-builder
-
s-stdio
-
s-sugar-config
-
s-sugar-json
-
s-theme
-
s-theme-switcher-component
-
s-typescript-builder
-
s-view-renderer
-
s-vite
Spec files
A spec file is mainly a file that describe something like:
frontspec.json
: Describe what the project has to offer for the frontend (js, css, typos, etc...)viewspec.json
: Describe what are the data to pass to a view. Useful to build your backend dynamically
These files are legit by some specifications that you can discover separatly in each files documentations.
Why these spec files?
The goal of these files is to describe each part of your frontend like the views, resources (js, css), etc...
If we take the viewspec.json
file for example. His goal is to describe a particular view like hello.blade.php
.
By describing the data that this view depends on, you can use that and build your backend automatically. Pretty usefull for medium/large projects.