June 2016 Web Design Meeting Report

At our June session, we followed up on the May meeting with some additional notes on using Google Forms.

The main topic was Microsoft Sway. Sway is a cloud-based application that according to Microsoft makes it quick and easy to create and share polished, interactive reports, presentations, personal stories, and more.

We watched a video on Sway called Learn Microsoft Sway – New! 2016 Tutorial. We also looked at a Sway that I created, and we created a Sway of our own to get the idea of how the design can be changed on the fly.

There are plenty of other videos along with examples at the Sway website.

Note that a Microsoft account is required to create a Sway.

June Web Design SIG — Microsoft Sway

Q: Why did the programmer quit her job?
A: Because she didn’t get arrays.

Speaking of quitting, this month is the last meeting of PACS until September. Our SIG will go out with a look at Microsoft Sway, a web-based application for creating presentations emphasizing multimedia. Sway has not received a lot of attention, but it could be a good solution for those times when put together a site quickly and easily.

We will also do a couple of follow ups to last month’s discussion of Google Forms, and we will look ahead to next season.

May 2016 Web Design Meeting Report

At our May meeting, we looked at using Google Forms for a free and effective way to add data gathering to a site. The system connects a form with a Google Sheet through Google Drive, so a Gmail account is required.

We watched two instructional videos based on using Google Forms in a classroom situation:

Some of the settings described in these videos depend on an educational account with Google, but most of what is described is generally applicable.

When searching for videos or tutorials on Google Forms, watch the dates and be sure the instructions relate to the new version of Google Forms, not the older version that is being replaced.

May Web Design SIG — Google Forms

Q: Why did the web developer add body {padding-top: 1000px;} to his Facebook page?
A: Because he wanted to keep a low profile.

The topic for our next meeting will be Google Forms. I recently needed to do a quick form for a site, and I used a Google Form quite successfully. We will look at how they work and build one on the fly as a test. Depending on time, we will look at some more advanced examples of styling forms, and anything else that comes up.

And please note: If you want to raise your profile, don’t rely on padding-top. Your chance to provide leadership for PACS is coming up shortly at our annual meeting in June. Please consider running for a position as Director. The qualifications are spelled out in our bylaws accessible from the About tab of any PACSnet.org page. Blank nominating petitions are available there also and will be at the member table in May and June. If you have any questions, ask the president or any other board member.

April 2016 Web Design Meeting Report

At the April meeting, we talked about some issues with a WordPress template that I have been using, with emphasis on good HTML and CSS practices. We then looked at a new browser called Vivaldi, from the same developer who started Opera. Member Jerry Greene forwarded this article on Vivaldi from the How-To Geek site.

And please remember: Your chance to provide leadership for PACS is coming up shortly at our annual meeting in June. Please consider running for a position as Director. The qualifications are spelled out in our bylaws accessible from the About tab of any PACSnet.org page. Blank nominating petitions are available there also and will be at the member table in May and June. If you have any questions, ask the president or any other board member.

April 2016 Web Design SIG – C’mon, Man!

Q: Why did the web developer send a few extra bucks to his hosting provider?
A: Because he heard that he should always tip his server.

We’ll serve up some good tips at the April meeting of the Web Design SIG. Our topic will be “C’mon, Man!” I’ll explain why, but it will involve my experiences using a WordPress theme. It won’t be a WordPress session — we have a SIG for that — but we will look at how a good handle on HTML and CSS can be helpful in working with a theme.

Depending on time, we will also look at a recent online form I developed using Google Forms and maybe check out a new browser.

And please note: Your chance to provide leadership for PACS is coming up shortly at our annual meeting in June. Please consider running for a position as Director. The qualifications are spelled out in our bylaws accessible from the About tab of any PACSnet.org page. Blank nominating petitions are available there also and will be at the member table in April, May and June. If you have any questions, ask the president or any other board member.

March 2016 Web Design SIG – The Results

Q: When Apple employees die, do their lives HTML5 in front of their eyes?

We’ll leave that answer to another SIG. At our SIG this month, member Jerry Greene will wrap up his series of presentations on web development tools that he uses. We will see the results of the test project that we looked at in previous meetings — properly formatted printouts from a membership database, with on the fly selection of items to be included. It is something that would be important to anyone managing a group’s membership list.

There are sure to be some new ideas Flash in your mind.

The CSS page-break Property

As a follow up to our last meeting, member Jerry Green put together a cheat sheet on the “page-break” property from information at W3Schools. There are now 3 types:

page-break-after Property:
CSS Syntax
page-break-after: auto|always|avoid|left|right|initial|inherit;
Definition and Usage
The page-break-after property sets whether a page break should occur AFTER a specified element.

page-break-before Property:
CSS Syntax
page-break-before: auto|always|avoid|left|right|initial|inherit;
Definition and Usage
The page-break-before property sets whether a page break should occur BEFORE a specified element.

page-break-inside Property:
CSS Syntax
page-break-inside: auto|avoid|initial|inherit;
Definition and Usage
The page-break-inside property sets whether a page break is allowed inside a specified element.