Skip to content

Commit

Permalink
New website changes
Browse files Browse the repository at this point in the history
  • Loading branch information
Kameshwaran committed Sep 19, 2018
1 parent 0469f90 commit 9c5f543
Show file tree
Hide file tree
Showing 1,087 changed files with 119,009 additions and 30 deletions.
97 changes: 97 additions & 0 deletions .eslintrc
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
{
"parser": "babel-eslint",
"extends": [
"eslint:recommended",
"plugin:react/recommended"
],
"env": {
"browser": true,
"node": true
},
"plugins": [
"react"
],
"parserOptions": {
"ecmaVersion": 6,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true,
"generators": true,
"experimentalObjectRestSpread": true
}
},
"rules": {
"max-len": 0,
"semi": [
2,
"never"
],
"comma-dangle": 0,
"arrow-parens": 0,
"no-useless-escape": 0,
"consistent-return": 0,
"arrow-body-style": 0,
"no-underscore-dangle": 0,
"no-plusplus": 0,
"no-console": [
1,
{
"allow": [
"warn",
"error"
]
}
],
"no-unused-vars": [
1,
{
"vars": "all",
"args": "none"
}
],
"no-use-before-define": 0,
"import/newline-after-import": 0,
"import/extensions": 0,
"object-shorthand": 0,
"import/no-unresolved": 0,
"no-warning-comments": [
"warn",
{
"terms": [
"todo",
"fixme",
"@todo",
"@fixme"
],
"location": "start"
}
],
"jsx-quotes": [
2,
"prefer-single"
],
"react/forbid-prop-types": 0,
"react/prefer-stateless-function": 1,
"react/prop-types": 0,
"react/no-string-refs": 0,
"react/no-unescaped-entities": 0,
"react/no-unused-prop-types": 0,
"react/jsx-filename-extension": 0,
"react/no-danger": 0,
"react/no-deprecated": 0,
"react/no-is-mounted": 0,
"react/sort-comp": [
2,
{
"order": [
"type-annotations",
"static-methods",
"lifecycle",
"/^on.+$/",
"everything-else",
"render"
]
}
]
}
}
42 changes: 12 additions & 30 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,35 +1,17 @@
# node / npm
# Project dependencies
.cache
node_modules
serverless
serverless-blog
.serverless
*.log

# serverless backend
config.json
githubUser.json

# third party external content
content-external
yarn-error.log
.idea/

# phenomic build
dist
backend/post-scheduler
secrets.json
.env

#IDE Stuff
**/.idea
.idea

#OS STUFF
# Build directory
/public
.DS_Store
.tmp

# Ignore stuff pull from serverless core repo
content/framework/docs
# Blog content gets pulled from https://github.com/serverless/blog
content/blog
src/pages/Blog/generated-authors.json
# blogs
serverless-blog
serverless

generated-menu-items.js
# dynamic config
.env.development
.env.production
3 changes: 3 additions & 0 deletions .gitmodules
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
[submodule "serverless-design-system"]
path = serverless-design-system
url = https://github.com/Codebrahma/serverless-design-system.git
6 changes: 6 additions & 0 deletions .prettierrc
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"semi": false,
"singleQuote": true,
"trailingComma": "es5",
"printWidth": 80
}
22 changes: 22 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
The MIT License (MIT)

Copyright (c) 2015 gatsbyjs

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

89 changes: 89 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
# [Serverless Site](https://serverless.com/)

This site is 100% serverless! :tada:

