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

Update contact for dbt speakers and dbt blog the community section of the docs #5065

Closed
1 task done
mirnawong1 opened this issue Mar 12, 2024 · 0 comments · Fixed by #5919
Closed
1 task done

Update contact for dbt speakers and dbt blog the community section of the docs #5065

mirnawong1 opened this issue Mar 12, 2024 · 0 comments · Fixed by #5919
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: low Improves docs but doesn’t block workflows, like grammar fixes & nice to haves

Comments

@mirnawong1
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

The speaking at a meetup page might need some tweaking as the following items seem out of date or would benefit from some reformatting:

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/community/resources/speaking-at-a-meetup#responding-to-a-conference-call-for-speakers
https://docs.getdbt.com/community/resources/speaking-at-a-meetup#pair-it-with-a-blog-post

Additional information

No response

@mirnawong1 mirnawong1 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: low Improves docs but doesn’t block workflows, like grammar fixes & nice to haves labels Mar 12, 2024
runleonarun added a commit that referenced this issue Aug 14, 2024
closes #5065

## What are you changing in this pull request and why?
<!---
Describe your changes and why you're making them. If related to an open 
issue or a pull request on dbt Core, then link to them here! 

To learn more about the writing conventions used in the dbt Labs docs,
see the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
-->

## Checklist
<!--
Uncomment when publishing docs for a prerelease version of dbt:
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/vercel.json`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages

---------

Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: low Improves docs but doesn’t block workflows, like grammar fixes & nice to haves
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant