Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering/Edit modes for guides #6299

Closed
tolusha opened this issue Sep 15, 2017 · 1 comment
Closed

Rendering/Edit modes for guides #6299

tolusha opened this issue Sep 15, 2017 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@tolusha
Copy link
Contributor

tolusha commented Sep 15, 2017

We should use the editor area to display the guides directly. We will provide a switcher so that it's possible to go from one mode into the other one.

The basic requirements here is to provide a convenient editor for markdown/asciidoc files, which allow edition and preview.

By using tabs from the editor area to do that, there will be a lot of benefits:

User can split editor panes and organize the layout exactly the way he wants. He could display the guide on the left/right side by side with the code or other IDE elements.
User could open a guide in two different tabs, split the panes and display the two different modes (editing/rendering) side by side. This would make the edition and the turn around on the guides really convenient.
We don't invent any UX, we reuse what we already have in place and which users are easily understanding.
By default, we would open a guide in redering mode.

Epic: #6150

@tolusha tolusha added kind/task Internal things, technical debt, and to-do tasks to be performed. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach team/enterprise labels Sep 15, 2017
@che-bot
Copy link
Contributor

che-bot commented Sep 7, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot che-bot closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

2 participants