Git Product home page Git Product logo

edx-documentation's Introduction

edX Documentation

The edx-documentation repository contains source files for most of the documentation for edX partners and the Open edX community.

  • A new site, docs.openedx.org, is currently being built. Before adding new documentation to this repo, consider if the documentation should be added, or moved, to the new site. See the rationale for this decision, as well as more on how the new site is organized, in this decision document.
  • API documentation that includes docstrings from code files is stored in the repository of that module.
  • Documentation source files for Insights is in the edx-analytics-dashboard repository.

Documentation for developers, researchers, course staff, and students is located in the language-specific subdirectories.

View Published Documentation

edX documentation is published through Read the Docs. Links to all published documentation are available through docs.edx.org.

Submit Documentation Issues

You may submit issues via the edx-documentation GitHub Issues system.

Contribute to edX Documentation

You, the user community, can help update and revise edX documentation.

edX documentation is published from RST source files using Sphinx.

To suggest a revision, fork the project, make changes in your fork, and submit a pull request back to the original project: this is known as the GitHub Flow.

All pull requests need approval from project maintainers, who will look over and review your contributions.

Supplying Information with a Pull Request

The edX documentation team created a template that is automatically added to pull requests. You are strongly encouraged to use this template.

Testing a Contribution

Before submitting a pull request, it is recommended you run the test suite on your contribution to ensure it can be compiled into HTML format without errors.

You may first need to install GraphViz. See the Download Page for more instructions on how to install for your particular Operating System.

To run a test compilation of a contribution, first install the prerequisites.

make requirements

Then run the tests.

./run_tests.sh

Additionally, you can run tests for a single project. For example, to build an HTML version of the Installing, Configuring, and Running the Open edX Platform guide, you run this test.

./run_tests.sh en_us/install_operations/

A convenience script is provided to help you develop new documentation. To use it you must first install the optional tools, and then run the script.

pip install -r shared/tools.txt
./develop.sh en_us/install_operations/

It will output a line of text that looks like this.

Serving on http://127.0.0.1:9090

You can copy this URL into a web browser to see the HTML output for your project.

The command starts an HTTP server that renders the HTML for the project. This HTTP server also monitors the project and detects any changes. When you save a change to a file, the server rebuilds the HTML and refreshes your browser automatically. In this way you can rapidly see how changes you make will be rendered as HTML.

edx-documentation's People

Contributors

andy-armstrong avatar catong avatar cpennington avatar cptvitamin avatar debchatigny avatar dependabot[bot] avatar dianakhuang avatar edx-requirements-bot avatar feanil avatar giovannicimolin avatar grantgoodmanedx avatar gsong avatar hammadahmadwaqas avatar jansenk avatar jimjohnson8 avatar jmbowman avatar jristau1984 avatar justinhynes avatar marcotuts avatar mattdrayer avatar mehaknasir avatar mhoeber avatar mulby avatar nedbat avatar robrap avatar sarina avatar singingwolfboy avatar srpearce avatar thallada avatar vkaracic avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

edx-documentation's Issues

Outdated documentation for "Hinted Sign In"

The documentation suggests that there is a possibility to construct "hinted links" that will allow a user to log in via a Third Party and land on course pages. However, this feature appears to have been broken for quite a while as discussed in the following forum topics:

At the moment the documentation still gives examples to the legacy LMS and does not mention if this feature will be or was never meant to work with the Learning MFE.

Splitting edx.org from Open edX documentation in this repo

Ideally, we would like to split edX (2U) documentation from this Open edX documentation.

The challenge is how we accomplish these (incompatible) goals:

  • Keep edx-specific details out of an openedx-org repo
  • Publish docs that make sense to a edx.org-interested reader without expecting them to flip between an Open edX source and an edx.org source
  • Don’t duplicate source information

This ticket can be used to collect ideas, or detailed problems, for how this might be accomplished.

Maintained versions of documentation for i18n support

If the documentation changes, the work towards i18n becomes obsolete. If versions of the documentation are maintained, then the Transifex Working group can focus on translating a version of the documentation without losing their progress.

Periodic Table Tool documentation links to files.edx.org, which contains file name errors

This is not solely a documentation issue, but it affects the documentation, and we were unable to come up with a better place to log this issue.

The documentation for the Periodic Table Tool instructs users to download a file from files.edx.org. The link to this is http, rather than https.

The file in question is a zip file containing 4 files:
image

The HTML in this file checks Files & Uploads for the two CSS and one JS file in the download, but it checks for periodic-table-colors.css and the file is named Periodic-Table-Colors.css - it's case sensitive.

This means that the tool does not actually function by following the documentation, because the files provided are named incorrectly.

Proposed solutions:

  1. Remove the periodic table tool from the documentation. It's not really a feature anyway.
  2. Update the files and host them somewhere else so that they can be maintained (such as this repository?)
  3. Someone on the edX.org end fixes the files and reuploads them

Bad link

http://edx.readthedocs.org/projects/devdata/en/latest/glossary.html#c (for content experiment) points to http://edx.readthedocs.org/projects/edx-partner-course-staff/en/latest/content_experiments/index.html which is a bad link.

Aside from that, it really ought to have a pointer to:
http://edx.readthedocs.org/projects/devdata/en/latest/internal_data_formats/sql_schema.html#columns-in-the-user-api-usercoursetag-table

