Skip to content

Commit 2f7c9f2

Browse files
committed
Rename Serverless Stack to SST
1 parent 4f1a0cc commit 2f7c9f2

File tree

107 files changed

+198
-198
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

107 files changed

+198
-198
lines changed

CONTRIBUTING.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# Contributing
22

3-
Thank you for considering to contribute. Here is what Serverless Stack Guide is trying to accomplish and how you can help. We use [Discord][discord] for our contributors, feel free to join us there.
3+
Thank you for considering to contribute. Here is what SST Guide is trying to accomplish and how you can help. We use [Discord][discord] for our contributors, feel free to join us there.
44

55
## Project Goals
66

77
We are trying to create a really comprehensive and up to date guide to help people build production ready full-stack serverless applications. To start, we are focussing on building a CRUD API backend with Serverless Framework on AWS and a single-page app web frontend using React.
88

9-
We want Serverless Stack Guide to cover a very broad collection of technologies, services, and concepts that gives people the confidence to use this guide to build their next project. Too often we come across tutorials or blog posts that sound very promising but leave us hanging once we get to the complicated bits.
9+
We want SST Guide to cover a very broad collection of technologies, services, and concepts that gives people the confidence to use this guide to build their next project. Too often we come across tutorials or blog posts that sound very promising but leave us hanging once we get to the complicated bits.
1010

1111
However while we want to be as comprehensive as possible, we also want to make sure that you can get started easily. To achieve this we are using the following structure and layout.
1212

@@ -44,7 +44,7 @@ Additionally, you are welcome to provide general feedback and suggestions via ou
4444

4545
### Keep the core guide updated
4646

47-
The Serverless Stack Guide is reliant on a large number of services and open source libraries and projects. Here is what needs updating:
47+
The SST Guide is reliant on a large number of services and open source libraries and projects. Here is what needs updating:
4848

4949
### Updating Screenshots
5050

@@ -74,7 +74,7 @@ Once all the PRs are merged, we'll tag the repo (tutorial & demo app) with the n
7474

7575
### Add an Extra Credit Chapter
7676

77-
The core chapters are missing some extra details (for the sake of simplicity) that are necessary once you start customizing the Serverless Stack setup. Additionally, there are cases that we just don't handle in the core chapters. [Here is a rough list of topics that have been requested](https://github.com/AnomalyInnovations/serverless-stack-com/projects/1#column-2785572). This is not an exhaustive list. If you have some ideas to extend some of the demo app functionality, feel free to get in touch with us. Here is how to go about adding a new extra credit chapter:
77+
The core chapters are missing some extra details (for the sake of simplicity) that are necessary once you start customizing SST setup. Additionally, there are cases that we just don't handle in the core chapters. [Here is a rough list of topics that have been requested](https://github.com/AnomalyInnovations/serverless-stack-com/projects/1#column-2785572). This is not an exhaustive list. If you have some ideas to extend some of the demo app functionality, feel free to get in touch with us. Here is how to go about adding a new extra credit chapter:
7878

7979
- Let us know via [Discord][discord] that you are planning to work on it
8080
- Create a new issue in GitHub to track progress

README.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<p align="center">
22
<a href="https://serverless-stack.com/">
3-
<img alt="Serverless Stack" src="https://github.com/AnomalyInnovations/serverless-stack-com/raw/master/assets/logo-large.png" width="377" />
3+
<img alt="SST" src="https://github.com/AnomalyInnovations/serverless-stack-com/raw/master/assets/logo-large.png" width="377" />
44
</a>
55
</p>
66

@@ -12,7 +12,7 @@
1212

1313
------------------------------------------------------------------------------------
1414

