organise directories for pages

[supernord]

No description provided.

[tlitfin-unsw]

LGTM!

I noticed that there are several content pages that we don't currently index but can be accessed via a direct link (guide_template, provide_documentation, basics, pymol, binder_access, example_page, EBI-alphafold-guide, protein_struct_inference). I think some of these are good to have as placeholders since we will likely add content and index them in the future.

We can probably remove "activities/binder_access" since it has been superseded by the bindcraft_access activity. Not sure if we should clean up any others?

[supernord]

Thanks @tlitfin-unsw 😄

I’ve removed a couple of the markdowns, as they duplicated information.
I also organised the guides into a single directory pages/guides.

Questions:

• Should a guide be written for pymol? Maybe one exists already that we can link to from the interactive tables?
• There’s also a lot we could potentially add to the CLI instructions (cli_instruct directory), but I’m unsure if this website is the right place for this information
• For protein_struct_inference.md, should this be the start for a list of software that has been optimised and/or tested on specific computational infrastructures?

[tlitfin-unsw]

1. There are many PyMOL guides floating around. I will have to see if one or more is suitable for our purpose otherwise we can make something here.
2. Not sure about this one. I don't think we have the content to populate at this time either way.
3. I think we are also not ready to populate this yet but could be useful to index available resources in the future.

We can either leave the pages for now or delete them and get them from git history if we want to recover them later. Either way we can merge this PR. I will create an issue for the PyMOL guide at least because it would be good to have something available for that.