Git Product home page Git Product logo

gsod's Introduction

Metanorma’s Google Season of Docs 2021

Purpose

Metanorma is a participant in the Google Season of Docs (GSoD) 2021.

This repository is used to organize work relating to our GSoD projects.

See our original project proposal for more details.

Participating tech writers

  • Ankita Tripathi (@techtrailhead)

  • Tina Lüdtke (@kickoke)

For more details, see the kickoff post.

Project schedule

Project phase

Tasks

Assigned to

Timeline

Analysis

Quantitative content audit

both

finish until June 6th ✅

Target audience analysis

both

finish until June 13th ✅

Qualitative content audit

both

finish until June 13th ✅

Create analysis report

both

finish until June 15th ✅

Information architecture

Create content models and discuss reuse strategy

both

finish until June 20th ✅

Create new site structure for docs & navigation

both

finish until 27th June ✅

Technical and editorial implementation of the new site structure

Ankita [no capacity] -→ Tina

finish until August 10th ✅

Community

Set up a community platform [Discussions on GitHub works for now]

Ankita

finish until June 29th ✅

New Content

Create an FAQ page [Done initial work]

Ankita

 — 

Create a troubleshooting reference

Tina

finish until July 20th ✅

Authoring Guide for New Users

Create an introductory tutorial

Tina

finish until August 1st ✅

Review

Metanorma mentors

finish until August 7th ✅

Implement feedback

Tina

finish until August 15th ✅

Flavor-specific Authoring guides

Create OGC Authoring guide

Ankita

finish until August 15th

Create ISO & IETF Authoring guide

Ankita

finish until August 15th

Review (Metanorma + SDOs)

TBD

finish until August 10th

Implement feedback

Ankita

finish until August 15th

If we have time left

Create another SDO flavor Authoring Guide

TBD

finish until August 15th

Wrap up

Create final GSoD report and roadmap for the future of docs

both

until August 15th ✅

Deliverables

  1. Audit report of the current state of documentation

    1. Familiarize and audit existing documentation and software

    2. Develop an understanding of existing community needs

    3. Strengths and weaknesses of current documentation

  2. Information architecture

    1. The desired information architecture should:

      1. Allow the audience to discover the information they need;

      2. Use a layered approach, where the audience can learn more detailed information step-by-step, allowing the novice to progress in knowledge without being overwhelmed; and

      3. Be understandable to laymen. Most Metanorma users are standardization experts and professionals in diverse industries — they cannot be expected to have a level of computer knowledge comparable to that of developers.

  3. Metanorma authoring guide for new users

    1. Consolidate information across existing documentation, covering these topics:

      1. Introduction to Metanorma;

      2. A “quick start” that allows new users to get up and running quickly, with pointers to existing documents where appropriate;

      3. Flavors of Metanorma and their authoring guidance (see next deliverable);

      4. Metanorma standards and specifications; and

      5. A list of related tools and guidance of their usage

  4. SDO-specific authoring guides for IETF, OGC, ISO and another organization

    1. Covering the topics of:

      1. Introduction to the usage of Metanorma in the SDO

      2. Describe the publication flow of a standard at the SDO, and where Metanorma applies within that workflow

      3. Provide authoring guidance on how to author a standard for that SDO, including pointers to existing reference guides

      4. Provide actionable guidance on how to submit the Metanorma-created standard to the SDO for publication

    2. Able to publish them as separate documentation sites for the SDO-specific audience

  5. GSoD project case study (one per technical writer)

    1. Authored by the technical writer and interested project mentors

    2. Describes the success and challenges faced during the GSoD project for future reference

Identified issues

  1. Lack of a general authoring guide, especially geared towards the novice author.

    • New Metanorma users have pointed out the lack of an authoring guide that guides the novice on the steps on setting up the environment, on creating a document, and on preparing a document for publication. Visitors to the site have indicated that it is easy to be overwhelmed by the number of repositories and specifications at first glance.

  2. Lack of flavor-specific authoring guides.

    • Standards authors use Metanorma to create SDO-specific standards, for example, IETF or OGC. Each SDO applies different encoding requirements and content rules on their standards and requires different metadata elements to be entered. While Metanorma does provide reference documentation, they are not sufficient to initiate the author of a standard who is new to Metanorma.

  3. Unintuitive information architecture.

    • Existing Metanorma users have suggested that the information requested is often scattered across multiple locations. One may need to go back and forth across several documents to find the desired information.

  4. Non-development direct enquiries.

    • New users often directly contact project contributors via email or create issues at the GitHub repositories for information they could not locate in the documents. Most of these topics are actually covered on the project website, but they can be difficult to locate for new users.

gsod's People

Contributors

kickoke avatar wkwong-ribose avatar techtrailhead avatar ronaldtse avatar

Stargazers

 avatar

Watchers

 avatar Sebastian Skałacki avatar Ildar Manzhikov avatar James Cloos avatar Nick Nicholas avatar Maxim Samsonov avatar  avatar Alexander Dyuzhev avatar Mehmet Sabırlı avatar Vasil Buraliev avatar webdev778 avatar KW Kwan avatar  avatar Manuel Fuenmayor avatar

Forkers

techtrailhead

gsod's Issues

Develop schedule/timeline for deliverables

For Metanorma

  • Audit report of the current state of documentation
  • Information architecture
  • Metanorma authoring guide for new users
  • SDO-specific “pilot” authoring guides for IETF, OGC, ISO and another flavor

For GSoD

  • GSoD project case study

ISO: FAQ entry about multiline NOTEs

From David Leal (ISO TC 184 SC 4):

  1. Blockquotes within notes
    How do I do an indented blockquote within a note, without the font size being smaller within the blockquote? The form of such a note would be:
>>>>>>>
[NOTE]
====
It says in bla bla:

Bla bla text shown indented.
====
>>>>>>>

My response:

Have you tried this?

[NOTE]
--
It says in bla bla:

Bla bla text shown indented.
-- 

I’m not sure if the whole Note will be indented. We had a discussion with ISO EPMs before about multi-line NOTEs, and there is no current best practice on whether the whole NOTE is indented (IEC Directives does that), or the font size reduction is the only distinguisher of the NOTE vs body text (ISO Directives demonstrates that).

The further consideration on whether the NOTE gets indented is that Metanorma doesn’t support “tabs” (aha), because HTML doesn’t support it. Metanorma uses HTML to inject content into Word. It is possible to encode NOTEs as tables for a consistent indent (ISO's Word templates used to do that) but this approach is now deprecated by ISO EPMs because it is difficult to convert tables into NOTEs.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.