There are still some useful "information and tutorial" links for new mbed users that exist only on the cookbook main page and not anywhere else on the site. Given the search makes things hard to find, it is helpful to have these links posted somewhere. Most of these links already go to notebook pages - so I think the main issue is perhaps the cookbook main page links. It does not seem to make sense to setup these useful cookbook links somehow as a component page instead (at least the way it is setup now)?

A couple of useful pages are still setup as cookbook pages (I think there was a time when notebook pages were not available). There is no easy migration path for these to a notebook page for users if you can't open an edit window and cut the wiki markup language source to a new notebook page. It would be nice if there was a way to do this. About same issue occurs if someone ever needs to fix/update another MIA users notebook page. I saw this issue when I was asked to move some of the drivers from the cookbook to the component page.

One solution might be to have someone at ARM that understands mbed very well and can tell quickly what is useful to be the owner/editor of just the cookbook main page links. A new version of the cookbook main page could kill off quite a few of the old cookbook links that no longer make sense and still keep it useful. Moving "most" of the drivers to component pages has left it a bit messed up and a shorter version would also be more useful for new users.

In any case, the cookbook instructions at https://developer.mbed.org/cookbook/About-the-Cookbook should be updated.

Search is now back (17/8/2015), thank you.

I'm not offering to make changes. I'm offering for someone to create a new page in a new place where it can be maintained by them and to change links to the old page so they point to the new one as a way to allow the content that is in the cookbook to be visible and the bits that are still worth maintaining can be.

This is only the second time someone has asked about editing a page on the cookbook since it was made read-only.

Martin was.

And it really did look like you were too. But if it even ends up to only changing currently existing links, then you really should just do the rm -rf /cookbook.

Hi Paul, I know the search is a problem, it's something I'm hoping to get some time to work on next week. I can't think of anything else that's not working off the top of my head.

We already require a working email address before allowing posting, the spammers have no problems passing this test because they are actual people as far as I can tell. This means they will pass any test that you are able to pass. There's some discussion about this already here.

mbed-src is, frankly, an enormous library. If you can use the built version I would strongly recommend it. I can well imagine that mbed-src compiles are slow and I suspect they are when done on a local machine as well. Your comment is the first I've heard that they are unreliable though.

You can compile locally already if you export your project but system load is not a major factor in compile times, compile times don't increase significantly when there are more users using the compiler.

Thanks for a good explanation Steven, that spam is a headache.

Compiling with mbed-src is only unreliable if the system times out, that doesn't happen too often.

It's only the search that remains an issue, it might be an idea to auto remove unanswered questions after a period of say 90 days though. It would trim them down a bit.

Paul, I've created a handbook page to try to help track the known issues with the website /handbook/Website_Known_Issues

Here is a short term user search solution - use Google search restricted to the mbed domain. Here is an example of what to type in the Google search line for mbed LCD items:

"lcd" site:https://developer.mbed.org/

You can also set this under settings->Advanced search on the main Google page.