autoyast.html in SUMA 4.0/4.1 docs not linked in sidebar

[uyuni-project]

autoyast.html in SUMA 4.0/4.1 docs not linked in sidebar

Ftr, I have no stakes in this issue, I just randomly stumbled across this file because it was linked from somewhere.

Lana just explained to me that removal from the sidebar tree might be the precursor to files being deleted. I am a bit confused about that practice -- because taking it out of the sidebar tree does not look intentional or explicit to me, and there is no discernible difference to an actual bug. Maybe a note saying "hey, do you think this document is helpful? please file a bug report or it will be removed next week" (paraphrasing, obviously) might be a more explicit way of achieving this..?

[Loquacity]

So I think this case might actually be an error. Investigating now.

[Loquacity]

Lana just explained to me that removal from the sidebar tree might be the precursor to files being deleted. I am a bit confused about that practice -- because taking it out of the sidebar tree does not look intentional or explicit to me, and there is no discernible difference to an actual bug. Maybe a note saying "hey, do you think this document is helpful? please file a bug report or it will be removed next week" (paraphrasing, obviously) might be a more explicit way of achieving this..?

This is a result of the major content reorganisations we've been doing over the past couple of releases, and also a function of how our search tool works. Usually, we determine that the content needs to be moved elsewhere in the suite, so we comment out the page in the nav, leave a comment to explain why and where the content has moved to (datestamped), but leave the page published. This means that when we come across the page next, we can make an educated guess about whether or not to delete the page, based on how much time has elapsed, and whether or not anyone has yelled. Our search tool indexes the entire suite, not just the pages linked in the nav, so it will turn up results that have been delinked. That means that we have been able to use this method as a sort of "soft" deletion, which has been useful with all the content restructures we have been dealing with. All that said, I do agree that a more formal process is probably required. Now that our docs suite is starting to stabilise, that is something we will be able to introduce. I'll add it to my list, and make sure it gets discussed in planning.