<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on BWRGY</title><link>https://handbook-bwrgy-org-971173.gitlab.io/</link><description>Recent content in Home on BWRGY</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://handbook-bwrgy-org-971173.gitlab.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Developer Onboarding</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/onboarding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/onboarding/</guid><description>&lt;h2 id="getting-started"&gt;Getting Started&lt;/h2&gt;
&lt;p&gt;Welcome to the development team! This guide will help you get up to speed with our codebase, workflows, and team culture. Make sure you&amp;rsquo;ve checked out our &lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/getting-started/onboarding/"&gt;General Onboarding&lt;/a&gt; beforehand. Follow the steps below to ensure a smooth onboarding experience.&lt;/p&gt;
&lt;h3 id="prerequisites"&gt;Prerequisites&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;Complete these prerequisites before Call 1.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id="1-gitlab-access-setup"&gt;1. GitLab Access Setup&lt;/h4&gt;
&lt;p&gt;We use &lt;strong&gt;GitLab&lt;/strong&gt; as our primary development and project management platform.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;See &lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/gitlab/"&gt;GitLab Guide&lt;/a&gt; for application overview and setup instructions.&lt;/p&gt;</description></item><item><title>Environment Setup</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/setup/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;This guide will help you get our documentation (Hugo) website running locally for development and contribution.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Prerequisites:&lt;/strong&gt; Before beginning, ensure you&amp;rsquo;ve completed the &lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/gitlab/"&gt;GitLab setup&lt;/a&gt; in our handbook, including SSH key configuration and repository access.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="step-1-install-required-tools"&gt;Step 1: Install Required Tools&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;macOS:&lt;/strong&gt;&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;brew install hugo git go
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;export GOPATH&lt;span style="color:#f92672"&gt;=&lt;/span&gt;$HOME/go
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;export PATH&lt;span style="color:#f92672"&gt;=&lt;/span&gt;$PATH:$GOPATH/bin
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;source ~/.zshrc &lt;span style="color:#75715e"&gt;# or source ~/.bashrc&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Windows:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Download Hugo from &lt;a href="https://github.com/gohugoio/hugo/releases"&gt;releases page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Download Git from &lt;a href="https://git-scm.com"&gt;git-scm.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Download Go from &lt;a href="https://go.dev/dl/"&gt;golang.org/dl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Add all tools to your PATH environment variable&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Linux:&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Brand Identity</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/brand/brand-identity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/brand/brand-identity/</guid><description>&lt;ul&gt;
&lt;li&gt;Mission, vision, and values&lt;/li&gt;
&lt;li&gt;Brand personality and positioning&lt;/li&gt;
&lt;li&gt;Target audience definition&lt;/li&gt;
&lt;li&gt;Brand promise and key messaging&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Content Style Guide</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/content/content-style-guide/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/content/content-style-guide/</guid><description>&lt;ul&gt;
&lt;li&gt;Organization&amp;rsquo;s writing voice and tone&lt;/li&gt;
&lt;li&gt;Grammar, punctuation, and formatting standards&lt;/li&gt;
&lt;li&gt;Terminology and word choices&lt;/li&gt;
&lt;li&gt;Basic writing rules everyone must follow&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Content Writer</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/content-writer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/content-writer/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Content Strategy and Brand Voice&lt;/strong&gt;: Develop and maintain consistent messaging and tone across multiple platforms and channels, ensuring cohesive brand communication and engagement. Create content frameworks, style guides, and editorial calendars that align with organizational goals and audience needs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Writing and Editorial&lt;/strong&gt;: Produce clear, compelling, and accessible content including website copy, blog articles, documentation, and marketing materials. Collaborate with cross-functional teams to ensure content accuracy, brand alignment, and optimal user experience across all touchpoints.&lt;/p&gt;</description></item><item><title>Contributing</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/contributing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/contributing/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;h4 id="please-do"&gt;Please Do&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Check if there is an existing issue before submitting a new one&lt;/li&gt;
&lt;li&gt;Open an issue if:
&lt;ul&gt;
&lt;li&gt;Something isn’t working as expected&lt;/li&gt;
&lt;li&gt;You’re proposing a significant change&lt;/li&gt;
&lt;li&gt;You’re suggesting a new feature&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Open a merge request (MR) to:
&lt;ul&gt;
&lt;li&gt;Implement a change discussed in an issue (link the related issue)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;In general, open an issue before submitting a merge request. It improves visibility, avoids duplicate work, and allows early feedback.&lt;/p&gt;</description></item><item><title>Design Principles</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/ux/design-principles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/ux/design-principles/</guid><description>&lt;ul&gt;
&lt;li&gt;Accessibility-first design principles&lt;/li&gt;
&lt;li&gt;User personas and target audience definitions&lt;/li&gt;
&lt;li&gt;User research methods (interviews, testing, surveys)&lt;/li&gt;
&lt;li&gt;Usability guidelines and standards&lt;/li&gt;
&lt;li&gt;Design decision-making framework&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Designer</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/product/designer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/product/designer/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Visual Design and Branding&lt;/strong&gt;: Develop and maintain consistent visual identities across multiple subdomains (websites), ensuring cohesive branding and aesthetic appeal. Create wireframes, mockups, and prototypes that align with user experience (UX) best practices and project requirements.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User Interface (UI) Design&lt;/strong&gt;: Design intuitive, responsive, and accessible user interfaces that enhance usability across various devices. Collaborate with developers to implement designs and ensure they are accurately translated into functional web pages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Graphic Design and Content Creation&lt;/strong&gt;: Produce high-quality graphics, illustrations, and other visual content to support marketing campaigns, social media, and website content. Ensure all designs adhere to accessibility standards and reflect the brand&amp;rsquo;s voice.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Technical Skills&lt;/strong&gt;: Proficiency in design tools such as Adobe Photoshop, Illustrator, or Figma. Experience with responsive and adaptive design principles, and knowledge of colour theory, typography, and layout design. Basic understanding of HTML/CSS for better communication with developers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Soft Skills&lt;/strong&gt;: Creative problem-solving ability, strong attention to detail, and the ability to handle multiple tasks simultaneously. Excellent communication and collaboration skills to work effectively with cross-functional teams, and an openness to feedback and iterative design processes.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Digital Marketing</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/marketing/digital-marketing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/marketing/digital-marketing/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Digital Campaign Management&lt;/strong&gt;: Develop and execute comprehensive digital marketing campaigns across multiple platforms to increase brand awareness and drive engagement with Tibetan cultural content.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Social Media Strategy and Analytics&lt;/strong&gt;: Manage social media presence, create engaging content calendars, and analyze performance metrics to optimize reach and audience engagement across platforms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SEO and Content Optimization&lt;/strong&gt;: Implement SEO strategies to improve website visibility, optimize content for search engines, and drive organic traffic to support platform growth objectives.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Digital Marketing Expertise&lt;/strong&gt;: Proven experience with digital marketing tools and platforms including social media management, Google Analytics, SEO tools, and email marketing systems. Knowledge of content marketing and paid advertising preferred.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Strategic Skills&lt;/strong&gt;: Strong analytical abilities for campaign performance assessment, creative thinking for content strategy development, and excellent communication skills for cross-team collaboration and audience engagement.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Element</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/element/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/element/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Element is an app used for chat and collaboration, built on the Matrix protocol. Think of it like Gmail, but for messaging—secure, private, and decentralised. It&amp;rsquo;s a secure alternative to platforms like Slack.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="key-features"&gt;Key Features&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Secure &amp;amp; Private:&lt;/strong&gt; End-to-end encryption (E2EE) for all messages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decentralized:&lt;/strong&gt; No single company controls your account.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Flexible:&lt;/strong&gt; Works with multiple apps and can bridge to WhatsApp, Telegram, Discord.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="element-structure"&gt;Element Structure&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;🏢 &lt;strong&gt;Spaces:&lt;/strong&gt; Groups of related rooms (e.g., team, topic, project). Can be nested.&lt;/li&gt;
&lt;li&gt;💬 &lt;strong&gt;Rooms:&lt;/strong&gt; Where conversations happen. Public or private. Private rooms are encrypted.&lt;/li&gt;
&lt;li&gt;🔑 &lt;strong&gt;Roles:&lt;/strong&gt; Admin (manage settings), Moderator (manage content), Member (participate).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="user-setup-steps"&gt;User Setup Steps&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Step 1:&lt;/strong&gt; Create your account: &lt;a href="https://app.element.io"&gt;https://app.element.io&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Google Page Rank Analysis</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/problem/page-rank-analysis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/problem/page-rank-analysis/</guid><description>&lt;h2 id="page-1-rankings"&gt;Page 1 Rankings&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Keyword&lt;/th&gt;
 &lt;th&gt;General (News, Edu, etc.)&lt;/th&gt;
 &lt;th&gt;Operated by Non-Tibetans&lt;/th&gt;
 &lt;th&gt;Operated by Tibetans&lt;/th&gt;
 &lt;th&gt;Operated in China&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;6&lt;/strong&gt; (Wikipedia, Britannica, BBC, Aljazeera)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;3&lt;/strong&gt; (ICT, Free Tibet, ITN)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (CTA)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;is tibet a country?&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;9&lt;/strong&gt; (Wikipedia, BBC, Britannica, ToI, Cultural Survival, IAUNRC, Freedom House)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (Free Tibet)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan art&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;7&lt;/strong&gt; (Wikipedia, Met Museum, Pinterest, Brown, Britannica, New World Encyclopedia)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Norbulingka (e-com))&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan buddhism&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;9&lt;/strong&gt; (Wikipedia, Britannica, Khan Academy, BBC, Brown, Tricycle, Delhi University, Isha)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (Sakya)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan culture&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;7&lt;/strong&gt; (Wikipedia, NY Times, Britannica, Study, Cultural Survival, JSTOR)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (Free Tibet)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Tibet Travel, Wonders of Tibet)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet history&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;5&lt;/strong&gt; (Wikipedia, Study, Britannica, BBC)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;4&lt;/strong&gt; (ICT, Tibet House (US), Free Tibet)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (CTA)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;prayer flags&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;8&lt;/strong&gt; (Wikipedia, Amazon, Folk Bazar (e-com), Mountain Kingdoms, G Adventures, Study, Dharma Shop, India Times)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Tibetan Nuns Project)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan festival&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;3&lt;/strong&gt; (Trekking Plus, Wikipedia, Third Rock Adventures)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;7&lt;/strong&gt; (Tibet Travel, Tibet Tour, Tibetan Guide, Great Tibet Tour, Wonders of Tibet)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;losar festival&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;10&lt;/strong&gt; (Wikipedia, Shiyomi, Outlook traveller, Fab Hotels, ToI, CNBC, Bank Bazar, Tour My India, Utsav)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;is tibet part of china?&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;8&lt;/strong&gt; (Wikipedia, ToI, BBC, CECC, Cultural Survival, Study)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Free Tibet)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet map&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;6&lt;/strong&gt; (Wikipedia, Britannica, Google, BBC, Library of Congress)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Free Tibet, ITN)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (CTA, SFT)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan language&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;9&lt;/strong&gt; (Wikipedia, Britannica, Australian National University, Max Planck Uni, Kansas Uni, Chicago Uni, E Alliance)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;1&lt;/strong&gt; (Tibet Travel)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan uprising day&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;4&lt;/strong&gt; (Wikipedia, Indian Express, National Today)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (Free Tibet, ICT)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;4&lt;/strong&gt; (SFT, Universal Compassion Foundation, CTA)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet news&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;4&lt;/strong&gt; (Wikipedia, Indian Express, National Today)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;2&lt;/strong&gt; (ICT, Free Tibet)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;3&lt;/strong&gt; (CTA, VoT, Phayul)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet china&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;7&lt;/strong&gt; (Wikipedia, Britannica, BBC, HRW, UCA, Drishtiias)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;3&lt;/strong&gt; (Free Tibet, ICT)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Metric&lt;/th&gt;
 &lt;th&gt;General (News, Edu, etc.)&lt;/th&gt;
 &lt;th&gt;Operated by Non-Tibetans&lt;/th&gt;
 &lt;th&gt;Operated by Tibetans&lt;/th&gt;
 &lt;th&gt;Operated in China&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;SEO Authority&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;69%&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;13%&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;11%&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;7%&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Total Rankings&lt;/td&gt;
 &lt;td&gt;104/150&lt;/td&gt;
 &lt;td&gt;19/150&lt;/td&gt;
 &lt;td&gt;16/150&lt;/td&gt;
 &lt;td&gt;11/150&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Most Ranking Site&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Wikipedia (13/15)&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Free Tibet (9/15)&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;CTA (5/15)&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Tibet Travel (4/15)&lt;/strong&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt; &lt;/p&gt;</description></item><item><title>HR Coordinator</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/people/hr-coordinator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/people/hr-coordinator/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Requirement and Selection&lt;/strong&gt;: Finding the right talent, and people with strong character who fit the team culture. We want to create a team culture where accountability is a shared value, supporting everyone to grow together.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Setting the Right Team Culture&lt;/strong&gt;: Passion, accountability, initiative — building a team where these values show up every day.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Communication&lt;/strong&gt;: Both informal and formal — clear, articulate, and honest. Making sure everyone’s understood and on the same page. Supporting the team through conflicts when they arise.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Encouraging&lt;/strong&gt;: Motivating applicants and the team with energy and clarity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proactive&lt;/strong&gt;: Taking ownership and accountability for the recruitment process.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Open-minded&lt;/strong&gt;: Not letting personal beliefs influence decisions — we want everyone from the community, regardless of their stance, to be able to contribute.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Initial Setup</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/setup/</guid><description>&lt;h2 id="install-git"&gt;Install Git&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Linux&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;# For CentOS/RHEL&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;sudo yum install git
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;or&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;# For Debian/Ubuntu&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;sudo apt install git
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;macOS (Homebrew)&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;brew install git
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Windows&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Download Git from the official website:&lt;br&gt;
&lt;code&gt;https://git-scm.com/downloads&lt;/code&gt; or click here: &lt;a href="https://git-scm.com/downloads"&gt;Git&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Verify Installation&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git --version
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="vs-code-setup-for-gitlab"&gt;VS Code Setup for Gitlab&lt;/h2&gt;
&lt;p&gt;Git integration is built into VS Code.&lt;/p&gt;
&lt;h3 id="install-gitlab-extension"&gt;Install GitLab Extension&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;strong&gt;Extensions&lt;/strong&gt; (&lt;code&gt;Ctrl+Shift+X&lt;/code&gt; / &lt;code&gt;Cmd+Shift+X&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Search for &lt;strong&gt;GitLab Workflow&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Install&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="set-git-user"&gt;Set Git User&lt;/h3&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git init
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git config --global user.name &lt;span style="color:#e6db74"&gt;&amp;#34;Your Name&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git config --global user.email &lt;span style="color:#e6db74"&gt;&amp;#34;your_email@example.com&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="ssh-authentication-setup"&gt;SSH Authentication Setup&lt;/h2&gt;
&lt;h3 id="1-generate-ssh-key"&gt;1. Generate SSH Key&lt;/h3&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ssh-keygen -t ed25519 -C &lt;span style="color:#e6db74"&gt;&amp;#34;your_email@example.com&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Replace with your GitLab email address.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="2-save-ssh_key"&gt;2. Save SSH_KEY&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;When prompted to &amp;ldquo;Enter a file in which to save the key,&amp;rdquo; press Enter. This will save the key to the default location or specify a custom one.&lt;/p&gt;</description></item><item><title>Legal Operations</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/legal/legal-operations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/legal/legal-operations/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Organisational Setup and Legal Compliance&lt;/strong&gt;: Handle compliance of non-profit (NPO) and for-profit (FP) entities, ensuring legal structure and regulations are followed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Legal Strategy&lt;/strong&gt;: Provide legal advice on contracts, grant applications, and organisational structure for both for-profit and non-profit entities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Financial Management and Reporting&lt;/strong&gt;: Oversee financial operations, including managing bank accounts, budgets, and tax filings for both entities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Risk Management and Compliance&lt;/strong&gt;: Implement risk management protocols and ensure legal and financial compliance across the organization.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Technical Skills&lt;/strong&gt;: Proficiency in corporate and non-profit law, financial operations, and compliance. Proven experience in setting up and managing both FP and NPO organizations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Soft Skills&lt;/strong&gt;: Strong problem-solving abilities, organisational skills, and effective communication.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Local WP Setup</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/setup/</guid><description>&lt;p&gt;This guide helps you set up your local WordPress dev environment.&lt;/p&gt;
&lt;h2 id="set-up-localwp"&gt;Set Up LocalWP&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Download and install &lt;a href="https://localwp.com/"&gt;LocalWP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Create a new site (use &amp;ldquo;Preferred&amp;rdquo; environment)&lt;/li&gt;
&lt;li&gt;Set credentials (e.g. &lt;code&gt;admin&lt;/code&gt; / &lt;code&gt;admin&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Access:
&lt;ul&gt;
&lt;li&gt;Site: &lt;code&gt;http://your-site.local&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Admin: &lt;code&gt;http://your-site.local/wp-admin&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;</description></item><item><title>Portfolio Strategy</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/satellite-projects/strategy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/satellite-projects/strategy/</guid><description>&lt;h2 id="multi-project-ecosystem"&gt;Multi-Project Ecosystem&lt;/h2&gt;
&lt;p&gt;Building satellite projects creates a network of related websites that compete in the same market while using different technical approaches. This expands digital footprint by targeting the same keywords from multiple angles.&lt;/p&gt;
&lt;h4 id="framework-distribution-strategy"&gt;Framework Distribution Strategy&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Each satellite project uses different technology stack&lt;/li&gt;
&lt;li&gt;Learn multiple approaches to solving same problems&lt;/li&gt;
&lt;li&gt;Reduce technical risk through diversification&lt;/li&gt;
&lt;li&gt;Test different performance and user experience approaches&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="market-positioning"&gt;Market Positioning&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Target overlapping keywords and audiences&lt;/li&gt;
&lt;li&gt;Different brand positioning per project&lt;/li&gt;
&lt;li&gt;Varied content approaches and user experiences&lt;/li&gt;
&lt;li&gt;Replicate effective features in other projects&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; &lt;/p&gt;</description></item><item><title>Recruitment</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/operations/recruitment/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/operations/recruitment/</guid><description>&lt;h2 id="collaboration-framework"&gt;Collaboration Framework&lt;/h2&gt;
&lt;h3 id="process-overview"&gt;Process Overview&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Step 1: Preparation&lt;/strong&gt; - Initial research on background and expertise&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 2: Informal Chat&lt;/strong&gt; - Brief conversation to assess initial mutual interest&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 3: Formal Meeting&lt;/strong&gt; - Main discussion where we present the project in detail and explore alignment&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 4: Expectations Discussion&lt;/strong&gt; - Second conversation to clarify roles, deliverables, and working arrangements&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 5: Collaboration Decision&lt;/strong&gt; - Final decision point for both parties&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: Steps 3 and 4 are conducted as video calls and represent our main meetings in the collaboration process.&lt;/p&gt;</description></item><item><title>SEO Basics</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/fundamentals/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/fundamentals/</guid><description/></item><item><title>SEO Guidelines</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/strategy/seo-guidelines/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/strategy/seo-guidelines/</guid><description>&lt;ul&gt;
&lt;li&gt;Keyword research and target selection&lt;/li&gt;
&lt;li&gt;On-page optimization basics&lt;/li&gt;
&lt;li&gt;Content structure and headings&lt;/li&gt;
&lt;li&gt;Technical SEO requirements&lt;/li&gt;
&lt;li&gt;Performance tracking and measurement&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Social Media Guidelines</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/outreach/social-media-guidelines/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/outreach/social-media-guidelines/</guid><description>&lt;ul&gt;
&lt;li&gt;Platform-specific posting guidelines&lt;/li&gt;
&lt;li&gt;Brand voice and tone on social media&lt;/li&gt;
&lt;li&gt;Community engagement best practices&lt;/li&gt;
&lt;li&gt;Content approval and review process&lt;/li&gt;
&lt;li&gt;Crisis communication and response protocols&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Suggest a Name</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/general/suggest-name/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/general/suggest-name/</guid><description>&lt;h3 id="naming-guidelines"&gt;Naming Guidelines&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Should be a Tibetan word (can also be a made up word)&lt;/li&gt;
&lt;li&gt;Focus on Tibetans, not just Tibet&lt;/li&gt;
&lt;li&gt;Symbolic representation (represent Tibet and Tibetans without using the the word &amp;ldquo;Tibet&amp;rdquo;)&lt;/li&gt;
&lt;li&gt;Around 5-7 letters&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="suggestions"&gt;Suggestions&lt;/h3&gt;
&lt;p&gt;Tibetan words for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Platform&lt;/li&gt;
&lt;li&gt;Digital/modern&lt;/li&gt;
&lt;li&gt;Space&lt;/li&gt;
&lt;li&gt;Search/find&lt;/li&gt;
&lt;li&gt;Write/script/scroll&lt;/li&gt;
&lt;li&gt;Collection&lt;/li&gt;
&lt;li&gt;Truth/authentic&lt;/li&gt;
&lt;li&gt;Canvas&lt;/li&gt;
&lt;li&gt;Flux/change&lt;/li&gt;
&lt;li&gt;Information&lt;/li&gt;
&lt;li&gt;Tibetan Hub&lt;/li&gt;
&lt;li&gt;Verb (or any Tibetan word)&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Visual Identity</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/brand/visual-identity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/brand/visual-identity/</guid><description>&lt;ul&gt;
&lt;li&gt;Logo usage guidelines and variations&lt;/li&gt;
&lt;li&gt;Color palette (hex codes, usage rules)&lt;/li&gt;
&lt;li&gt;Typography hierarchy and font choices&lt;/li&gt;
&lt;li&gt;Visual style principles and examples&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Website Developer</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/engineering/web-developer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/engineering/web-developer/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Website Development and Optimisation&lt;/strong&gt;: Design, develop, and maintain multiple subdomains using frontend (HTML, CSS, JavaScript) and back-end technologies (PHP, MYSQL), ensuring a cohesive and responsive user experience across devices.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Content Management and Security&lt;/strong&gt;: Integrate and customise CMS platforms (WordPress) for easy content updates, ensuring all content follows best practices for accessibility, SEO, and security.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Testing, Debugging, and Collaboration&lt;/strong&gt;: Conduct thorough testing and debugging, implement CI/CD practices, ensure web application security, and collaborate with product and business teams to translate requirements into technical specifications and document processes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Technical Skills&lt;/strong&gt;: Proficiency in HTML, CSS, JavaScript, PHP, and understanding of Chrome DevTools. Experience with WordPress administration, theme files, plugins, and server-related tasks. Familiarity with version control systems such as Git.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Soft Skills&lt;/strong&gt;: Open-mindedness to learning new languages and tools, detail-oriented approach to development and optimisation, strong problem-solving skills, and effective communication skills.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Website Ecosystem</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/core-project/ecosystem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/core-project/ecosystem/</guid><description>&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Subdomain&lt;/th&gt;
 &lt;th&gt;Content Scope&lt;/th&gt;
 &lt;th&gt;Target Audience&lt;/th&gt;
 &lt;th&gt;Existing Platforms&lt;/th&gt;
 &lt;th&gt;Collaborations&lt;/th&gt;
 &lt;th&gt;Keywords&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Main&lt;/td&gt;
 &lt;td&gt;Tibet 101, Tibetan profile, org info (Tibet House, Lha), monasteries/nunneries, CTA info, blogs&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Non-Tibetans; &lt;strong&gt;Secondary&lt;/strong&gt;: Tibetans&lt;/td&gt;
 &lt;td&gt;NA&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Organization&lt;/strong&gt;: CTA&lt;/td&gt;
 &lt;td&gt;tibet, tibetan buddhism, tibetan astrology, tibetan medicine, tibetan prayer flags, tibetan monks, tibet house, tibetan refugees, tibetan history, tibetan exiles, tibetan youth congress, free tibet, tibet plateau, tibet movement&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Arts &amp;amp; Culture&lt;/td&gt;
 &lt;td&gt;Artist portfolios, Tibetan arts, museums/exhibitions, films/documentaries&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Non-Tibetans; &lt;strong&gt;Secondary&lt;/strong&gt;: Tibetan artists&lt;/td&gt;
 &lt;td&gt;Norbulingka, TIPA, art orgs&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;People&lt;/strong&gt;: Tibetan artists&lt;/td&gt;
 &lt;td&gt;tibetan art, tibetan culture, tibetan yoga, losar, tibetan singing bowl, incense, healing sound, bon, cuisine, zen music, meditation, handicraft, mandala, jewelry, language, book of the dead, seven years in tibet&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;News&lt;/td&gt;
 &lt;td&gt;Authentic Tibet-related news (India, Tibet, overseas)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Tibetans; &lt;strong&gt;Secondary&lt;/strong&gt;: Non-Tibetans&lt;/td&gt;
 &lt;td&gt;CTA News, Phayul, Tibetan Journal, Yarloong&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Organization&lt;/strong&gt;: CTA&lt;/td&gt;
 &lt;td&gt;tibet news, tibetan news&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Career&lt;/td&gt;
 &lt;td&gt;Centralized job platform for all Tibetan orgs&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Tibetans&lt;/td&gt;
 &lt;td&gt;Tibet Career Centre, CTA&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;People&lt;/strong&gt;: Facebook group admins&lt;/td&gt;
 &lt;td&gt;tibetan jobs, employment, careers&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Facts&lt;/td&gt;
 &lt;td&gt;Statistics: research papers, census, etc.&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Tibetan orgs, researchers&lt;/td&gt;
 &lt;td&gt;CTA&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;People&lt;/strong&gt;: international and tibetan researchers&lt;/td&gt;
 &lt;td&gt;tibet stats, tibetan demographics&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Events (Calendar)&lt;/td&gt;
 &lt;td&gt;Event listings from Tibetan orgs, Tibetan holidays&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Tibetans; &lt;strong&gt;Secondary&lt;/strong&gt;: Non-Tibetans&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;tibetan events, tibetan holidays&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Tourism*&lt;/td&gt;
 &lt;td&gt;Local business info (restaurants, guesthouses, artists, tattooists)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Travelers (local &amp;amp; international)&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;tibet travel, tibet tourism&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Language&lt;/td&gt;
 &lt;td&gt;Language learning (Tibetan, English), freelance teachers, Zoom classes&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Non-Tibetans, monks, nuns; &lt;strong&gt;Secondary&lt;/strong&gt;: monastic institutions&lt;/td&gt;
 &lt;td&gt;Lha&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;learn tibetan, tibetan-english translation&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Diaspora&lt;/td&gt;
 &lt;td&gt;Info about Tibetan settlements globally, forums, community platform&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Tibetans&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;tibetan settlements, tibetan diaspora&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Stories&lt;/td&gt;
 &lt;td&gt;Stories and documentaries of Tibetans&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Non-Tibetans&lt;/td&gt;
 &lt;td&gt;Stories of Tibetans&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;tibetan stories, tibetan people&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Shop*&lt;/td&gt;
 &lt;td&gt;Merchandise (Thangka, bowls, etc.)&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;buy thangka, singing bowl, tibetan crafts&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Mental Health / Psychology&lt;/td&gt;
 &lt;td&gt;Mental health resources, chat, research&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Primary&lt;/strong&gt;: Both Tibetans and Non-Tibetans&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;—&lt;/td&gt;
 &lt;td&gt;tibetan mental health, psychology&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item><item><title>Build Workflow</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/satellite-projects/workflow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/satellite-projects/workflow/</guid><description>&lt;h2 id="implementation-process"&gt;Implementation Process&lt;/h2&gt;
&lt;p&gt;Every satellite project starts with selecting a framework to learn while building something that competes in the target market. Development happens in completely isolated environments.&lt;/p&gt;
&lt;h4 id="project-setup"&gt;Project Setup&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Choose framework to explore&lt;/li&gt;
&lt;li&gt;Acquire relevant domain name&lt;/li&gt;
&lt;li&gt;Set up independent hosting and infrastructure&lt;/li&gt;
&lt;li&gt;Create separate repository and analytics&lt;/li&gt;
&lt;li&gt;Build minimal viable solution&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="technical-standards"&gt;Technical Standards&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Minimal page implementations (1-5 pages max)&lt;/li&gt;
&lt;li&gt;Open source with MIT/Apache licensing&lt;/li&gt;
&lt;li&gt;Public repositories with clear documentation&lt;/li&gt;
&lt;li&gt;Learning notes and setup instructions included&lt;/li&gt;
&lt;li&gt;Individual tracking and performance monitoring&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="success-metrics"&gt;Success Metrics&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Technical mastery of chosen framework&lt;/li&gt;
&lt;li&gt;Keyword ranking performance&lt;/li&gt;
&lt;li&gt;Documented learning outcomes&lt;/li&gt;
&lt;li&gt;Portfolio growth and sustainability&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; &lt;/p&gt;</description></item><item><title>Communication</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/communication/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/communication/</guid><description>&lt;h2 id="core-practices"&gt;Core Practices&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;MR discussions stay in the MR:&lt;/strong&gt; Use comments and threads to capture all decisions and changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project-wide updates via Element:&lt;/strong&gt; Use the &lt;code&gt;Team: Dev&lt;/code&gt;room for updates, questions, and async check-ins.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fortnightly engineering calls:&lt;/strong&gt; Used for check-ins, blockers, or architectural discussions that require live input.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Write before you speak:&lt;/strong&gt; Prefer documenting your thoughts over unscheduled pings.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="tools"&gt;Tools&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Tool&lt;/th&gt;
 &lt;th&gt;Purpose&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;GitLab&lt;/td&gt;
 &lt;td&gt;Issues, Merge Requests, technical discussion&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Element&lt;/td&gt;
 &lt;td&gt;Team chat, async updates, questions&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Handbook&lt;/td&gt;
 &lt;td&gt;Long-term documentation and decisions&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="expectations"&gt;Expectations&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Keep MR threads clear, focused, and self-contained&lt;/li&gt;
&lt;li&gt;Use threads in Element to reduce noise&lt;/li&gt;
&lt;li&gt;Post blockers or major updates before calls&lt;/li&gt;
&lt;li&gt;Document meeting outcomes for future reference&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Community Partnerships</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/outreach/community-partnerships/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/outreach/community-partnerships/</guid><description>&lt;ul&gt;
&lt;li&gt;Partnership identification and outreach&lt;/li&gt;
&lt;li&gt;Relationship building and maintenance&lt;/li&gt;
&lt;li&gt;Collaboration agreements and expectations&lt;/li&gt;
&lt;li&gt;Community engagement activities&lt;/li&gt;
&lt;li&gt;Event planning and coordination&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Content Strategy</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/strategy/content-strategy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/marketing/strategy/content-strategy/</guid><description>&lt;ul&gt;
&lt;li&gt;Content goals and objectives&lt;/li&gt;
&lt;li&gt;Target audience and messaging&lt;/li&gt;
&lt;li&gt;Editorial calendar and planning&lt;/li&gt;
&lt;li&gt;Content types and formats&lt;/li&gt;
&lt;li&gt;Distribution and promotion strategy&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Design System</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/ux/design-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/ux/design-system/</guid><description>&lt;ul&gt;
&lt;li&gt;UI component library (buttons, forms, cards, navigation)&lt;/li&gt;
&lt;li&gt;Layout grids and spacing standards&lt;/li&gt;
&lt;li&gt;Color usage for interfaces (different from brand colors)&lt;/li&gt;
&lt;li&gt;Typography hierarchy for digital interfaces&lt;/li&gt;
&lt;li&gt;Interactive states and animation guidelines&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Editorial Workflow</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/content/editorial-workflow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/product/content/editorial-workflow/</guid><description>&lt;ul&gt;
&lt;li&gt;How content gets created (who does what, when)&lt;/li&gt;
&lt;li&gt;The step-by-step workflow from idea to publication&lt;/li&gt;
&lt;li&gt;Roles and responsibilities&lt;/li&gt;
&lt;li&gt;Approval and review processes&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Mission</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/mission/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/mission/</guid><description>&lt;h2 id="infrastructure-for-identity"&gt;Infrastructure for Identity&lt;/h2&gt;
&lt;p&gt;Our mission is to build a digital ecosystem that authentically represents Tibet’s history, culture, and current realities.&lt;/p&gt;
&lt;p&gt;We aim to promote Tibetan arts, language, and enterprise, while equipping our community with tools, opportunities, and platforms to thrive—now and for generations to come.&lt;/p&gt;</description></item><item><title>MVP</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/core-project/mvp/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/core-project/mvp/</guid><description>&lt;h2 id="main-domain"&gt;Main Domain&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/main.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/main.png" alt="Main"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="arts--culture"&gt;Arts &amp;amp; Culture&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/arts.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/arts.png" alt="Arts"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="news"&gt;News&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/news.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/news.png" alt="News"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="career"&gt;Career&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/career.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/career.png" alt="Career"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="facts"&gt;Facts&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/facts.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/facts.png" alt="Facts"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Onboarding</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/getting-started/onboarding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/getting-started/onboarding/</guid><description>&lt;h2 id="general-setup"&gt;General Setup&lt;/h2&gt;
&lt;h3 id="1-communication-platform"&gt;1. Communication Platform&lt;/h3&gt;
&lt;p&gt;We use &lt;strong&gt;Element&lt;/strong&gt; as our primary platform for all internal communication.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;See &lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/element/"&gt;Element Guide&lt;/a&gt; for application overview and setup instructions.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="2-file-sharing"&gt;2. File Sharing&lt;/h3&gt;
&lt;p&gt;We use &lt;strong&gt;Proton Drive&lt;/strong&gt; for internal documents and file exchange.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;See &lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/proton/"&gt;Proton Guide&lt;/a&gt; for application overview and access instructions.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="next-steps"&gt;Next Steps&lt;/h2&gt;
&lt;p&gt;After completing the general onboarding above, continue with your role-specific onboarding (if any) in the relevant section: Development, Product, Marketing, or Operations.&lt;/p&gt;
&lt;h3 id="additional-onboarding-pages"&gt;Additional Onboarding Pages&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/onboarding/"&gt;Developer Onboarding&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Program Coordinator</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/marketing/program-coordinator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/marketing/program-coordinator/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Partnership Development&lt;/strong&gt;: Identify and engage with Tibetan organizations and networks aligned with our mission, establishing collaborative relationships that support mutual goals and long-term impact.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contributor Engagement&lt;/strong&gt;: Bring in contributors who align with our values and can support various roles, helping them integrate into ongoing initiatives and programs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Community Outreach and Engagement&lt;/strong&gt;: Build connections with external groups and stakeholders to expand organizational reach, increase visibility, and strengthen trust within the broader community.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Technical Skills&lt;/strong&gt;: Experience in partnership development, stakeholder engagement, or community organizing. Ability to identify collaboration opportunities, assess organizational needs, and work effectively with remote communication and project management tools.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Soft Skills&lt;/strong&gt;: Strong relationship-building and communication abilities, self-motivated with good organizational skills, and comfortable working independently in a remote, volunteer-driven environment.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Proton Drive</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/proton/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/proton/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Proton Drive is a secure, privacy-focused cloud storage service. It&amp;rsquo;s used to store and share all work-related files in one central place. It&amp;rsquo;s a secure alternative to platforms like Google Drive.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="key-features"&gt;Key Features&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;End-to-End Encrypted:&lt;/strong&gt; Files are encrypted in storage and during transfer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No Account Needed:&lt;/strong&gt; Access shared folders directly via link. Optional account for easier management.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Structured Folders:&lt;/strong&gt; Each team member has a personal folder to manage files.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="user-setup-steps"&gt;User Setup Steps&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Step 1:&lt;/strong&gt; Receive a secure Proton Drive folder link via Element chat.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 2:&lt;/strong&gt; Use the link and enter the password provided.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Step 3:&lt;/strong&gt; Upload, view, and edit files directly in the browser.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optional:&lt;/strong&gt; If you have a Proton account, you can share your Proton email for direct folder access.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="general-proton-drive-guidelines"&gt;General Proton Drive Guidelines&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Keep Files Organized: Use folders and clear filenames when adding content.&lt;/p&gt;</description></item><item><title>Site Audit</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/audit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/audit/</guid><description/></item><item><title>Theme Development</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/theme/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/theme/</guid><description>&lt;h2 id="block-themes"&gt;Block Themes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Block themes use &lt;code&gt;theme.json&lt;/code&gt;, &lt;code&gt;templates/&lt;/code&gt;, and &lt;code&gt;parts/&lt;/code&gt; folders&lt;/li&gt;
&lt;li&gt;All parts of the site are editable via WP Admin → Appearance → Editor&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="resources"&gt;Resources&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/block-editor/"&gt;Developer Handbook&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/themes/core-concepts/"&gt;Core Concepts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/themes/templates/template-hierarchy/"&gt;Template Hierarchy&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Vision</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/vision/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/vision/</guid><description>&lt;h2 id="designed-for-continuity"&gt;Designed for Continuity&lt;/h2&gt;
&lt;p&gt;We envision a thriving digital ecosystem where Tibetan identity is not only preserved, but evolves to inspire, empower, and connect.&lt;/p&gt;
&lt;p&gt;This is more than digital presence—it is cultural continuity, economic opportunity, and global visibility, grounded in Tibetan values and voices.&lt;/p&gt;</description></item><item><title>Workflow Guide</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/workflow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/workflow/</guid><description>&lt;h2 id="visual-representation"&gt;Visual Representation&lt;/h2&gt;
&lt;p&gt;Here is a simple visual representation of the Git workflow:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;git add&lt;/code&gt; &amp;ndash;&amp;gt; &lt;code&gt;git commit&lt;/code&gt; &amp;ndash;&amp;gt; &lt;code&gt;git push&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id="1-working-directory"&gt;1. Working Directory&lt;/h3&gt;
&lt;p&gt;The working directory is where you create and modify your files. This is the starting point of the Git workflow.&lt;/p&gt;
&lt;h3 id="2-staging-area"&gt;2. Staging Area&lt;/h3&gt;
&lt;p&gt;The staging area is where you prepare your files for the next commit. You can think of it as a temporary holding area for your files before they are committed to the local repository.&lt;/p&gt;</description></item><item><title>Business Model Canvas</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/bmc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/bmc/</guid><description>&lt;p&gt;&lt;a href="https://handbook-bwrgy-org-971173.gitlab.io/images/bmc.png"&gt;&lt;img src="https://handbook-bwrgy-org-971173.gitlab.io/images/bmc.png" alt="BMC"&gt;&lt;/a&gt;
 &lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Segment&lt;/th&gt;
 &lt;th&gt;Driving Questions&lt;/th&gt;
 &lt;th&gt;Segment Description&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Value Propositions&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;What problem are we solving? Why does it need to be solved?&lt;/td&gt;
 &lt;td&gt;VP1: Build a website ecosystem. VP2: Establish frameworks and best practices for efficiency. Refer to problem statement sheet&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Customer Segments&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Who are we solving the problem for? Who will value the proposition? What are their characteristics?&lt;/td&gt;
 &lt;td&gt;Persona 1: Non-Tibetans curious about the Tibetan situation and culture. Persona 2: Tibetan youth (10–40 y.o., diaspora). Persona 3: Tourists. Persona 4: Volunteers (e.g., in Dharamshala). Other: Tibetan artists, business owners, Free Tibet orgs, monasteries (4 sub-segments)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Customer Relationships&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;What is our interaction with customers like?&lt;/td&gt;
 &lt;td&gt;Online: Websites. Offline: Events&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Channels&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;How do customers come in contact with the product? How do we communicate the value proposition? Where are the customers?&lt;/td&gt;
 &lt;td&gt;Social media (Instagram), Networking with Tibetan orgs, SEO (organic search), Existing platforms (Tibetan websites), Community events, Offline marketing (posters, boards), Word of mouth&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Key Activities&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;What activities must the business undertake to achieve the value proposition? How is the product distributed?&lt;/td&gt;
 &lt;td&gt;Web development, Recruitment&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Key Resources&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;What practical resources are needed for the key activities?&lt;/td&gt;
 &lt;td&gt;People, Workspaces, Computers&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Key Partners&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Who are our key partners? Why do we need them?&lt;/td&gt;
 &lt;td&gt;KP1: Tibetan experts (art, dev, design, history). KP2: Tibetan organisations. KP3: CTA (security, mentorship, advisory). KP4: Investors/funding partners&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Cost Structure&lt;/strong&gt; ($)&lt;/td&gt;
 &lt;td&gt;What are the monetary costs of operating? What costs are tied to activities, partners, and resources? Legal, insurance, etc?&lt;/td&gt;
 &lt;td&gt;Salaries for full-time dev/designer/team, Workspace rent, Hosting, domain, security, SEO tools, Slack, ClickUp, GitHub&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Revenue Streams&lt;/strong&gt; ($)&lt;/td&gt;
 &lt;td&gt;How do we convert our value proposition into financial gain?&lt;/td&gt;
 &lt;td&gt;Year 1: Funding (possibly via Kickstarter). Later: Tourism partnerships, ads, merchandise, skill outsourcing&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item><item><title>Merge and Rebase</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/merge-rebase/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/merge-rebase/</guid><description>&lt;h2 id="core-strategy"&gt;Core Strategy&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Rebase:&lt;/strong&gt; Use when bringing changes from main into your feature branch&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Merge:&lt;/strong&gt; Use when integrating your feature branch into main (via MR/PR)&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Aspect&lt;/th&gt;
 &lt;th&gt;Rebase&lt;/th&gt;
 &lt;th&gt;Merge&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;History&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Linear, clean&lt;/td&gt;
 &lt;td&gt;Preserves branching context&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Command&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;git rebase origin/main&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;git merge feature-branch&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Conflicts&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Resolve per commit&lt;/td&gt;
 &lt;td&gt;Resolve once&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Force Push&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Required after rebase&lt;/td&gt;
 &lt;td&gt;Not needed&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Team Impact&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Changes commit hashes&lt;/td&gt;
 &lt;td&gt;Safe for shared branches&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Best For&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Keeping feature current&lt;/td&gt;
 &lt;td&gt;Final integration&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="example-scenario"&gt;Example Scenario&lt;/h2&gt;
&lt;h3 id="initial-state"&gt;Initial State&lt;/h3&gt;
&lt;p&gt;You create a feature branch from commit F, then make several commits while main continues to evolve:&lt;/p&gt;</description></item><item><title>Multisite</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/multisite/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/wordpress/multisite/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;WordPress Multisite is a feature built into WordPress that allows us to run multiple websites from a single WordPress installation. Here’s a breakdown of how it works under the hood:&lt;/p&gt;
&lt;h4 id="1-single-codebase-multiple-sites"&gt;1. Single Codebase, Multiple Sites&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Only one set of WordPress core files.&lt;/li&gt;
&lt;li&gt;All sites share plugins and themes (though individual sites can enable/disable them).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="2-database-structure"&gt;2. Database Structure&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;All sites share a single database, but WordPress creates separate tables per site.&lt;/li&gt;
&lt;li&gt;Table structure:
&lt;ul&gt;
&lt;li&gt;Main site: wp_options, wp_posts, etc.&lt;/li&gt;
&lt;li&gt;Sub-sites: wp_2_options, wp_2_posts, wp_3_options, etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Global/shared tables include:
&lt;ul&gt;
&lt;li&gt;wp_users and wp_usermeta (users are shared across the network)&lt;/li&gt;
&lt;li&gt;wp_site, wp_blogs, wp_sitemeta for network management&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="3-domain-mapping"&gt;3. Domain Mapping&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Sites can be:
&lt;ul&gt;
&lt;li&gt;Subdomains: site1.example.com&lt;/li&gt;
&lt;li&gt;Subdirectories: example.com/site1&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;With a plugin or custom configuration, you can map custom domains (e.g., site1.com, site2.net).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="4-htaccess-and-wp-configphp"&gt;4. .htaccess and wp-config.php&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Multisite modifies both:
&lt;ul&gt;
&lt;li&gt;wp-config.php: defines MULTISITE, SUBDOMAIN_INSTALL, and other constants.&lt;/li&gt;
&lt;li&gt;.htaccess: rewrites URLs to route traffic correctly to each site.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="5-admin-interface"&gt;5. Admin Interface&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Two admin layers:
&lt;ul&gt;
&lt;li&gt;Network Admin (/wp-admin/network): For managing the entire network (users, themes, plugins, sites).&lt;/li&gt;
&lt;li&gt;Site Admin: Each site has its own admin dashboard (/wp-admin) with scoped permissions.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="6-security-and-isolation"&gt;6. Security and Isolation&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Sites are not fully isolated like containerized apps.&lt;/li&gt;
&lt;li&gt;Plugins and themes are network-wide, so a faulty plugin can affect all sites.&lt;/li&gt;
&lt;li&gt;User roles and capabilities can be restricted per site, but full sandboxing is not native.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="7-performance-and-caching"&gt;7. Performance and Caching&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Because of shared resources and a single DB, high-traffic multisites often need:
&lt;ul&gt;
&lt;li&gt;Advanced object caching (e.g., Redis)&lt;/li&gt;
&lt;li&gt;CDN and page caching&lt;/li&gt;
&lt;li&gt;DB scaling (e.g., using HyperDB or shard-based plugins)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Optimization</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/optimization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/tech-seo/optimization/</guid><description/></item><item><title>Git Commands</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/commands/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/git/commands/</guid><description>&lt;h2 id="1-getting-started"&gt;1. Getting Started&lt;/h2&gt;
&lt;h3 id="git-init"&gt;Git init&lt;/h3&gt;
&lt;p&gt;This command is used to initialize a new git repository or to add an existing repository to a new directory. Transform the current directory into a Git repository. This adds a .git subdirectory to the current directory and makes it possible to start recording revisions of the project.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;# It creates a new .git subdirectory in the current working directory&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git init 
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="git-config"&gt;Git config&lt;/h3&gt;
&lt;p&gt;A convenient way to set configuration options for your Git installation. You’ll typically only need to use this immediately after installing Git on a new development machine.&lt;/p&gt;</description></item><item><title>GitLab</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/gitlab/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/gitlab/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;GitLab is a comprehensive DevOps platform that combines version control, project management, CI/CD, and collaboration tools in one unified interface. It&amp;rsquo;s built around Git version control and provides everything needed for the complete software development lifecycle.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-is-git"&gt;What is Git?&lt;/h2&gt;
&lt;p&gt;Git is a distributed version control system that tracks changes in files and coordinates work between multiple people.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Version Control:&lt;/strong&gt; Track every change made to files over time—see what changed, when, and by whom.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Distributed:&lt;/strong&gt; Everyone has a complete copy of the project history. Work offline and sync when ready.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Branching &amp;amp; Merging:&lt;/strong&gt; Create separate &amp;ldquo;branches&amp;rdquo; to work on features, then merge them back when complete.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Collaboration:&lt;/strong&gt; Multiple people can work on the same project without conflicts through systematic merging.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-is-gitlab"&gt;What is GitLab?&lt;/h2&gt;
&lt;p&gt;GitLab is a comprehensive DevOps platform that uses Git as its foundation.&lt;/p&gt;</description></item><item><title>Keyword Research</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/keywords/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/solution/keywords/</guid><description>&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Keyword&lt;/th&gt;
 &lt;th&gt;Search Volume (India)&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;dharamshala&lt;/td&gt;
 &lt;td&gt;201,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet&lt;/td&gt;
 &lt;td&gt;90,500&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;dalai lama&lt;/td&gt;
 &lt;td&gt;74,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;dharamshala places to visit&lt;/td&gt;
 &lt;td&gt;14,800&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet map&lt;/td&gt;
 &lt;td&gt;12,100&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;losar festival&lt;/td&gt;
 &lt;td&gt;12,100&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan flags&lt;/td&gt;
 &lt;td&gt;9,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;is tibet a country&lt;/td&gt;
 &lt;td&gt;9,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan flag&lt;/td&gt;
 &lt;td&gt;9,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;losar&lt;/td&gt;
 &lt;td&gt;6,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;buddhist meditation&lt;/td&gt;
 &lt;td&gt;6,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;thangka painting&lt;/td&gt;
 &lt;td&gt;6,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tingmo&lt;/td&gt;
 &lt;td&gt;4,400&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet china&lt;/td&gt;
 &lt;td&gt;3,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan language&lt;/td&gt;
 &lt;td&gt;3,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan monastery&lt;/td&gt;
 &lt;td&gt;2,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan food&lt;/td&gt;
 &lt;td&gt;2,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan restaurant&lt;/td&gt;
 &lt;td&gt;1,900&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan buddhism&lt;/td&gt;
 &lt;td&gt;1,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet india&lt;/td&gt;
 &lt;td&gt;1,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan singing bowl&lt;/td&gt;
 &lt;td&gt;1,600&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan medicine&lt;/td&gt;
 &lt;td&gt;1,300&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;prayer flags&lt;/td&gt;
 &lt;td&gt;1,300&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan prayer flags&lt;/td&gt;
 &lt;td&gt;1,300&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;free tibet&lt;/td&gt;
 &lt;td&gt;1,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;is tibet free&lt;/td&gt;
 &lt;td&gt;1,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;india tibet map&lt;/td&gt;
 &lt;td&gt;1,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan alphabet&lt;/td&gt;
 &lt;td&gt;1,000&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet culture&lt;/td&gt;
 &lt;td&gt;720&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan culture&lt;/td&gt;
 &lt;td&gt;720&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibet news&lt;/td&gt;
 &lt;td&gt;720&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan astrology&lt;/td&gt;
 &lt;td&gt;480&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan paintings&lt;/td&gt;
 &lt;td&gt;390&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;tibetan meditation&lt;/td&gt;
 &lt;td&gt;170&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item><item><title>Culture</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/culture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/culture/</guid><description>&lt;h2 id="collaborative-by-design"&gt;Collaborative by Design&lt;/h2&gt;
&lt;p&gt;We work openly with shared responsibility. From designing icons to drafting policy briefs, we invite input early and often. We use asynchronous tools, clear documentation, and default to kindness and clarity in all communication.&lt;/p&gt;
&lt;h4 id="our-foundation"&gt;Our foundation&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Clear ownership (DRI) and accountability&lt;/li&gt;
&lt;li&gt;Defined processes for decisions and content&lt;/li&gt;
&lt;li&gt;Regular retrospectives for improvement&lt;/li&gt;
&lt;li&gt;Low-ego, respectful collaboration&lt;/li&gt;
&lt;li&gt;Clarity over assumptions&lt;/li&gt;
&lt;li&gt;Alignment with shared vision&lt;/li&gt;
&lt;li&gt;Principled action over impulse&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="deliberate-by-choice"&gt;Deliberate by Choice&lt;/h2&gt;
&lt;p&gt;We pause to think before we act, choose understanding over assumption, and build solutions that last.&lt;/p&gt;</description></item><item><title>MacOS</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/macos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/macos/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;</description></item><item><title>Linux</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/linux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/linux/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;</description></item><item><title>Values</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/values/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/values/</guid><description>&lt;h2 id="guided-by-purpose"&gt;Guided by Purpose&lt;/h2&gt;
&lt;p&gt;Our values guide how we build, collaborate, and serve. They inspire every decision—from platform design to team dynamics—and connect us to our mission of creating an authentic, empowering digital presence for the Tibetan community.&lt;/p&gt;
&lt;p&gt;Our core values include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Truth with Integrity&lt;/strong&gt;: We represent Tibet and Tibetan voices with honesty, accuracy, and care. Our work honors facts and lived experience, embracing complexity and nuance.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Empowerment through Ownership&lt;/strong&gt;: We create meaningful opportunities for Tibetans to lead, contribute, and shape their digital future. We believe in shared ownership and collective success.&lt;/p&gt;</description></item><item><title>Team</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/team/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/team/</guid><description>&lt;h2 id="1-strategy-team"&gt;1. Strategy Team&lt;/h2&gt;
&lt;p&gt;The strategy team is responsible for overall direction, strategic alignment, and prioritization. It ensures that our decisions remain mission-aligned and that all efforts contribute toward our long-term vision.&lt;/p&gt;
&lt;h2 id="2-operations-team"&gt;2. Operations Team&lt;/h2&gt;
&lt;p&gt;The operations team oversees the people, processes, and relationships that make our work possible. It ensures smooth coordination, nurtures partnerships, and maintains a healthy, accountable internal environment.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sub-teams&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Legal&lt;/strong&gt;: Handles governance, compliance, and policy frameworks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Outreach&lt;/strong&gt;: Leads external relations, partnerships, and community engagement.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Talent&lt;/strong&gt;: Manages roles, onboarding, internal communication, and team well-being.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="3-engineering-team"&gt;3. Engineering Team&lt;/h2&gt;
&lt;p&gt;The engineering team designs, builds, and maintains all digital systems, tools, and infrastructure. It ensures that our platforms are robust, accessible, and scalable.&lt;/p&gt;</description></item><item><title>Meetings</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/getting-started/meetings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/getting-started/meetings/</guid><description>&lt;h2 id="scheduled-meetings"&gt;Scheduled Meetings&lt;/h2&gt;
&lt;h3 id="strategy-meeting"&gt;Strategy Meeting&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;When:&lt;/strong&gt; Quarterly First Saturdays, 60 minutes&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who:&lt;/strong&gt; Strategy team&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Strategic planning, organization updates, and key decision-making&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="operations-meeting"&gt;Operations Meeting&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;When:&lt;/strong&gt; Monthly Saturdays, 60 minutes (with additional ad-hoc meetings based on collaboration preparation needs)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who:&lt;/strong&gt; Operations team&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Review collaboration status, discuss new partnership opportunities, and operational updates&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="engineering-meeting"&gt;Engineering Meeting&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;When:&lt;/strong&gt; Fortnightly Saturdays, 60 minutes&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who:&lt;/strong&gt; Engineering team&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Share progress on product development, technical discussions, and clarifications&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="watering-together-activity-check-in"&gt;Watering-Together Activity Check-in&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;When:&lt;/strong&gt; Weekly Saturdays, 45 minutes&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who:&lt;/strong&gt; All participants in the watering together activity&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Purpose:&lt;/strong&gt; Share updates on tasks, experiences, observations, etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="guidelines"&gt;Guidelines&lt;/h2&gt;
&lt;h3 id="meeting-standards"&gt;Meeting Standards&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;All meetings accommodate multiple time zones (currently, GMT, CET, CST, and IST.)&lt;/li&gt;
&lt;li&gt;Meeting agendas are discussed and finalized 72 hours before the meeting to allow adequate preparation time&lt;/li&gt;
&lt;li&gt;Come prepared with any required pre-work&lt;/li&gt;
&lt;li&gt;Use Element for questions during presentations&lt;/li&gt;
&lt;li&gt;Action items are documented and assigned before meeting ends&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="meeting-template"&gt;Meeting Template&lt;/h3&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-txt" data-lang="txt"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;[Meeting Title]
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;[Participants] | [Date] | [Platform] | [Duration]
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;💬 Segue (5 MIN)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- Quick check-ins and context
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;📋 Agenda (45 MIN)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- Topic 1:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- Topic 2:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;🎯 Action Items (5 MIN)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- [ ] Task - Owner - Due date
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;➡️ Next Steps/Notes (5 MIN)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- Key takeaways
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description></item><item><title>Contact</title><link>https://handbook-bwrgy-org-971173.gitlab.io/about/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/about/contact/</guid><description>&lt;p&gt;We&amp;rsquo;d love to hear from you. Send us an email and we&amp;rsquo;ll get back to you as soon as possible.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Email: &lt;a href="mailto:tashidelek@bwrgy.org?subject=BWRGY%20%7C%20Collaboration%20Interest"&gt;tashidelek@bwrgy.org&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;When reaching out, please include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your name and organization (if applicable)&lt;/li&gt;
&lt;li&gt;A brief description of your inquiry&lt;/li&gt;
&lt;li&gt;Any relevant details that might help us assist you better&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We look forward to connecting with you!&lt;/p&gt;</description></item><item><title>Research Documents</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/research/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/tools/research/</guid><description>&lt;p&gt;Browse our community-based &lt;a href="https://drive.proton.me/urls/AVVGY12E9M#2ivWZEyt2YK4"&gt;research documents&lt;/a&gt;—a collection of field reports, studies, and insights published by other scholars, organizations, and institutions from Tibetan communities.&lt;/p&gt;</description></item><item><title>AWS</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/infrastructure/aws/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/infrastructure/aws/</guid><description/></item><item><title>Cloudflare</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/infrastructure/cloudflare/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/infrastructure/cloudflare/</guid><description/></item><item><title>CSS</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/css/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/css/</guid><description>&lt;h2 id="formatting--naming"&gt;Formatting &amp;amp; Naming&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use 2 spaces for indentation&lt;/li&gt;
&lt;li&gt;One selector per line in multi-selector rules&lt;/li&gt;
&lt;li&gt;Use kebab-case for class names: &lt;code&gt;.main-header&lt;/code&gt;, &lt;code&gt;.btn-primary&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Prefix component classes: &lt;code&gt;.card-title&lt;/code&gt;, &lt;code&gt;.nav-item&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Use meaningful, descriptive names over abbreviated ones&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="organization--structure"&gt;Organization &amp;amp; Structure&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Group related properties together (positioning, box model, typography, visual)&lt;/li&gt;
&lt;li&gt;Use comments to separate major sections&lt;/li&gt;
&lt;li&gt;Keep specificity low - avoid deep nesting&lt;/li&gt;
&lt;li&gt;Mobile-first approach with min-width media queries&lt;/li&gt;
&lt;li&gt;Separate layout, components, and utility classes&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="best-practices--tools"&gt;Best Practices &amp;amp; Tools&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Avoid &lt;code&gt;!important&lt;/code&gt; - use higher specificity instead&lt;/li&gt;
&lt;li&gt;Use CSS custom properties for repeated values&lt;/li&gt;
&lt;li&gt;Prefer classes over IDs for styling&lt;/li&gt;
&lt;li&gt;Use Prettier for consistent formatting&lt;/li&gt;
&lt;li&gt;Lint with stylelint for error checking&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://css-tricks.com/guides/"&gt;CSS-Tricks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/CSS"&gt;MDN Web Docs – CSS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.smashingmagazine.com/tag/css/"&gt;Smashing Magazine – CSS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Docsy</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/docsy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/docsy/</guid><description>&lt;h2 id="formatting--structure"&gt;Formatting &amp;amp; Structure&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use TOML frontmatter for all content files&lt;/li&gt;
&lt;li&gt;Follow Hugo&amp;rsquo;s content organization with &lt;code&gt;_index.md&lt;/code&gt; for sections&lt;/li&gt;
&lt;li&gt;Use consistent weight values for navigation ordering&lt;/li&gt;
&lt;li&gt;Keep markdown files clean with proper heading hierarchy&lt;/li&gt;
&lt;li&gt;Use Hugo shortcodes for complex content blocks&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="content--navigation"&gt;Content &amp;amp; Navigation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Include proper frontmatter: &lt;code&gt;title&lt;/code&gt;, &lt;code&gt;description&lt;/code&gt;, &lt;code&gt;type&lt;/code&gt;, &lt;code&gt;weight&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Use descriptive page titles and meta descriptions&lt;/li&gt;
&lt;li&gt;Organize content in logical directory structures&lt;/li&gt;
&lt;li&gt;Set up proper menu navigation with parent-child relationships&lt;/li&gt;
&lt;li&gt;Use &lt;code&gt;no_list: true&lt;/code&gt; to exclude pages from section listings&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="best-practices--tools"&gt;Best Practices &amp;amp; Tools&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Test responsive design across different screen sizes&lt;/li&gt;
&lt;li&gt;Validate Hugo build process with &lt;code&gt;hugo --gc --minify&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Use Hugo&amp;rsquo;s built-in syntax highlighting for code blocks&lt;/li&gt;
&lt;li&gt;Implement proper search functionality with Docsy&amp;rsquo;s search features&lt;/li&gt;
&lt;li&gt;Follow accessibility guidelines for documentation sites&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.docsy.dev/docs/"&gt;Docsy theme documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://gohugo.io/content-management/"&gt;Hugo content management&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Domain Consultant (Arts &amp; Culture)</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/domain-consultant-arts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/domain-consultant-arts/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cultural Authority and Validation&lt;/strong&gt;: Serve as subject matter expert (for the &lt;strong&gt;Arts &amp;amp; Culture&lt;/strong&gt; subdomain) on Tibetan arts and culture, ensuring website content maintains authenticity and cultural accuracy through detailed reviews and recommendations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Community Network Liaison&lt;/strong&gt;: Leverage established relationships within the global Tibetan arts community to identify and connect with artists, historians, and cultural practitioners for content collaboration.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Strategic Content Advisory&lt;/strong&gt;: Guide content strategy by participating in research interviews and providing expert insights on cultural representation and storytelling approaches.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Domain Expertise&lt;/strong&gt;: Advanced knowledge of Tibetan art, history, and culture with formal academic background or equivalent professional experience. Extensive network within Tibetan cultural communities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Advisory Skills&lt;/strong&gt;: Exceptional attention to detail for cultural authenticity, strong communication abilities for stakeholder engagement, and collaborative approach to cross-cultural content development.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Domain Consultant (News)</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/domain-consultant-news/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/domain-consultant-news/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;News Content Authority&lt;/strong&gt;: Serve as subject matter expert (for the &lt;strong&gt;News&lt;/strong&gt; subdomain) on Tibetan current affairs and contemporary issues, ensuring news content maintains journalistic integrity and cultural context.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Media Source Network&lt;/strong&gt;: Leverage established relationships within journalism and media communities to connect with credible news sources, reporters, and media outlets covering Tibet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;News Strategy Advisory&lt;/strong&gt;: Provide expert guidance on news content strategy, story development, and editorial decisions while participating in research interviews on current Tibetan affairs.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Domain Expertise&lt;/strong&gt;: Deep knowledge of Tibetan current affairs, contemporary issues, and media landscape with formal journalism background or equivalent professional experience. Extensive network within news and media organizations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Advisory Skills&lt;/strong&gt;: Strong news judgment and editorial instincts, excellent communication abilities for stakeholder engagement, and collaborative approach to news content validation and development.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>HTML</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/html/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/html/</guid><description/></item><item><title>Javascript</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/javascript/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/javascript/</guid><description/></item><item><title>PHP</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/php/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/php/</guid><description/></item><item><title>Researcher</title><link>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/researcher/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/contribute/content/researcher/</guid><description>&lt;h2 id="responsibilities"&gt;Responsibilities&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Research and Fact-Checking&lt;/strong&gt;: Conduct thorough research on Tibetan history, culture, and current affairs to ensure all content is accurate, well-sourced, and academically rigorous.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Source Documentation and Verification&lt;/strong&gt;: Identify, evaluate, and document primary and secondary sources while maintaining comprehensive citation standards and verifying information authenticity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Content Investigation and Analysis&lt;/strong&gt;: Investigate complex topics requiring deep research, analyze trends and patterns in Tibetan affairs, and provide evidence-based insights for content development.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Research Expertise&lt;/strong&gt;: Advanced research methodology skills with experience in academic or professional research environments. Knowledge of Tibetan studies, history, or related fields preferred.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Analytical Skills&lt;/strong&gt;: Strong critical thinking abilities, proficiency with research databases and tools, excellent source evaluation skills, and meticulous attention to detail for fact verification.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>WordPress</title><link>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/wordpress/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://handbook-bwrgy-org-971173.gitlab.io/handbook/development/coding-standards/wordpress/</guid><description>&lt;h2 id="formatting--naming"&gt;Formatting &amp;amp; Naming&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Follow WordPress PHP coding standards (tabs for indentation)&lt;/li&gt;
&lt;li&gt;Use snake_case for function names: &lt;code&gt;get_custom_post_data()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Prefix all functions, classes, and globals with unique identifier&lt;/li&gt;
&lt;li&gt;Use descriptive hook names: &lt;code&gt;my_plugin_before_content_display&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Follow WordPress file naming conventions&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="hooks--functions"&gt;Hooks &amp;amp; Functions&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use proper WordPress hooks instead of direct file modifications&lt;/li&gt;
&lt;li&gt;Sanitize and validate all user input&lt;/li&gt;
&lt;li&gt;Escape output data with appropriate functions: &lt;code&gt;esc_html()&lt;/code&gt;, &lt;code&gt;esc_attr()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Use WordPress functions over PHP equivalents when available&lt;/li&gt;
&lt;li&gt;Check user capabilities before executing admin functions&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="best-practices--tools"&gt;Best Practices &amp;amp; Tools&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use WordPress coding standards with PHPCS&lt;/li&gt;
&lt;li&gt;Follow the WordPress Plugin/Theme directory guidelines&lt;/li&gt;
&lt;li&gt;Implement proper nonce verification for forms&lt;/li&gt;
&lt;li&gt;Use WordPress transients for caching&lt;/li&gt;
&lt;li&gt;Test with WordPress debug mode enabled&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/coding-standards/wordpress-coding-standards/"&gt;WordPress coding standards&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/themes/basics/"&gt;Theme development guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.wordpress.org/themes/functionality/security/"&gt;Theme security and validation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>