Field Trip to the Bay Model: June 3

Mark you calendars! All Bay Area STC Chapters are organizing a trip to the Bay Model. The excursion is sponsored by Berkeley and Eastbay Chapters of the STC. It is open to all STC members and friends, but please RSVP, as the size of the guided tour is limited.

When: Saturday, June 3, 2017, 2:00 pm to 5:00. Guided tour at 3:00 pm.

Where: Bay Model in Sausalito, CA

Bay Model Visitor Center
2100 Bridgeway

What: Tour of the Bay Model Visitor Center, which is a fully accessible education center administered by the U.S. Army Corps of Engineers which hosts a working hydraulic model of the San Francisco Bay and Sacramento – San Joaquin River Delta System.

Price: Free admission and parking.

How to Register: Please RSVP to Patrick Lufkin, lufkin@ix.netcom.com

Full Announcement

Visit one of the Bay Area’s hidden treasures, the San Francisco Bay Model in Sausalito.

The Bay Model is a three dimensional, working model capable of simulating the complex tides, currents, and flows of the San Francisco Bay and Delta. Built in 1957 by the U.S. Corps of Engineers to study the region’s water flows, the facility’s research played an important part in our economy, and in efforts to save the Bay.

With its core mission since transferred to computers, the facility now educates the public on the natural and cultural history of the Bay and its watershed.

About the size of two football fields, the facility is a marvel. Pumps move the tides up and down on a regular cycle. The model is fully labeled and detailed. You can circumnavigate the bay and delta, walk over parts of it on bridges, and become aware of out-of-the-way places most of us have never visited.

To educate and inform, the facility marshals a full range of technical communication techniques. It uses dioramas, posters, signage, and more. There is a small theatre. There are audio stations with head phones. And of course, there is the Model itself, and the guided tour we will be taking.

There is also a room dedicated to ship building on the Bay during the “Rosie the Riveter” period of WWII.

The Bay Model is easily accessed from either the Richmond or the Golden Gate Bridge.

 

Tech Writing Students Need Your Help

Every year, we partner with the Technical and Professional Writing program at San Francisco State University to help the students with their research papers. Each student needs to write a white paper on a technical writing trend. As part of this, they need to interview someone knowledgeable about the trend.

If you are interested in volunteering your time to talk to a student about one of these topics, please let us know at info@stc-sf.org.

  • Freemind mind mapping software
  • Lightweight DITA
  • Slack collaboration tool applications for grant writers
  • Content marketing analysis/automation tools
  • Use of video blogs for training
  • Motion in web design

Leveraging Structured Authoring/DITA Techniques When All You Have are Unstructured Tools

For the January 18, 2017, meeting, Monique Semp gave a presentation called “Leveraging Structured Authoring/DITA Techniques When All You Have are Unstructured Tools.” This meeting summary was written by Pete Babb.

The limitations of DITA

Good structured writing has consistency in everything from the order of information to use of terminology to citation style. DITA is a particularly rigid form of structured writing that’s great for content reuse and translation, but because it’s so narrowly focused, it’s not always the best choice for a given writing task and often can be a solution in search of a problem.

DITA tools enforce consistency by making users to comply with certain formats (think of the Task, Concept, and Reference topics), but that same sense of structure can be found in unstructured tools like Microsoft Word, Adobe FrameMaker, and MadCap Flare. This is important because most companies today are not likely to pay for dedicated DITA tools like oXygen.

There are tradeoffs between structured and unstructured writing tools. Structured tools make content reuse, semantic styling, and version control easier, but all of these can be done without them. With diligence and some familiarity with advanced features (and hopefully a good editorial team behind you), you can gain the advantages of structured writing.

These 8 basic steps will help you bring structured writing principles to unstructured tools.

How to apply structure

Step 1: Write topics, not books or chapters
Structured writing is topic-focused, with each document addressing a single topic. These pieces can then be collated into a master document, like a ditamap does with individual DITA docs. In FrameMaker, you’d create a .book file, and then for each “chapter,” add a folder to the .book file. In Microsoft Word, create separate files for every topic and put them in a master doc. Flare, meanwhile, is already set up for topic-based writing, so structure is inherent in the content.

Step 1b: Use consistent styling
No matter what tool you work with, you’ll want to adhere to file naming conventions (“R” for reference, e.g.) and make good templates. This way, all your writing will be consistent, and your files will be easy to find and sort.

Step 2: Write a short description (<shortdesc>)
The <shortdesc> tag in DITA provides an abstract highlighting what will be in the rest of the topic. This can also be accomplished by creating a shortdesc paragraph type in FrameMaker or Word. In Flare, you’ll want to create a CSS class for this paragraph type.

Step 3: Reuse content
Topics can easily be reused in DITA by adding them to multiple ditamaps. This function can be roughly replicated with unstructured tools, but you’ll need to manually track topic use. In FrameMaker, each topic should be a standalone .fm file, which can then be imported as a text insert when needed. In Word, you’ll want to use Master docs, or try tools like thirtysix.net, riverfloe.com to help with reuse. The ability for topics to be included in multiple projects is a standard feature in Flare.

Step 3b: Reusing fragments instead of whole topics
Reusing pieces of a topic instead of the entire topic will typically be done through the use of variables. In FrameMaker, you would customize your system variables, while in Word, you’d use AutoText to define fragments, then use the AutoText field code to enable easy doc updates.

Step 3c: Reuse content, but change it just a little
If you need to slightly change content–for example, “We want to reuse this list of instructions, but we need to change step 3”–you may have to use some workarounds. FrameMaker includes conditional text management, which allows for reuse with changes, and Flare has a conditional text feature that lets you tag content for reuse at multiple levels, including small snippets. In Word, though, you can try to use hidden text as a substitute, but you may need to use third-party tools like SmartDocs or Clio to do it well.

