pods-framework / pods-support Goto Github PK

LOVE this example from Give with VERY Directed Focus

TaskList for New Landing Page for support.pods.io:

• Search Box for Documentation
• Bug Report route to GitHub
• Route to Chat with Current Support Hours and Online Agents
• Open a Ticket for help form with the sign off provided (basically a Support 'dashboard') that forces them to think before they submit.
  

This is for tracking our Projects that we offer support for, documentation and github links and links to WordPress projects & forum.

Will also give us a place to track the roadmap and releases for each project.

• Create Projects & RoadMaps structure
• Create Table Template for front Dashboard
• Publish all projects
• Create Single Project Template with related Road Map
• Create Single Road Map Template linked Project
• Need Rewrite (maybe Pods Pages?) to map /project/{@project}/roadmap/ to current full road map for specific project
• Publish existing and big history roadmaps

Write a quick function that determine the Day of Week and displays the current Support Hours with a link to Support Policy and Hours.

We could use same function to tailor the display/details on the Chat Window and Landing Page

Also create a simpler one for the collapsed menu that is just the logo with SUPPORT, same with DOCS and FRIENDS

• Fixed Logo for Support
• 75h Logo: Docs
• 75h Logo: Support
• 75h Logo: Friends

Hey. I'm stuck in a logical/syntax pit, wondering if any of you could point me in the right direction.

Creating a template for a CPT Adresse, I'm referencing the field adresseid, and I want to fetch all materiel from another CPT, with that adresseid. If use a pods shortcode in the template, with a fixed id (in this case 56329), things works as expected, but if I attempt to use the magic tag {@adresseid} instead, it does not work.

Snippet of my template with fixed and variable id below:

`

AdresseID (eg 56329):{@adresseid}

Pods shortcode with fixed adresseid works:

Pods shortcode referencing magic tag does not work:

Any suggestions? The themes I expect to use, would allow me to insert a piece of PHP code instead, if that would make things easier, but I've have very limited knowledge on PHP and I have only got a few days to get this to work..

Any help would be greatly appreciated

• Add Support for Logged in Users
• Load async
• Load Network wide

https://docs.small.chat/threads

and make sure we put scripts into the footer and they are loaded async

Tracking just the items that are needed to make these the official 'support' link:

• Support Policy Updated
• ALL projects on WordPress.org linking to THIS Support Policy & Chat
• Footers (sitewide finished)
• Chat Etiquette/FAQ Finished
• Search the Docs input/autocomplete from docs.pods.io/search/ (is this even possible?)

Create a Slack - HelpScout - Zap Integration to be able to turn on/off during office hours. Need to make sure we have the integration slot available. Flow for the process would be:

• When enabled, it will watch for NEW conversations started in #support
• Reply to new conversation in a thread with notice that it is after hours (link to support policy and support hours), welcome them to our Slack Chat and let them know we're logging their question.
• Open a New Conversation in HelpScout registering their email address for the User and the ticket. Get the Ticket number.
• Reply with 'We have created a ticket in our Support System for your question. The link is here:" provide HelpScout Link. Our Support Staff has been alerted and you should get a response back during our regular support hours.'

http://pods.io/forums/topic/advice-for-getting-help-quickly-and-efficiently/

Should explain how our chat works, give easy screenshot examples and purpose of many of our common channels.

The goal would be to import the existing forums in a read-only format as we determine what code by post or information by post needs to be migrated into docs. This would also maintain SEO connectivity to our current search forums, the goal would be for the forum post to re-direct them into our newer support channels and also provide the 'Did you find this helpful?' form for improving our documentation.