One blueprint could contain a page, with the functions needed on that page. Or an event that operates independently. Or a function that is called from other blueprints. As a rule of thumb, keep the number of blocks around 300 to maintain a good performance.
The blueprint will open with a menu showing you optional blocks to start with.
After a few seconds this menu disappears. If you have not made a choice yet, you can do this later with the menu that opens on right-click (see below).
- leave anytime, unsaved changes will be kept
- type a name for your blueprint on the … in the top left
- you can change the blueprint name anytime
- tags help you organize the blueprints overview
- the (de)activate button works on pages or events
- the options button will open a sub menu
m. The options menu is especially useful in larger blueprints.
- function relations show calls from or to other blueprints
- open a console here to record console log actions
- recent changes lists changes that were saved
- use view recent change for unsaved changes
- deprecated items folder
- pages folder
- functions folder
- document actions folder
- undo all changes, also from other developers
- view recent change will jump to the changed actions
If you run a simulation, the control buttons will also show up on the left side of the bottom bar.
Use the ?staging mode to see unsaved styling and debug modals in the frontend. Simulations, console log and debug all work with unsaved changes.
- hold right mouse button to select blocks
- use mouse wheel to zoom in or out
- open right click menu to go to the center
- add function
- go to center
- add comment
- reload
part of the Introduction series