Sagamore PTA Google Sites notes: Difference between revisions
(Link to site) |
(Reorg lead) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* '''http://test-google-sites.sagamorehillspta.org/''' |
* '''http://test-google-sites.sagamorehillspta.org/''' |
||
'''This site was ''deleted'' 2015-02-17 by [[Dave Barker]] after completing [[Sagamore online goals 2014#Incorporate_test-google-sites_content]], but you can visit an [https://web.archive.org/web/20140904221603/http://test-google-sites.sagamorehillspta.org/ archived snapshot]''' |
|||
==Conclusion== |
|||
We're thinking of ''not'' using Google Sites, and going with Wordpress instead. |
|||
See the comments around the [http://list.9.0ne.org/archive/sagamore.online/2014-March/000192.html 2014-03 Website Discussion], like: |
|||
<blockquote><div> |
|||
[http://test-google-sites.sagamorehillspta.org/ My Google Sites experiment] has ''not'' blown me away. Possible advantages that did ''not'' materialize were: |
|||
* Simplified individual logins (wrecked by how Google Drive assigns file ownership) |
|||
* Google Drive integration (a bit clunky and distracts from real web content) |
|||
Though it is nice for an organization like ours (and the corporate intranets Google Sites mainly serves) that there's really no maintenance. Unlike Wordpress (I think), which does require at least some administering---like updating and upgrading (at least for security, if not because of forced obsolescence)---which is unnecessary with Google Sites. But, like John mentioned, we can probably scrape together enough Wordpress expertise for our needs. |
|||
</div></blockquote> |
|||
==Editing== |
==Editing== |
||
Latest revision as of 17:01, 17 February 2015
In November 2013, Dave Barker started experimenting with Google Sites for future use by the Sagamore Hills PTA, leveraging the free Sagamore Hills PTA Google account.
This site was deleted 2015-02-17 by Dave Barker after completing Sagamore online goals 2014#Incorporate_test-google-sites_content, but you can visit an archived snapshot
Conclusion[edit]
We're thinking of not using Google Sites, and going with Wordpress instead.
See the comments around the 2014-03 Website Discussion, like:
My Google Sites experiment has not blown me away. Possible advantages that did not materialize were:
- Simplified individual logins (wrecked by how Google Drive assigns file ownership)
- Google Drive integration (a bit clunky and distracts from real web content)
Though it is nice for an organization like ours (and the corporate intranets Google Sites mainly serves) that there's really no maintenance. Unlike Wordpress (I think), which does require at least some administering---like updating and upgrading (at least for security, if not because of forced obsolescence)---which is unnecessary with Google Sites. But, like John mentioned, we can probably scrape together enough Wordpress expertise for our needs.
Editing[edit]
- Follow the "Sign in" link at the bottom of the page
- Sign in with
sagamorehillspta@sagamorehillspta.org
Refer to Google Sites Help
Styling[edit]
Styling (theme'ing, skin'ing) Google sites is fairly limited. There's no access to the underlying code (css). Basic customization is available under Manage Site → Themes, Colors, and Fonts.
Major style elements, such as line-height and content width, are defined in the selected Base theme, so it's important to see what they bring.
Dave Barker took a survey of Google Sites base themes Nov 2013, and chose the base theme, Micro Light, because it's almost full width, and has a nice line-height (1.5).
Permissions[edit]
The site is public viewable and editable by sagamorehillspta@sagamorehillspta.org (site permission details).