-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out a better subtitle #50
Comments
Instead of "Maintenance - From Apprentice to Master"? Maybe "Maintenance - Optimising Front-End Workflow". |
That's a good try! It's not only about front-end, though. Maybe we can move from that a bit. "Maintenance - Optimize Your JavaScript Workflow" (american spelling 🥇 ). We also thought about variants like "Tame your JavaScript projects" and “How to keep your sanity maintaining open source library”. |
I like that :) Or "Maintenance - Optimizing JavaScript Workflow"... |
“Streamlining JavaScript Workflow”. Optimizing may feel like we’re going to teach performance. A good example from another area. |
Yeah, streamlining sounds much better. |
I like "streamlining" (and of course all of this is up to you guys) - the word just sounds to me a bit like the user already knows all this stuff but you're just going to organise what they know a bit better. With "optimising" it's like they might be doing everything manually but you're going to show them all the things that can automate it! These are very subtle things though, and that's a sound point that "optimising" has a specific meaning in computing (namely speed/performance) - so streamlining sounds good! |
Ideas from a friend. |
The current one feels too vague and doesn’t reflect the content accurately. I think we might need something more concrete here.
The text was updated successfully, but these errors were encountered: