Talk:Web and Social Media Pages

This page is intended to serve several purposes:

1. Serve as an inventory of all social media accounts, web pages, and related resources that need to be maintained.
2. Outline the purpose for each resource, the intended audience, and suggested update cycle, etc. in order to better understand how each resource fits into the overall social media plan for sandbox.
3. Identify the key person or people who maintain access to these resources
4. Identify the individuals who currently have access to change these resources

---

Any questions about what should be on this page & how it is to be used?

Gfc (talk) 21:40, 20 November 2019 (UTC)

---

notes for October 2024 Revision: (copied from main page and revised. Changes marked in red comments marked in red italic)

Overview of Sandbox web resources:

Primary web pages and social media accounts used by Sandbox

New Sandbox web address url sandbox.umd.edu

• We need to plan how to best use this address and (assuming we keep sandbox.iribe.umd.edu) what goes where. For example, we could use sandbox.iribe.umd.edu for external-facing sites and use sandbox.umd.edu for internal-facing sites such as our wiki, tool reservation forms, tool checkout pages, etc.

Sandbox UMD web page (sandbox.iribe.umd.edu )

• This is relatively static, changing rarely. Ideally we'll embed twitter and Instagram feeds in this page but for now, they are linked.

TerpLink

• TerpLink is the UMD directory of student organizations. Used to introduce students to Sandbox. May be useful for announcing events. TerpLink is new as of Fall 2020 so we need to experiment with it to better learn other uses.

Facebook

• Public announcements for the general community. Updated more frequently than the website, but not as frequently as the Twitter.

Twitter

• Frequent updates. Best place to get high-level information about what's happening in Sandbox!

Should we stop using Twitter? Or use it just to cross post from more important sites such as Instagram?

Instagram

• Frequent updates, ideal place to feature short video clips. We haven't done a good job using Instagram.

Slack

• Used by managers and staff to discuss issues of internal importance, scheduling issues, broken equipment, etc.

Should we stop using Slack? Do we need to replace it with something like Notion? Because we have free version of Slack, old posts dissapear. Also, the calendar plug-in we were using no longer works.

Comprehensive (hopefully) List of Sandbox-Related Web Pages & Social Media Accounts

Sandbox has several web pages and social media accounts:

Social Media and Promotional

Sandbox UMD web page

• description: Web page on UMD CS official web site.
• audience: UMD Community, primarily students, faculty, staff. Possibly alumni, local residents, and other maker spaces.
• optimal update frequency: Monthly or when events occur.
• url: sandbox.iribe.umd.edu
• managed by (umd email address): gfc
• credentials managed by (person or vault location): (currently in transition contact gordon for info)
• individuals with access to update / make changes: (currently in transition contact gordon for info)

TerpLink

• description: TerpLink is the UMD directory of student organizations
• audience: UMD Students. (secondary: others in UMD Community)
• optimal update frequency: update for all planned events and announcements, check site daily for new student requests and messages.
• url: terplink.umd.edu/organization/sandbox
• managed by (umd email address): gfc
• credentials managed by (person or vault location): self-managed, for problems work with SORC

Facebook

• description: Public announcements for the general community. Updated more frequently than the website, but not as frequently as the Twitter.
• audience: General community
• optimal update frequency: Monthly
• url: facebook.com/SandboxUMD/
• managed by (umd email address): gfc
• credentials managed by (person or vault location): ?

Twitter

• description: Frequent updates. Best place to get high-level information about what's happening in Sandbox!
• audience: General public, and anybody interested in the space.
• optimal update frequency: 2-3 times per week updates on the space. Let people connect to the space if they can't be there in person. More detailed information should be conveyed elsewhere.
• url: @sandboxumd
• managed by (umd email address): gfc
• credentials managed by (person or vault location): only one login credential reset via email and third party authentication (TPA). (TPA emails sent to sandboxUMD@gmail.com TPA texts sent to Nate)

Instagram

• description: ?
• audience: ?
• optimal update frequency:
• url: https://www.instagram.com/sandbox_at_umd/
• managed by (email address): sandboxUMD (gmail)
• credentials managed by (person or vault location): only one login credential reset via email and third party authentication (TPA). (TPA emails sent to sandboxUMD@gmail.com)

Facebook (Internal Private Group for Managers)

• description: ? Uncertain if this will continue or be replaced by Slack
• audience: ?
• optimal update frequency:
• url: https://www.facebook.com/groups/432758753591002/
• managed by (email address): ?
• credentials managed by (person or vault location): ?

