aspinsiders / aspinsiders.com Goto Github PK

The CSS is simple but using SCSS would make it look better. For example, this:

nav {
    background-color: black;
    display: block;
}

nav ul {
    list-style-type: none;
}

nav ul li {
    display: inline-block;
}

nav ul li a {
    padding: 15px;
    display: inline-block;
    text-decoration: none;
    color: #FFF;
    font-weight: normal;
    font-size: 12px;
}

nav ul li a:hover {
    background-color: #333;
}

could be better organized into this:

nav {
    background-color: black;
    display: block;
  ul {
    list-style-type: none;

    li {
      display: inline-block;

      a {
          padding: 15px;
          display: inline-block;
          text-decoration: none;
          color: #FFF;
          font-weight: normal;
          font-size: 12px;

          &:hover {
            background-color: #333;
          }
      }
    }
  }
}

We should try and get members to vote on a new website design from existing Jekyll themes, suggested by the membership & shortlisted to a handful for voting on.

Initial ideas for features:

• Github sync with members activity, showing ASPInsider contributions across the .NET space (not entirely sure how this might work with GH tokens & a static site, but an idea nevertheless)
• Extended personal bios (Gravatar, social media contact info, optional email address display, personal/professional website, etc.)
• Blog synchronisation (aspinsiders.com would act as an RSS aggregator, containing excerpts, categories, and linking direct to a member's blog, for SEO purposes)

Please comment to upvote or add other features you'd like to see.

... instead of redirecting to it.

@nothingmn / @vcsjones, instructions on how to set the DNS entries are here:
https://help.github.com/articles/using-a-custom-domain-with-github-pages/

I'll send a PR with the CNAME file, shortly.

GitHub recently announced support for HTTPS on custom domains hosted on GitHub Pages by partnering with Let's Encrypt who issues the certificates.

We can benefit from that and in order to support HTTPS we just need to change the A records in the DNS settings for our domain.

@ardalis, could you please:

1. Delete all existing A records for aspinsiders.com

2. Add the 4 (four) A records below to aspinsiders.com

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

More detailed instructions here if you need.

ps: Please, let me know when it's done, so I can flip the switch on the GitHub settings for HTTPS.