Not really sure what this should look like, but should be information for people interested in coming to UNC, and resources for them. Something encouraging, maybe an interest form for highschoolers? Lots of options here.

Since we don't control the HTML of the rendered posts, we can't inject custom components to use our preferred styles. Instead we have to apply styles to the container of the post.

Content management is the most important part of the current website. Giving non-technical users the ability to edit nearly all content is a big benefit.

Please comment with thoughts on the approaches or if you have additional ideas.

Approaches

Here are a few of the approaches we could take.

Use a Pre-built CMS

If we integrated something like KeystoneJS, we would get this functionality with the downside of having to integrate with what the framework expects.

Use a Static Site Generator

There are plenty of static site generators, Hugo, Jekyll, Gatsby, etc., which allow us to write content, typically in Markdown. The benefit of this approach is we don't have to implement rich text editing which would save a ton of time. The downside is that the content would live in the repository, meaning users would have to be able to use Git to make edits. This raises the entry barrier for new editors and requires more training as the website gets passed down.

Use an Existing CMS in Headless Mode

With this approach, we would only have to handle the frontend of the editing process. This eliminates the necessity for a backend which would save time. One downside of this approach is we would also have to worry about deploying the CMS providing the backend separately.

Happens on Chrome.

In addition to having pictures, we should also have organized bits of film/callahan/highlight videos.

The team page should default to showing the most recent roster. There should also be a method for viewing the roster of any year.

When viewing an individual post, its unclear as a user where I am in relation to the rest of the site. We should have some sort of breadcrumb-like navigation at the top and bottom.

Similar to the info at the top of the individual post page, we should use icons and colors to make the post list more visually appealing.

The styling on the navbar could be cleaned up. It would be nice to actually collapse the navigation on smaller screens. The title could also look better if we add an icon. Finally, the divider between the main navigation bar and the links on smaller screens stands out too much.

If a blog post title is long enough to wrap, the underline looks off.

Potential solutions are to use text-decoration: underline so we actually get an underline on the whole text or we could get rid of the border on the header and add a more neutral grey <hr /> separating the title and rest of the post information.

The contact page should contain links to our Facebook, Twitter, and Instagram accounts.

The footer should contain links to our social media pages as well as a copyright notice. I think it would also be cool to have a link to the source code.

The current title for all pages is "Webpack App". We should have a default title and then set titles for each page using something like react-helmet.

Probably on the home page.

Right now the mobile menu remains open after clicking a link, which is rather unexpected.

Where they can provide their email and their level of engagement. (if they want to be notified when highlight videos come out, or when we are doing fundraisers, or going to tournaments.)

The homepage can have a horizontal scroll on small screens if there is a long unbroken string of text, such as a link. The fix is to add the following CSS snippet:

overflow-wrap: break-word;

The info panels with a heading, picture, and text should be pulled from the API.