Add jobs, community guidelines, and promotion docs

- Add jobs section with rules/templates, relevant jobs list, and suspicious job postings guide
- Move community guidelines from main site: code of conduct, discussions, asking for help, promotion
- Add promotion templates for events, content, social, and shameless promotion channels
- Update site title to "DataTalks.Club Documentation"
- Update Slack page nav order

Author: alexeygrigorev

_config.yml

@@ -16,7 +16,7 @@ theme: just-the-docs
 # you will see them accessed via {{ site.title }}, {{ site.github_repo }}, and so on.
 # You can create any custom variable you would like, and they will be accessible
 # in the templates via {{ site.myvariable }}.
-title: DataTalks.Club Zoomcamps Notes and Resources
+title: DataTalks.Club Documentation
 description: A collection of notes and resources for the DataTalks.Club Zoomcamps, our free courses.
 baseurl: "" # the subpath of your site, e.g. /blog
 url: "https://datatalks.club" # the base hostname & protocol for your site, e.g. http://example.com

assets/images/guidelines/example-events.png

@@ -0,0 +1,26 @@
+---
+title: "Community Guidelines"
+layout: default
+nav_order: 2
+parent: General
+has_children: true
+---
+
+# Community guidelines
+
+Thank you for joining our community! We hope you'll like it here.
+
+DataTalks.Club is a place to talk, learn, discuss, and share. To ensure our discussions remain organized, productive, and welcoming for everyone, we've established these community guidelines.
+
+- [Code of conduct]({{ '/general/guidelines/code-of-conduct/' | relative_url }}) - our expectations for respectful behavior
+- [Discussions]({{ '/general/guidelines/discussions/' | relative_url }}) - how to communicate effectively, use threads, and keep channels organized
+- [Asking for help]({{ '/general/guidelines/asking-for-help/' | relative_url }}) - how to ask questions, share errors, and get homework help
+- [Promotion]({{ '/general/guidelines/promotion/' | relative_url }}) - where and how to promote your work, events, and content
+
+## Channels
+
+Our Slack workspace is organized into channels to keep discussions focused and easy to find. Using the right channel helps ensure your message reaches the right people and keeps our workspace organized.
+
+When you post in the appropriate channel, you're more likely to get helpful responses from people who are interested in that topic. For example, instead of asking a machine learning question in [`#general`](https://app.slack.com/client/T01ATQK62F8/C01B6N9FZTN), post it in [`#datascience`](https://app.slack.com/client/T01ATQK62F8/C01BQDWEAHW) where ML enthusiasts actively participate.
+
+For a full list of channels, see the [Slack channels page]({{ '/general/slack/' | relative_url }}).

assets/images/guidelines/example-shameless-promotion.png

