SSWConsulting / SSWConsulting/SSW.Rules

🦙 TinaCMS Dependency - Rule Editing Improvements - Editing area on the left

Open
#2,198 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

TinaCMS YakShaver
Dominant language
TypeScript
Stars
26
Forks
17
Avg merge
14h 39m
Merged PRs (30d)
2

Description

Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @tiagov8, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (2 min 11 sec)

  Url from screen share: https://www.ssw.com.au/rules/admin#/?rules/does-your-website-have-an-about-us-section

Pain

Enhance the rule editing experience by hiding the H1 tag option, disabling the link on the intro embed tag, and adding a separator line option.

Acceptance Criteria
  1. The H1 tag option should be hidden in the rule editor as the heading is always the title.
    as per https://www.ssw.com.au/rules/use-heading-tags-h1-h2-h3
  2. The intro embed tag should not be clickable to prevent navigation to a non-functional page.
  3. A separator line option should be available in the editor to visually separate content sections, similar to the effect of adding three dashes.
Screenshot

Screenshot
Figure: Heading one tag should not be available as it is always the title.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the TinaCMS rule editor shown at the provided SSW Rules admin URL and trace the controls for headings, intro embeds, and content separators. Verify the current editor behavior against the three acceptance criteria. Done means H1 is unavailable, the intro embed is not clickable, and a separator option produces the requested visual separation.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.