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
the logic is data-driven: in case there is no previousPageRecord, the last page button will get the hidden config set to true, which then won't render it into the DOM at all.
a button has flex: 1 which is fine in case there are 2 buttons, but not so much in case there is just one.
the chicken and egg problem: the ticket is related to the new learning section, which you will need to actually understand how the framework works and more importantly how to use it as a developer. we need around 4 more weeks to publish the new portal app.
you could create a fork, run npm i, then npm run build-all, then ideally enable the theme watcher: npm run watch-themes to get your SCSS compiled into CSS when doing changes. afterwards npm run server-start and open the portal app inside the browser.
my recommendation would be: join the slack channel first. @maxrahder is moderating weekly workshops and can help interested devs in getting up to speed.
Assuming this one should not take the full width, but the last 50%.
The text was updated successfully, but these errors were encountered: