I’m a bit lost with the guide. When we come to the...
# sst
d
I’m a bit lost with the guide. When we come to the Best Practices section, it starts speaking about template.yml and uses the
serverless
command. Are the best practices for the Serverless Framework or for SST? This is specially confusing as the Best Practices chapter comes before Serverless Framework chapter
d
Yeah that’s a bit tricky for sure. The focus on CDK seems to make the current best practices a little clumsy for now. IIRCX there’s some conversation about getting new content in there but it’s a process just like everything. Do you think that reordering those 3 sections to be
Copy code
Extra Credit
Serverless Framework
Best Practices
Would clarify that? Or would you prefer to just wait for new content?
f
cc @Jay
j
Yeah we haven’t updated that section yet. I think we should make it clear.
d
I would definitively have
The Basics
, then
Extra Credits
then
Serverless
then
Best Practices (for serverless)
But mainly I would add a disclaimer at the beginning of each section that is for serverless saying
This section was originally written when SST was an "addon" for the serverless framework. You can skip it if you are doing the SST guide.
I can’t speak for the others but for myself, looking at SST today, I wouldn’t even consider using Serverless Framework at all. They don’t even do the same thing anymore. It actually felt weird that the guide keeps mentioning it or showing a “competitor’s” perspective. This feels like legacy-syndrom. The extras have some nice parts but some are still serverless related for example: • API Gateway and Lambda LogsDebugging serverless API Issues • etc…
g
Maybe create a different page.. and link in the main sst guide..
Looking for the serverless framework guide: click here
j
Yeah thanks for ideas guys. We haven’t had a chance to reorganize the older sections yet.
We’ll work on it in the coming weeks.