15-
The [Serverless Stack Guide](https://serverless-stack.com/guide.html) is a comprehensive open source tutorial for building and deploying full-stack apps using Serverless and React on AWS.
15+
The [SST Guide](https://serverless-stack.com/guide.html) is a comprehensive open source tutorial for building and deploying full-stack apps using Serverless and React on AWS.
1616

1717
We are going to create a [note taking app](https://demo.serverless-stack.com) from scratch using React.js, AWS Lambda, API Gateway, DynamoDB, and Cognito.
1818

@@ -44,11 +44,11 @@ We also have an alternative Serverless Framework version: [backend serverless AP
4444

4545
## Contributing
4646

47-
Thank you for your considering to contribute. [Read more about how you can contribute to Serverless Stack][Contributing].
47+
Thank you for your considering to contribute. [Read more about how you can contribute to SST][Contributing].
4848

4949
## Running Locally
5050

51-
Serverless Stack is built using [Jekyll](https://jekyllrb.com). [Follow these steps to install Jekyll](https://jekyllrb.com/docs/installation/).
51+
SST is built using [Jekyll](https://jekyllrb.com). [Follow these steps to install Jekyll](https://jekyllrb.com/docs/installation/).
5252

5353
#### Viewing Locally
5454

@@ -96,12 +96,12 @@ The above are run automatically through [Github Actions](https://github.com/Anom
9696
<!--
9797
## Sponsors
9898
99-
[**Sponsor Serverless Stack on GitHub**](https://github.com/sponsors/jayair) if you've found this guide useful or would like to be an official supporter. [A big thanks to our supporters](https://serverless-stack.com/sponsors.html)!
99+
[**Sponsor SST on GitHub**](https://github.com/sponsors/jayair) if you've found this guide useful or would like to be an official supporter. [A big thanks to our supporters](https://serverless-stack.com/sponsors.html)!
100100
-->
101101

102102
## Contributors
103103

104-
Thanks to these folks for their contributions to the content of Serverless Stack.
104+
Thanks to these folks for their contributions to the content of SST.
105105

106106
- [Peter Eman Paver Abastillas](https://github.com/jatazoulja): Social login chapters
107107
- [Bernardo Bugmann](https://github.com/bernardobugmann): Translating chapters to Portuguese
@@ -117,7 +117,7 @@ Thanks to these folks for their contributions to the content of Serverless Stack
117117

118118
---
119119

120-
This repo is maintained by [Serverless Stack](https://serverless-stack.com).
120+
This repo is maintained by [SST](https://serverless-stack.com).
121121

122122

123123
[Slack]: https://serverless-stack.com/slack

_chapters/best-practices-for-building-serverless-apps.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ In this section of the guide we'll be covering the best practices for developing
1010

1111
### Background
1212

13-
Serverless Stack was launched back in March 2017. Since then thousands of folks have used the guide to build their first full-stack Serverless app. Many of you have used this as a starting point to build really large applications. Applications that are made up of scores of services worked on by a team of developers.
13+
SST was launched back in March 2017. Since then thousands of folks have used the guide to build their first full-stack Serverless app. Many of you have used this as a starting point to build really large applications. Applications that are made up of scores of services worked on by a team of developers.
1414

1515
However, the challenges that teams face while developing large scale Serverless applications are very different from the one an individual faces while building his or her first app. You've to deal with architectural design decisions and questions that can be hard to answer if you haven't built and managed a large scale Serverless app before. Questions like:
1616

@@ -27,7 +27,7 @@ While there are tons of blog posts out there that answer some of these questions
2727

2828
### A new perspective
2929

30-
Now nearly 3 years into working on Serverless Stack and building large scale Serverless applications, there are some common design patterns that we can confidently share with our readers. Additionally, Serverless as a technology and community has also matured to the point where there are reasonable answers for the above questions.
30+
Now nearly 3 years into working on SST and building large scale Serverless applications, there are some common design patterns that we can confidently share with our readers. Additionally, Serverless as a technology and community has also matured to the point where there are reasonable answers for the above questions.
3131

3232
This new addition to the guide is designed to lay out some of the best practices and give you a solid foundation to use Serverless at your company. You can be confident that as your application and team grows, you'll be on the right track for building something that scales.
3333

_chapters/changelog.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@ title: Changelog
44
lang: en
55
redirect_from: /chapters/older-versions.html
66
date: 2018-04-01 00:00:00
7-
description: A list of all the updates made to Serverless Stack
7+
description: A list of all the updates made to SST
88
ref: changelog
99
comments_id: comments-for-changelog/17
1010
---
1111

12-
As we continue to update Serverless Stack, we want to make sure that we give you a clear idea of all the changes that are being made. This is to ensure that you won't have to go through the entire tutorial again to get caught up on the updates. We also want to leave the older versions up in case you need a reference. This is also useful for readers who are working through the tutorial while it gets updated.
12+
As we continue to update SST, we want to make sure that we give you a clear idea of all the changes that are being made. This is to ensure that you won't have to go through the entire tutorial again to get caught up on the updates. We also want to leave the older versions up in case you need a reference. This is also useful for readers who are working through the tutorial while it gets updated.
1313

14-
Below are the updates we’ve made to Serverless Stack, each with:
14+
Below are the updates we’ve made to SST, each with:
1515

1616
- Each update has a link to an **archived version of the tutorial**
1717
- Updates to the tutorial **compared to the last version**

_chapters/create-an-iam-user.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Select **Add User**.
3030

3131
Enter a **User name** and check **Programmatic access**, then select **Next: Permissions**.
3232

33-
This account will be used by our [AWS CLI](https://aws.amazon.com/cli/) and [Serverless Stack Framework (SST)]({{ site.sst_github_repo }}). They'll be connecting to the AWS API directly and will not be using the Management Console.
33+
This account will be used by our [AWS CLI](https://aws.amazon.com/cli/) and [SST]({{ site.sst_github_repo }}). They'll be connecting to the AWS API directly and will not be using the Management Console.
3434

3535
![Fill in IAM User Info Screenshot](/assets/iam-user/fill-in-iam-user-info.png)
3636

_chapters/deploy-your-serverless-infrastructure.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ layout: post
33
title: Deploy Your Serverless Infrastructure
44
date: 2018-03-04 00:00:00
55
lang: en
6-
description: In this chapter we'll be deploying our entire serverless infrastructure. We are using CDK to define our resources and we are deploying it using the Serverless Stack Toolkit (SST). Our API on the other hand is deployed using Serverless Framework.
6+
description: In this chapter we'll be deploying our entire serverless infrastructure. We are using CDK to define our resources and we are deploying it using SST. Our API on the other hand is deployed using Serverless Framework.
77
code: backend_full
88
ref: deploy-your-serverless-infrastructure
99
comments_id: deploy-your-serverless-infrastructure/167

_chapters/dynamically-generate-social-share-images-with-serverless.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ layout: post
33
title: Dynamically generate social share images with serverless
44
date: 2021-06-25 00:00:00
55
lang: en
6-
description: In this chapter we'll look at how to create a serverless service that dynamically generates social cards for our website or blog. It uses the Serverless Stack Framework (SST) and Puppeteer to generate these images.
6+
description: In this chapter we'll look at how to create a serverless service that dynamically generates social cards for our website or blog. It uses SST and Puppeteer to generate these images.
77
repo: https://github.com/serverless-stack/social-cards
88
ref: dynamically-generate-social-share-images-with-serverless
99
comments_id: dynamically-generate-social-share-images-with-serverless/2419
@@ -15,17 +15,17 @@ Social cards or social share images or open graph images are preview images that
1515

1616
However, creating a unique image for each blog post or page of your website can be time consuming and impractical. So we ideally want to be able to generate these images dynamically based on the title of the blog post or page and some other accompanying information.
1717

18-
We wanted to do something like this for [Serverless Stack](/). And this was a perfect use case for [serverless]({% link _chapters/what-is-serverless.md %}). These images will be generated when your website is shared and it doesn't make sense to run a server to serve these out. So we built our own social cards service with [SST](/)! It's also deployed and managed with [Seed](https://seed.run).
18+
We wanted to do something like this for [SST](/). And this was a perfect use case for [serverless]({% link _chapters/what-is-serverless.md %}). These images will be generated when your website is shared and it doesn't make sense to run a server to serve these out. So we built our own social cards service with [SST](/)! It's also deployed and managed with [Seed](https://seed.run).
1919

2020
For instance, here is what the social card for one of our chapters looks like.
2121

22-
![Social card for Serverless Stack chapter](/assets/dynamically-generate-social-share-images-with-serverless/social-card-for-serverless-stack-chapter.png)
22+
![Social card for SST chapter](/assets/dynamically-generate-social-share-images-with-serverless/social-card-for-serverless-stack-chapter.png)
2323

2424
We also have multiple templates to generate these social cards. Here's one for our blog.
2525

2626
![Social card for sample blog post](/assets/dynamically-generate-social-share-images-with-serverless/social-card-for-sample-blog-post.png)
2727

28-
These images are served out of our social cards service. It's built using [Serverless Stack (SST)](/) and is hosted on AWS:
28+
These images are served out of our social cards service. It's built using [SST](/) and is hosted on AWS:
2929

3030
```bash
3131
https://social-cards.serverless-stack.com
@@ -99,7 +99,7 @@ For now our Lambda function in `functions/lambda.js` just prints out _"Hello Wor
9999

100100
The first step is to create a template for our social share images. These HTML files will be loaded locally and we'll pass in the parameters for our template via the query string.
101101

102-
Let's look at the blog template that we use in Serverless Stack as an example.
102+
Let's look at the blog template that we use in SST as an example.
103103

104104
![Template for social card running locally](/assets/dynamically-generate-social-share-images-with-serverless/template-for-social-card-running-locally.png)
105105

_chapters/es/create-an-iam-user.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Podemos proporcionar una política más detallada aquí y lo cubriremos más ade
4343

4444
![Captura: política de administración añadida](/assets/es/iam-user/added-admin-policy.png)
4545

46-
Este paso es opcional, aquí puedes agregar las etiquetas que creas necesarias al nuevo usuario de IAM, para organizar, seguir o controlar el acceso de los usuarios, por ejemplo, la etiqueta _Application_ tiene el valor _Serverless Stack Guide_ para saber que este usuario fue creado para esta aplicación específica. Luego selecciona **Siguiente: Revisar**.
46+
Este paso es opcional, aquí puedes agregar las etiquetas que creas necesarias al nuevo usuario de IAM, para organizar, seguir o controlar el acceso de los usuarios, por ejemplo, la etiqueta _Application_ tiene el valor _SST Guide_ para saber que este usuario fue creado para esta aplicación específica. Luego selecciona **Siguiente: Revisar**.
4747

4848
![Captura: agregar etiquetas a usuario de IAM](/assets/es/iam-user/add-iam-user-tags.png)
4949

_chapters/es/how-to-get-help.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ En caso de que tengas problemas con un determinado paso, queremos asegurarnos de
1212
- Usamos los foros de [Discourse]({{site.forum_url}}) como sistema de comentarios y hemos ayudado a resolver algunos problemas antes. Así que asegúrate de revisar los comentarios debajo de cada capítulo para ver si alguien más se ha encontrado con el mismo problema que tú.
1313
- Publica en los comentarios del capítulo específico, detallando tu problema y uno de nosotros responderá.
1414

15-
![Captura del foro de Discourse de Serverless Stack](/assets/serverless-stack-discourse-forums.png)
15+
![Captura del foro de Discourse de SST](/assets/serverless-stack-discourse-forums.png)
1616

1717
Esta guía completa está alojada en [GitHub]({{site.github_repo}}). Así que si encuentras un error siempre puedes:
1818

_chapters/es/what-does-this-guide-cover.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Necesitas [Node v8.10 + y NPM v5.5 +](https://nodejs.org/en/). También debes te
5858

5959
### Cómo está estructurada esta guía
6060

61-
La guía se divide en dos partes. Ambas son relativamente independientes. La primera parte cubre lo básico, mientras que la segunda cubre un par de temas avanzados junto con una forma de automatizar la configuración. Lanzamos esta guía a principios de 2017 con solo la primera parte. La comunidad de Serverless Stack ha crecido y muchos de nuestros lectores han usado la configuración descrita en esta guía para crear aplicaciones que impulsan sus negocios.
61+
La guía se divide en dos partes. Ambas son relativamente independientes. La primera parte cubre lo básico, mientras que la segunda cubre un par de temas avanzados junto con una forma de automatizar la configuración. Lanzamos esta guía a principios de 2017 con solo la primera parte. La comunidad de SST ha crecido y muchos de nuestros lectores han usado la configuración descrita en esta guía para crear aplicaciones que impulsan sus negocios.
6262

6363
Así que decidimos ampliar la guía y añadirle una segunda parte. Esta está dirigida a las personas que tienen la intención de utilizar esta configuración para sus proyectos. Automatiza todos los pasos manuales de la parte 1 y lo ayuda a crear un flujo de trabajo listo para producción que puede utilizar para todos sus proyectos sin servidor. Esto es lo que cubrimos en las dos partes.
6464

@@ -91,7 +91,7 @@ Para el frontend:
9191

9292
#### Parte II
9393

94-
Dirigido a personas que buscan utilizar Serverless Stack para sus proyectos del día a día. Automatizamos todos los pasos de la primera parte. Aquí está lo que se cubre en orden.
94+
Dirigido a personas que buscan utilizar SST para sus proyectos del día a día. Automatizamos todos los pasos de la primera parte. Aquí está lo que se cubre en orden.
9595

9696
Para el backend:
9797

_chapters/es/who-is-this-guide-for.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ Por lo tanto, podrías ser un desarrollador de backend que le gustaría aprender
1414

1515
También estamos, por ahora, enfocando esto únicamente a los desarrolladores de JavaScript. Podríamos apuntar a otros idiomas y entornos en el futuro. Pero creemos que este es un buen punto de partida porque puede ser realmente beneficioso para un desarrollador fullstack usar un solo lenguaje (JavaScript) y un entorno (Node.js) para crear toda la aplicación.
1616

17-
Como nota personal, el enfoque sin servidor ha sido una revelación gigante para nosotros y queríamos crear un recurso donde pudiéramos compartir lo que hemos aprendido. Puedes leer más sobre nosotros [**aquí**]({% link about/index.html %}). Y [echar un vistazo a una muestra de lo que la gente ha creado con Serverless Stack]({% link showcase.md %}).
17+
Como nota personal, el enfoque sin servidor ha sido una revelación gigante para nosotros y queríamos crear un recurso donde pudiéramos compartir lo que hemos aprendido. Puedes leer más sobre nosotros [**aquí**]({% link about/index.html %}). Y [echar un vistazo a una muestra de lo que la gente ha creado con SST]({% link showcase.md %}).
1818

1919
Comencemos mirando lo que estaremos cubriendo.

_chapters/fr/how-to-get-help.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Si vous rencontrez des problèmes avec une étape en particulier, nous voulons n
1212
- Nous utilisons [les sujets d'un forum de discussion Discourse]({{ site.forum_url }}) pour recevoir des commentaires et nous avons réussi à résoudre un certain nombre de problèmes dans le passé. Vérifiez donc les commentaires sous chaque chapitre pour voir si quelqu'un a déjà rencontré le même problème que vous (en anglais).
1313
- Postez votre problème dans les commentaires pour le chapitre spécifique et l'un d'entre nous vous répondra (en anglais).
1414

15-
![Serverless Stack Discourse Forums screenshot](/assets/serverless-stack-discourse-forums.png)
15+
![SST Discourse Forums screenshot](/assets/serverless-stack-discourse-forums.png)
1616

1717
Le guide complet est hébergé sur[GitHub]({{ site.github_repo }}). Si vous trouvez une erreur, vous pouvez toujours:
1818

0 commit comments

Comments
 (0)