Skip to content
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

Mini rebrand myst-tools.org --> mystmd.org #21

Closed
15 tasks done
rowanc1 opened this issue Jun 15, 2023 · 8 comments
Closed
15 tasks done

Mini rebrand myst-tools.org --> mystmd.org #21

rowanc1 opened this issue Jun 15, 2023 · 8 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@rowanc1
Copy link
Member

rowanc1 commented Jun 15, 2023

This is following up on conversations from the last month around branding of myst-tools.org that @choldgraf started at JupyterCon. @choldgraf proposed to move the website and social media to mystmd.org, this issue is tracking progress following through on that choice!

The thinking on this is that it (1) is easier to say/spell/talk about the URL (myst-dash-tools-dot-org vs myst-M-D-dot-org); (2) is not tied to a programming language (e.g. mystjs). The one challenge is that it might be "just" markdown, @choldgraf gave an example of Obsidian (note-taking tool) using this branding pattern and it being successful for them.

Some of the outstanding tasks:

I will continue adding a few PRs around the place to point to the new domain.

@rowanc1 rowanc1 added the documentation Improvements or additions to documentation label Jun 15, 2023
@rowanc1 rowanc1 self-assigned this Jun 15, 2023
@welcome
Copy link

welcome bot commented Jun 15, 2023

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉

rowanc1 added a commit to jupyter-book/myst-enhancement-proposals that referenced this issue Jun 15, 2023
rowanc1 added a commit to executablebooks/meta that referenced this issue Jun 15, 2023
rowanc1 added a commit to executablebooks/.github that referenced this issue Jun 15, 2023
choldgraf pushed a commit to jupyter-book/myst-enhancement-proposals that referenced this issue Jun 16, 2023
choldgraf added a commit to executablebooks/.github that referenced this issue Jun 16, 2023
* 👋 Welcome page

* Update to mystmd.org

See executablebooks/team-compass#21

* Update profile/README.md

Co-authored-by: Chris Holdgraf <[email protected]>

---------

Co-authored-by: Chris Holdgraf <[email protected]>
@choldgraf
Copy link
Member

I've merged the PRs opened above!

@rowanc1
Copy link
Member Author

rowanc1 commented Jun 16, 2023

Thanks @choldgraf! Do you have access to myst-spec on read the docs? It looks pretty out-dated, and confused someone I talked to a few days ago.

@choldgraf
Copy link
Member

Nope I just checked and apparently only @chrisjsewell has access to it. Chris can you provide admin access to others on the team so that we can make the necessary domain changes?

@chrisjsewell
Copy link
Member

Heya, invited you as maintainer

@choldgraf
Copy link
Member

Nice, thanks - I added @rowanc1 as well

@rowanc1
Copy link
Member Author

rowanc1 commented Jun 16, 2023

🚀 that is now forwarding, thanks!

@rowanc1
Copy link
Member Author

rowanc1 commented Jun 29, 2023

Finally moved Mastodon over today! Closing this! :)

@rowanc1 rowanc1 closed this as completed Jun 29, 2023
rowanc1 added a commit to jupyter-book/mystmd that referenced this issue Jun 30, 2023
This is a follow on task from executablebooks/team-compass#21.

This will eventually allow a consistent install experience across pip and npm.

See #139
rowanc1 added a commit to jupyter-book/mystmd that referenced this issue Jul 3, 2023
This is a follow on task from executablebooks/team-compass#21.

This will eventually allow a consistent install experience across pip and npm.

See #139
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants