Learning task 1

Install and configure a text editor with a viewer plugin

  • What is your favorite text editor?
    • Notepad++, Visual Studio Code, ...
  • Does it have a plugin or extension for Markdown?

Using Notepad++ for Markdown

AddingMDprojplan

To use Notepad++ for Markdown you need to install a plugin to view the formatting. We recommend Markdown Panel.

Install the Markdown Panel in Notepad++

  1. From the Plugins menu, choose Plugin Admin
  2. In the search box, type markd
  3. Check (tick) the box beside Markdown Panel
  4. Click Install
    A dialog is displayed.
  5. Click Yes
  6. Wait for the operations to finish.
  7. Click Notepad++ icon on the taskbar.
  8. From the Plugins menu, choose Toggle Markdown panel

Configuring the Markdown Panel

Once you have installed the plugin, you need to configure it as the default Zoom size is far too small.

  1. From the **Plugins **menu, choose MarkdownPanel,
  2. Then Toggle Markdown Panel
  3. A message in the Panel warns that the current file is not markdown. Ignore this for now.
  4. From the **Plugins **menu, choose MarkdownPanel, then Settings
    ConfigureMarkdownPanelluginNotePad
  5. Drag the Zoom level slider to 250%
  6. Check (tick) the checkbox “Automatically show panel for supported files”.
  7. Click Save

Then save the file as a markdown file

  1. Click the Save icon
  2. Choose a markdown format
  3. Change the folder
  4. Click Save
  5. If you still get the error message that it is not markdown, close then reopen the panel.

Reflect: What challenges did you encounter?


Learning task 2

The text in the description of the tasks in the Paratext Project Plan can now be formatted using Markdown.
Your task is to add Markdown codes to each task in YOUR project to make it easier to read and understand.

How to edit descriptions

  1. Open your project in Paratext.
  2. From the Project menu, choose Project settings, then Project Plan
  3. In the list of tasks on the left, click on a task.
  4. In the Description pane on the right, edit the text using markdown codes.
  5. Click the Preview link at the bottom right of the description pane.

AddingMDprojplan

Reflect: What challenges did you encounter?


Learning task 3

The two markdown texts below contain several errors. Here are some common pitfalls to watch out for:

  • Space missing after heading codes (#) before the text
  • Spaces before formatting codes
  • Unclosed bold (**) or italic (*) formatting codes
  • Unintended format codes
  • Inconsistent bullets

How would you resolve the errors in these markdown texts?

Text 1: from a genAI coure

##In defense of genAI
AI won't ** replace humans, 
- but humans who use AI 
* will **replace humans** that ***don't.
*Fei Fei Li, Stanford Professor, AI researcher

Desired result

In defense of genAI

AI won't replace humans,

  • but humans who use AI
  • will replace humans that don't.
    • Fei Fei Li, Stanford Professor, AI researcher

Text 2: (From ChatGPT)

##Embrace the Journey
In life, the road to success is never straightforward. **Every challenge you face is a stepping stone to greatness, and with persistence, even the steepest hills can be overcome.

-Embrace change as an essential part of growth.
*Believe in your inner strength and resilience.

  • Learn from every mistake, for each error teaches a lesson.
    *Strive for progress, not perfection.

"It is not the mountain we conquer but ourselves." - Sir Edmund Hillary

Remember:
Hope and *determination are the fuels that keep our dreams alive.
Without them, the journey becomes a struggle.

Let us commit to:

  1. Cultivating a positive mindset.
  2. Supporting one another through life's challenges.
  3. Celebrating our small victories along the way.

Take a moment to reflect on your own journey, identify where you have grown, and envision the path ahead.

`This line looks like a code snippet, but it might not be intended that way.

What other errors did you see in this text?

Reflect: What challenges did you encounter?

==Errors: ==

  1. space before ** > not bolded,
  2. no space added after ## > so not a heading,
  3. wrong level heading (too many #)
  4. mixture of * and - for bullets > uneven spacing in bullet list
  5. missing * for bold or italic
  6. Any others??