|
| 1 | +--- |
| 2 | +title: Version 10.7.0 release notes |
| 3 | +description: Discover the new features in Version 10.7.0, including GitHub Copilot prompts, media actions, and enhanced SEO panel improvements. |
| 4 | +date: 2024-12-31T14:22:26.767Z |
| 5 | +lastmod: 2024-12-31T14:22:39.496Z |
| 6 | +slug: v10.7.0 |
| 7 | +fmContentType: changelog |
| 8 | +--- |
| 9 | + |
| 10 | +## Ability to prompt GitHub Copilot from a custom script/action |
| 11 | + |
| 12 | +You are now able to prompt GitHub Copilot straight from your custom script/action. This functionality allows you to use the power of AI to generate titles, descriptions, or any other content you need. |
| 13 | + |
| 14 | +Here is an example of how you can prompt GitHub Copilot to generate a social message for sharing an article on Bluesky: |
| 15 | + |
| 16 | +```javascript {{ "title": "Prompting GitHub Copilot", "description": "./scripts/share.mjs" }} |
| 17 | +import { ContentScript } from "@frontmatter/extensibility"; |
| 18 | + |
| 19 | +(() => { |
| 20 | + const contentScriptArgs = ContentScript.getArguments(); |
| 21 | + if (contentScriptArgs) { |
| 22 | + const { |
| 23 | + frontMatter: { title, description, slug }, |
| 24 | + promptResponse |
| 25 | + } = contentScriptArgs; |
| 26 | + |
| 27 | + if (!promptResponse) { |
| 28 | + ContentScript.promptCopilot(`Create me a social message for sharing this article on Bluesky. |
| 29 | + To generate the post, please use the following information: |
| 30 | +
|
| 31 | + Title: """${title}""" |
| 32 | + Description: """${description}""" |
| 33 | +
|
| 34 | + The output should be plain text and should not include any markdown or HTML tags. |
| 35 | + You are free to add hashtags. |
| 36 | +
|
| 37 | + IMPORTANT: Please make sure to keep the post under 265 characters.`); |
| 38 | + return; |
| 39 | + } |
| 40 | + |
| 41 | + const shareUrl = `https://bsky.app/intent/compose?text=${encodeURIComponent(promptResponse)}%20${encodeURIComponent(url)}`; |
| 42 | + ContentScript.open(shareUrl); |
| 43 | +})(); |
| 44 | +``` |
| 45 | + |
| 46 | +Here is an example of how you can configure the script in your `frontmatter.json`: |
| 47 | + |
| 48 | +```json {{ "title": "The script configuration", "description": "frontmatter.json" }} |
| 49 | +{ |
| 50 | + "frontMatter.custom.scripts": [{ |
| 51 | + "title": "Share blog post", |
| 52 | + "script": "./scripts/share.mjs", |
| 53 | + "type": "content" |
| 54 | + }] |
| 55 | +} |
| 56 | +``` |
| 57 | + |
| 58 | +> **Info**: You can find more information about in the [prompting GitHub Copilot](/docs/custom-actions/advanced#prompting-github-copilot) documentation section. |
| 59 | +
|
| 60 | +## Added media folder common actions |
| 61 | + |
| 62 | +You can now perform common actions on media folders. These actions include: |
| 63 | + |
| 64 | +- **Edit**: Change the folder name |
| 65 | +- **Delete**: Remove the folder |
| 66 | + |
| 67 | + |
| 68 | + |
| 69 | +## UX improvements for the SEO panel view |
| 70 | + |
| 71 | +With the help of [Tooster](https://github.com/T3sT3ro), the Front Matter side panel view has been improved. The SEO section has been completely redesigned and now provides a better overview of the SEO status of your content. |
| 72 | + |
| 73 | + |
| 74 | + |
| 75 | +## Ability to define custom "group by" options |
| 76 | + |
| 77 | +Like defining your own filter and sorting options, you can now also define your own "group by" options. This functionality allows you to group your content by custom fields. |
| 78 | + |
| 79 | +Here is an example of how you can define custom "group by" options: |
| 80 | + |
| 81 | +```json {{ "title": "Example of adding custom grouping options" }} |
| 82 | +{ |
| 83 | + "frontMatter.content.grouping": [ |
| 84 | + { |
| 85 | + "title": "Content Type", |
| 86 | + "name": "fmContentType" |
| 87 | + } |
| 88 | + ] |
| 89 | +} |
| 90 | +``` |
| 91 | + |
| 92 | +> **Info**: You can find more information about in the [grouping](/docs/dashboard/content-view#grouping) documentation section. |
| 93 | +
|
| 94 | +## New setting to define the default timezone for date formatting |
| 95 | + |
| 96 | +A new setting has been added to define the default timezone for date formatting. By default, it is set to `UTC`. |
| 97 | + |
| 98 | +```json {{ "title": "Setting the default timezone", "description": "frontmatter.json" }} |
| 99 | +{ |
| 100 | + "frontMatter.global.timezone": "UTC" |
| 101 | +} |
| 102 | +``` |
| 103 | + |
| 104 | +## Related issues/enhancements |
| 105 | + |
| 106 | +### 🎨 Enhancements |
| 107 | + |
| 108 | +- [#405](https://github.com/estruyf/vscode-front-matter/issues/405): Added new `frontMatter.content.grouping` setting which allows you to define custom "group by" options |
| 109 | +- [#705](https://github.com/estruyf/vscode-front-matter/issues/705): UX improvements for the panel view |
| 110 | +- [#887](https://github.com/estruyf/vscode-front-matter/issues/887): Added new `frontMatter.global.timezone` setting, by default it is set to `UTC` for date formatting |
| 111 | +- [#888](https://github.com/estruyf/vscode-front-matter/issues/888): Added the ability to prompt GitHub Copilot from a custom script/action |
| 112 | +- [#892](https://github.com/estruyf/vscode-front-matter/issues/892): Added media folder common actions |
| 113 | + |
| 114 | +### 🐞 Fixes |
| 115 | + |
| 116 | +- [#895](https://github.com/estruyf/vscode-front-matter/issues/895): Fix issue with array values in filters |
0 commit comments