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

[DOC]: Update README with instructions for creating Consulting blogs #702

Open
bskinn opened this issue Mar 27, 2023 · 1 comment
Open
Assignees
Labels
area: documentation 📖 Improvements or additions to documentation consulting 🤝 Items on the Quansight Consulting site owner: Quansight For Quansight work, regardless of timing/priority type: maintenance 🛠

Comments

@bskinn
Copy link
Contributor

bskinn commented Mar 27, 2023

The current Labs instructions for blog post workflow are close in many details to the procedures/locations/etc. for the new GitHub-based Consulting blog workflow, but they are not identical.

This documentation in the README needs to be updated to accurately reflect the Consulting flow as well as the Labs flow.

@bskinn bskinn added area: documentation 📖 Improvements or additions to documentation consulting 🤝 Items on the Quansight Consulting site owner: Quansight For Quansight work, regardless of timing/priority type: maintenance 🛠 labels Mar 27, 2023
@bskinn bskinn self-assigned this Mar 27, 2023
@bskinn
Copy link
Contributor Author

bskinn commented Nov 13, 2023

Now that (a) Consulting site has moved to Wordpress and (b) we've started the Medium, the instructions needed for Consulting blogs are quite different.

Whether we house those full instructions here or not, this needs to be updated to reflect the new state of the stack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation 📖 Improvements or additions to documentation consulting 🤝 Items on the Quansight Consulting site owner: Quansight For Quansight work, regardless of timing/priority type: maintenance 🛠
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant