Skip to content

Replace complex Job Specs page with minimal HTML page and alert button#1

Open
PreetM07 wants to merge 1 commit into
testingfrom
codex/create-simple-html-page-with-alert-button
Open

Replace complex Job Specs page with minimal HTML page and alert button#1
PreetM07 wants to merge 1 commit into
testingfrom
codex/create-simple-html-page-with-alert-button

Conversation

@PreetM07

@PreetM07 PreetM07 commented Apr 4, 2026

Copy link
Copy Markdown
Owner

Motivation

  • Provide a minimal standalone HTML example page that demonstrates a clickable button triggering a JavaScript alert.
  • Replace the large, project-specific index.html that included many assets and app logic with a compact, self-contained file for simple demo or testing use.

Description

  • Replaced the existing index.html contents with a minimal HTML document including <!DOCTYPE html>, meta charset and viewport, and a title of Simple Alert Page.
  • Added a visible heading and a button with id="alertButton" wired to a JavaScript event listener that calls alert('Button clicked!') on click.
  • Removed references to many previous assets, scripts and the large job-specs UI to produce a single-file, self-contained example page.

Testing

  • Inspected the new file contents with nl -ba index.html to confirm the expected HTML and JavaScript are present and correct.
  • Verified repository status with git status --short to confirm index.html was updated in the working tree.
  • No automated test suite was run for this static HTML change.

Codex Task

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 631a5dd714

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread index.html
Comment on lines -6 to +10
</p>
</div>
</div>
<div class="card" id="si-Grammar&amp;Punctuation-Weights" primarysort="2" secondarysort="Style_Guide">
<h5 class="alert alert-success">
<a data-toggle="collapse" data-target="#si-Weights" href="javascript:void(0);">
<span class="badge role-icon badge-success">Style Guide</span>
<span>Weights</span>
</a>
</h5>
<div id="si-Weights" class="card-body card-normal collapse">
<p>
<table width="100%" cellpadding="2" class="table table-condensed table-bordered">
<th colspan="2">Job Spec</th>
<tr>
<td>
<p>Weights are typed as signs and numerals, not words. For example: 5g instead of five grams.</p>
</td>
</tr>
</table>
</p>
</div>
</div>
</div>
</div>
<div id="tab-SupportMaterial" style="padding-bottom: 40px;">
<h3 class="cathead">Support Material</h3>
<p>Any job specs that relate specifically to support material can be found in this section.</p>
<div class="catcards">
<div class="card" id="si-SupportMaterial-Research" primarysort="2" secondarysort="Style_Guide">
<h5 class="alert alert-success">
<a data-toggle="collapse" data-target="#si-Research" href="javascript:void(0);">
<span class="badge role-icon badge-success">Style Guide</span>
<span>Research</span>
</a>
</h5>
<div id="si-Research" class="card-body card-normal collapse">
<p>
<table width="100%" cellpadding="2" class="table table-condensed table-bordered">
<th colspan="2">Job Spec</th>
<tr>
<td>
<p>If the spelling of a name, word, phrase or specialist term is unsure, then it needs verifying with an internet search. Highlight it by writing it in [].</p>
</td>
</tr>
</table>
</p>
<div class="troubleshootingopen">
<h5 style="padding-top: 30px;" class="troubleshootingheader">Troubleshooting tips:</h5>
<table width="100%" cellpadding="2" class="table table-condensed table-bordered">
<tr>
<th class="troubleshooting" width="180px">Problem</th>
<th class="troubleshooting">Solution</th>
</tr>
<tr>
<td class="troubleshooting">Quick Google check</td>
<td class="troubleshooting">If there is a name, word, phrase or specialist term that needs varifying with an internet search, then it is easy to search for the word by highlighting it.</td>
</tr>
</table>
</div>
</div>
</div>
<div class="card" id="si-SupportMaterial-Usingfacesheetsandsupportmaterial" primarysort="2" secondarysort="Style_Guide">
<h5 class="alert alert-success">
<a data-toggle="collapse" data-target="#si-Usingfacesheetsandsupportmaterial" href="javascript:void(0);">
<span class="badge role-icon badge-success">Style Guide</span>
<span>Using face sheets and support material</span>
</a>
</h5>
<div id="si-Usingfacesheetsandsupportmaterial" class="card-body card-normal collapse">
<p>
<table width="100%" cellpadding="2" class="table table-condensed table-bordered">
<th colspan="2">Job Spec</th>
<tr>
<td>
<p>If you have been provided support material, then ensure that it is used when transcribing the media file.</p>
<p>Support material is provided to us by the client, it is not created by eLanguageWorld.</p>
<p>Support material can come in many forms, but the most common type of support material provided for pre-edit jobs is the face sheet.</p>
<p>If a face sheet has been provided, ensure that your script's speaker labels reflect the spellings of the names in the face sheet.</p>
<p>Also, people often refer to other speakers in their dialogue. When this happens, make sure that use the correct spelling according to the face sheet. However, if someone refers to somebody by their nickname in the dialogue, but the source script only has their actual name, make sure you type what was actually said. Make an educated guess to the spelling of the nickname.</p>
<p>If support material has been provided, the client expects it to be visible and referred to whilst typing the script. Consider opening the face sheet on a second screen or printing it out in order to fulfil this expectation. Mistakes found in a script that could have been avoided by referring to the support material will be perceived as negligent and inattentive by the client.</p>
</td>
</tr>
</table>
</p>
</div>
</div>
</div>
</div>
<div id="tab-Admin" style="padding-bottom: 40px;">
<h3 class="cathead">Admin</h3>
<p>Any job specs that relate specifically to admin and availability can be found in this section.</p>
<div class="catcards"/>
</div>
</div>
</div>
</div>
<script>$(document).ready(function () {$("#sidebar").mCustomScrollbar({ theme: "minimal" }); $('#sidebarCollapse').on('click', function () { $('#sidebar, #content').toggleClass('active'); $('.collapse.in').toggleClass('in'); $('a[aria-expanded=true]').attr('aria-expanded', 'false'); }); });</script>
<h1>Welcome to My Simple Page</h1>
<button id="alertButton" type="button">Show Alert</button>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Badge Restore job-specs app in the main entrypoint

This change turns index.html into a standalone alert demo and removes the entire Job Specs interface (all sections, navigation, and supporting asset wiring), so any user opening the main page will no longer be able to access the product’s actual content. Because index.html is the repository’s primary entrypoint, this is a release-blocking functional regression rather than a cosmetic simplification; the demo should live in a separate file instead of replacing the app page.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant