Jump to content

Recommended Posts

SomeDay Tool

I'm working on a series of restricted collaborative websites that are geared towards me working with my clients.  It's a mashup of CRM, Project/Task Management, Tracking, Documentation and Configuration Control features.  Everything is controlled by PW Roles.  It's a tool that allows me to have a great deal of transparency with those I work with.  The objective is to easily know the who, what, when, where and how of whatever is being worked on.  I call it a Collaborative Resource Management System (CRMS) which has the nickname of SomeDay.

I currently have one of these websites for each of my important clients and an additional one to keep track of my internal work. They all use the inherent native power of PW to produce specialized status reports. The websites intentionally incorporates the front-end and back-end of the PW platform.

There is a lot of information stored within this type of website, what I like to call an Information Portal. You are able to easily query a status and get a good view of what's going on. 

This is a long-term ongoing project and I will update this post as more features/capabilities are added.

Meanwhile, here are a few pictures of the CRMS Tool:

Figure 1-3 (The SomeDay Tool for one of my clients)

post-756-0-14703400-1413122818_thumb.png

Figure 1 (Login courtesy of Adrian's Protected Mode Module)

post-756-0-55487200-1413122836_thumb.png

Figure 2, Homepage is a summary of all information

post-756-0-50232000-1413122851_thumb.png

Figure 3, Each item can be clicked on to get to detailed information

Figures 4-7 (My internal SomeDay Tool website)

post-756-0-46343100-1413122865_thumb.png

Figure 4, (Login)

post-756-0-13385100-1413122883_thumb.png

Figure 5, Homepage Summary for my internal work

post-756-0-76746300-1413122915_thumb.png

Figure 6 , Homepage Summary

post-756-0-42151700-1413122930_thumb.png

Figure 7, FlagPages showing Bookmarks

Figures 8-11 (Looking at a Task)

post-756-0-53283400-1413122943_thumb.png

Figure 8, Front-end view

post-756-0-02378600-1413122956_thumb.png

Figure 9, Back-end view (editing)

post-756-0-01951000-1413122972_thumb.png

Figure 10, Place for adding Priority or Statuses

post-756-0-77966000-1413122983_thumb.png

Figure 11, Private Tab only available to selected PW Roles

Figures 12 and 13 (Site Structure)

post-756-0-67964100-1413122996_thumb.png

Figure 12, CRMS structural flow

post-756-0-94849000-1413123009_thumb.png

Figure 13, Tasks and Sub-Tasks can be added to Projects

Figures 14-16 (Customized Reports)

post-756-0-93913800-1413123022_thumb.png

Figure 14, Review all items based on what type of work it is

post-756-0-66203500-1413123035_thumb.png

Figure 15, Review items based on their status

post-756-0-21787800-1413123048_thumb.png

Figure 16, Listing of all items with a status category of Active

That's it for now.

  • Like 12

Share this post


Link to post
Share on other sites

@Charles, this looks awesome! I like the SEO resources idea (the videos, etc.)  ^-^  :rolleyes:

  • Like 1

Share this post


Link to post
Share on other sites

Nico, most of your clients seem to be pretty blurry, but that one fellow is exceptionally bright!

  • Like 4

Share this post


Link to post
Share on other sites

left this one unblurred because everybody knows him anyway (kind of a rockstar) ;)

  • Like 2

Share this post


Link to post
Share on other sites

Nico, most of your clients seem to be pretty blurry, but that one fellow is exceptionally bright!

Well, he had to have had ONE good day.....

@cstevensjr

You have been having fun! I approve.... :)

Share this post


Link to post
Share on other sites

