[Idea]: Labelling nginx and nginx plus features seperately in the header of each feature

[pumpumx]

What is your idea for improving documentation?

I am skimming through docs and realized that it's hard to distinguish between the regular nginx and nginx plus feature. The desirable solution is simply adding a plus symbol or (NGINX PLUS) alongside with each header tab.
Example : slow_server is nginx plus feature so in the header we can instead add slow server (PLUS/NGINX PLUS/+)
I am ready to work on it , small feature but increases readability.

Which product or products does this idea relate to?

NGINX Plus

Does this idea relate to other issues?

No response

Are there alternative ideas for improving the same topic?

No response

Any additional information

No response

[mjang]

Hello @pumpumx . This is a really good idea. I've started an internal conversation to see if we've looked at this idea before.

The desirable solution is simply adding a plus symbol or (NGINX PLUS) alongside with each header tab.

My initial concern is how we would address links to each header / tab. If we only add a label, that could break links to pages and sections in the NGINX Plus docs

[pumpumx]

The point is not about addressing link , when i was reading let's say the http_health section of the documents i was having issues in differentiating which directive is a nginx and nginx plus feature , so in order to make the document clear i provided that solution in which we can add a certain symbol (+) or (NGINX PLUS) using simple h1/h2 html tag at the adjacent position of each header so that skimming through docs is easier.

The difference:

[pumpumx]

Should i start working on this feature?

[mjang]

@pumpumx can you submit a PR with an example of what you're proposing? We can test it in local builds. I'll be happy to share our results / feedback