Updates for order and more 'why' as well as 'what' #619
Conversation
| * **Extensions**: Create workspace recommended Extension lists. Extension packs to automatically include dependencies. | ||
| * **Debugging**: Support for running NPM and other script runners on launch. | ||
| * **Extension Authoring**: New APIs to update settings and modify files before save. Debug protocol updates including programmatic access to `launch.json`. | ||
|  |
There was a problem hiding this comment.
With the image the lists seamed redundant - but I do miss explainign ghte 'why' it's cool and the image does not allow for that.
There was a problem hiding this comment.
Aslo we can update the image again think of this as a placeholder v1.
There was a problem hiding this comment.
I'm not keen on the image only introduction. It isn't accessible, as you say doesn't tell a story and I find the purple with yellow text jarring. I think the banner is great for a tweet where you don't have much real estate but I don't know how much people can get out of short four or five word descriptions.
There was a problem hiding this comment.
We can certainly try it for this release.
There was a problem hiding this comment.
Did you include the image in the commit?
There was a problem hiding this comment.
I think it is accessible - I filled the Alt text completely. I direct committed the image. Do we need the image or can it be hidden for the social stuff [sorry should know]. Then I can have my cake (tweets) and eat it too. I would in the bulled list like to focus more on value/why to drive excitement not just what I can help there. I'd also like to see what it looks like in product we could o that Monday?
There was a problem hiding this comment.
Yes, the image doesn't need to be displayed to be available for tweets.
Just needs to be included in the header as
MetaSocialImage: 1_6_ReleaseHighlights_1.6.jpg
We can rename it to simply social.jpg like the others.
It's easy to configure code-insiders to display the release notes. We can do it Monday or you can follow the test plan instructions. microsoft/vscode#12520
| ### Release notes inside VS Code | ||
|
|
||
| There is no need to go to our website to review the latest release notes - you can now see these inline within VS Code itself. Use the global **Show Release Notes** command or the **Help** > **Release Notes** menu to access them. With any luck this is how you are reading these notes right now :) | ||
|
|
There was a problem hiding this comment.
This si an example of where I wanted to change the order a little for emphasis and also lighten the tone + say why it helps vs just what we did.
There was a problem hiding this comment.
I don't think we need to lead with this since it is discoverable. As you mention most people will be reading from within VS Code.
There was a problem hiding this comment.
I just don't want to lead w/ Icons and this is the most visible change release over release hece I do think we should put right up here to explain why we did it.
|
|
||
|  |
There was a problem hiding this comment.
This image seams a little big - should be shrunk and loose shadow?
There was a problem hiding this comment.
Agree. I tried to crop the bottom but was having trouble on Windows with Paint. The outer transparency was turning to a white background. Can you crop it easily on your Mac.
There was a problem hiding this comment.
I'll ask Brad to crop the image next week.
|
|
||
| We have found ourselves spending many hours investigating VS Code issues that were ultimately caused by corrupt VS Code installations. Some extensions directly modify (patch) the VS Code product in such a way that is semi-permanent (until the next update) and this can cause hard to reproduce issues. | ||
| ### Improving command discoverability |
There was a problem hiding this comment.
Part of me felt we could skip this section but I think it's OK - it's just that for some people they won't see it. I therefore attempted to refactor to explain why were were doing it - our goals
|
|
||
| * You can now quickly enable auto save by selecting **Auto Save** from the **File** menu. This will write the auto save setting to your global configuration file. | ||
| Auto save is a great feature for amny scenarios. In an effort to make this more discoverable you can now quickly enable auto save [in a persistant way] by selecting **Auto Save** from the **File** menu. This will write the auto save setting to your global [User] configuration file. |
There was a problem hiding this comment.
We should ensure this is in User settings - I think it is.
| @@ -186,6 +203,7 @@ We will work on bringing these features back during the next iteration. | |||
|
|
|||
| However, we are not done yet.. Now that we have extracted languages into extensions, the next challenge is to support the nesting of these languages, that is, embed JavaScript or CSS inside HTML. We will be working on this in October. | |||
|
|
|||
|
|
|||
| ## Extensions | |||
|
|
|||
| ### Workspace Recommended Extensions | |||
There was a problem hiding this comment.
Really should add in the why here - we added this so that as athe maintainer of a project you can suggest the best extensions to use with it....
No description provided.