Doc/#1209 - #1250 - Add documentation page for each application and page template #1263
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trgiangdo
added
📈 Improvement
jrobinAV
reviewed
Feb 3, 2025
There was a problem hiding this comment.
I would move the templates/ folder from docs/userman/ecosystem/ to docs/. I propose to expose the templates at the top level next to the tutorials. On the contrary, the cli/ folder remains unchanged, under docs/userman/ecosystem/ folder. Does it make sense?
I would also like to have a templates/index.md page that list all templates (for application and page).
What do you think?
Co-authored-by: Jean-Robin <[email protected]>
jrobinAV
reviewed
Feb 5, 2025
jrobinAV
requested changes
Feb 5, 2025
Co-authored-by: Jean-Robin <[email protected]>
…n description and customize the application sections
Co-authored-by: Jean-Robin <[email protected]>
jrobinAV
reviewed
Feb 12, 2025
jrobinAV
approved these changes
Feb 12, 2025
…eginning of the doc page
trgiangdo
changed the title
jrobinAV
approved these changes
Feb 17, 2025
|
I am getting 404 answers on the new |
jrobinAV
approved these changes
Feb 18, 2025
jrobinAV
reviewed
Feb 19, 2025
jrobinAV
reviewed
Feb 19, 2025
jrobinAV
reviewed
Feb 19, 2025
Comment on lines
1
to
12
| Building a Taipy application with multiple complex scenarios usually requires a | ||
| significant amount of time and effort, in particular at the beginning of a project | ||
| when the user interface requirements are not completely stable. This can delay the | ||
| time-to-market and increase development costs. | ||
|
|
||
| To reduce the development time, Taipy provides a scenario management application template, | ||
| which leverages Taipy visual elements to speed up bootstrapping a standard application. | ||
|
|
||
| Out-of-the-box, the scenario management application is a multi-page Taipy application | ||
| that allows the user to visualize and manage scenarios and data nodes. The user can select a | ||
| scenario, view its directed acyclic graph (DAG), manage its data nodes, upload data files, | ||
| and submit the scenario for execution. |
There was a problem hiding this comment.
Suggested change
| Building a Taipy application with multiple complex scenarios usually requires a | |
| significant amount of time and effort, in particular at the beginning of a project | |
| when the user interface requirements are not completely stable. This can delay the | |
| time-to-market and increase development costs. | |
| To reduce the development time, Taipy provides a scenario management application template, | |
| which leverages Taipy visual elements to speed up bootstrapping a standard application. | |
| Out-of-the-box, the scenario management application is a multi-page Taipy application | |
| that allows the user to visualize and manage scenarios and data nodes. The user can select a | |
| scenario, view its directed acyclic graph (DAG), manage its data nodes, upload data files, | |
| and submit the scenario for execution. | |
| The scenario management template provides a foundational structure for applications | |
| requiring scenario-based analysis and data management. It's designed to help users create, | |
| manage, and compare different scenarios to facilitate decision-making and what-if | |
| analyses. It is ideal for applications in forecasting, simulation, and optimization, where | |
| multiple scenarios need to be evaluated and compared. | |
| Out of the box, the template provides a multi-page application structure with two pages predefined: | |
| - A scenario page to select, visualize, submit, analyze, and manage scenarios and data nodes. | |
| - A job page to monitor and manage submissions and jobs. |
FabienLelaquais
requested changes
Feb 19, 2025
trgiangdo
commented
Feb 20, 2025
trgiangdo
commented
Feb 20, 2025
Co-authored-by: Jean-Robin <[email protected]> Co-authored-by: Fabien Lelaquais <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #1209
See temporary results on ReadTheDocs/doc-1209-application-templates.
TODO: