Theme is MIT licensed but no name is added, we should do that: https://github.com/datatogether/website/blob/44b1129aa56299084807e890f4d3493eda6ae0f1/themes/datatogether/LICENSE.md

Non-blogposts are showing up in the blog submenu

The join link and links to semester notes are broken on https://datatogether.org/readings/. They point to github page urls: datatogether.github.io that respond with a 404. Not sure how to fix this correctly. But think it might have to do with config.toml.

I don't understand how the github page interacts with the .org site, but there seems to be re-direction of some kind. This link https://datatogether.github.io/website/posts/02_civics/ on the "alternatives" blog post re-directs and does work for some reason

/cc @Frijol

From @mhucka in #12:

"We hope to build a future in which networks of collaborators make their data accessible to their peers, immediately discoverable, easily verifiable, and robustly preserved."

Minor grammatical issue: the referent of "immediately discoverable" and the tail end of that sentence strike me as ambiguous. Here are some ideas for how to avoid the problem:

• Replace the comma after "peers" with a long dash (using whichever "long dash" convention is being used throughout the project, whether that's an em-dash without spaces or an en-dash surrounded by spaces)
• Add the words "in ways that are" before "immediately"
• Replace the comma after "peers" with "and the data is" (or "and the data are" if we're following the tradition that "data" is considered plural)

"Creating proof-of-concept tools that communities can use to collectively steward data"

Split infinitive. Suggested replacement: "to steward data collectively".

"There are many ways to get involved and to contribute, the most important of which is to test the Data Together model with your community and then share back where things work, where the approach opens new possibilities, and where there’s room for improvement."

The expression "share back" sounds weird. How about "share your experiences about"?

@b5 is there a shared login for CircleCI so other admins can see deployment logs?

"Readings" page doesn't show up on the deployed site (in the menu or as a /readings page), even though it works fine from a local version on master branch.

Deploy issue perhaps?

Hey there, thank you for submitting an issue!

We are trying to keep issues for feature requests and bug reports. Please complete the following checklist before creating a new one:

• feature request

Just noticing when cloning the repo that it is quite large, the keynote presentations are over 20MB, wondering if we just switch to pdf-only as those can be reduced in size?

If we want to publish presentation materials that are editable maybe we consider a different publishing approach (... 😏 ) rather than surfacing/storing in the website repo

Video: https://archive.org/download/ndsr-dc-2017/04_Speaker_3_Matt_Zumwalt.mp4
Slides are on dropbox

on the Join page– it's not obvious that it's a link! Make a button, as it's the main call to action for this page?

Tell Story of the emergence of the need for a "data rescue" public record, and the creation of alpha.archivers.space

• all the data rescue efforts happened
• need a way to answer "what has been rescued so far?"
• challenge: reconciling disparate metadata patterns -- original discussion in datatogether/dataset_registries#1
• upshot: alpha.archivers.space > datatogether/public-record

@rgardaphe demoed wireframes at the 2018-03-19 Rountable and got some oohs and aahs 🎉 , things to finalize them in order to move onto the reboot:

• review and add feedback on Zeplin (add your comments here or request ability from @rgardaphe and @weatherpattern in app dashboard! now til APR 30
• confirm IA APR 30
• request final stage feedback!

Then we can lock down a version for May-ish

"Data Together empowers people to create a decentralized civic layer for the web, leveraging community, trust, and shared interest to steward data they care about." from our docs

When we 404 we get the github pages 404, it would be much better to have something with at least our nav bar at the top

By @michellebrous largely copy edits I believe. Mocked up at https://www.figma.com/file/GMig6gS4TMCrQ0ZPIvf7nE/Data-Together-Homepage-Mockup?node-id=0%3A1 - needs to be implemented

Pages that are not blog posts have the date in the header. If the date is removed from the .md file a default date of Jan 1, 0001 appears anyway.

We need a new template that doesn't have the date in the header.

Slides: https://github.com/datatogether/datatogether/files/1171166/Data.Together.-.ESIP.Summer.Meeting.July.2017.pdf (from datatogether/datatogether#1)
Video: https://www.youtube.com/watch?v=8fP4M0iAYGs (of the whole plenary, we could queue to the right moment I believe?

In the previous theme, the blog posts were in a folder called posts, leading to urls like https://datatogether.org/posts/03_alternatives_capitalist/ which now 404s.

The new links are from a blog folder, so the new urls are e.g. https://datatogether.org/blog/03_alternatives_capitalist/

Change the folder? Or redirect?

cc @lightandluck

Our site is currently live from https://datatogether.github.io/website/

Might need to re-update baseURL and params>domain in config.toml when this goes through

Just a heads up that I set the publish date for the trust (d1ab133) and private data (ebd8700) posts after the new year because they're still stubs and I'm not sure what the planned publishing date is. The trust blog was appearing on the live site.

Let's close this issue whenever the correct date is put in for them?

Hello there!

We're currently making all websites under ipfs/libp2p/ipld/multiformats be automatically built and deployed via Jenkins.

If wanted, we could also activate that for this website. This would give you a link to a preview (via IPFS) for each commit and PR and also automatically update the _dnslink TXT record when changes to master happened. Makes maintenance of the website super simple!

Let me know if we should activate that for this repository as well.

Hey there, thank you for submitting an issue!

We are trying to keep issues for feature requests and bug reports. Please
complete the following checklist before creating a new one:

• feature request

Just poking about and it looks like we have jquery and maybe normalize twice, footer scripts and more that are not relevant to this site.

I feel like this setup was pulled over from another site and we can probably revisit and clean up?

There are some oddities of text width, spacing, and maybe font size that make our blog a bit hard to read. It would be very nice to have someone take a look at/tweak these!

I'd be happy to help/implement if someone with more design chops could take a look and call out what needs changing!

Currently pretty odd because it's just alphabetical:

IPFS Companion (https://github.com/ipfs-shipyard/ipfs-companion) tries and fails to load our site, such that you get loading forever-type behavior. I suspect this is because the companion looks for an IPFS version of the site, but we used to have a pin but don't anymore.

Still familiarizing myself with Hugo, but it seems to break pattern that the main page copy is stuck in website/themes/datatogether/layouts/index.html
rather than
website/content/

can change this?

Aggregators vs Public Record (line is blurry)
The role of a Public Record in enabling discovery

Examples of Public Records

need to build out this list

Examples of aggregated datasets used to view and track data that is being stored by many parties.

• https://data.gov
• https://dp.la
• https://europeana.eu
• https://alpha.archivers.space -- soon to be moved into datatogether as a proof of concept public record

Tools for Maintaining a Public Record

need to build out this list

• Consensus-based Distributed Ledgers (aka. Blockchains)
• Datatgether public record code: https://github.com/datatogether/context

https://docs.google.com/presentation/d/1R4OXvaMYCG_pGlxRoxJ228OADgV0ZhgKcYEXFFP9Ulk/edit#slide=id.p DWeb Spark Meeting slides

http://www.esipfed.org/press-releases/stronger-together

Add links and context showing how this connects to the data together pattern.

The footer info is just text. We should link them to our Github and Twitter accounts:

• Github: https://github.com/datatogether
• Twitter: https://twitter.com/Data_Together

Flagging that the website is down and has been for about a week (or more?).

Based on chat in Slack (thanks @Mr0grog @lightandluck @b5) our site is pinned to the IPFS public gateway (http://gateway.ipfs.io/), which is working, and our dnslink records are right, but the hash is failing to resolve.

Broken off of #12:

I think we want to fix something in the iframe height/width -- I'm getting some odd column crop effects... (both simulating mobile/small screens and not)

Perhaps we can we set height to 100% to resolve?

The CircleCI build failed because we're using an image for Hugo 0.46, and the new theme just merged (#86) requires Hugo 0.55

Updating my local version of Hugo to latest (0.60) and testing. And will update our image if it works ok.

They're at https://archive.org/details/dwebcamp2019 but I haven't looked through them. @dcwalk @lightandluck do you have any suggestions?

Make sure this repo has the following files:

• Readme README.md
  • Repo Badges for: Github Project, Slack, License
  • 1-3 sentence description of repository contents
  • Getting Involved section
  • Development section
• License -- LICENSE
• Contributing Guidelines (minimal and pointing to org-wide) .github/CONTRIBUTING.md
• Issue Template -- .github/ISSUE_TEMPLATE.md
• GitHub Description from 1-3 sentence readme blurb

This issue forms part of a project-wide meta-issue

Current CSS does not translate to mobile.

I think we should avoid constantly having to bother @lgierth to repoint the IPNS entry for this page on updates. Some options include:

• replicate a script like the one contained in ipfs/website that makes updates extra easy for someone at protocol to perform
• we set up an IPFS gateway, request a one time DNS point at the IPNS entry of that gateway, self-manage updates
• switch to a "more traditional" static hosting solution 😢

Now that we have a blog post nearly ready we need a venue for it! Hugo is set up to be a blogging platform, so it seemed reasonable to add that capacity to our site.

What do we need to take into consideration when spinning up blogging for Data Together?

The simplest version (in the blog branch) is just to add the blog as a page, which looks like:

menu:

post:

file structure:

This would make more sense (menu-wise) if we deleted the other menu links (Data Together, which goes to the homepage (but is also linked in the header), and Public Record, which I'm confused about.

Feel free to check out/play with the blog branch but note that the content and formatting of the post is from the rough draft/will be edited before posting.

I set the date/time for them to go live and they work fine locally but don't show up in the live site

It has taken ~7months to work through an automated deploy process, and it doesn't appear as if it current works.

Can we build and deploy on a non-IPFS solution while we get an automated process sorted out, given the complexity of this site (low), and the centrality of our hopes to have it used for engagement and messaging (increasing, see datatogether/datatogether#34)?

This could be:

• manual builds onto gh pages
• automated builds onto gh pages
• ?? something fancy on our own VPS?

Looking at this chunk:

There are many ways to get involved and to contribute, the most important of which is to test the Data Together model with your community and then share back where things work, where the approach opens new possibilities, and where there’s room for improvement.

I made a comment in the google doc draft:

This needs handholds -- like do we have a worksheet-styled doc "use the model"?
Not sure I'd suggest 3 wheres... think we'd want a 5W almost as a guide to report back (this could be part of a "worksheet" as above?)

With an excellent follow up comment (TBD if I can post publicly)

Some additional resources I dug up around 5W activities:

• http://www.readwritethink.org/resources/resource-print.html?id=290
• http://www.esmonline.org/webpages/tdonahue/index.cfm?subpage=1873266 (nice language on questions)

Maybe as simple as putting a link/button to the Readings page on the Join page (and maybe change the link to the Join page to a button on the Readings page)

Should be quick, need to check out why * are appearing rather than being interpreted as italics (even though sometimes italics are appearing):

on https://datatogether.org/posts/03_alternatives_capitalist/

It seems it has been posting errors for quite a while now. But the website does update with the Circle CI from main, so maybe this doesn't matter?

https://app.circleci.com/pipelines/github/datatogether/website?branch=gh-pages

Originally posted by @Frijol in #106 (comment)

• Add links and explanation info to the examples
• Provide more background explanation (or completely rewrite if that's better)

We're pushing this live before the semester closes so will need to grab:

• Stewardship blog post link
• Decentralization notes link
• Decentralization recording link
• Decentralization blog post link

• Provide better explanation
• Provide links to more tools, with explanations