Built using react, redux and [gatsby](https://github.com/gatsbyjs/gatsby) this site is statically built and hosted on the [netlify](https://www.netlify.com/) CDN for 🔥blazingly fast performance and scale.

The [site content](https://github.com/serverless/site/tree/master/content), [docs](https://github.com/serverless/serverless/tree/master/docs), and [blog](https://github.com/serverless/blog) are hosted on github, so if you see a typo or error feel free to contribute back!

API calls are made with the [serverless framework](https://github.com/serverless/serverless/tree/master/docs) pinging AWS lambda functions. User Authentication is handled via [Auth0](https://auth0.com). Site search handled by [Algolia](https://community.algolia.com/docsearch/).

- [See the site](https://serverless.com/) :point_right: [View the SRC Luke](https://github.com/serverless/site/tree/master/src)
- [Check out the blog](https://serverless.com/blog) :point_right: [Contribute to the blog](https://github.com/serverless/blog)
- [Read the docs](https://serverless.com/framework/docs) :point_right: [Contribute to the docs](https://github.com/serverless/serverless)

# Quick Start

**1. Make sure that you have the Gatsby CLI program installed:**

```sh
npm install --global gatsby-cli
```

**2. Clone down the site**

```bash
git clone [email protected]:serverless/site.git
```

**3. Install site dependencies**

```bash
npm install
```

**3. Run site on your local computer**

```bash
npm run dev
```

Open your browser to http://localhost:8000

Run `npm run syncProd` or `npm run syncLocal` to pull in the blog and docs repos (if the postinstall command doesn't run for you). These 2 commands pull in the external content sources the site uses.

# Editing Site Content

Fork the site and submit a pull request!

When you start the site with `npm start` it will start watching for file changes and they will be automatically refreshed in the site on `http://localhost:8000`

### **Blog edits:**

To make edits to blog posts, edit the files in `./serverless-blog/posts` (this directory is added on `npm i`)

### **Doc edits:**

To make edits to framework docs, edit the files in `./serverless/docs` (this directory is added on `npm i`)

### Editing other pages

To make edits to other pages, edit the markdown in `./content`

Some pages have custom designs/layouts and the html might need to be altered. That content can be found in `./src/layouts` or `./src/pages`

# Publishing Site Updates

**1. Test the build command locally**

```bash
npm run build
```

**2. If build command succeeds, push up your changes to a new branch**

We are using [netlify](http://netlify.com) to distribute the site.

When pushing up to a new branch, netlify will automatically publish that change to a unique subdomain, like: `https://[lowercase-branch-name]--serverless.netlify.com`

For example the branch `updateDocsSetup` published to `https://updatedocssetup--serverless.netlify.com`

Successful deploys are published to the [notifications slack channel](https://serverlessteam.slack.com/archives/notifications)

**Note: The `master` branch is the live site. Never push directly to the master branch!**

**3. Review your live site changes**

If everything looks good on your unique netlify subdomain, you can go ahead and merge your branch to master on github.

Merging branches into master will trigger a site rebuild and `serverless.com` will be updated.
13 changes: 13 additions & 0 deletions content/blog/.MAKE_EDITS_IN_SERVERLESS-BLOG_DIRECTORY
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
-------------
.MAKE_EDITS_IN_SERVERLESS-BLOG_DIRECTORY
Notice to anyone working on the blog
-------------

Any local edits in this /Users/kamesh/Documents/Projects/serverless-gatsby/content/blog/ directory will not be saved

These blog markdown files are pulled from ./serverless-blog directory

Please make changes to blog posts in /Users/kamesh/Documents/Projects/serverless-gatsby/serverless-blog/posts/.

Then you can push up those changes to the https://github.com/codebrahma/blog repo

64 changes: 64 additions & 0 deletions content/blog/10-serverless-experts-you-should-follow-on-twitter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
---
title: '10 Serverless Experts You Should Follow on Twitter'
description: 'The top Twitter accounts you should follow to stay on top of serverless, event-driven architecture, and other tech news.'
date: '2017-08-16'
layout: Post
thumbnail: 'https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/twitter+follow.jpg'
authors:
- AndreaPasswater
gitLink: /2017-08-16-10-serverless-experts-you-should-follow-on-twitter.md
---

This list was ordered more or less by a random number generator, so don’t take these as ranked recommendations. They’re all equally worth an add.

## Mark Russinovich ([@markrussinovich](https://twitter.com/markrussinovich))
Mark is the CTO of Azure, so suffice to say he’s an insider. He’s (obviously) always the first to post about updates from Azure, but what we love most about his feed is that he re-tweets the best stuff from all over. It isn’t all product all the time—there are also server jokes.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/markrussinovich1.png "markrussinovich.png")](https://twitter.com/markrussinovich)

## Marcia Villalba ([@mavi888uy](https://twitter.com/mavi888uy?lang=en))
Marcia makes some stellar content: she runs the FooBar blog and also creates tech(and serverless)-centric videos for the FooBar YouTube channel. Follow her to make sure you get her latest knowledge nuggets first.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/mavi888uy.png "mavi888uy.png")](https://twitter.com/mavi888uy?lang=en)

## David Packman ([@david_packman](https://twitter.com/david_packman))
David founded Beijing’s AWS meetup group, and somehow has an incredibly in-depth tech news dive happening on his twitter feed, despite having relatively few retweets. He must be reading *everything published on the internet*. It isn’t just serverless and cloud he talks about, but Docker, IoT, and cybersecurity.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/david_packman.png "david_packman.png")](https://twitter.com/david_packman)

## Charity Majors ([@mipsytipsy](https://twitter.com/mipsytipsy))
Charity is lined up to speak at ServerlessConf 2017, so clearly she's doing several things right. Her feed is all about CloudOps, debugging, AWS and maximizing efficiency with tools. She's incredibly active on twitter, but hardly retweets. All original content here.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/mipsytipsy.png "mipsytipsy.png")](https://twitter.com/mipsytipsy)

## Ben Kehoe ([@ben11kehoe](https://twitter.com/ben11kehoe))
Ben makes serverless robots for his day job. Not to mention, he’s an AWS Community Hero. His feed is brimming with serverless and AWS insights. Plus, he’s got a nice perspective on IoT, and is right on the pulse of the greater cloud community.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/ben11kehoe.png "ben11kehoe.png")](https://twitter.com/ben11kehoe)

## Ryan Scott Brown ([@ryan_sb](https://twitter.com/ryan_sb))
Ryan is a Red Hatter who has an eye for tech-centric think pieces. He’s a huge advocate of serverless and culls a lot of really helpful resources into his feed. Warning: he’ll convert you to Python.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/ryan_sb.png "ryan_sb.png")](https://twitter.com/ryan_sb)

## Jared Short ([@ShortJared](https://twitter.com/ShortJared))
Jared is the kind of person that, when he says something sounds ‘interesting’, at least ten people scramble to turn it into a product. He has a hacker’s experimental mindset about all the tools he uses, and tweets directly at the companies to start conversations about new features. Bonus: as a person who actively gives talks and presentations himself, he’ll also let you know about the best ones he’s seen lately.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/ShortJared.png "ShortJared.png")](https://twitter.com/ShortJared)

## Ryan Lewis ([@ryanmurakami](https://twitter.com/ryanmurakami))
Ryan makes a lot of content for his tech-centric blog and YouTube channel. He’s often the first person we see post overviews of new tools and frameworks—NPX, Webpack 3, AWS CodeStar. Really useful info for watercooler factoids and bragging rights.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/ryanmurakami.png "ryanmurakami.png")](https://twitter.com/ryanmurakami)

## Linda Nichols ([@lynnaloo](https://twitter.com/lynnaloo))
Linda is a true technology advocate. She’s active in the open source community and teaches kids how to program robots. Her cred recently got her an interview on the Serverless Podcast. In addition to serverless news, her feed includes, VR, arduino, photos of JavaScript-powered fighting robots and (wait for it…) cats.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/lynnaloo.png "lynnaloo.png")](https://twitter.com/lynnaloo)

## Erica Windisch ([@ewindisch](https://twitter.com/ewindisch))
Erica is the CTO at IOPipes, and the first thing you’ll see on her Twitter bio is that she’s “making the cloud and destroying monoliths.” She gets into enlightening Twitter conversations with leaders at Azure and Lambda about where serverless is today, and where it is (or should be) going next.

[![](https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/10+Serverless+Heroes/ewindisch.png "ewindisch.png")](https://twitter.com/ewindisch)

Now, is this everyone to follow on Twitter? Definitely not. But we hope it'll give you a good start.
Loading

0 comments on commit 9c5f543

Please sign in to comment.