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

Create marketing/docs site #149

Closed
KyleAMathews opened this issue Feb 26, 2016 · 24 comments
Closed

Create marketing/docs site #149

KyleAMathews opened this issue Feb 26, 2016 · 24 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more.
Milestone

Comments

@KyleAMathews
Copy link
Contributor

KyleAMathews commented Feb 26, 2016

If anyone is interested in a doc writing party in SF/online let me know :)

Stuff (beyond the normal) to document

  • Default webpack config (which loaders/plugins are added + why) + how to modify it + common modifications
  • Deployment
  • Project philosophy. What it isn't and isn't. Constraints you should be aware + their advantages/disadvantages.
  • List starters Browsable/searchable list of starters #56
  • document how to accomplish common patterns in Gatsby/React.js e.g. Disqus, generating Atom/RSS feeds & site maps, etc.
  • Pointers to learning React to React newbies.

Other things that should be there? E.g. what did you find confusing when playing with Gatsby?

Let's continue to flesh out the list of topics to cover and then start writing docs (in markdown) and land them as PRs against the 1.0 branch in a /docs directory.

@tychota
Copy link

tychota commented Feb 26, 2016

in common pattern , generating an atom/rss feed could be added ! I manage to do it, using the post-build from your blog but I wasn't an easy road.

@KyleAMathews
Copy link
Contributor Author

@tychota absolutely, I'll add that to the list.

@kaihendry
Copy link
Contributor

Keen for some pointers how to generate an RSS feed from the starter blog template. Cheers!

@KyleAMathews
Copy link
Contributor Author

@kaihendry check out what I did for my personal blog (need to convert this to JS) https://github.com/KyleAMathews/blog/blob/master/post-build.coffee

@KyleAMathews
Copy link
Contributor Author

Hey folks — been working on design + components for Gatsby powered documentation sites. As a test case I've been working on a PR to convert the new Webpack website to use Gatsby. Would love feedback on the design, etc. as whatever that ends up being will be what we will use here (or very similar).

webpack/webpack.js.org#202

@kaihendry
Copy link
Contributor

Looks good @KyleAMathews. My only niggle is that View Source is FUGLY.
view-source:https://webpack-gatsby.netlify.com/concepts/targets/

I know one is supposed to use Chrome Dev tools to explore the markup in 2016, but I prefer to have readable markup. It's the way I learnt the Web and as a result, any site that has fugly markup gets minus points from me.

Oh btw CONFIGURATION is line breaked? http://s.natalian.org/2016-10-05/1475643336_2558x1404.png

@KyleAMathews
Copy link
Contributor Author

@kaihendry ahhh I see you're an old-timey web developer who likes the fine patina developed on hand-crafted, hand-polished HTML ;-)

You'll love the new plugin system with Gatsby 1.0 as you could create a plugin to pretty-print Gatsby's output :-)

Hmmm... yeah, it looks like that line breaks at 872 pixels wide on my mac chrome. I'll shrink it down or set a min-width on that column in the morning.

@MoOx
Copy link

MoOx commented Oct 5, 2016

@KyleAMathews I think the current visible css is very redundant. Is this something that can be improved?

@KyleAMathews
Copy link
Contributor Author

@MoOx not sure I understand what you mean? Which css? Redundant to what?

@MoOx
Copy link

MoOx commented Oct 5, 2016

@KyleAMathews
Copy link
Contributor Author

@MoOx oh gotcha... hmmm you're right, there is a lot of duplicates there. That's the output from extracting styles from Glamor — I'll file an issue there about deduping rules when server rendering. In the meantime though, all hail the magic of gzip :-)

@threepointone
Copy link

my bad, spotted this earlier today, will get a fix in soon.

@kaihendry
Copy link
Contributor

Btw the hero graphic doesn't look good http://s.natalian.org/2016-10-06/iphone7+.PNG

Actually I'm pretty confused by https://webpack-gatsby.netlify.com/93881a5096732dfdf25532ff4596690a.png

I thought the "idea" with Webpack is that you can put js,css,png,jpg(as data uris) etc etc all in one payload, the bundle.js! https://www.youtube.com/watch?v=WQue1AN93YU

@KyleAMathews
Copy link
Contributor Author

Interesting write-up on doc sites' sidebar navigation http://idratherbewriting.com/2016/10/23/coding-sidebar-navigation-for-documentation-websites/

@KyleAMathews
Copy link
Contributor Author

Very early preview of new site is up — https://gatsbyjs.netlify.com/

Going to be working on a sketch soon for a proposal for the information architecture.

@KyleAMathews
Copy link
Contributor Author

Something that'd be fun/useful to explore for mobile is a bottom navigation bar. Perhaps with links to home, docs, news, and a hamburger menu with an extended navigation menu.

Links:

Quartz is a web site that showcases this nicely http://qz.com/

@KyleAMathews
Copy link
Contributor Author

StackOverflow's documentation project is really interesting — http://meta.stackoverflow.com/questions/339974/the-dawn-of-documentation-a-solstice-update?cb=1

This bit is suggestive of some things we could add to Gatsby's docs:

Wikipedia offered low transaction costs to participation, and it de-emphasized the social ownership of content. Editing Wikipedia is easy, and instant, and virtually commitment-free. “You can come along and do a drive-by edit and never make a contribution again,” Hill pointed out. And the fact that it’s difficult to tell who wrote an article, or who edited it — rather than discouraging contribution, as you might assume — actually encouraged contributions, Hill found. “Low textual ownership resulted in more collaboration,” he put it.

It might be helpful to let people edit the Gatsby docs site directly on the site so you click a button on a page and up pops a model.

@erlend-sh
Copy link

It might be helpful to let people edit the Gatsby docs site directly on the site so you click a button on a page and up pops a model.

I pitched such a thing for Jekyll, and @mushishi78 actually rolled with it and developed a working prototype:

https://github.com/wiki-hub
https://jekyll-anon.surge.sh/gods/2015/02/18/vesta.html (live demo)

wikihub-piclite-gif-crop

It needs to be running persistently on a service like Heroku though. As far as I know there's no way around that.

@KyleAMathews
Copy link
Contributor Author

@erlend-sh nifty! Yeah, that's exactly what I was thinking of. User clicks edit, auths against github, makes change w/ commit message, and a PR is created.

@m4rrc0
Copy link
Contributor

m4rrc0 commented Mar 23, 2017

Maybe using Netlify CMS. Though I don't know if you can even access the Editing UI if you are not a collaborator on the repo...

@mchandleraz
Copy link
Contributor

I'm trying to get Disqus integrated to a new Gatsby project and I'm not having much success so far. I saw #133, but the link from @KyleAMathews 404s now and I wasn't able to find anything disqus related in that repo.

I'd be happy to write the docs, if someone can point me in the direction of some more info or a reference implementation.

Thanks!

@KyleAMathews
Copy link
Contributor Author

@mchandleraz this is the react component that I was using https://github.com/mzabriskie/react-disqus-thread

@stale
Copy link

stale bot commented Oct 22, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Oct 22, 2017
@stale
Copy link

stale bot commented Nov 7, 2017

This issue has been automatically closed due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more.
Projects
None yet
Development

No branches or pull requests

8 participants