Step 4: Style content sematically
As with DITA, it’s best to avoid hard-coding content style like boldface or italic in unstructured tools and instead create character and paragraph styles: <bold>, <cite>, <uicontrol>, etc. In Flare, you’ll need to create CSS classes to apply styles.

Step 5: Standardize navigation aids
DITA will automatically add navigation text based on tags (i.e. adding “What to do next:” before a <postreq> tag). With unstructured tools, you’ll need to create paragraph styles to automatically include such lead-ins. You can then mimic the mandatory styling of DITA by using these styles in templates.

Step 6: Add metadata
Most unstructured tools have good metadata capabilities. FrameMaker supports XMP (Extensible Metadata Platform), and Flare has built-in metadata controls for topic types, custom file tags, and other user-created and XHTML-compliant tagging. In Word, you’ll need to configure the document’s properties to add metadata.

Step 7: Publish to multiple channels
While DITA doesn’t give great PDFs, FrameMaker and Word do. You just need a good designer and good templates, and you can easily output high-quality PDFs. Flare has good built-in PDF capability as well, but it’s more limited than that of FrameMaker or Word.

Step 7b: Publish in non-PDF formats
FrameMaker and Flare also excel at non-PDF outputs, such as HTML and EPUB. Word, however, will probably require a third-party tool like WebWorks ePublishing to do acceptable non-PDF documents.

Step 8: Version control
DITA allows for version control just like software code, and DITA tools often feature integrations with version control systems like Subversion. But FrameMaker and Word lack these capabilities, so you’ll likely have to do binary files by saving as .txt and manually handling diffs. Fortunately, Flare has built-in support for Git and Subversion, so it makes version control easy.

For more detailed program-specific tips and examples on how to do each step, see the dek at Monique’s LinkedIn page: https://www.linkedin.com/in/moniquesemp

March 8: Expose UX and General Assembly SF Conference About Gender Parity in Tech

Join Expose UX and General Assembly SF for a tech-focused celebration of International Women’s Day on March 8, 2017. Observed worldwide, this year’s theme is #BeBoldForChange: celebrate and declare bold actions taken to help progress gender parity in tech.

Network with other techies and share your bold actions, watch a special Expose UX episode featuring two female entrepreneurs, then learn from a panel discussion with local women tech leaders about their bold stories.

Agenda

  • 6:00 Networking
  • 7:00 Welcome / Expose UX Screening
  • 7:45 #BeBoldForChange in Tech Discussion Panel
  • 8:30 More Networking (until local leaders decide to end)

About #BeBoldForChange in Tech Discussion Panel

Local women in tech explain that exact moment when they themselves took bold action to improve or develop an aspect of their own livelihood, career or business – or that of another woman’s, or women’s status overall. They’ll discuss what constitutes bold action, the conditions necessary to enable bold action, and what it’s consequences are.

About Expose UX Screening

Watch a special episode of Expose UX, the web show where user experience experts help startups improve their products. Filmed at the international Ladies that UX conference, Talk UX, two women-lead startups showcase their talents. One helps blind people perform tasks on inaccessible websites, the other is a tracking device to protect victims with restraining orders.

Judged on their UX Research, Interaction Design, and UX Strategies, the episode triumphs women entrepreneurship while teaching user experience concepts. Featured guest experts are Marti Gold, Managing UX Director of Tonic3; Amanda Stockwell, former VP of UX at 352; and Kelley Mitchell-Price, Global Creative Director for InterContinental Hotels Group.

Happy New Year: Some Exciting Changes to Our Monthly Meetings!

Happy 2017 technical communicators!

With the new year comes a few exciting changes for the SF Chapter.

First of all, all of our monthly meetings are now free for everyone. Whether you are an STC member or not, you get in for free. This also means that we won’t be offering student discounts or free meeting coupons. It’s free coupons for everyone.

Now, why still become a STC member or join the SF Chapter through the STC? Because your generosity is how we can offer free meetings for everyone. That $25 due goes a long way to provide sandwiches for guest, keep this website running, and pay for our PO box. We sincerely hope that you get enough enjoyment and education from our monthly meetings to continue making us your home chapter.

Not an STC member but still want to contribute? We’ll have a tip jar at the meetings, plus a virtual tip jar on our new Meetup page. It’s easier than ever to register for the meeting. You’ll get reminders and get to see who else is attending.

Why register at all if there’s no charge. We use this for the all important sandwich ordering. Plus, since we’re still at the Salesforce office, it makes checking in faster for you.

Here’s wishing you a great year. Hope to see you and catch up in January!

Intern Needed!

NGINX is a fast-growing startup located in San Francisco in the South of Market area (SOMA). We are seeking an intern to work with our Marketing team, contributing to our popular blog at https://blog.nginx.com. The internship position is paid on an hourly basis.

The ideal candidate for this internship will be:
– A current or recently graduated college student
– Seeking to major in computer science, communications, marketing, or a combination
– A crisp, clear, and concise communicator, in written and spoken communications
– Analytically minded; math skills appreciated
– Aware of search engine optimization (SEO) and how SEO is used in marketing
– Aware of web server technology and how web servers are used in websites and apps such as Amazon, Airbnb, and Uber
– Work experience related to technology development (from startup to Fortune 500)
– Available up to 20 hours a week for next few months, mostly at our offices

Also desirable: High test scores, good grades, print or online publication of your work, and other supporting information relating to the qualifications above.