You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

Development Logistics: 

Do we want to create the HTML in GitHub?  Yes, public can read, contributor access only 

    • use git clone for backup of repository



  • Keep the membership local, no remotes (comment: enforced by requirement to attend one Wed. mtg)  (possible exception for known cases?)
  • Job-hunting role is the original focus, but (a) include professional-interest of any sort (b) avoid the term “transition”
    • embrace the term "learn"?
    • NOTE: “transition” is used in the LinkedIn "about us" section, Lora emailed TSSG MGT to find out who can edit that info 3/20
  • Volunteer nature of org
  • add mouse-hover aids, at the least alt strings (use them to differentiate the links that look similar?)
  • don’t publish individuals’ contact info (names ok) – note this may not really hide much from the interested snooper w/ access to LinkedIn etc.
  • L+A principle: attraction not sales pitch / marketing
    • what is L+A?
  • Technologically attractive/up-to-date 
  • Determine web layout style - via pages or on the same page vertically?
  • “cleanliness” is part of attractiveness – we looked at models that distinguished sections of a page by unobtrusive changes in background color & nothing else
    • Example of attractive and vertical = Confluence website https://www.atlassian.com/software/confluence or others... list___ 
    • Example of attractive and horizontal (meaning multiple pages) = 
    • AND less is more, lead with just enough to pique interest - too much is a turn-off at the start, people move on from new things quickly
  • RESPONSIVE is a top priority
    • Website needs to work well on mobile, tablet/laptop and desktop screen devices
  • Everyone is fond of the claim that We help you answer the question “What have you been doing lately?” – should find a way to include it – is in the Acton Networkers presentation & was in the original mission statement (where’s that?)
    • NOTE: we should comb our documentation for mission/vision statements already published
      • Added the Linkedin Group "about us" section to the Project Parameters page 
  • Build an essel bill board for Acton and Hopkinton Networking
  • Use word clusters or word-cloud? esp. for the technologies
  • Stress variety – including roles (try on hats you haven’t done in the workplace)
  • Stress Outlet?

Some ideas broke down into just implementation details, perhaps to address at once in v.0 while we work on real thing:

TSSG.TECH is a non-secure HTTP site, and we do NOT need it to move into being a secure site.

  • this issue came up because Norm could not login - the note in the address bar was a red lock and "this is not a secure site" - he had an app loaded that blocked any sites that were not secure


Issues about current TSSG.TECH site: 

  • Fix the scattering of panels on page 2
  • resolve the confusing 2 rows of similar-looking graphics with different links – in parallel, decide which link to a page vs. a [labeled] section on a page
    •  I'd rather start this project design from scratch - no need to resolve or fix anything... (Lora 3/19)

 List of potential customers “(as defined in current website)”:

  • CUSTOMERS, anyone interested in any aspect of the software development life cycle
  • CUSTOMERS, software developers
  • CUSTOMERS, web designers
  • CUSTOMERS, project managers
  • CUSTOMERS, support persons
  • CUSTOMERS, quality people
  • CUSTOMERS, agile people
  • CUSTOMERS, scrum masters
  • CUSTOMERS, product owners
  • CUSTOMERS, those interested in learning about these and other roles

and some statements for consideration (I’ll forward them to Thursday’s invitee list) from which I’ll extract here some purposes for viewing site / joining TSSG:

  • PURPOSE TO VIEW TSSG.TECH SITE, between jobs - see if TSSG is doing something I want to do
  • PURPOSE TO VIEW TSSG.TECH SITE, software engineer - learn new programming skills
  • PURPOSE TO VIEW TSSG.TECH SITE, between jobs - break up my job search with hands-on development
  • PURPOSE TO VIEW TSSG.TECH SITE, between jobs - show that you are still active in roles
  • PURPOSE TO VIEW TSSG.TECH SITE, UX designer between contracts - showcase my skills to a prospective employer

NOTE: at least once a month, we should read the on-boarding documentation & compare w/ the site

NOTE: https://www.atlassian.com/software/confluence/jira-integration

review Andy (VOICE OF THE CUSTOMER) inputs (including what NOT to do) & maybe add

New: down the line we need the customer to decide whether to scatter logos (&c) across the "Technologies" pages

   (and BTW some other decisions about those pp)


--- Don't want to interrupt your list, the following are comments:  

  • Determine web layout style - via pages or on the same page vertically?
  • I was looking at a youtube video on creating CSS grids - that's a really easy way to make reposnsive design. Let's go over that more... we may want to go the hard way with bootstrap... different images for different screen sizes, text wraps to screen etc.
  • I have a client that I many do a website for - I'm making an exception for him, I don't do websites. I've done it for a few clients too - just because the prices for web developers was out of budget for them. BTW: with very good rerason... this isn't hight school kids making websites anymore, it's far more complicated and sophisticated looking than in the past.
  • Make website work on mobile and standard devices. responsive design
  • Create some reporting format in JIRA with a date feature so we can view what tickets are closed, in-process and pending - that is brought back as a link in CONFLUENCE. 
    • The Confluence Page would be at the same level as Meeting Notes.


  • No labels