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
This will definitely need to be broken down further.
With frontmatter and standalone SQL in place, there are three new "standalone" page types we'd like to build. Each of these would be a "full page" experience, powered by WASM duck db.
There are two goals beyond the value of the features themselves. I think we can achieve these by tackling any one of the proposed page types:
Bring WASM ddb into the product. We have big plans here, and want to gain experience without touching the entire core product
Set up the infrastructure for new page types beyond the core markdown report
Page types
A full page pivot experience
A full page sql console
A full page record search
Indicating the page type in frontmatter
Each page would map to a single data source.
Eventually, you could see markdown body being included in a slide-over or similar to serve as end user documentation, or similar.
**Where to start **
I think the console is the easiest starting place, the pivot experience is the most valuable, and the record view is the most complex.
This discussion was converted from issue #765 on August 14, 2024 21:12.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This will definitely need to be broken down further.
With frontmatter and standalone SQL in place, there are three new "standalone" page types we'd like to build. Each of these would be a "full page" experience, powered by WASM duck db.
There are two goals beyond the value of the features themselves. I think we can achieve these by tackling any one of the proposed page types:
Page types
Indicating the page type in frontmatter
Each page would map to a single data source.
Treatment of markdown body
Initially, markdown body could be ignored.
Eventually, you could see markdown body being included in a slide-over or similar to serve as end user documentation, or similar.
**Where to start **
I think the console is the easiest starting place, the pivot experience is the most valuable, and the record view is the most complex.
super rough drawings for reference
Beta Was this translation helpful? Give feedback.
All reactions