A common question a researcher might ask is "How do I analyze randomized control trials?" That's not possible to figure out without reading through basically all the docs.

Open Learning XML to pdf converter?

Hello,

I am thinking of creating a collection of questions and answers with additional detailed explanations.

A web search brought me to Open Learning XML? (https://edx.readthedocs.io/projects/edx-open-learning-xml/en/latest/what-is-olx.html)
My desired output-format would be a pdf-file, or lets say two version of the pdf (one with one the questions and the possible
solutions) and the other with the questions, the correct solutions and the detailed explanations.

The example and code listing at 11.23.1.1. Example Multiple Choice Problem
(https://edx.readthedocs.io/projects/edx-open-learning-xml/en/latest/problem-xml/multiple_choice.html)
seem like a suitable format for me.

At this point my question comes into play, are there any alread realized ways to achieve my desired result? An XLST file or XSD?

Thank you

Andreas

Guideline about "TODO" is ambiguous

See https://edx.readthedocs.io/projects/edx-developer-guide/en/latest/style_guides/python-guidelines.html#pylint-guidelines-and-practices:

Adding a TODO in one place requires you to make a pylint fix in another (just to force us to clean up more code).

Please state explicitly whether "TODO" or "FIXME" is discourage and offer a viable alternative for flagging technical debt in the codebase when it cannot be addressed immediately due to time and scope constraints.

Might need to edit old doc versions of open edX so it is evident which release they apply to easily....

For example, I was trying to understand better how to build a circuit simulation problem (in my hawthorn installation), and so I copy/pasted the problem at the end of the page here into my course. It won't allow me to save it. I deleted references to files that I don't have in my course, but that made no difference. Then I wondered if it was a release issue, and so I searched specifically for Hawthorn Circuit Schematic Builder problem, and found this page. I tried the example there, and it worked just fine. Then I looked closely and found that if I read the URL carefully, I can tell the original docs were from Birch. Fortunately the new docs have Hawthorn called out prominently. :-)

Thanks for all your good work on these documents!
Rob

App upload issue

Your app contains an Implicit PendingIntent vulnerability. Please see this Google Help Center article for details.

i am unable to find issue in Edx code

Why is the speed of light 2.998^8 and not 2.988*10^8?

I hope you don't mind the question, but same goes for The Boltzmann constant and the fundamental charge.

  • The Boltzmann constant should be ~1.38*10^-23 J/K whereas, it is ~1.38^-23
  • and The fundamental charge should be ~1.602*10^-19 C but it is written as ~1.602^-19 C

Change password validator configuration to be secure

Investigating a security issue on a bank's site led me to this project. The password policy defined in lms.yml configuration file appears to cause numerous productive systems to allow for passwords of length 2. This is because developers apparently miss to override the min_length: 2 validator option in production.

See also password.rst:

AUTH_PASSWORD_VALIDATORS:
-   NAME: django.contrib.auth.password_validation.UserAttributeSimilarityValidator
-   NAME: common.djangoapps.util.password_policy_validators.MinimumLengthValidator
      OPTIONS:
        min_length: 2

Although it is not really the responsibility of this project, I suggest this value to be changed to conform to latest password policy recommendations. For example, regarding password length NIST says minimum of 8. Microsoft says minimum of 12. OWASP says minimum of 8, in some places.

Changing ID in an user (table auth_user)

ID of every user in edX is set automatically (with a new number from last users we have, as a primary key)
For example,
ID User
1 userA
2 userB
3 userC

But, Microsoft (for example Academy.microsoft.com) use this ID for different activities (for example certificates)

For example, userB has finished lot of courses, but its id (2) is problematic. How can it be changed to a new ID? renaming previous user and creating a new one is not an option, because new user has not all his/her courses.

Is it possible? Changing directly in MySQL will affect information in Mongo, so it doesn't appear to be an option.
For example
ID User
888 UserB

We are Microsoft's partner, with an edX portal and we've got trouble with this elements.
Thanks and regards
Julio

Best practices for feature flag changes and a niptuk for the code snippets

The documentation for feature flags mentions lms.env.json and similar files. I think it's worth mentioning (in the guideline) that Ansible is the recommended way for building such files.

Additionally, the documentations features Python code when mentioning JSON files. While one can guess and do the right thing. I'd rather see a JSON syntax instead of Python.

Python: Notice the missing double quotes " and the constant True:

FEATURES = {
    'LICENSING': True,
    ...

JSON: Notice the lowercase true and the double quotes ":

"FEATURES": {
    "LICENSING": true, 
    ...

Upgrade the requirements

Sphinx has undergone a pretty significant upgrade. Docs are going to produce more warnings and this will require a non-trivial amount of effort.

i18n Support For Documentation

To expand access to the Open edX platform, we'd like to have all the relevant documentation also be translated. Because the master version of documentation can be more volatile, we would instead like to maintain translated versions of named releases.

AC:

Adding product language to DEPR tickets

This is an epic with the task of adding product language to DEPR tickets. The immediate goal is to improve the Olive Release Notes with more comprehensive descriptions and context for DEPR work. The longer term goal is to set the DEPR Board up for product prioritization input and guidance.

Update edx-documentation README

Update the README to correct "EdX" capitalizations, remove outdated links, and explain our move to docs.openedx.org

@feanil I'm happy to do a cleanup pass, but probably can't add the detail you can about the moving strategy/timeline

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.