FC-0068: Adding and converting txt files into rst format

[jesgreco]

adding and cleaning up for create_unit.rst

[openedx-webhooks]

Thanks for the pull request, @jesgreco!

This repository is currently maintained by @openedx/docs-openedx-org-maintainers.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[jswope00]

You have "duplicate label" warnings in your build. They are coming because we already have "create a section", "create a subsection", and "create a unit" targets.

So the question becomes where you got these instructions from? I think you got them from the old .txt files, and didn't write this anew?

In that case, the short term fix might be to give these unique target names. But please bring this up in your next meeting, because this is a scenario where we have two very overlapping how-tos, and we should fix that together.

[jesgreco]

@jswope00 ok! I'll write this in our channel to see if we can have a solution before the next meeting which will be 8th January.

[jesgreco]

@jswope00 I've solved the conflict for merging but, still we need to solve the label duplication.

[jesgreco]

@jswope00 I've solved the conflict for merging but, still we need to solve the label duplication.

[jswope00]

We have duplicate files and labels for "Create a Subsection" "Create a Section" and "Create a Unit". Here is what needs to happen here.

1. Manually merge each (section, subsection, unit) into one golden-copy file.
2. Delete the extra files and labels.
3. If we need to include a particular section in another file, then use this method: https://docs.openedx.org/en/latest/documentors/references/templates/doc_quickstart_template.html#how-to-embed-only-a-section

[jesgreco]

@jswope00 I've deleted the duplicated files, and try to include one single file (create.rst) but, then I've realized they are all included. So, there is no need to include a "golden-copy" file. Let me know if you agree on this.

[jswope00]

Just to clarify this commit for anyone looking at it in the future.
It essentially deletes two files:

• create_section.rst
• create_subsection.rst

Because those files already exist as create_hide_delete_sections.rst and create_edit_publish_subsections.rst. So this removes the redundancy.

[jswope00]

@jesgreco can you resolve the conflicts on this one?

[jesgreco]

so, I assume we can proceed with this PR to be merged.

[sarina]

@jesgreco we can't merge the PR until the conflicts are resolved (Git won't let us).

[jesgreco]

I believe we should delete this PR since there were duplication of files within this PR, and now no changes are included in this PR. If we delete the PR, those conflicts should be solved (and I cannot solve them since I don't have write access).

[sarina]

You only need write access to your own branch to solve conflicts, could you get someone on your team to help you out? I don't want to assume just because there are conflicts that there's nothing useful in this PR.