@@ -0,0 +1,43 @@
+---
+title: "Asking for Help"
+layout: default
+nav_order: 2
+parent: Community Guidelines
+grand_parent: General
+---
+
+# Asking for help
+
+If you get stuck, our Slack community is the right place to ask for help. Our members are generally happy to assist, but following these guidelines will make it much easier for others to help you effectively.
+
+## Avoid meta questions
+
+Meta questions are questions about asking questions (e.g., "Can I ask a question about X?"). They add an unnecessary step and delay getting the help you need.
+
+[Don't ask to ask, just ask](https://dontasktoask.com/). If you have a question, post it directly in the appropriate channel. The people who can help will see it and respond.
+
+Examples of meta questions to avoid:
+
+- "Can I ask a question about data science here?" - just ask your data science question directly. That's what this Slack exists for.
+- "Is there anyone who knows marketing? I have a question about it." - just ask your marketing question directly. If someone knows the answer, they'll respond.
+- "Has anyone done Machine Learning Zoomcamp? I have a question about it." - just ask your question about Machine Learning Zoomcamp. If someone has done it, they'll answer.
+
+## Code problems and errors
+
+When something doesn't work and you need help figuring it out, we'll be happy to help. To get the best assistance quickly, please follow these recommendations:
+
+- Use threads for errors. First describe the problem briefly in the main channel, then put the actual error message and code in a thread.
+- Copy-paste text, don't screenshot. Don't take screenshots of your code or terminal output. Instead, copy-paste the error message and code as text. Use code blocks (three backticks) to format your code. Text is searchable, easier to read, and allows helpers to copy your code if needed.
+- Never photograph your screen. Don't take pictures of your code with a phone. It's even harder to read than screenshots. Always copy-paste text. In rare cases when you need to show what happens on your screen visually (like a UI issue), a screenshot is acceptable, but code and errors should always be text.
+
+## Homework help
+
+We're generally happy to help with your homework, provided that you show genuine effort from your side and are transparent about the source of your question.
+
+- Show your work. Don't just copy-paste an exercise and expect others to solve it for you. Share what you've tried, what you understand, and where you're stuck.
+- Be transparent. Clearly state that it's a homework assignment. This helps people provide appropriate guidance (teaching concepts rather than just giving answers).
+- Ask for guidance, not answers. Frame your question to ask for help understanding concepts or debugging your approach, rather than asking for the complete solution.
+
+For more detailed guidance on asking homework questions effectively, consult [this guide from StackOverflow](https://meta.stackoverflow.com/questions/334822/how-do-i-ask-and-answer-homework-questions).
+
+The same principles apply to interview take-home assignments. We're happy to help, but be transparent and focus on understanding concepts rather than getting complete solutions.

general/guidelines.md

@@ -0,0 +1,22 @@
+---
+title: "Code of Conduct"
+layout: default
+nav_order: 0
+parent: Community Guidelines
+grand_parent: General
+---
+
+# Code of conduct
+
+Our community is built on mutual respect, kindness, and a shared passion for data science. Be respectful and remember that there's a human on the other side of the screen.
+
+While we don't have our own separate code of conduct, we follow the [Python Software Foundation's Code of Conduct](https://www.python.org/psf/conduct/). Please read the "Inappropriate Behavior" section to understand what we consider unacceptable.
+
+In addition to the behaviors outlined in the Python Software Foundation's code, here are specific examples of inappropriate behavior in our community:
+
+- Judging the question or the person asking the question ("this is a stupid question and everyone who can read docs knows the answer")
+- Soliciting any kind of personal information (such as marital status, sexual orientation, phone number, address, income, etc)
+- Asking for personal or professional details in DM (such as location, current job, or skills)
+- Asking people to share their profiles (such as LinkedIn or Upwork)
+- Offering collaboration in DM without prior public communication
+- Continuing one-on-one communication after requests to cease

general/guidelines/asking-for-help.md

@@ -0,0 +1,31 @@
+---
+title: "Discussions"
+layout: default
+nav_order: 1
+parent: Community Guidelines
+grand_parent: General
+---
+
+# Taking part in discussions
+
+Effective communication makes our community more valuable for everyone. Following these principles helps ensure your messages get the attention they deserve and contribute to building our shared knowledge base.
+
+Key principles:
+
+- Do not double post. Select the best channel for your message and post it only once. Posting the same message in multiple channels creates noise and fragments the discussion.
+- Avoid asking questions in DM. If you ask your question in a public channel, others will also benefit from the answers. Public discussions create a knowledge base that helps the entire community.
+- Use [threads](https://slack.com/help/articles/115000769927-Use-threads-to-organize-discussions-). Threads help keep discussions organized and make it easier to follow conversations, especially in active channels.
+
+## Thread best practices
+
+- Put everything in one message. Don't break your question into multiple messages. This makes it easier for others to understand the full context at once.
+- Use threads for long content. For long questions, write a few sentences in the first message to provide context, then put the rest in a thread. This keeps the main channel readable and scannable.
+- Put code in threads. If there's a code snippet (more than 5 lines of code), put it inside the thread. This prevents long code blocks from cluttering the main channel.
+- Use "also send to channel" sparingly. Avoid using this feature unless it's really necessary. Most thread replies don't need to appear in the main channel.
+- Separate multiple questions. If your question contains multiple distinct questions, break them into separate messages so each can be answered in its own thread.
+
+## Additional tips
+
+- Provide context when sharing links. Don't just share a link and expect others to jump in. Share your thoughts, explain why it's interesting or relevant, and include a clear question in your message. "Any thoughts on this?" is not a clear question - be specific about what you'd like to discuss.
+- Be concise. While it's important to provide context, try to be concise in your questions when possible. Not everyone has time to read lengthy messages. If you need to provide extensive background, use the thread approach mentioned above.
+- Don't delete answered questions. Your question and its answer will help others who might have a similar problem. This builds our community knowledge base.

general/guidelines/code-of-conduct.md

@@ -0,0 +1,164 @@
+---
+title: "Promotion"
+layout: default
+nav_order: 3
+parent: Community Guidelines
+grand_parent: General
+---
+
+# Promotion
+
+Promoting your work is welcome - for both companies and individuals. We believe that sharing valuable content, events, and tools benefits our entire community. However, to keep our workspace organized and ensure promotions add value rather than create noise, we have specific channels and guidelines for this.
+
+## Where to promote
+
+We have four dedicated channels for promotions:
+
+- [`#events`](https://app.slack.com/client/T01ATQK62F8/C01BDQVAS5P) - events that you organize or events that you find interesting
+- [`#interesting-content`](https://app.slack.com/client/T01ATQK62F8/C02N6N3S1FV) - content you published or content you find interesting
+- [`#shameless-social`](https://app.slack.com/client/T01ATQK62F8/C02MS2K0ACF) - for all social links: Twitter, LinkedIn, etc.
+- [`#shameless-promotion`](https://app.slack.com/client/T01ATQK62F8/C01F53D373M) - for everything else
+
+If you want to share a job, use [`#jobs`](https://app.slack.com/client/T01ATQK62F8/C01BFQBRB5Z). If you're looking for a job, use [`#job-search`](https://app.slack.com/client/T01ATQK62F8/C06A1QBFJ94). See [job posting rules]({{ '/general/jobs/' | relative_url }}).
+
+## Rules
+
+- Posts in the shameless channels should follow the template (see below)
+- Posting the same content in multiple channels is not allowed
+- Posting promotional content outside of these 4 channels is not allowed
+- Don't post more than two promotional posts per week
+- Don't include more than one link per post
+- Non-relevant topics aren't allowed
+- If what you promote isn't free, you should mention the price
+- Don't share files like docx documents or pdf, use these channels only for sharing links
+- Don't make the post too long (if it doesn't fit one phone screen, it's too long)
+- Remove the previews, if there's more than one
+- Don't make your `#welcome` message a pitch. Introduce yourself as a person, not your tool or agency
+- The content must be in English
+- Think of the reader: why is it relevant for them? Why should they actually click on your link?
+
+Messages that don't follow these rules will be deleted.
+
+## Templates
+
+We ask that your posts in the shameless channels follow a template.
+
+How to use it:
+
+- Replace the <placeholders> with your content
+- Try to keep the formatting (e.g. bold fonts)
+- Don't be sloppy and follow the punctuation rules:
+    - Use ":", not ";"
+    - There should be no space before ":" and a space after ":"
+- Don't use "everyone" for the "who is it for" part
+
+### For [`#events`](https://app.slack.com/client/T01ATQK62F8/C01BDQVAS5P):
+
+> <Title of the event>
+>
+> **Date:** &lt;date and time, don't forget the time zones&gt;<br>
+> **Who is it for:** &lt;data scientists, data engineers, ML engineers, managers, etc&gt;<br>
+> **Why is it relevant:** &lt;describe what's in there for the attendees&gt;<br>
+> **Price:** &lt;free or price&gt;
+>
+> &lt;Anything else you'd want to add&gt;
+>
+> **Registration link:** &lt;link&gt;
+
+Example:
+
+<img src="{{ '/assets/images/guidelines/example-events.png' | relative_url }}" alt="Example of a good events post" width="80%">
+
+### For [`#interesting-content`](https://app.slack.com/client/T01ATQK62F8/C02N6N3S1FV):
+
+> &lt;Title of the content&gt; (&lt;content type: video, blog, podcast, etc&gt;)
+>
+> **Who is it for:** &lt;data scientists, data engineers, ML engineers, managers, etc&gt;<br>
+> **Why is it relevant:** &lt;describe what's in there for the readers/listeners/etc&gt;
+>
+> &lt;Anything else you'd want to add&gt;
+>
+> &lt;link&gt;
+
+### For [`#shameless-social`](https://app.slack.com/client/T01ATQK62F8/C02MS2K0ACF):
+
+> &lt;What is it?&gt;
+>
+> **Who is it for:** &lt;data scientists, data engineers, ML engineers, managers, etc&gt;<br>
+> **Why is it relevant:** &lt;describe what's in there for the readers/listeners/etc&gt;
+>
+> &lt;Anything else you'd want to add&gt;
+>
+> &lt;link&gt;
+
+### For [`#shameless-promotion`](https://app.slack.com/client/T01ATQK62F8/C01F53D373M):
+
+> &lt;What is it?&gt;
+>
+> **Who is it for:** &lt;data scientists, data engineers, ML engineers, managers, etc&gt;<br>
+> **Why is it relevant:** &lt;describe what's in there for the readers/listeners/etc&gt;
+>
+> &lt;Anything else you'd want to add&gt;
+>
+> &lt;link&gt;
+
+Example:
+
+<img src="{{ '/assets/images/guidelines/example-shameless-promotion.png' | relative_url }}" alt="Example of a good shameless promotion post" width="80%">
+
+## Surveys, product discovery, and feedback requests
+
+Messages that ask the community for feedback on your product, service, or tool are considered promotional and should be posted in [`#shameless-promotion`](https://app.slack.com/client/T01ATQK62F8/C01F53D373M). This includes:
+
+- Surveys and research: any requests to fill out surveys or participate in research
+- Product feedback: requests for feedback on products, tools, or services
+- User interviews: requests to talk to community members about their needs or pain points
+- Beta testing: invitations to test new products or features
+
+Examples of promotional feedback requests:
+
+- "We're conducting a survey to better understand how people use ____."
+- "We'd like to show you our product and get some feedback from you."
+- "We're working on ____ and would like to talk to data scientists and ML engineers to understand their pain points."
+- "We're working on a tool to do ____ and we're wondering if it's useful."
+
+User research, product discovery, and feedback requests are all considered promotional content and must follow the same guidelines as other promotions.
+
+## Rules for vendors and company representatives
+
+If you represent a company and suggest using your services or products when answering questions in the community, you must clearly indicate your affiliation. Transparency is essential - community members deserve to know when recommendations come from someone with a commercial interest.
+
+For example, if someone asks about ML monitoring tools and you work for a company that provides such tools, you can recommend it, but you must clearly state your affiliation (e.g., "I work at [Company Name], and we offer [product] which might help...").
+
+## Unsolicited promotions in DMs
+
+We do not welcome unsolicited promotional messages in DMs. Violating this rule will result in a ban.
+
+Unsolicited DMs feel invasive and spammy. They violate people's privacy and create a negative experience. If someone wants to learn about your product or service, they'll reach out to you after seeing your post in the appropriate channel.
+
+What counts as unsolicited promotion:
+
+- Sending promotional messages about products or services via DM
+- Mass-sending your CV or resume in DMs
+- Promoting yourself and your services via DM
+- Offering collaboration in DMs without prior public communication
+
+If you want to collaborate with someone, first engage with them in public channels before reaching out via DM. This ensures the interaction is welcome and builds on an existing relationship.
+
+If you receive unsolicited promotional DMs, please report it to Alexey Grigorev. We take this seriously and will take action to protect the community.
+
+## Non-relevant promotions
+
+The promotional content must be relevant to our data science community. It should be related to data science, machine learning, data engineering, analytics, or closely related fields. If it's not relevant, don't post it.
+
+Examples of content not relevant for this community:
+
+- COVID surveys for $5 (unless specifically about data science/ML applications)
+- Coupon codes for lawn mowers, pizzas, or other unrelated products
+- Photoshop alternatives or general design tools
+- Databases with contact information (unless for data science purposes)
+- General sales tools unrelated to data
+- Wellness apps unrelated to data science
+- General business services with no data science connection
+
+Such messages will be removed without a warning. Repeated posting of irrelevant content may result in a ban.

general/guidelines/discussions.md

@@ -0,0 +1,15 @@
+---
+title: "Jobs"
+layout: default
+nav_order: 3
+parent: General
+has_children: true
+---
+
+# Jobs
+
+Guidelines for posting and finding jobs in our Slack community.
+
+- [Rules and templates]({{ '/general/jobs/rules/' | relative_url }}) - posting rules, channel guidelines, and message templates
+- [Relevant jobs]({{ '/general/jobs/relevant-jobs/' | relative_url }}) - what types of jobs are appropriate for our community
+- [Suspicious job postings]({{ '/general/jobs/suspicious-job-postings/' | relative_url }}) - how to spot scams and protect yourself

general/guidelines/promotion.md

@@ -0,0 +1,39 @@
+---
+title: "Relevant Jobs"
+layout: default
+nav_order: 1
+parent: Jobs
+grand_parent: General
+---
+
+# Relevant jobs
+
+The jobs you post must be specific and relevant to the community.
+
+Examples of relevant jobs:
+
+- Data/product analyst
+- Data scientist
+- Machine learning engineer
+- AI engineer
+- Data engineer
+- Analytics engineer
+- Developer advocate
+- Software engineer / Python developer
+
+Examples of non-relevant jobs:
+
+- Full-stack developers
+- Blockchain developers
+- Joomla/wordpress developers
+- Php developers
+- Accountants
+- Bookkeepers
+- Designers
+- Assistants
+
+Examples of non-specific jobs:
+
+- "We're looking for students"
+
+Non-relevant and/or non-specific job postings will be deleted.