Initial commit for .New Shortcuts extension

[chrismessina]

Description

This extension provides quick access to all the shortcuts publicly listed in the Whats.New registry, managed by Google.

Screenshots

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npx ray build -e dist and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

You can expect an initial review within five business days.

Once the PR is approved and merged, the extension will be available on our Store.

[koinzhang]

dot-new already available in the store

[chrismessina]

dot-new already available in the store

Oh no! You're totally right.

I'll need to make a PR for that extension. 🫣

[pernielsentikaer]

It would indeed be best to only have one of the same in the store, could some of your features enhance the other one from @natterstefan

[chrismessina]

It would indeed be best to only have one of the same in the store, could some of your features enhance the other one from @natterstefan

Ok — I'll work on that later this week. Moving this PR to a draft for now.

[natterstefan]

Hi 👋,

thanks for the mention and your work @chrismessina. I'm happy to review and implement new ideas and improvements to the existing extension.

[chrismessina]

Hi 👋,

thanks for the mention and your work @chrismessina. I'm happy to review and implement new ideas and improvements to the existing extension.

Super. A couple comments/clarifying questions:

• I was super impressed to discover how you populated your extension by scraping the table on whats.new. Like a n00b, I manually extracted the data and then built an Airtable so I could have more control over the data, including handling duplicate entries (i.e. handling shortcut synonyms like building.new, floorplan.new, and interiorspace.new). It appears that your extension doesn't handle these cases:

• I also added a few custom shortcuts that aren't strictly using the .new TLD (e.g. New Claude Project).
• I added categories to make it easier to filter the shortcuts and that seems easy enough to add to your extension, though the data model would need to change.
• Going forward, what do you think is the best strategy for 1) maintaining the list of shortcuts (e.g. using your scraping method) and 2) allowing managing shortcuts (favoriting, hiding, adding new additions)?
• How might we align the data model, since mine includes a Category attribute?

FYI, I previously created an Alfred Workflow called "Cloud New Documents" built around these TLD shortcuts, but my goal this time is to create an extension that parallels some of the functions of the Easy New File extension but for the cloud docs.

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[chrismessina]

Bumping; hoping to work on this this week!

[natterstefan]

Bumping; hoping to work on this this week!

Hi @chrismessina. I'm sorry I got caught up in work. I will get back to you within the next few days. Thanks for everything you've invested so far in preparing and coming up with ideas on how to proceed!

[natterstefan]

Hi @chrismessina,

thanks for your kind words. I am also impressed with how you added new features, including categories, aliases, and other services outside of .new's scope to the extension. That makes the extension even more useful.

I am still thinking about how to brainstorm and find a way to harmonize the two approaches and ideas into one together.

What about scheduling a call to share ideas, or do you want to exchange thoughts/plans here in the PR asynchronously?

Btw, sorry again for the delay.

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[natterstefan]

👋🏻👋🏻

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[raycastbot]

This issue has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.