starred/ALwrity

Fork 0

mirror of https://github.com/AJaySi/ALwrity.git synced 2026-04-26 01:15:52 +03:00

[GH-ISSUE #90] Interactive Content writer - Chain of Thoughts content writing #71

New issue

Closed

opened 2026-03-02 23:33:24 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 23:33:24 +03:00

Owner

Originally created by @AJaySi on GitHub (Jun 25, 2024).
Original GitHub issue: https://github.com/AJaySi/ALwrity/issues/90

Originally assigned to: @AJaySi, @DikshaDisciplines on GitHub.

Alwrity is highly opinionated and takes few keywords/input to write the content.
There is not much control over generating titles, outlines, sections and research questions.

An interactive content writer will have "Human in the Loop"(HITL) for each stage of generating content.
This option will make alwrity chatty, but some users may prefer a fine grained control.

Having a fine-grained control will also reduce iterations of editing.

Originally created by @AJaySi on GitHub (Jun 25, 2024). Original GitHub issue: https://github.com/AJaySi/ALwrity/issues/90 Originally assigned to: @AJaySi, @DikshaDisciplines on GitHub. Alwrity is highly opinionated and takes few keywords/input to write the content. There is not much control over generating titles, outlines, sections and research questions. An interactive content writer will have "Human in the Loop"(HITL) for each stage of generating content. This option will make alwrity chatty, but some users may prefer a fine grained control. Having a fine-grained control will also reduce iterations of editing.

kerem

2026-03-02 23:33:24 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 23:33:25 +03:00

Author

Owner

@AJaySi commented on GitHub (Jun 30, 2024):

Explanation:
Step 1: The user is prompted to enter keywords or a blog title. This step only displays the text input field.
Step 2: Once the keywords are entered and the user clicks "Next", the title options are generated and displayed.
Step 3: After selecting and confirming the title, the user is asked to confirm the topic.
Step 4: Once the topic is confirmed, the outline is generated and displayed. The user then confirms the outline.
Step 5: The article is generated based on the confirmed outline, and the user confirms the final article.
This step-wise approach ensures a smooth and interactive user experience where each step is displayed sequentially after the previous one is completed.

@AJaySi commented on GitHub (Jun 30, 2024): Explanation: Step 1: The user is prompted to enter keywords or a blog title. This step only displays the text input field. Step 2: Once the keywords are entered and the user clicks "Next", the title options are generated and displayed. Step 3: After selecting and confirming the title, the user is asked to confirm the topic. Step 4: Once the topic is confirmed, the outline is generated and displayed. The user then confirms the outline. Step 5: The article is generated based on the confirmed outline, and the user confirms the final article. This step-wise approach ensures a smooth and interactive user experience where each step is displayed sequentially after the previous one is completed.

kerem commented

2026-03-02 23:33:25 +03:00

Author

Owner

@AJaySi commented on GitHub (Jun 30, 2024):

Explanation:
State Management: The st.session_state is used to track the current step and store intermediate data like keywords, chosen title, and outline.
Navigation: Each step has buttons for "Next" or "Confirm" and a "Back" button to navigate to the previous step.
Step-wise Flow: The steps are implemented sequentially, only moving to the next step once the current step is confirmed.

@AJaySi commented on GitHub (Jun 30, 2024): Explanation: State Management: The st.session_state is used to track the current step and store intermediate data like keywords, chosen title, and outline. Navigation: Each step has buttons for "Next" or "Confirm" and a "Back" button to navigate to the previous step. Step-wise Flow: The steps are implemented sequentially, only moving to the next step once the current step is confirmed.

kerem commented

2026-03-02 23:33:26 +03:00

Author

Owner

@AJaySi commented on GitHub (Jul 15, 2024):

As we are moving to a better UI. All the above issues will do solved there.

@AJaySi commented on GitHub (Jul 15, 2024): As we are moving to a better UI. All the above issues will do solved there.

kerem referenced this issue

2026-03-13 20:14:58 +03:00

[GH-ISSUE #71] TBDs & Alwrity tools to implement - Roadmap #393

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ALwrity#71

No description provided.

Rows
Columns