@borpin Brian, you’ve managed to elucidate a lot of the points that I’ve struggled with for a long time. I think the key problem is that OEM had grown organically over time and …
Yes, but there comes a time when old stuff simply has to go. Or be incorporated into current data & practice. There’s nothing to stop you from marking the material “Obsolete” or something like that as a warning that it is superseded/not supported/not in development or whatever.
Having contributed a fair slice to Building Blocks, I’m only too well aware that there’s a lot of duplication in there. This is where a critical review based on “what would we have, knowing what we know now, if we were starting from nothing” should take place and only when that overall strategy been decided should you look at the old material to decide what is usable for incorporation.
But it does if it’s greyed out - it serves as a signpost to let you know where you are. Sorry Brian, but I hate menus that reload the page I’m on. [F5] does that if I need it.
I concur. When I was putting together a website for my friend’s B&B business, I spent quite a bit of time reading up about page layout and where to place things, and the point that everyone hammered home was “you’re only ever one click away from losing a customer”. Everybody involved here needs to step back and look at the site from an ignorant newcomer’s viewpoint. And make sure that new customer doesn’t click away for all the reasons everybody has mentioned.
That’s what I mean by ‘what is usable for incorporation’. They’re good pages. Students etc still use them and build projects with them. But they must not be shoehorned into a structure just because the structure is there. If ‘Learn’ is about Megni-supplied kit and OEM software, those pages should NOT be there. I think I’m with Trystan here - those pages demonstrate the theory, so that’s where they go (but maybe rewritten to incorporate the material better into the theory rather than transplanting them wholesale). Like a lot of the material here, there’s a lot of crossover, and that’s the source of many of the problems that are surfacing in this discussion.
That’s the biggest understatement of the year (so far). It’s not ‘not easy’, it’s very, very hard. And time-consuming. And not often appreciated. And definitely not cool.
But done properly, it’ll cut a slice off the support effort that goes into the forum.