-
Notifications
You must be signed in to change notification settings - Fork 218
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
docs: Improve XBlock tutorial sections 1-3 #692
Conversation
33dbf92
to
fc120e4
Compare
@feanil this PR has a stalled build |
|
||
You use the XBlock SDK to create skeleton files for an XBlock. To do this, | ||
follow these steps at a command prompt. | ||
|
||
#. Change to the ``xblock_development`` directory, which contains the ``venv`` and ``xblock-sdk`` subdirectories. | ||
#. Change to the ``xblock_development`` directory, which contains the | ||
``var``, ``xblock-env``, and ``xblock-sdk`` subdirectories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added var
because we're told to do that in the clone-sdk file
|
||
#. You are prompted to indicate whether or not to create a Django superuser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
812cba3
to
0cda2e1
Compare
@sarina I added a commit that should fix up the doc errors, so I think this should be good to go once you rebase and fix the glossary conflict. |
These aliases got renamed in the source file so update them where they are referenced.
d9ed1bf
to
64fff3c
Compare
Simplify XBlock Tutorial introduction section (removed "front matter" section and consolidated on one page; moved "Browsers" under "Overview")
Update XBlock Tutorial overview section - particularly, renaming
venv
toxblock-env
to make it clear that you're making a specific venv for this xblock, and also, that venvs can have unique names. I'm open to feedback on the exact name of the env. I'm also open to keeping itvenv
but explaining more that it's the name we're choosing for the environment (as written I think it can be a bit confusing that we're using venv as a name but also it's the name of the tool)Correct and update the Getting Started section. Updated the screenshot of the SDK workbench, depends on Use Open edX logo on workbench xblock-sdk#332