Help shape the transition toward fully decentralized applications on GRIDNET OS<\/li>\n<\/ul>\nWhether you’re a developer, creator, visionary, or simply curious about decentralized futures, GRIDNET Basecamp offers an entry point into this emerging paradigm.<\/p>\n
The Circle Completes<\/h2>\n
For 300,000 years, Homo sapiens organized in circles around fires, sharing tasks and resources within small, trusted groups. For 10,000 years, we built hierarchies that enabled coordination among strangers but concentrated power in the hands of the few. For 300 years, we’ve experimented with distributing power more broadly through democratic systems and markets.<\/p>\n
Now, digital technology enables us to combine the intimacy and trust of tribal circles with the scale and efficiency of modern systems. GRIDNET represents one of the boldest experiments in this new synthesis \u2013 a return to circular organization, but at unprecedented scale and with remarkable new capabilities.<\/p>\n
By joining this community, you’re not just adopting a new technology. You’re participating in the ongoing evolution of how humans cooperate and organize. The circle is completing \u2013 not by returning to the past, but by spiraling forward into new possibilities that our ancestors could scarcely have imagined.<\/p>\n
<\/h2>\nAssets Request Board for GRIDNET Basecamp<\/h2>\n
The\u00a0Assets Request Board<\/strong>\u00a0is a public Kanban-style board in GRIDNET’s Basecamp (Deck app) where community members and influencers can request new explanatory content assets (graphics, videos, tutorials, etc.). Approved\u00a0Content Creators<\/strong>\u00a0can then be assigned to produce these assets.\u00a0Wizards<\/strong>\u00a0(community moderators) oversee this board \u2013 they approve requests, assign tasks to creators, and ensure each request moves through stages from initial idea to final delivery and GNC reward payment. This unified board simplifies the content creation process, providing transparency and a clear structure for everyone involved.<\/p>\n![\"\"](\"https:\/\/gridnet.org\/wpp\/wp-content\/uploads\/2025\/04\/Screenshot-2025-04-25-at-21.22.20.png\")
<\/p>\n
Board Columns and Asset Lifecycle<\/h2>\n
The board is organized into several columns (lists), each representing a stage in the lifecycle of an asset request. Only Wizards can move cards between columns, ensuring that each stage is properly managed. The columns on the Assets Request Board are:<\/p>\n
\n- New Request (Submitted)<\/strong>\u00a0\u2013 Newly submitted asset requests from community members or influencers appear here. Each card in this column represents a content idea awaiting review. The card includes details of what content is needed (using the template provided). Wizards monitor this list and review each request in turn.<\/li>\n
- Approved (Open for Assignment)<\/strong>\u00a0\u2013 Once our team reviews a request and deems it appropriate (feasible, non-duplicate, aligned with community goals), the card is moved to\u00a0Approved<\/strong>. In this column, the request is officially accepted. Wizards will typically update the card with a confirmed\u00a0reward amount (in GNC)<\/strong>\u00a0and any additional notes or requirements. The task is now open to be assigned to an approved Content Creator. (At this stage, Wizards may either wait for a Content Creator to volunteer via comments or proactively assign one.)<\/li>\n
- Assigned & In Progress<\/strong>\u00a0\u2013 When\u00a0our team assigns an approved request to a specific Content Creator, the card moves into\u00a0Assigned & In Progress<\/strong>. The Content Creator\u2019s name is noted on the card, along with a due date if applicable. In this column, the asset is actively being created. The Content Creator works on the graphic\/video\/tutorial and posts updates or questions in the card\u2019s comments. The requester and Wizards can also chime in to clarify details as needed. This stage is all about execution and iteration.<\/li>\n
- Ready for Review (Content Delivered)<\/strong>\u00a0\u2013 Once the Content Creator finishes the asset, they attach the content or provide a link in the card and notify the Wizards (via a comment) that it’s ready. The card then moves to\u00a0Ready for Review<\/strong>. Wizards (and possibly the original requester, if needed) will review the delivered content here. They check that it meets the requirements, is accurate, and follows any style guidelines. If changes are required, the card remains in this column while the Content Creator makes revisions (with the status updated in the card\/comments).<\/li>\n
- Completed (Delivered & Paid)<\/strong>\u00a0\u2013 After the content passes review and is approved by a Wizard, the task is marked completed and the card moves to\u00a0Completed<\/strong>. At this final stage, Wizards arrange for the reward payment in\u00a0GNC<\/strong>\u00a0to the Content Creator as promised. The card\u2019s description or comments should be updated with a final note (e.g., confirmation of delivery and payment). Completed tasks remain visible here as a record of fulfilled requests and as a reference library of created assets.<\/li>\n<\/ol>\n
(Optional: There can be an additional\u00a0Closed\/Rejected<\/strong>\u00a0column for requests that do not get approved. For example, if a request is a duplicate, inappropriate, or not feasible, Wizards can move the card to “Closed” with an explanation in the comments. This keeps the “New Request” column clean while providing transparency about why certain requests did not proceed.)<\/em><\/p>\nEach column is publicly viewable so community members can track the progress of their requests in real time. Because only Wizards have permission to move cards, the workflow remains orderly \u2013 community requesters submit ideas, Content Creators focus on execution, and Wizards handle the stage transitions.<\/p>\n
Card Templates for Each Stage<\/h2>\n
To ensure consistency, each card on the Assets Request Board should follow a template that is updated as it progresses through the stages. Below are recommended card content templates for each stage of the process. When creating or updating a card, copy the relevant template sections into the card\u2019s description and fill in the details.<\/p>\n
\n- New Request (Submission Stage) \u2013 Card Template:<\/strong>When a community member or influencer creates a new request, they should format the card as follows:\n
Asset Title: [A short, descriptive title for the requested asset]\r\n\r\nDescription\/Purpose: [A detailed description of what the asset should cover or achieve. Include the topic, key points to explain, and why this content is needed.]\r\n\r\nAsset Type: [Graphic \/ Video \/ Article \/ Tutorial \/ Other \u2013 specify the format of content being requested]\r\n\r\nTarget Audience: [e.g., Beginner, Advanced, General Audience \u2013 who is this content aimed at?]\r\n\r\nLanguage: [Preferred language for the content, e.g., English, Polish, Spanish]\r\n\r\nAdditional Requirements: [Any specific requirements or preferences \u2013 e.g., length\/duration, image dimensions, style or branding guidelines, platform where it will be used]\r\n\r\nRequester: [Your name or handle, if not automatically noted on the card]\r\n\r\nReferences\/Links: [Optional \u2013 links to relevant materials or examples for inspiration]\r\n<\/pre>\nThe requester should fill in all applicable fields. The card\u2019s title should be concise (e.g., “Tutorial: Setting Up a Node on GRIDNET”) and the description should clearly outline expectations. Providing thorough info at this stage helps Wizards and Content Creators understand the request.<\/li>\n
- Approved (Post-Review Stage) \u2013 Card Template Update:<\/strong>Once a Wizard moves the card to “Approved,” they will augment the card with additional fields for assignment and reward:\n
Status: \u2705 Approved by on [Date]. (Ready for assignment to a Content Creator)\r\n\r\nReward: [X] GNC (to be paid upon completion)\r\n\r\nPriority: [High \/ Medium \/ Low] (optional, if applicable based on urgency or importance)\r\n\r\nAssigned Content Creator: [To be determined or @Name once assigned]\r\n<\/pre>\nIn this stage, the Wizards make it clear that the task is approved and what the incentives are. The “Assigned Content Creator” can remain “To be determined” at first. Wizards may add a comment calling for volunteers or indicating that they are seeking an assignee.<\/li>\n
- Assigned & In Progress \u2013 Card Template Update:<\/strong>When a task is assigned, Wizards (or the Content Creator) should update the card description to reflect the current status:\n
Status: \ud83d\udea7 In Progress \u2013 Assigned to [Content Creator Name] on [Date].\r\n\r\nAssigned Content Creator: [Name (@username)]\r\n\r\nDeadline: [Date or timeframe for completion, if set]\r\n\r\nCurrent Progress: [Optional \u2013 brief notes on progress, e.g., \"Outline drafted\", \"50% complete\", \"Awaiting feedback on script\"]\r\n<\/pre>\nThe Content Creator can also add a checklist or sub-tasks in the card (e.g., “Storyboard”, “Draft version”, “Review edits”, “Final production”) to track work internally. Throughout this stage, the card\u2019s comments serve as the primary communication channel for updates, questions, and clarifications.<\/li>\n
- Ready for Review \u2013 Card Template Update:<\/strong>When the content is finished and uploaded, update the card as follows:\n
Status: \ud83d\udccb Ready for Review \u2013 Content submitted on [Date].\r\n\r\nDeliverables: [Link or attachment to the completed asset. For example: \"See attached video file\", \"Image uploaded above\", or \"Draft article: link to Google Doc\"]\r\n\r\nNotes for Review: [Any notes from the creator about the submission, e.g., \"Please check audio at 2:00 for volume\", \"Colors can be adjusted if needed\", or \"Alternate version in second attachment\".]\r\n<\/pre>\nThe Wizard(s) reviewing will use the comments to give feedback or approval. If revisions are needed, the card stays in this column; the Content Creator should address the feedback and update the deliverables, then comment again to notify Wizards for another review round.<\/li>\n
- Completed \u2013 Card Template Update:<\/strong>After final approval, the card should be updated to record completion:\n
Status: \ud83c\udf89 Completed \u2013 Approved on [Date].\r\n\r\nOutcome: [Summary of the final outcome, e.g., \"Infographic published on Twitter and community wiki\", or \"Video uploaded to official YouTube channel\".]\r\n\r\nReward Payment: [X] GNC transferred to [Content Creator Name] on [Date]. (Transaction reference: [Optional TX ID or confirmation if applicable])\r\n\r\nAcknowledgements: [Optional \u2013 e.g., \"Thanks to [Content Creator] for the great work on this asset!\" and\/or \"Requested by [Requester Name]\".]\r\n<\/pre>\nWizards should ensure the reward payment details are recorded for transparency. After this, the task is considered closed. The card remains in the Completed column as a public record and for future reference (others can see the asset or find it via tags).<\/li>\n<\/ul>\n
Using these templates at each stage ensures anyone viewing the card can quickly understand its history and current status. The structured format helps Wizards, Requesters, and Content Creators stay aligned and not miss important information.<\/p>\n
Guidelines for Requesters (Community Members & Influencers)<\/h2>\n
Community members and influencers who want to request content should follow these guidelines to make the process smooth and successful:<\/p>\n
\n- Search Before Requesting:<\/strong>\u00a0Before creating a new request, check the board (especially the Completed column or any existing asset library) to see if a similar asset already exists or is in progress. This avoids duplicate requests and shows you what\u2019s already available.<\/li>\n
- Use the Template:<\/strong>\u00a0When submitting a request, use the\u00a0New Request<\/strong>\u00a0card template provided above. Provide a clear title and a thorough description. The more details you give, the easier it is for Content Creators to deliver exactly what you need. Incomplete requests might be delayed while Wizards seek clarification.<\/li>\n
- Specify Audience and Purpose:<\/strong>\u00a0Clearly state who the content is for and what you want to achieve. For example, “This video is for beginner users who need help setting up a wallet” or “This graphic will be used in social media to explain our project.” This context helps creators tailor the content appropriately in tone and depth.\n
\n- Provide a clear title and a thorough description.<\/strong> The more details you give, the easier it is for Content Creators to deliver exactly what you need. Incomplete requests might be delayed while Wizards seek clarification.<\/li>\n
- Specify Audience and Purpose:<\/strong> Clearly state who the content is for and what you want to achieve. For example, “This video is for beginner users who need help setting up a wallet” or “This graphic will be used in social media to explain our project.” This context helps creators tailor the content appropriately in tone and depth.<\/li>\n
- Tag Your Request:<\/strong> Apply relevant tags\/labels<\/strong> to your card if possible. For example, tag the asset type (Graphic<\/strong>, Video<\/strong>, Tutorial<\/strong>), the difficulty level (Beginner<\/strong> or Advanced<\/strong>), and the language. Proper tagging ensures your request is categorized correctly and can be filtered easily by others. If you’re not sure about tags, Wizards will adjust them, but it’s helpful if you add what you can.<\/li>\n
- Be Responsive to Questions:<\/strong> After submitting, keep an eye on your request card. Wizards might ask clarifying questions in the comments or suggest changes to your description. Respond promptly to keep the process moving.<\/li>\n<\/ul>\n<\/li>\n
- Be Responsive to Questions:<\/strong>\u00a0After submitting, keep an eye on your request card. Wizards might ask clarifying questions in the comments or suggest changes to your description. Respond promptly to any questions or requests for info \u2013 this helps move your request to the Approved stage faster. If you disappear, your request might stagnate or be closed due to lack of info.<\/li>\n
- Stay Informed (but Patient):<\/strong>\u00a0Once your request is approved, understand that it may take some time to be assigned and completed. You can watch as it moves through the columns. It\u2019s okay to ask for status updates politely (for instance, if it’s been quiet for much longer than usual), but keep in mind Content Creators may be balancing tasks. Wizards will ensure nothing is forgotten.<\/li>\n
- Engage During Review:<\/strong>\u00a0If you\u2019re the requester, you might be tagged when the content is ready for review, especially if your input is needed to verify that it meets your needs. Provide feedback if you have any (e.g., “This covers everything I wanted, thanks!” or “It\u2019s great, but can we also mention X?”). Your perspective is valuable, but also trust the Content Creator and Wizards\u2019 expertise on quality and style.<\/li>\n
- Express Gratitude and Feedback:<\/strong>\u00a0After completion, if you found the asset useful, do thank the Content Creator and Wizards in the card comments. If you have suggestions for improvement, you can mention them as well (constructively). Positive feedback motivates creators, and constructive feedback can help in future tasks.<\/li>\n<\/ul>\n
By following these guidelines, requesters help ensure their ideas are understood and acted on efficiently. A well-prepared request with active requester participation is more likely to result in a high-quality asset that meets the need.<\/p>\n
Guidelines for Content Creators<\/h2>\n
Approved Content Creators are community members who have applied and been authorized to create official content assets. If you are a Content Creator working on this board, please keep the following guidelines in mind to collaborate effectively:<\/p>\n
\n- Review Available Tasks:<\/strong>\u00a0Regularly check the\u00a0Approved (Open for Assignment)<\/strong>\u00a0column for new requests that match your skill set (e.g., graphic design, video editing, technical writing). If you see a request you\u2019d like to work on, leave a comment on that card expressing interest. For example: “I can take this on, I have experience with infographic design. @WizardName”. This lets Wizards know you’re available. (If multiple creators volunteer, a\u00a0we will decide who to assign, so don\u2019t be discouraged if not every volunteer opportunity is assigned to you.)<\/li>\n
- Wait for Official Assignment:<\/strong>\u00a0Only start working on a task\u00a0after we<\/strong>\u00a0assign it to you and moves the card to In Progress with your name. This prevents confusion or duplicate work. Wizards may confirm assignment by tagging you in a comment like “Assigned to @YourName” and updating the card. If you commented to volunteer and haven\u2019t heard back yet, you can follow up after some time or look for another task in the meantime.<\/li>\n
- Clarify Requirements Up Front:<\/strong>\u00a0As soon as you\u2019re assigned, review the entire card (description and prior comments) carefully. If anything is unclear or if you need additional resources (logos, data, access, etc.), ask in the card comments. It\u2019s better to gather clarity at the start than to redo work later. Tag the requester or Wizards as needed for specific questions.<\/li>\n
- Use the Card to Track Work:<\/strong>\u00a0Follow the\u00a0In Progress<\/strong>\u00a0template by updating the card description with your name and the start date, and note any deadline. Feel free to add a checklist of sub-tasks on the card (Deck allows adding checklist items). Checking off items (like “script written”, “voiceover recorded”, “first draft complete”) not only helps you stay on track but also lets Wizards and the requester see progress at a glance. You can also post periodic short updates in comments, especially for longer tasks (e.g., “Drafting completed, moving on to recording audio”).<\/li>\n
- Maintain Quality and Branding:<\/strong>\u00a0Ensure the content you produce meets the community\u2019s quality standards and branding. Follow any style guides provided. For example, use official logos and correct color schemes for graphics, maintain accuracy and clarity in tutorials, and ensure good production values in videos (clear audio, proper resolution). If no formal guide exists, look at similar past assets in the Completed column as a reference for the expected tone and quality.<\/li>\n
- Time Management:<\/strong>\u00a0Honor the deadlines given. If a card has a due date or is tagged
\nUrgent, prioritize accordingly. If no deadline is explicit, use reasonable judgment (Wizards might give guidance like “hope to have this in about 2 weeks”). If you encounter delays (personal issues, unexpected complexity, etc.), inform us\u00a0before<\/strong>\u00a0the deadline passes. They can possibly extend the deadline or find additional help. Communication is key \u2013 it\u2019s understood that delays can happen, but keeping silent is not okay.<\/li>\n- Submit Work for Review:<\/strong>\u00a0When you finish the asset, attach the file(s) to the card or provide a stable link. For large files, you might use a cloud storage link or a specialized platform (e.g., upload a video to an unlisted YouTube link for preview). Ensure the\u00a0Deliverables<\/strong>\u00a0section in the card description is filled out with where to find the content. Then add a comment tagging the relevant Wizard(s) and requester: e.g., “@WizardName @RequesterName The video is ready for review, please check the link above.” After this, move on to other work while waiting \u2013 do not mark the card complete yourself.<\/li>\n
- Handle Feedback Gracefully:<\/strong>\u00a0It’s common to receive some feedback or requests for edits. Check the card comments after submission. If Wizards\/requester suggest changes, acknowledge the feedback and make the revisions as needed. Use the\u00a0Notes for Review<\/strong>\u00a0field or follow-up comments to describe what you changed or address any concerns. For example, “I’ve increased the font size on the infographic for readability, and corrected the stats in section 2.” Re-submit the updated content promptly. Remember, feedback isn\u2019t personal criticism \u2013 it\u2019s to ensure the final asset is the best it can be.<\/li>\n
- Completion and Reward:<\/strong>\u00a0Once we approve the content and moves the card to Completed, your job on that card is done! We will handle the GNC reward payment. Make sure you have provided your wallet\/address to them beforehand (probably during your application or via a profile). The card will note that you were paid. If there\u2019s any discrepancy (e.g., you haven’t received payment after a reasonable time), reach out to us directly (you can use Talk for a private message if needed and contact Wizards account). Typically, though, this process is smooth: you create great content, the community benefits, and you earn your reward.<\/li>\n
- Continuous Improvement:<\/strong>\u00a0As an approved Content Creator, you are a part of the GRIDNET content team. Feel free to share tips with fellow creators, ask for help if stuck, or suggest improvements to these processes. You might use a separate forum or group chat for creators to discuss things outside specific request cards. Wizards will appreciate suggestions that can streamline the workflow or address common issues. Also, maintain a good record \u2013 reliable and high-quality work might lead to more frequent assignments or even higher rewards over time.<\/li>\n<\/ul>\n
By following these guidelines, Content Creators can effectively contribute to the community, build a portfolio of work, and earn GNC rewards. The key is communication, quality, and collaboration at each step of the process.<\/p>\n
Process for Applying to Be a Content Creator<\/h2>\n
Community members who want to become approved Content Creators (so they can be assigned tasks on this board) need to go through an application process. This ensures that creators have the necessary skills and understand GRIDNET\u2019s content standards. Here\u2019s how to apply:<\/p>\n
\n- Visit the Content Creator Application Board:<\/strong>\u00a0GRIDNET Basecamp provides a separate Deck board for creator applications. (This could be linked from the Assets Request Board or mentioned in community docs \u2013 e.g., an “Apply to be a Content Creator” link.) On that Application Board, you’ll find instructions and an application card template.<\/li>\n
- Submit Your Application Card:<\/strong>\u00a0Create a new card in the Application board, filling out the required details. Typically, include:\n
\n- Name and Contact:<\/strong>\u00a0Who you are and how to reach you (your Basecamp username, email, or other contact info).<\/li>\n
- Skills and Content Areas:<\/strong>\u00a0Describe what kind of content you can create. Mention your specialties (e.g., “infographic design”, “animated videos”, “technical writing”) and any specific domain knowledge (e.g., “familiar with blockchain and DeFi concepts”).<\/li>\n
- Experience and Portfolio:<\/strong>\u00a0List any relevant experience or qualifications. Provide links to examples of your work if available (e.g., a portfolio, previous graphics or videos, blog posts\/tutorials you’ve written, etc.). If you have contributed to other community projects or open-source efforts, mention those too.<\/li>\n
- Availability:<\/strong>\u00a0Note how much time you expect to dedicate (for instance, “5-10 hours per week” or “mostly weekends”) and any schedule constraints. This helps Wizards know what scope of tasks to assign.<\/li>\n
- Motivation:<\/strong>\u00a0A brief statement on why you want to be a content creator for GRIDNET. Enthusiasm and alignment with the community\u2019s mission can help your application.<\/li>\n
- GNC Wallet Address:<\/strong>\u00a0(If applicable at this stage) Provide the address where you would like to receive rewards. If security is a concern, you could optionally provide this after acceptance via a secure channel instead of on the public card.<\/li>\n<\/ul>\n<\/li>\n
- Wizards’ Review of Application:<\/strong>\u00a0Wizards will monitor the Application Board and review new submissions. They may leave comments on your application card with questions or requests for clarification. For example, they might ask to see a specific type of work sample or inquire about your knowledge of a topic. Engage with these questions promptly and thoroughly.<\/li>\n
- Approval & Onboarding:<\/strong>\u00a0If your application is approved, Wizards will move your card to an “Approved” or similar column on the Application Board (or otherwise indicate acceptance). We will likely reach out with a welcome message. You will be granted the “Content Creator” role or added to the list of approved creators. This may include giving you certain permissions on the Basecamp (Deck) boards (like the ability to comment on the Assets Request Board cards and access any private creator resources). They might also invite you to a communication channel for Content Creators (for example, a Talk chat room or a forum thread for creators).<\/li>\n
- Orientation:<\/strong>\u00a0Upon approval, you might receive onboarding materials. This could be a guide with best practices, branding assets (logos, design templates), and references to past exemplary content. You might even be asked to start with a small test task or contribute to a simple request to get familiar with the process. Take time to review any guidelines provided \u2013 this sets you up for success in handling real requests.<\/li>\n
- Start Taking Tasks:<\/strong>\u00a0After onboarding, you can start picking up tasks from the Assets Request Board as described in the creators\u2019 guidelines. You now have the green light to volunteer for requests in the Approved column. Make sure to always follow the board process even though you\u2019re now an official creator.<\/li>\n
- Ongoing Evaluation:<\/strong>\u00a0Note that being an approved Content Creator is an ongoing role. Wizards may periodically review creators\u2019 performance. Consistently good work means you remain in good standing (and might get perks or higher-value assignments). If someone repeatedly fails to deliver or violates guidelines, Wizards might remove them from the creator list. This is rare and avoided by selecting good applicants and giving feedback, but it’s part of maintaining quality.<\/li>\n<\/ol>\n
By following this application process, the community ensures that those who produce content have demonstrated their ability and commitment. For applicants, it\u2019s a chance to show your passion and skills. Once on the team, you become a crucial part of educating and growing the GRIDNET community while earning rewards for your contributions.<\/p>\n
Roles and Responsibilities of Wizards<\/h2>\n
Wizards act as facilitators and gatekeepers on the Assets Request Board. They have special permissions and responsibilities to ensure the system runs smoothly and fairly:<\/p>\n
\n- Moderating New Requests:<\/strong>\u00a0Wizards regularly monitor the\u00a0New Request<\/strong>\u00a0column. For each incoming request, they verify that it\u2019s clear, relevant to the community, and not a duplicate of existing content. If a request is unclear or missing information, we will comment to ask the requester for clarification or additional details (and may @mention the requester to get their attention). They might also make minor edits to the card (formatting, tagging) to ensure it fits the template and standards.<\/li>\n
- Approval or Rejection Decisions:<\/strong>\u00a0Wizards decide which requests get approved. Criteria may include usefulness to the community, alignment with current goals or topics of interest, and feasibility (do we have creators with the necessary skills\/time?). If approved, a wizard moves the card to the Approved column, and updates the card with the reward amount and any notes. If a request is rejected or put on hold, one of us moves it to\u00a0Closed\/Rejected<\/strong>\u00a0(or leaves it in New Request with an explanatory comment) and provides a polite explanation. For example: “Rejected \u2013 a similar tutorial already exists” or “On hold \u2013 awaiting more details from requester.”<\/li>\n
- Setting Reward Amounts:<\/strong>\u00a0For each approved request, Wizards determine an appropriate\u00a0reward in GNC<\/strong>\u00a0for the task, based on its complexity and the effort required. They should be fair and perhaps follow a guideline or budget. (For instance, a simple graphic might have a smaller reward than a full video tutorial.) The reward is clearly noted on the card so that any potential Content Creator knows the incentive upfront. All rewards are paid only after successful completion and approval of the content.<\/li>\n
- Assigning Tasks to Creators:<\/strong>\u00a0Wizards oversee the assignment of tasks to Content Creators. They ensure that only\u00a0approved Content Creators<\/strong>\u00a0take on tasks. When a creator volunteers for a task via a comment, a\u00a0wizard\u00a0will typically confirm by assigning that creator: they might reply “Okay, @CreatorName you\u2019ve got it,” then\u00a0move the card to In Progress<\/em>\u00a0and update the “Assigned Content Creator” field. If multiple creators offer, Wizards decide who to assign \u2013 they might consider the first volunteer, or choose based on expertise or current workload. (Wizards aim to be fair and transparent in these choices, possibly explaining in a comment like “Assigning to @Alice as she has relevant design experience. @Bob, we\u2019ll have more tasks coming up!”). Sometimes, for high-priority tasks, Wizards might directly approach a specific creator they know is best suited or available.<\/li>\n
- Supervising Work in Progress:<\/strong>\u00a0While content is being created, Wizards keep an eye on the\u00a0Assigned & In Progress<\/strong>\u00a0column. They check that progress updates are coming in and intervene if a card seems stalled. If a deadline is looming or past, a Wizard will follow up with the Content Creator via comment or direct message. In case a Content Creator becomes unresponsive or cannot complete the task, Wizards have to make a call: either extend the deadline, find another creator to take over (reassign the card), or in rare cases, move the card back to Approved (open for others) or Closed if it\u2019s not going to be done. Their role is to keep things moving toward completion.<\/li>\n
- Reviewing and Quality Control:<\/strong>\u00a0When a card is in\u00a0Ready for Review<\/strong>, Wizards (often the one who approved\/assigned it, or another with relevant knowledge) meticulously review the submitted content. They verify that it fulfills the request, is factually correct, and meets quality standards. If the content is good, they approve it. If it needs work, they compile clear, actionable feedback in the comments. Wizards might also loop in the original requester for their input if needed (“@RequesterName, does this meet what you were looking for?”). They ensure that any feedback is constructive and that the Content Creator knows exactly what to address in a revision. This may involve multiple review iterations, and Wizards coordinate this efficiently.<\/li>\n
- Approving Completion:<\/strong>\u00a0Once satisfied with the content, a Wizard will mark the task as completed. They move the card to\u00a0Completed<\/strong>\u00a0and update the status in the description (as per the template) to indicate approval. They also make sure the content is delivered to wherever it needs to go. For example, if the asset is a video that should be published on an official channel, a Wizard might handle that upload or coordinate with the team responsible. If it\u2019s an infographic, they might add it to the community wiki or resources page. While this step might be outside the board\u2019s direct scope, noting the outcome (where the content ended up) on the card is good practice.<\/li>\n
- Reward Distribution:<\/strong>\u00a0Wizards are responsible for distributing the promised\u00a0GNC rewards<\/strong>\u00a0to Content Creators once a task is completed. This involves initiating the token transfer from the community treasury or a rewards wallet. Wizards should follow whatever internal procedure exists for payments (which might require a second sign-off or a multi-sig transaction if it’s a DAO-like setup). Once done, they update the card (in the Completed template) with confirmation of payment (and possibly transaction details for transparency). This closes the loop, showing that the creator was compensated as agreed.<\/li>\n
- Board Maintenance and Oversight:<\/strong>\u00a0Beyond individual tasks, Wizards maintain the board\u2019s overall health. They ensure tags are used consistently and might refine tag categories over time. They archive or clean up old cards if the Completed column becomes too large (maybe moving very old completed cards to an archive board or changing their visibility). They also update any instructions on the board if processes change. For example, if a new type of asset becomes common (say, interactive demos), they might add a tag for it and mention it in the guidelines. Wizards could also periodically summarize board activity to the wider community (e.g., “Monthly update: 5 assets created and delivered this month!”), showcasing the productive output of the system.<\/li>\n
- Handling Conflicts or Issues:<\/strong>\u00a0If any conflicts arise (e.g., a requester is unhappy with the final content, or a creator disputes the amount of reward given), Wizards mediate and resolve the issue. They will refer to these guidelines and community rules. For instance, if a requester feels their request wasn\u2019t fully met even after revisions, a Wizard could discuss possible remedies (perhaps scheduling a follow-up asset or adjusting the content). If a Content Creator feels under-rewarded due to extra work, Wizards can consider a bonus or at least note the feedback for future reward calculations. The goal is to keep all parties satisfied and maintain a spirit of fairness.<\/li>\n<\/ul>\n
In summary, Wizards act as project managers and quality control for the Assets Request Board. Their active involvement at each stage (from vetting requests to final payout) is key to making the pipeline work. They ensure that the board remains a trusted system where good content is created efficiently and everyone\u2019s contributions are respected and rewarded.<\/p>\n
Tags and Filters for Asset Categorization<\/h2>\n
To keep the Assets Request Board organized and easily navigable, we use tags (labels)<\/strong> on cards to categorize each request. Tags help filter and search for specific types of tasks or content. Here are the recommended tag categories and examples of each:<\/p>\nAsset Type:<\/code> Tag the format of the content. Examples: Graphic<\/code>, Video<\/code>, Article<\/code>, Tutorial<\/code>, Infographic<\/code>, Animation<\/code>, etc. This allows anyone to quickly see what form the requested asset will take. (For instance, a card tagged <\/em> Video<\/code> vs. one tagged Infographic<\/code> might be picked up by different creators specialized in those areas.)<\/p>\nDifficulty\/Level:<\/code> Tag the intended audience skill level or complexity. Common tags: Beginner<\/code>, Intermediate<\/code>, Advanced<\/code>. Use Beginner<\/code> for content that explains basic concepts or is for newcomers; use Advanced<\/code> for in-depth or technical content targeting experienced users. These tags help content creators gauge if a task aligns with their ability to simplify or elaborate on topics appropriately.<\/p>\nLanguage:<\/code> If the community is multi-lingual, tag the language of the content. Examples: English<\/code>, Spanish<\/code>, Polish<\/code>, Mandarin<\/code>, etc. A request might even have multiple language tags if versions in different languages are needed. Language tags help in assigning creators who are fluent in those languages, and they allow community members to filter requests or completed assets by language.<\/p>\nTopic\/Category:<\/code> (Optional, but very useful) Tag the subject matter or domain of the content. Examples might include GridScript<\/code> (if the content relates to GRIDNET’s scripting language), Wallet<\/code>, Governance<\/code>, DeFi<\/code>, Security<\/code>, Tutorial-Series<\/code>, etc. These tags will depend on common themes in the GRIDNET ecosystem. Topic tags group related content together and help creators with domain expertise find tasks that suit them.<\/p>\nPriority\/Urgency:<\/code> If needed, use tags like Urgent<\/code> or High Priority<\/code> for tasks that have a time constraint or are particularly important. For example, a tutorial needed before an upcoming event or a graphic for an imminent announcement might be tagged urgent. This signals to creators that a task should be handled ASAP. (Wizards will assign these sparingly to keep everything from seeming high priority.)<\/p>\nUsing tags:<\/strong> Requesters are encouraged to add relevant tags when creating the card (Deck app allows adding labels to cards). Wizards will review tags upon approval and adjust for consistency (they might have a standard set of label colors\/names). Content Creators can also suggest adding a tag if they see something missing or if the scope changes. On the Deck board, tags will appear as colored labels on each card, and users can filter the view by tag (for example, view only Graphic<\/code> tasks or only Completed<\/code> tasks tagged Beginner<\/code> to find intro-level materials).<\/p>\nHaving a robust tagging system makes it much easier to navigate the board. For instance:<\/p>\n
\n- A new Content Creator who specializes in video might filter by the
Video<\/code> tag to see all video requests.<\/li>\n- A community member looking for resources might filter the Completed column by
Tutorial<\/code> and Beginner<\/code> tags to find all beginner tutorials that have been made.<\/li>\n- Wizards could use tags to generate reports (e.g., how many
Spanish<\/code> content pieces have been requested\/completed).<\/li>\n<\/ul>\nTags are an optional organizational tool, but when used consistently they greatly enhance the usability of the board.<\/p>\n
Communication and Collaboration Expectations<\/h2>\n
Effective communication is crucial for a collaborative board like this. We emphasize transparency and openness so that everyone (requesters, creators, Wizards, and the wider community) can follow along. Here’s what is expected:<\/p>\n
\n- Use Deck Comments as the Primary Channel:<\/strong> Each card’s comment thread is the main channel for discussing that specific task. All significant interactions \u2013 clarifying questions, status updates, feedback, decisions \u2013 should happen in the comments<\/strong>. This keeps a written record tied to the task, which is helpful for accountability and for anyone later reviewing what was done. It also means information isn’t lost in private chats and everyone involved with the task stays informed.<\/li>\n
![\"\"](\"https:\/\/gridnet.org\/wpp\/wp-content\/uploads\/2025\/04\/25.png\")
<\/p>\n![\"\"](\"https:\/\/gridnet.org\/wpp\/wp-content\/uploads\/2025\/04\/Screenshot-2025-04-25-at-21.23.01.png\")
<\/p>\n![\"\"](\"https:\/\/gridnet.org\/wpp\/wp-content\/uploads\/2025\/04\/Screenshot-2025-04-25-at-21.23.41.png\")
<\/p>\n