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
We would like to get rid of the existing elements notebooks and have an Elements section in the website sidebar which expands with a list of all the elements. At the top of this list would be a navigation page showing a grid of thumbnails for all the different backends.
Each element notebook would then show how that element is constructed across backends. This proposal has the following advantages:
Makes it easier to add new elements (no need to update the whole notebook)
Makes it easier to test elements (identify which element went wrong given a failure)
Makes it easier to update those notebook tests
Make it easier to compare elements across backends.
To generate thumbnails, we would use a notebook archive. These thumbnails would be shown in a grid and there could be buttons to toggle the thumbnails between backends (unsupported elements would be greyed out appropriately).
This could all be organized in doc in an Elements subdirectory. For instance, I can imagine the following file paths:
This issue summarises a discussion I've have with @jbednar and @philippjfr
We would like to get rid of the existing elements notebooks and have an Elements section in the website sidebar which expands with a list of all the elements. At the top of this list would be a navigation page showing a grid of thumbnails for all the different backends.
Each element notebook would then show how that element is constructed across backends. This proposal has the following advantages:
To generate thumbnails, we would use a notebook archive. These thumbnails would be shown in a grid and there could be buttons to toggle the thumbnails between backends (unsupported elements would be greyed out appropriately).
This could all be organized in
doc
in an Elements subdirectory. For instance, I can imagine the following file paths:The text was updated successfully, but these errors were encountered: