• Stand-up:
    • Joel has converted current TSSG.Tech into Bootstrap (hosted locally on his system)
      • Demo later in meeting
    • Ken: nothing new, following along with the email threads
    • Paul: working on Docker for Windows stuff, hope to have something to show group soon
    • Tyler: nothing new for web project at this time
    • Jim: is having internet problems.
      • Reminder: can NOT send to Google Group unless logged in as the account that is registered with the group
    • Lora said she will be running late
  • Joel shared a website that reviews 10 popular Android emulators for Windows
  • Joel's demo of Bootstrap:
    • Starting point: copy current TSSG.Tech with Bootstrap
    • Only has a few pages converted so far, no style sheets yet
    • Joel has questions for group
    • Currently no nav bar, which is what bootstrap uses for navigation
    • Testimonials will become "Reviews of TSSG on Meetup.com"
    • In Bootstrap, main information below the header is the Jumbotron
    • Paul reminded the group that the Laravel effort used Bootstrap
      • Ralph had hosted this project when it was done back in 2017
    • Mobile Friendly (aka Simple HTML) site was changed to version 3 - see shared links, replaced with the Production (aka Original) Site 
    • Should we keep the buttons on the bottom or have a nav bar on the top as is typical for a bootstrap site?
    • Need to keep in mind with these discussions that we are currently working on the MVP site that will be public facing while we do the big site redesign.
      • Need to separate what is for MVP and what is for the final project release
    • The bootstrap demo opens new pages in the same tab

  • Ralph pointed the team to a wire frame tool called Pencil at https://pencil.evolus.vn/
  • Has the team decided that we will go with Bootstrap?
    • Is our site too simple to use Bootstrap on it?
      • Would it be easier to stick with using HTML and CSS?
      • Would CSS Grid and/or Flexbox be better for doing responsive design?
    • How easy will it be for someone new on the team to maintain and update the web site once the current developers leave?
    • Can NOT depend on all this information being stored in Confluence
    • 6 yes to use bootstrap, 1 abstain (don't care)
    • We may use Bootstrap for the MVP site, and will revisit this question for the main project
  • Ralph wants to form a project to update the TSSG infrastructure so that if his Confluence site suddenly goes away, we will not lose valuable information
    • Longevity Project
    • Bring this up at Wednesday meeting as this is TSSG overall, not just Web Team
  • CSS3 is NOT supported by all browsers   (to me, this sounds like a deal breaker if it's true - Lora)
    • CSS is being updated faster than browsers are being updated to support it
    • Different levels of CSS are supported by different browsers
  • Ralph provided a list of possible technologies for post MVP release:
    • Bootsrap
    • CSS3 Grid   (if NOT supported by all browsers, this sounds like a deal breaker - define ALL, if 90+% supported, may be ok - Lora)
    • Angular
    • Material Design
    • Flexbox
    • Combination of multiple choices above
  • We still need decisions on design, look & feel, navigation, content on each page for the post MVP release
  • Next steps:
    • Need a minimal number of stories for the MVP website
    • Need sprint planning meeting to choose stories to do in the first sprint
    • End result is the MVP website that is shown to the customer (TSSG general meeting)
  • Can we just let Joel finish his bootstrap conversion of Lora's TSSG.Tech and call that the MVP site
    • That lets us focus our stories on what we want post-MVP
    • At this point, a wire frame is not needed for MVP website
  • Story workflow:
    • Start by putting it in Confluence as a Suggested User Story
    • Team works out details of the story
    • Once ready, story is moved into Jira will it can be assigned and worked on  (this contradicts prior item on to-do list - to move the stories into Jira as Issues)
  • For MVP website, we want to undo the black-and-white-only change.
    • When presented at main meeting, people did not like the changed site
    • We want simple, single color scheme - most likely Blue to match logo  (and including multiple shades of gray? Full color pictures?)
    • The original site would not let us insert details about each teams, so going back to that is not a good choice (ref version 3) 
    • TSSG.Tech is NOT a practice site, it is the production site -- what the public sees.  We need to keep it stable while we develop the new site
  • Lora will restore the original version of the TSSG.Tech site  (done at meeting)
    • Once ready, we will put the MVP version on this site
    • An understanding has developed that NO changes will be made to the live site except after sprint review by everyone



  • No labels