YouTube

• description: ?
• audience: ?
• optimal update frequency:
• url: ?
• managed by (email address): gfc
• credentials managed by (person or vault location): ?

Campus Makerspace Initiative (MSI)

MSI

Operational Resources Used by our Community, Managers, and Staff

Twitter (door open / close)

• description: Twitterbot tweets whenever the door is opened or closed. Allows makers to know if the Sandbox is open for business!
• audience: People interested in coming to the space
• optimal update frequency: Multiple times per day
• url: @sandboxDoor

UMD Canvas Training Modules

• description: Safety & Basic Usage Training for users of Sandbox
• audience: Sandbox users /potential users.
• optimal update frequency: As needed for new tools & safety requirements.
• url: myelms.umd.edu.
  • (testing & beta: https://umd.test.instructure.com/ https://umd.beta.instructure.com/)
  • (API testing: https://umd.test.instructure.com/doc/api/live#!
• managed by (email address):
  • Gordon (gfc@umd.edu)
  • Nate (nself1@umd.edu)
• credentials managed by (person or vault location): Tied to CAS / UMD logins

UMD Canvas Site For Managers

• description: Safety & Basic Usage Training for users of Sandbox
• audience: Sandbox users /potential users.
• optimal update frequency: As needed for new tools & safety requirements.
• url: myelms.umd.edu.
  • (testing & beta: https://umd.test.instructure.com/ https://umd.beta.instructure.com/)
  • (API testing: https://umd.test.instructure.com/doc/api/live#!
• managed by (email address):
  • Gordon (gfc@umd.edu)
  • Nate (nself1@umd.edu)
• credentials managed by (person or vault location): Tied to CAS / UMD logins

Sandbox Wiki

• description: The instruction book for Sandbox.
• audience: Staff, managers, and users of Sandbox.
• optimal update frequency: As needed / daily / weekly
• url: https://wiki.umiacs.umd.edu/sandbox
• managed by (email address): Gordon (gfc@umd.edu) Nate (nself1@umd.edu) Jacob (jacooper@terpmail.umd.edu)
• credentials managed by (person or vault location): Any wiki user in group administrators

Slack

• description: Communications tool used by Sandbox managers and staff.
• audience: Internal management
• optimal update frequency: As needed, multiple times per day
• url: Dozuki
• managed by (email address): ?
• credentials managed by (CAS authentication): ?

Dozuki

• description: System for creating work instructions, initial planned use if for internal instructions for managers and staff of Sandbox (e.g. How to clean laser cutter or start-of-shift procedures)?
• audience: Managers and Staff
• optimal update frequency: Only as needed when new procedures are added or existing procedures are modified.
• url: Dozuki
• managed by (email address): Sandbox staff
• credentials managed by (CAS authentication): TBD

ter.ps url shortener

go.umd url shortener links (gfc account)

go.umd.edu/SB-Manager-App https://docs.google.com/forms/d/e/1FAIpQLSdcGljtC0r0yWlIvTTVmZra6kksjRMgVXUZjT9eAOLmsFQ4Lw/viewform

go.umd.edu/SandboxWiki https://wiki.umiacs.umd.edu/sandbox/index.php/Main_Page

go.umd.edu/Learn2Make https://wiki.umiacs.umd.edu/sandbox/index.php/Main_Page

---

Website sandbox.iribe.umd.edu

Gfc (talk) 23:08, 27 September 2024 (UTC) Updated sandbox website to fix broken link for manager application form.

updating site:

The sandbox site is hosted using UMIACS Object Store (https://wiki.umiacs.umd.edu/umiacs/index.php/OBJ)

Editors will need a umiacs login and then need to be added to the sandbox group

---

MSI Site make.umd.edu

Here’s how to add/update your space after you have access:

Log in to the MSI website at https://makerspace.umd.edu/wp-admin using the UMD CAS button.

Click Makerspaces in the left menu.

Either click the name of your makerspace in the list or click the New Makerspace button at the top of the page.

Fill out or update the form fields as appropriate. Required fields are marked with a red asterisk.

Add or update the Featured image on the right side of the edit screen. Although WordPress will allow you to save without a featured image set, please make sure you add one as the listing will not look right without one. Try to keep the image size small (500-1000px width). It will crop automagically.

Hit Publish or Update.

Your makerspace is immediately live on the website!