We link a lot to different pages internally and externally. What do you guys think of adding a new component: "Broken link"? IMO, the Correction/Clarification component can be concentrated to correction and clarification of content.

cheers,

John
----------------------
Drupal Norge
hvor oversettere, brukere, utviklere og leverandører av Drupal i Norge samles

Comments

Wolfflow’s picture

Hi @JohnNoc, I have somehow understand your suggestion, could you please add some explanations on where and what we will be using the "Broken Link?" flag. Maybe my question is really naive but would help me to understand better. Thanks

johnnoc’s picture

Here is a scenario.
A user is viewing a handbook page then clicked on a link. Ooops! Page not found. The user then decides to submit an issue to the Documentation project queue. Issue settings: Project? Documentation, yup that's appropriate. Component? Hmm... Should it be under "correction/clarification" or "outdated"?

IMO, the docs team will have a better overview of the issue components if "correction/clarification" and "outdated" are specific to to the content. It will also lessen the confusion of some users in submitting an issue if it is just a broken link, especially the NNEs.

So my proposal is...
Issue settings:
Project: Documentation
Component: Broken links

Cheers,
John

Wolfflow’s picture

+1 Yes, very good feedback. Thanks.

alexanderpas’s picture

currently, broken link is under webmasters, however, it would be good to add it for documentation too.

leehunter’s picture

Title: New component? » New doc issue queue component for broken links?

Expanded title a bit for clarity

add1sun’s picture

Hm, I'd actually like to avoid adding more components. Now that people can edit the handbook pages, they can fix most broken links themselves. I'm not sure that we really need a whole component for this.

johnnoc’s picture

Status: Active » Closed (won't fix)

I started this issue before we opened editing rights. With what we have today, I would have not suggested this :-)

Since I am the one who made this feature request, and I don't want it anymore... "wont fix"