|
|
| Line 14: |
Line 14: |
| | Blah blah blah <ref>Hello! I'm a footnote. Do you read me?</ref> | | Blah blah blah <ref>Hello! I'm a footnote. Do you read me?</ref> |
| | | | |
| − | = Exporting Markdown to Mediawiki Tests = | + | = More tests= |
| | | | |
| − | = DisCO.coop — Creative Catalyst Grant Report 1 (add tag) =
| + | We could ideally write direclty on '''Wikitext'''. One of the benefits is the great time savings. Most of us working on Mothership/Floor are translators, also, if you type well, learning the languages means that you can format ''while'' you're typing. Isn't that great? |
| | | | |
| − | <!-- The text in these bracketed sections will not appear once you publish the post. -->
| + | == The woes of bilinguism == |
| − | <!-- Be sure to update all text in the {brackets} that appear in the title of your post. -->
| |
| − | <!-- As a Grant for the Web grantee it is important that you update the community and the program on the progress of your work. This is a chance to brag a little, name where you might have struggled and get feedback from the Web Monetization Community. -->
| |
| − | == Image (optional) ==
| |
| | | | |
| − | <!-- Share a project screenshot, a whiteboard doodle, or a photo of your team hard at work. -->
| + | '''False friend alert''' |
| − | == Project Update ==
| |
| | | | |
| − | <!-- Provide a short summary of how your project is going. Feel free to highlight a big win, a struggle you had or generally update us on where you are on your timeline. If this is your final report, provide a summary of how your project went during the funded period. --> | + | Wiki text <big>IS A DIFFERENT LANGUAGE FROM MARKDOWN</big>. Markdown (find out more in the [https://wiki.guerrillamediacollective.org/Markdown Guerrilla Media entry on it]) is very similar to wikitext, but like Spanish and Portuguese it may confuse people. For the benefit of the LABS, we want wiki editing to be as simple as possible so folks don't have to learn the language and just use the Wysiwig, but the editor is kinda meh. |
| − | <blockquote>What's a DisCO? Overall assesment and vibe Namedrop GWOB/FOundation Technology Multi Node DisCO Check other reports for tone/vibe Xxxxxx Xxxxxx xxxxxx | |
| − | </blockquote>
| |
| − | Hello GftW/WM Community. I'm [[xxxxx|Stacco Troncoso]] from DisCO.coop, co-writing this project update with my dear colleages [[xxxxx|Sílvia López]] and [[xxxxx|Caitlin Cole]]
| |
| | | | |
| − | == Progress on objectives ==
| + | Questions is ''can we do this in-team''. And how do we comment on shit? Or suggest changes or the many other features we use in Google docs??? |
| | | | |
| − | <!-- Referencing your original proposal, please update on each objective.
| + | Some problems with Gdocs |
| − | It's OK if some of them have evolved - simply share how and why that happened. If you have links to any outputs, either final or in-progress (e.g. mock ups, prototypes) share them here. This could include blogs, documentation, GitHub repos, tools audio-video content, etc. -->
| |
| − | <blockquote>Check green labels Check Trello Use bullet points + links where possible Highlight Gallery Blue Labels Continual prototyping - continual dogfooding xxxxxx xxxxxx
| |
| − | </blockquote>
| |
| − | "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum."
| |
| | | | |
| − | == Key activities ==
| + | # It's Google |
| − | | + | # Undermines our FLOSS/Political cred |
| − | <!-- Please report on the key activities outlined in your original proposal.
| + | # Inserts complexity in what should be a very streamlined process |
| − | It's OK if some of them have evolved - simply share how and why that happened. If you have links to any outputs, either final or in-progress (e.g. mock ups, prototypes) share them here. This could include blogs, documentation, GitHub repos, tools audio-video content, etc. -->
| + | # Converts like shit to mediwiki (yes, there are converters available... see the methodology [https://wiki.guerrillamediacollective.org/Mediawiki#Gdocs.2FHtml_to_Wiki_conversion here] |
| − | <blockquote>Check timeline and TLDR Green and Blue Status overview LABS, LABS LABS and intersectionality Add links galore from Blog, Wiki, Gwob Wiki, YouTube, SM
| |
| − | </blockquote>
| |
| − | == Communications and marketing ==
| |
| − | | |
| − | <!-- How have you discussed your work in public? Please include any links to writing, interviews, podcasts, webinars, tutorials etc. If you included marketing in your budget, provide examples of how those funds were spent. -->
| |
| − | <blockquote>Mention main DisCO Resources, then direct to Relevant links section
| |
| − | </blockquote>
| |
| − | == What’s next? ==
| |
| − | | |
| − | <!-- For Progress reports: What will you do during the remainder of your funded grant period? What is still left to accomplish on your timeline? For Final reports, let us know where you’ll take your work next? -->
| |
| − | <blockquote>Yellow labels Explain GMC Wiki > Mothership > Floor+Semantic wiki methodology See post its. Mention Jan vs Feb April
| |
| − | </blockquote>
| |
| − | == What community support would benefit your project? ==
| |
| − | | |
| − | <!-- Please let readers know if there are ways we can help problem-solve, advance your work or make connections. -->
| |
| − | <blockquote>Exposure, Running DisCO Simulator Checking our documentation on WM and IL (Geeks Wiki)
| |
| − | </blockquote>
| |
| − | == Additional comments ==
| |
| − | | |
| − | <!-- Is there something that we haven’t asked you would like to share? -->
| |
| − | <blockquote>==== Challenges! ====
| |
| − | | |
| − | Overscaling Feedback for GftW Team challenges Toxic masculinity and aggression Test for the team and DisCO Xxxxxx
| |
| − | </blockquote>
| |
| − | == Relevant links/resources (optional) ==
| |
NET.LABS example
Heading text
- Numbered list item
Insert non-formatted text here
Big text
Small text
Superscript text
Subscript text
Blah blah blah [1]
More tests
We could ideally write direclty on Wikitext. One of the benefits is the great time savings. Most of us working on Mothership/Floor are translators, also, if you type well, learning the languages means that you can format while you're typing. Isn't that great?
The woes of bilinguism
False friend alert
Wiki text IS A DIFFERENT LANGUAGE FROM MARKDOWN. Markdown (find out more in the Guerrilla Media entry on it) is very similar to wikitext, but like Spanish and Portuguese it may confuse people. For the benefit of the LABS, we want wiki editing to be as simple as possible so folks don't have to learn the language and just use the Wysiwig, but the editor is kinda meh.
Questions is can we do this in-team. And how do we comment on shit? Or suggest changes or the many other features we use in Google docs???
Some problems with Gdocs
- It's Google
- Undermines our FLOSS/Political cred
- Inserts complexity in what should be a very streamlined process
- Converts like shit to mediwiki (yes, there are converters available... see the methodology here
- ↑ Hello! I'm a footnote. Do you read me?