maths / stack-web Goto Github PK

I am due to upload at least one new case study by the end of the week. The last time I did this, sorting out the navigation within case studies was a bit of a nightmare. I am hoping to document things this time round to add it to the documentation in this repo but wanted to pose the question as to whether the navigation is valuable enough to keep or it could be simplified (eg don't navigate from the last back to the first and vice-versa).

I propose adding "STACK website contributor" to the "I am a..." list in the Get Started section to get to the website documentation. What would be required is:

1. an icon (I'm not good with design!)
2. a documentation landing page
3. an outline on what to include in the documentation, for example:

• Updating the website guide
• Adding a case study guide
• Adding a member to a community group
• Adding a project (once the relevant branch is published)

I will start working on this soon but any comments or additions on a possible design are welcome.

The Updating the website guide is missing details on syncing forks from maths/stack-web, branching (do we need to include this?) and conflicts missing from website updates guide.

A section on dealing with conflicts in PRs would be useful but I've never had to do this, it'd be good to do this in collaboration with someone else to artificially create conflicts

If you open the Case Studies dropdown and hover over the year then it gives you the different case studies for that year. However, if you click on a year, then it is impossible to get back to that year's case studies unless you refresh the website.

@samfearn could you replicate the process you set up in the case studies section for the projects in the projects branch? This could also be done in the meeting reports page but I think it's not as urgent (maybe a different issue?).

Thanks!