Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tools for Publication 0 #7

Open
sadasant opened this issue Feb 17, 2018 · 8 comments
Open

Tools for Publication 0 #7

sadasant opened this issue Feb 17, 2018 · 8 comments

Comments

@sadasant
Copy link
Member

sadasant commented Feb 17, 2018

List of tools we will share with the community for our first publication.

  1. fresh-yuca: I'm thinking that for starters we could have a simple NPM repo called fresh-yuca, that would help users consume our publications by:
  • Listing the available ones, in the available formats.
  • Allowing them to download specific ones in specific formats.
  • Allowing them to subscribe to a mailing list...
  • And other similar interactive features.
  1. miner.js a JavaScript miner provided by Carlos Guerrero. It will be super slow, but it will be a helpful way of learning how miners work.

  2. Some auto-publishing tool: Let's develop a CI tool for publishing our contents on social media platforms. We need to discuss where and to what degree we will do it, but I'm thinking this tool could:

  • Use fresh-yuca to generate a PDF of Publication 0, then store it on dropbox or other tool for storing public content (maybe even gitub).
  • Then, share a summary of the contents in different sizes and formats depending on the social media.
  • Then, share again some other pieces of the contents of Publication 0 in a timely manner, so that it could build up as a long-standing campaign, or at least last for a whole month while we work on Publication 1.

What other tools do you guys think we can share with people?

@aitbw
Copy link
Member

aitbw commented Feb 17, 2018

Re: formats, which ones have you thought about? I'm thinking .epub, .mobi and .pdf would serve us well for now.

@rivasvict
Copy link
Collaborator

Markdown still seems to be a good idea. I think it can be translated to other formats

@guerrerocarlos
Copy link

Count me in :)

@stefanmaric
Copy link
Member

On this topic, I just want to say that we should definitely stick to some - agreed upon - markdown flavor for editing, or something close.

It is always easier to migrate from a simpler system to a more complex one.

Once content is available as markdown, publication format is basically a matter of consumers' choice; pandoc offers a lot in this matter.

@sadasant
Copy link
Member Author

sadasant commented Feb 19, 2018

Definitely markdown as the source of all of the publications! We can post-produce other formats later. I'm adding that to the description of the New Format issue.

@sadasant
Copy link
Member Author

@stefanmaric Actually, just by coincidence, all the files that have content end in .md in the New Format issue: #4 , do you think we should also have it as a statement before them? Like all the content files must be in markdown?

@stefanmaric
Copy link
Member

all the content files must be in markdown

I strongly agree.

@sadasant
Copy link
Member Author

Added this:
screen shot 2018-02-19 at 2 43 12 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants