yangzhang75 opened a new pull request, #90:
URL: https://github.com/apache/incubator-texera-site/pull/90
### What changes were proposed in this PR?
- Adds `content/blog/form-view/index.md`, a feature-introduction post on the
Form View
- The post is in two halves. The first walks through the feature with no
assumptions about Texera's internals: why the canvas is the wrong surface for
someone who only runs a workflow, how an author chooses which operator
properties become fields and names them, what a reader sees and runs, how the
two views of one workflow relate, and what the feature does not do. The second
covers how it is built (the form as a lens over the same shared graph,
`formBinding` in the workflow content, `default_view` as a column, and the five
load-bearing PRs of the seventeen-PR stack) and six problems that shaped it.
- Adds two screenshots under `static/images/blog_hero/` and four demo videos
under `static/videos/`
### Any related issues, documentation, discussions?
Describes the feature tracked in apache/texera#8011.
Three of the six problems in the second half are fixes still in review
rather than shipped, and are labelled as such in the post: apache/texera#8351,
apache/texera#8540, and apache/texera#8581 with apache/texera#8582.
### How was this PR tested?
- Ran `npm run serve` and opened the post, confirmed both images render and
all four videos load and play
- Confirmed the post appears first on `/blog/` with its hero image and
description on the card
- Confirmed every referenced asset resolves; the post links six files under
`static/` and all six are included here
- Checked the post at a narrow viewport: every width in the post is relative
(`max-width: 100%`, `width: 90%`, `width: 70%`), so the media scale with the
content column and there is no horizontal overflow
- Checked the technical claims against the code rather than from memory.
Three were wrong in an earlier draft and are corrected here: a code property
cannot be exposed at all (`NON_FORM_FIELD_TYPES`), Projection's drag-reorder
list is exposable but falls back to a plain repeated list in the form
(`CANVAS_ONLY_FORMLY_TYPES`), and the tick box is offered only beside
properties that can become fields. Every PR number cited was checked against
the API for its title and merge state.
- Cropped a two-pixel dark strip off the top of the hero screenshot
### Was this PR authored or co-authored using generative AI tooling?
Co-authored with Claude Opus 5 in compliance with ASF
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
