From categories:
page 1 of 212next »
Beverly TheunisBeverly Theunis 04 Jun 2018 14:09
in discussion Hidden / Per page discussions » Project

Cases: "v." not "v" — agree
First or 1st? — 1st (to avoid longer headlines)
Should headings end with a colon or not? — Use colon before block quotes, otherwise do not use colon (this is how episode pages are already being done

by Beverly TheunisBeverly Theunis, 04 Jun 2018 14:09
Suggests
Paul DugganPaul Duggan 04 Jun 2018 07:24
in discussion Hidden / Per page discussions » Project
  • Cases: "v." not "v"
  • First or 1st?
  • Should headings end with a colon or not?
Suggests by Paul DugganPaul Duggan, 04 Jun 2018 07:24
Thoughts
Paul DugganPaul Duggan 02 Jun 2018 01:01
in discussion Hidden / Per page discussions » Project

Perhaps pull the explanation Title Case out and have it in a "definitions" section at the start, so readers can apply it to whichever bit they're using.

Perhaps another name for "original content" or an explanation of what it means.

But a good start.

Thoughts by Paul DugganPaul Duggan, 02 Jun 2018 01:01

1.1 - Will check that page.
1.2 - Edited, does this help? (The page still doesn't go anywhere but is the intent clear?
1.1 & 2 - "oa" is used where it is needed, "OA" is used where it is needed. I'm not sure how this is confusing.
1.4 - Discussed with group.
2 - Good.

by Paul DugganPaul Duggan, 01 Jun 2018 00:11
Edits
Paul DugganPaul Duggan 31 May 2018 23:51
in discussion Hidden / Per page discussions » Create A Page

Step 1, line 1, > link to three ways — Method 1, “in the box at the side of the box” is vague; Method 2, meaning of “Click on a broken link” unclear

Point 1 - fixed (I think)
Point 2 - do the images help at all?

Edits by Paul DugganPaul Duggan, 31 May 2018 23:51

I did Steps 1 and 2 for page for OA6 and stopped there as checkpoint for tags.

My thots:
Step 1, line 1, > link to three ways — Method 1, “in the box at the side of the box” is vague; Method 2, meaning of “Click on a broken link” unclear
Step 1, line 2 — “this link” does not go to official website as indicated
Step 1, lines 1 and 2 — showing both lower case oa and upper case OA is confusing as to which to use;
Step 1, line 4 — Should include instruction for inserting around guest name or include it on template; no instruction for deleting “(if any)” tho it seems it would be obvious to do it, if maker of page does not notice to do it, then proofreader must deal with it. Suggest either deleting “(if any)” from template (since the point of it is dealt with in instruction) or place it within an

Step 2 was clear and easy to follow.

Step 1 and 2 by Beverly TheunisBeverly Theunis, 31 May 2018 22:24
  • add
+++ Episodes including the segment:
[[module ListPages tags="SEGMENT-TAG" order="title"]]
* %%title_linked%%
[[/module]]

where SEGMENT-TAG is a tag used on episodes including the segment.
by Paul DugganPaul Duggan, 29 May 2018 22:02

Please clarify (thank you):

In copy below on Segment page:

"…
tag the page with segment.
tag the page with seg-clean-up or seg-ref-clean-up.
add
…."

Does the word, "add" mean "create a new tag". And is the module code following "add" what automates creation of a list for it, and then places new tag on said list?

Segment Tag Question by Beverly TheunisBeverly Theunis, 29 May 2018 15:07

I put in the strikethrough on OA1, using the strkethrough formatting from wikidot. Was that what caused the glitch?

Re: Formatting Glitches by Robin HofmannRobin Hofmann, 26 May 2018 19:48

I think we need some way of flagging specific problems needing guru attention … for instance, on ao1 I saw that the formatting had fallen apart and with a little guesswork I discovered that a strikethrough word copied over from official website caused the formatting to break. Lesson learned: Wikidot does not accept strikethrough text. I substituted em dashes around the word (change this if you have better idea).

Next, in cleaning up oa161 I came across typography glitch in text for "show notes & Links" and after trying, I cannot fathom the cause.

Maybe a new tag "guru-attention-needed" with a descriptive editor's note placed at the problem area, and whoever is able to fix it removes that tag?

Thoughts?

Formatting Glitches by Beverly TheunisBeverly Theunis, 26 May 2018 19:15

This is my suggestion:

TOP BAR
• ABOUT - Yes, on top bar (a good start on copy about the podcast has been made).
• MEMBERSHIP (join) - with this link visible, anybody in world can join; if we want to limit joining in some way we could bury it within the site and provide a direct link to it from Facebook Community, Patreon, wherever else.
• MEMBERS - Position this next to Membership (if we keep Membership in top bar), otherwise, move it within the site next to Membership.
• HELP DOCS - Pull down menu. - needs to stay on top bar because dropping attribute probably be awkward in side bar.
• CONTACT - to use it or delete it, that is the question; decision to use it means we must provide an email to someone somewhere, don’t think any of us want to our emails boxes flooded from around the world, so I suggest we have no contact page at all, unless Andrew wants us to use his gmail.

Side Bar

Clone this site (button) - leave as is
“Site Navigation” (head) - Change to “Site Management” (or some such)

• USER GUIDE - delete this because it can be accessed in Help Docs in Top bar
• FIRST TIME USER - keep this
• ABOUT - redundant, so delete this
• LAYOUT - move to side bar from top bar
• CONTACT - - redundant, so delete this
• LEGAL - If we have no legalities, disclaimers, etc. delete.
• DISCUSSION FORUMS - I assume this would be to discuss the episodes, and be open to the world, but it would compete with official web site, would it not? If so, I say delete it.
• TALK (but possibly left at top.) - Move to side bar
• CREATE A PAGE - keep as is

In my search through global css choices for the Standard Theme that we have, I see none for controlling headline size. All I can think of now for options are (1) use episode # for headline, and put title underneath as a subhead or (2) continue headline format as is and learn to love it.

Downside of option (1) is that only number of episode, not its title, appears in episode list. I don't know if that's good or bad.

Headline Appearance by Beverly TheunisBeverly Theunis, 24 May 2018 02:21
Headings
Paul DugganPaul Duggan 24 May 2018 01:21
in discussion Hidden / Per page discussions » Project

Most episode pages currently have some or all of the following headings:

  • Cases
  • Legal Terms
  • Legislation, regulations, and executive orders
  • People (mentioned)
  • References
  • Topics

I think "Legislation, regulations, and executive orders" needs a new shorter heading.

Headings by Paul DugganPaul Duggan, 24 May 2018 01:21

So, I googled for Wikidot example web sites (http://basicwiki101.wikidot.com/examples-of-wikis) and see that pretty much "anything goes." I think we can do whatever we want with the Legal Page … keep as is, edit it, delete it. My guess is that the manner in which it is provided by Wikidot is so that web site makers will be aware of it.

Legal (link) by Beverly TheunisBeverly Theunis, 24 May 2018 00:43

Either (so probably viewers)

  • About
  • User Guide (navigation)
  • Contact
  • Legal
  • Membership (join)

Worker

  • Layout
  • talk (but possibly left at top.)
  • User Guide (current)
  • Help Docs - Pull down menu.
  • First Time User
  • Discussion Forums
  • Members
  • Create a Page

Any that can be combined/removed? Anything that needs adding?

Workers vs Viewers menus by Paul DugganPaul Duggan, 24 May 2018 00:19
Paul DugganPaul Duggan 24 May 2018 00:12
in discussion Hidden / Per page discussions » Talk Place

That does sound like a good division of the menus. I agree on that.

I wasn't really suggesting that User Guide and New Users could go, rather adapted from the Generic Wikidot "add text here" to something usable. Good question on members vs non-members exclusion.

I read Legal as more generic, but you're right it's Wikidot's legal stuff. Best leave it alone.

by Paul DugganPaul Duggan, 24 May 2018 00:12

Noted "needs content" — my first understanding of this page was that it applies to Wikidot terms of use; however, fact that this page can be edited implies that terms for OpenArgsWiki could be merged into it or fully replace it; except, note, within Wikidot's current copy, the link "Terms of Use" goes deeper dive into Wikidot terms, and whatever we would write would need to keep that link (?) (click on it, see what I mean). So, it appears to me that the content question here would be, are "terms of use" that are applicable only to OpenArgWiki necessary?

Legal (link) by Beverly TheunisBeverly Theunis, 23 May 2018 23:50

I think side bar should stay on the side because (1) removing it did not help the page headline, which was purpose of moving it and (2) side bar info placement at top of page demotes hierarchal importance of Episode Title.

Both top and side bars have links that apply to both visitor and worker. I suggest a clean division between the two, visitor links at top, worker links at side.

On suggestion that “user guide” and “first time user” could go, consider that in future years of Opening Arguments podcasts, workers could be coming and going over time, so these links might be handy if not essential for newbie workers. That said, once we "announce" the site, are we interested in "closing off" "whole world" visibility to worker pages and, if so, is that possible?

Top Bar, Side Bar by Beverly TheunisBeverly Theunis, 23 May 2018 23:33
Teresa GomezTeresa Gomez 23 May 2018 00:51
in discussion Hidden / Per page discussions » Talk Place

“That's awesome!

1) If you notice, the patreon-only early answers are set to go public 5 days after their release, so we definitely don't mind including that information in the Wiki at the same time that it releases to the public. We're about to do a patreon-only bonus (here's an early bonus for you) where we post the *questions* for patrons-only, and obviously we'll need that to stay behind the wall.

2) You can absolutely do a transcript for the Wiki and use info from the site and show notes, so long as you post a copyright notice that this information is "Copyright (c) 2018 Opening Arguments Media, LLC. All rights reserved."

Let us know if you have other questions.”

Also the newsletters can’t be posted because they are only available to patrons.

by Teresa GomezTeresa Gomez, 23 May 2018 00:51
Paul DugganPaul Duggan 22 May 2018 23:48
in discussion Hidden / Per page discussions » Talk Place

For aesthetics at the moment. Remove redundancy is good, too.
I've updated my original comment with more info on each option.
On the "Discussion Forum" we don't need that for viewers, no point splitting off from Facebook. But it seems like a great place for workers to discuss stuff. Better in a global sense than the talk pages.

by Paul DugganPaul Duggan, 22 May 2018 23:48
page 1 of 212next »