hey nico, i would be very interested in a showcase how you did that :)

  • Like 1

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      The Page Hit Counter module for ProcessWire implements a simple page view counter in backend. Page views of visitors are automatically tracked on defined templates, with monitoring of multiple page views. This gives you a quick overview of how many visitors have read a news or a blog post, for example, without first having to open complex tools such as Google Analytics. This module quickly provides simple information, e.g. for editors. Or, for example, to sort certain news by most page views. For example for "Trending Topics".

       
      Works with ProCache and AdBlockers. With a lightweight tracking code of only ~320 bytes (gzipped). And no code changes necessary! In addition GDPR compliant, since no personal data or IP addresses are stored. Only session cookies are stored without information. 
      In addition, there are some options, for example filtering IP addresses (for CronJobs) and filtering bots, spiders and crawlers. You can also configure the lifetime of the session cookies. Repeated page views are not counted during this period. It is also possible to exclude certain roles from tracking. For example, logged in editors who work on a page are not counted as page views.

      Sort by hits and access page views (hit value)
      Each trackable template has an additional field called phits. For example, you want to output all news sorted by the number of page views.
      // It is assumed that the template, e.g. with the name "news", has been configured for tracking. $news = $pages->find("template=news, sort=-phits"); To output the page views of a tracked page, use:
      echo $page->phits; Example: Tracking a page hit via API and jQuery
      If you want to track a template that does not represent a full page to automatically inject a tracking script, you can define allowed API templates in the module that you can track. Below is an example of how you can track a click on news tag using jQuery. This will allow you to find out which keywords are clicked the most. For example, you can sort and display a tag cloud by the number of hits. Suppose your keywords have the template "news_tag". The template "news_tag" was also configured in the Page Hit Counter Module as a trackable API template.
      Example PHP output of keywords / tags:
      // Required: the data attribute "data-pid" with the ID of the template to be tracked. echo $pages->find("template=news_tag, sort=-phits")->each("<a href='{url}' class='news_tag' data-pid='{id}'>{title}</a>"); Example Tracking Script with jQuery:
      /** * Required: Data attribute "data-pid" with the ID of the news tag template * Required: Send the POST request to the URL "location.pathname.replace(/\/?$/, '/') + 'phcv1'" * Required: The POST parameter "pid" with the ID of the template */ $(function(){ if($('a.news_tag').length > 0) { $('a.news_tag').each(function(){ var tPID = $(this).data("pid"); if(tPID) { $(this).on("click", function(){ $.post(location.pathname.replace(/\/?$/, '/') + 'phcv1', {pid: tPID}); }); } }); } }); So simply every click on a tag is counted. Including all checks as for automatic tracking. Like Bot Filtering, Session Lifetime, etc.
      Notice: Tracking with URL segments
      If the option "Allow URL Segments" is activated on a template, the hits are only counted if the base URL of the page is called. If you want the hit to be counted even when a segment is requested, you MUST configure the segments in the template configuration. How to do this can be found here. If you use dynamic segments, configure them as RegEx. There is currently no other option. The problem is that the Page Hit Counter hooked into the PageNotFound process. If URL segments are allowed but not defined, a 404 is never triggered. This means that the Page Hit Counter cannot be called.
      _______________________________________________________
      Background: This module is the result of a customer requirement, where the editors are overwhelmed with analytics or no tracking tools were allowed to be used. However, a way had to be found to at least count page views in a simple form for evaluations. Furthermore, by using ProCache, a way had to be found to count views of a page without clearing the cache.
      _______________________________________________________
      Pros
      Automatic Page View Tracking Lightweight tracking code, only ~320 bytes (gzipped) No code or frontend changes necessary Works with ProCache! Even if no PHP is executed on the cached page, the tracking works Works with browser AdBlockers No cache triggers (for example, ProCache) are triggered. The cache remains persistent GDPR compliant, session-based cookie only, no personal information Filtering of IPs and bots possible Exclude certain roles from tracking Ability to reset Page Views Works with all admin themes Counter database is created as write-optimized InnoDB API to track events for templates that are not viewable No dependencies on libraries, pure VanillaJS (Automatic tracking script) Works in all modern browsers Pages are sortable by hits Cons
      Only for ProcessWire version 3.0.80 or higher (Requires wireCount()) Only for PHP version 5.6.x or higher No support for Internet Explorer <= version 9 (Because of XMLHttpRequest()) No historical data, just simple summation (Because of GDPR) Segment URLs can only be counted if the segments are defined Planned Features / ToDos
      API access to hit values Since version 1.2.1 Possibility to sort the pages by hits (Request by @Zeka) Since version 1.2.0 Don't track logged in users with certain roles (Request by @wbmnfktr) Since version 1.1.0 Possibility to reset the counter for certain pages or templates (Request by @wbmnfktr) Since version 1.1.0 Better bot filter Since version 1.1.0 Disable session lifetime, don't store cookies to track every page view (Request by @matjazp) Since version 1.2.1 Option to hide the counter in the page tree (Request by @matjazp) Since version 1.2.1 Option to hide the counter in the page tree on certain templates Since version 1.2.1 API to track events for templates that are not viewable Since version 1.2.2 Changelog
      1.2.5
      Bug-Fix: When counting 404 hits, cookies are no longer set. The session lifetime is deactivated for the 404 page Enhancement: Documentation improvement regarding URL segments 1.2.4
      Bug-Fix: Resetting the counters on system pages (e.g. 404) does not work (Reported by wbmnfktr) Bug-Fix: Tracking endpoint is logged as 404 if module "Jumplinks" is installed (Reported by wbmnfktr) Enhancement: Corrected few typos (Merged from Sergio #6 – THX!) 1.2.3
      Bug-Fix: Tracking script triggers 404 if pages are configured without slash (#3) Reported by @maxf5 Enhancement: Reduction of the tracking script size if it's gzipped (~320 bytes) Enhancement: Documentation improvement Enhancement: Corrected few typos 1.2.2
      New feature: API to track events for templates that are not viewable Enhancement: Documentation improvement 1.2.1
      API access to hit values Use $page->phits Bug-Fix: No tracking on welcomepage (Reported by wbmnfktr; Thx to matjazp) Bug-Fix: Tracking script path on subfolders (Reported by matjazp) Bug-Fix: Tracking on pages with status "hidden" Enhancement: Change database engine to InnoDB for phits field Enhancement: Option to disable session lifetime set session lifetime to 0, no cookies Enhancement: Better installation check Enhancement: AJAX Request asyncron Enhancement: Reduction of the tracking script size by ~20% Enhancement: Option to hide the counter in the page tree You can output the counter with the field name "phits" Enhancement: Option to hide the counter in the page tree on certain templates Enhancement: Option for activate general IP validation Enhancement: Reduction of tracking overhead up to ~30ms Enhancement: Better bot list for detection 1.2.0
      New feature: Sort pages by hits – New field phits Migrate old counter data to new field 1.1.0
      New feature: Exclude tracking of certain roles New feature: Reset Page Views Better bot filter and detection 1.0.0
      Initial release Notes
      By default, the page views are stored as INT in the database. This allows a maximum counter value of 4.2 billion views (4,294,967,295) per page. If you need more, change the type to BIGINT directly in the database. But I recommend to use Google Analytics or similar tools if you have such a large number of users.
      _______________________________________________________
      Download GitHub: ProcessWire Page Hit Counter (Version 1.2.5)
      PW Module Directory: ProcessWire Page Hit Counter (Version 1.2.5)
      Install via ProcessWire (Classname): PageHitCounter
      _______________________________________________________
      Update information
      If you have used version 1.2.1 from the DEV branch, please replace it completely with the new master version.
    • By quickjeff
      Hi Guys, I have seen some other threads that talk about this but nothing recent nor in line with what I need. 
       
      I have basically created a page in which I am tracking the number of views. I update the counter which is tied to a field I added to the page's template that I am tracking. The field is hidden from the website admin and only used for this data. 
       
      However, now I need to track it on a daily basis. I am thinking of keeping track of all time view total for 30 days and perhaps saving that and allowing the user to see the page views of last 7 days, each day as a number and then 30 days of data. This way if I want to build in reporting functionality I can. 
       
      What I need help with adding a date to the page_views field but also, knowing how many page_views for today, yesterday, day before etc. 
      Here is what I have so far and its working. Now I need to associate a date with every day. NOT every update of the page_views field. 
      if (!$user->hasRole('superuser')) { $page->page_views += 1; $page->of(false); $page->save('page_views'); $page->of(true); } echo $page->page_views; Any guidance, help, suggestions is absolutely appreciated. 
      Thanks!!!!
    • By dragan
      I'd much rather be in a swimming pool with these temperatures outside, alas.... work 😐
      Has anyone ever built Gantt charts with PW?
      The idea is to visualize somehow who is responsible for which task, when working in a team (e.g. we as agency, client, and a sub-contractor).
      You have some sort of timeline (week-numbers), and can see who is supposed to work on which tasks from date A to date B. There can be time-overlaps, of course.
      Is a Gantt chart the established way to go for such things? Or are there other types of charts / graphics that I'm not aware of?
      So far I came across these JS libraries:
      https://jsganttimproved.github.io/jsgantt-improved/
      https://developers.google.com/chart/interactive/docs/gallery/ganttchart
      https://frappe.io/gantt
      If somebody has experience with such tools, I'd happy to hear your opinions. If you've done something like this with data coming from PW, how did you do it? (not asking for a full-fledged tutorial or even code-snippets, just some pointers). I guess you'd setup something like Pro Table, with text and datepicker fields, then create XML/JSON/JS vars from that.
       
    • By Sabrina
      Hi,  
      I would like to start tracking my website visitors with Leady software. Searched the forum for similar discussion yet did not find the right answer. Could you please tell me how can I add their javascript to my website? Is there any step by step guide available?
      Any help appreciated. 
    • By ksymmons
      Hey guys,
      As the question says, I'd really like to learn about your initial client communication workflows. In other words, what's your process like from the moment you get a request to provide a quote for a website to the moment you actually send the quote?
      My current workflow:
      A client fills out the contact form on my site to request a quote. I review the information provided and send them a Word document questionnaire with a list of questions. I ask for things like project scope, features needed, desired timeline, allocated budget, etc. They fill out the document and send it back to me. I review the information provided and make sure I've got everything I need. I write and send the quote to the client. Client accepts the quote. I send them a contract, get it signed and collect 50% of total payment. I gather some extra information from them, usually just by asking questions via email or by sending them another Word document questionnaire. I start building their site. Lately, I've been thinking about changing this workflow a bit. Currently, my online contact form has three fields: name, email and message. What I'm thinking is, what if I provide a select toggle above my form so that clients can choose between a simple, general enquiries form and a larger form (with all the questions I've got in my Word document) to request a quote? This would allow me to do away with the Word document, and would make this a one-step process.
      The reason why I haven't done this so far is because I'm not sure how good of an idea it is to have a long contact form with say, 10-15 questions. What's your take on this?
      Another thing I'm not entirely happy with is having to send them two questionnaires (steps 2 and 8). The reason why I do this is because I don't want to overwhelm them with lots of questions at the beginning, and also because, to be honest, the questions I ask in the 2nd questionnaire do not really influence pricing, as they have more to do with the nature of their business, their goals with the new site, possible corporate colours they may have, things like that.
      What do you guys think? Does my workflow seem sensible to you? Is it similar to what you do? What would you change?
      Thanks, and sorry for the brick!
      P.S. If some of you guys are willing to share your client questionnaires I would certainly appreciate it.
×
×
  • Create New...