maintainerati / site Goto Github PK

The website is mostly geared towards being a blog. It's not a blog. The site needs to be redesigned to support how we actually use it: To make occasional announcements, and to share the event reports and other long-form (PDF) content we create.

• Redesign landing page with clear calls to action above the fold
• Create one single page for the Berlin reports (currently two: A landing page, and a blog post)
• Remove everything else from the front page (keeping existing content at existing URLs to the extent we can)

Hugo is a little bit of a pain for me and the other board members; it's hard for us to find templates we need to modify sometimes (and template organization has gone to shit as a result), and cumbersome to add new content (you have to remember not only the magic Hugo command, but run it from the right path). Maybe we're asking too much from a static site generator, I don't know.

Anyway, I've heard interesting things about 11ty, and I am curious to understand if it is going to help make site maintenance easier. The scope of this issue is to understand whether 11ty can help us with these problems:

• 1. Creating and modifying templates should happen in exactly one place (Hugo can do this, but since we're basing the theme on an existing template that we can't modify in place, we have two places for the templating as we're using it)
• 2. Building should be pretty straightforward
• 3. Testing too! Right now, I have three separate config files for Hugo, a common one, a production one, and a development one.
• 4. Creating new content should be really straightforward (secondary because we aren't making that much content yet!)
• 5. It should be pleasant for our front-end devs to use.

I'd like to add @GawainLynch and @erinbtaylor to this discussion as well.

I can make an initial draft and publish it on zeplin or something. If we get an actual designer to join that would be great, but I'll probably manage prototyping.

Things I'd like to push for:

• Component modularity
  Allowing us to move stuff around until we find something that works for us.

• Integrating social media on the page
  As much of the conversation seem to happen on twitter, it makes sense to me to integrate it into the webpage. Some options are lists, hashtags or just the official account.

• Content spotlight
  A section for content spotlight where we can highlight things that are important or current, for instance the Berlin Report or any upcoming event.

I always forget to build for production when I push my code. Let's move to Netlify, which will handle all of that for us automatically.

Sync? Async? Chat? Forums? Discord? Discourse?

Let's decide, and move forward.

The website says the next conference is in 2019. Should we change that copy?

Also, the copyright could be changed.