kz930 opened a new pull request, #91:
URL: https://github.com/apache/incubator-texera-site/pull/91
### What changes were proposed in this PR?
- Adds `content/blog/export-workflow-as-python/index.md`, a
feature-introduction post on taking a Texera workflow out of the system as a
standalone Python script
- The post is in two halves. The first shows what the export does with
no assumptions about Texera's internals: where the control sits in the toolbar,
the script a five-operator workflow produces, and what the export guarantees.
The second covers how the translation works, and how the result is kept honest
by running every operator through the engine and as the generated Python and
comparing the two answers.
- Adds four images under `static/images/blog_hero/`: the export modal, the
toolbar strip showing which control it is, and the two diagrams for the
translation path and for the two-path verification
### Any related issues, documentation, discussions?
Describes the export tracked in apache/texera#8325.
### How was this PR tested?
- Built with Hugo 0.152.2 extended, the version `publish-site.yml` installs,
using the same `hugo --minify -d public` command: 100 pages, no warnings or
errors
- Ran `npx hugo serve` and read the post end to end in the theme: both
diagrams render with their captions, both tables keep their own styling rather
than Docsy's `.td-table`, and the post holds together at a narrow viewport
- Confirmed the post appears first on `/blog/` with its card image,
description and tags
- The export modal is a screenshot of a local instance running the current
code, and the script in it is the export of the five-operator workflow on the
canvas behind it
- Confirmed every referenced asset resolves: the post links four files under
`static/`, and all four are included here
### 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]
