MARLO DEV NOTES
TO DO - NOTES
FORMS (2) SETTINGS 1. General i10C Qs + 2. TPAS info
- For the general I-10 Coalition questions/email FORM, pPlease add Lisa DeForest as the ADOT contact .
- Laura also suggested adding a message directed to media requests, where she would serve as the contact. Thank you, Charla
-
For the FORM: TPAS info we will need to create a group to include the following individuals:
Title-Hover-Text -- EXAMPLE
Here is an exampleThis is the CSS tooltip showing up when you mouse over the link of this type of hover-title capability. The TPASTruck Parking Availability System (TPAS) represents a major first step for the I-10 Coalition bla blaa blaaah.
icons - Article
24 pixels
48 pixels
FAQ feature image (options) 512x
marlo DEV NOTES - 9/2020
1. i10connects - files: G:\Communications\_temp20\i10connects\
0. RESOURCES page https://i10connects.com/truck-parking/tpas-resources
0. FINISH CSS for headings -- notes on vendor colors:
0. LOGO HEADER -- for use in web headers ;
BRIGHT RED
; contrast 5.6; (normal) AA=pass; AAA=fail
RGB: 200 34 48
WEB: #c82230
MEDIUM BLUE
; contrast 4.08; (large) AA=pass; AAA=fail) ; (normal AA=fail)
RGB: 38 131 198
WEB: #2683c6
BRIGHT BLUE
; contrast 2.57 ...fails large AA
RGB: 28 173 228
WEB: #1cade4
NAVY BLUE
RGB: 1 31 93
WEB: #011f5d
0. "Truck Parking" pages? from "menus" PDF -- where is content for this?
0. Why is everything spec'd like this is literature? (Calibri Light?) ; designs / artwork is not designed for web views ; illegibile; not reponsive; ; design assumes large PC screen view (ignores mobile)
0. IMAGES ARE NOT LEGIBLE at web size/quality
; Also, images not designed to be made into RESPONSIVE chunks; makes it hard for ADA req's
; examples:
OVERVIEW page https://i10connects.com/overview-tpas
SCHEDULE page https://i10connects.com/truck-parking/tpas-schedule
; graphic needs to be made into chunks or better yet, be re-designed to work on web pages (incl. phones))
0. Resources page is a whole page with 5 links on it
-- Organization Documents
-- Coalition Meeting Documents
-- Presentations
-- Reports
-- Articles
-- These categories seem random; no clear meaning or context, not mutually exclusive; is this a work in progress?
;...need to know more about the size and scope of document library. (expected web-content maintenance, etc.)
; organization of this doc library (or resources library or whatever it is) needs to work into the future (forever??); How many docs do you have so far? future expectations?
; discuss doc-list structure; i.e. tables or post-based (node teasers - e.g. title + blurb + feature image)
-- Some of these could be attached to their meeting nodes (if we make it that way)
-- 5 photos are arbitrary -- no relation to categories
; we discourage type on images (bad for ADA, bad for responsiveness)
; design assumes large PC screen view (ignores mobile)
; this struture is bad for tweek-ability; hard to edit (worse over time); discourages improvement with this rigid layout
; (bad web design.) (stacking horizontal rectangles = bad)
-- Is the plan to provide links only ? because if resources (links) were done in nodes, they'd have a title and summary (at least), plus attachments -- plus ability to list them many ways.
-- Aren't "presentations" also "meeting docs?"
-- Are Coalition Meetings announced? -- need a calendar?
-- Resources looks like an "Under Construction" site.
0. "Activity" was also intended to house site announcements or bulletins. It could also serve to document the Coalition meetings; A given entry about a meeting could have all meeting documents and presentations attached. -- Makes documents easy to find, and gives them context (meeting minutes, etc).