AbjadNLP Website Editing Guide

This guide explains how AbjadNLP organisers can update workshop webpages or create new shared-task pages using GitHub.

You do not need programming experience or special software. You only need a free GitHub account and a web browser.

Important: Organisers are responsible for preparing and submitting their own website changes. The website owner reviews and approves proposed changes but is not responsible for writing or uploading content on behalf of organisers.

Useful links

• GitHub repository: https://github.com/drelhaj/elhaj
• AbjadNLP 2027 page: https://github.com/drelhaj/elhaj/blob/main/abjad2027.html
• Pull requests: https://github.com/drelhaj/elhaj/pulls

1. Go to https://github.com.
2. Create a free account if you do not already have one.
3. Sign in to your account.
4. Open the AbjadNLP 2027 page using the link above.

You do not need to ask for direct access to the repository.

GitHub allows you to suggest changes through a Pull Request (PR). A Pull Request is simply a request for the website owner to review and publish your changes.

Step 1 — Open the page

Visit:

https://github.com/drelhaj/elhaj/blob/main/abjad2027.html

Step 2 — Click the pencil icon

Near the top-right area of the file, look for the pencil icon labelled "Edit this file". Click it.

If GitHub says you do not have permission to edit the repository, choose the option to fork the repository and propose changes. This creates your own copy without changing the original website.

Step 3 — Find the information you want to update

The file contains HTML code. Do not worry about understanding all of it.

Use Ctrl+F (Windows) or Cmd+F (Mac) to find the relevant text, such as:

• Important Dates
• Call for Papers
• Organising Committee
• Invited Speakers
• Shared Tasks
• Contact

Find the relevant section and carefully update the text.

Step 4 — Make your changes

For example, you may update an organiser's affiliation, correct a deadline, add a speaker biography, or insert an approved announcement.

Be careful not to delete surrounding HTML tags or unrelated content.

Step 5 — Save your proposed changes

Click "Commit changes".

Enter a short description, for example:

"Update AbjadNLP 2027 keynote information"

If GitHub offers to create a new branch or fork, use that option rather than changing the main branch.

Step 6 — Create a Pull Request

After saving, select "Propose changes", "Compare & pull request", or "Contribute → Open pull request", depending on the GitHub screen.

Make sure the proposed changes target:

drelhaj/elhaj → main

Give your Pull Request a clear title and explain what you changed.

Step 7 — Submit

Click "Create pull request".

Your changes have now been submitted for review. They are not yet published on the official website.

Step 8 — Respond to feedback

The website owner or authorised maintainer may approve the changes or request corrections.

If corrections are requested, update your proposed changes and respond in the Pull Request.

The organiser who submitted the Pull Request remains responsible for completing any required corrections.

Shared-task organisers can also create their own webpages without requiring the main workshop organisers to prepare them.

Step 1 — Open the repository

https://github.com/drelhaj/elhaj

Step 2 — Create your own copy

Click "Fork" and select "Create fork", if you have not already created one.

This creates a copy of the repository in your GitHub account.

Step 3 — Create a new file

In your fork, open the main file listing and choose "Add file → Create new file".

Step 4 — Name your page

Use the following format:

abjadYYYY-taskname.html

Examples:

• abjad2027-sentiment.html
• abjad2027-ocr.html
• abjad2028-translation.html

Use lowercase letters, numbers and hyphens. Avoid spaces.

Step 5 — Add your webpage content

You may copy an existing suitable HTML page as a starting template, then replace the content with your own shared-task information.

Include the task title, description, organisers, participation instructions, datasets, evaluation procedure, important dates, submission information, and contact details.

Remove any example content that does not apply to your task.

Step 6 — Save and submit

Click "Commit changes" and open a Pull Request to the original repository, as explained in Section 3.

In the Pull Request description, identify the new filename and explain what the page contains.

Step 7 — Request a link from the main workshop page

If your new shared-task page needs to appear in the main AbjadNLP workshop website, include the relevant link update in your Pull Request.

Creating a file alone does not automatically add a link to the workshop navigation.

Every Pull Request must clearly state:

• What changed: A short explanation of the new or updated information.
• Which page: The filename being edited or created.
• Who approved the content: The responsible Programme Chair, Shared-Task Chair, or other authorised person, where approval is required.
• What needs checking: Any links, formatting, or information that may need special attention.

Organisers must check their proposed changes for accuracy, spelling, working links, and unintended modifications before requesting approval.

Publicity Chairs are responsible for preparing and submitting changes to the main workshop webpages.

Shared-task organisers are responsible for creating and updating their own shared-task webpages.

The repository owner or authorised maintainer is responsible for reviewing proposed changes and deciding whether to merge them into the official repository.

Submitting a Pull Request does not guarantee approval or immediate publication. Organisers must submit updates early enough to allow review and any necessary corrections.

The website owner is not responsible for rewriting incomplete content, preparing webpages on behalf of organisers, or correcting avoidable errors in submitted materials.

Once a Pull Request has been approved and merged, the organiser must check the published webpage and promptly report any remaining problems.

When you open abjad2027.html for editing, you will see HTML code. You do not need to understand the entire file to make a simple text change.

For example, you might see:

Before:

<h2>Important Dates</h2><p>Submission deadline: To be announced</p>

To update the deadline, change only the relevant text:

After:

<h2>Important Dates</h2><p>Submission deadline: 20 January 2027</p>

The date above is only an example, not a confirmed workshop deadline.

Important:

• Change the text between the HTML tags.
• Do not remove or modify tags such as <h2>, </h2>, <p>, or </p>.
• Do not replace the entire webpage when making a small update.
• Do not change unrelated sections of the website.
• Check that dates, names, and links are accurate and approved before submitting changes.

After editing, click Commit changes and follow the steps in Section 3 to submit your Pull Request.

If you are unsure how to edit something, explain what you are trying to change in your Pull Request rather than modifying unrelated code.

Before submitting your Pull Request, confirm that:

• I have edited only the relevant AbjadNLP workshop or shared-task files.
• All names, dates, links, and announcements are accurate and approved.
• I have not accidentally deleted HTML tags or modified unrelated website content.
• I have checked the proposed changes using GitHub's preview or comparison view where available.
• I have clearly described what I changed in the Pull Request.
• I will respond to any requested corrections and verify the published page after approval.

Responsibility for corrections

The organiser submitting the Pull Request is responsible for correcting any errors identified during review.

The repository owner or authorised maintainer reviews and approves changes but is not responsible for preparing website content, rewriting incomplete submissions, or correcting errors on behalf of organisers.

Pull Requests containing incomplete information, unapproved announcements, or unrelated modifications may be returned for correction before approval.