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

Tracking Version 0.3.0 #77

Open
wants to merge 90 commits into
base: master
Choose a base branch
from
Open

Tracking Version 0.3.0 #77

wants to merge 90 commits into from

Conversation

jonschlinkert
Copy link
Member

Complete refactor.

This issue is for tracking progress against assemble-docs v0.3.0. This is a complete refactor.

I will be updating these issues, and the TODO's as we make progress. Please feel free to add your comments. There is still a lot to do, if you want to roll up your sleeves and help out, we'd love to have you! Pull requests are always greatly appreciated!

Complete refactor.
@jonschlinkert
Copy link
Member Author

General goals

In general, the goals for this refactor are:

  • generate the entire site with Assemble as before, but make the structure of the project an ideal way for newcomers to learn how to use Assemble. This has not been the case to date. Marking as done since the structure is already much better.
  • do a better job of welcoming newcomers and designers to Assemble. This means the content needs to be much more designer-friendly, and we need to have a much better introduction/getting started guide and documentation (see https://gist.github.com/jonschlinkert/9450158. this is just a start), some tutorials, a blog and ideally some videos.
  • better flow and transitions from section to section
  • better design for the home page (we might get some awesome custom icons from iconic!)
  • search. this might be challenging to do side-wide, but we filtering on each page would be a great start
  • add links to blog posts, tutorials and other write-ups about Assemble. Let us know if you've written one! Or if you happen to read one, we'd appreciate it if you could add a link to it here

Sections

See https://gist.github.com/jonschlinkert/9452935

Config

  • Use .assemblerc for global config, to make site variables easier to maintain
  • utility script to pull down Assemble's package.json, so the metadata can be passed to templates.

Plugins

Most of these will be published to their own projects (some are already), but I'm testing them here first. Any feedback/help in maintaining these as contrib plugins would be welcome:


  • search/filtering - initially filtering on each page, ideally site wide
    image

  • navigation plugin to automatically generate sidenav on each page
    image

  • anchors plugin to add linkable anchors to each section
    image

  • "link to source" plugin, to automatically generate a link to the source code for each section / file
    image

  • link-checker.js (courtesy of less.js / @lukeapage) - this is added, but still need to add credit to Luke in banner
  • 404 / holder.js plugin (courtesy of less.js / @lukeapage) needs attribution in banner
  • download plugin, to automatically pull down docs from other repos, helper docs in particular (usually .zip files, can be anything)
  • decompress plugin, to expand the zip files pulled down with the download plugin

Helpers

Same as with plugins, some of these will get their own repos. Some existing helpers will get upgraded with these.

scripts / jquery

  • quote rotation. we have a lot of quotes from users on twitter, etc. need something to rotate quotes

tbc

@pburtchaell
Copy link

Are you in need of any design related work with this PR? If not, I will gladly read though and edit documentation.

@jonschlinkert
Copy link
Member Author

I'm open to any kind of pr, although documentation in particular needs attention badly

Sent from my iPhone

On Mar 12, 2014, at 12:23 AM, Patrick Burtchaell notifications@github.com wrote:

Are you in need of any design related work with this PR? If not, I will gladly read though and edit documentation.


Reply to this email directly or view it on GitHub.

Patrick Burtchaell and others added 24 commits March 12, 2014 11:43
- Removed a few extra empty lines here and there
- Remove options.removeHbsWhiespace
- Add short examples to YFM options
- Move "YFM Custom Options" from H2 to an H3
- Rewrite example in the "custom variables" option
- Make examples more straightforward
- Add more context to the recommended naming scheme
- Merge "Include external content" example with "Markdown Includes"
example.
- Clean up the "Markdown block expression example"
…ds comments to these files to help others understand what's happening in the code.
Conflicts:
	content/docs/Workflows.md
	content/outline.md
Add remote-origin-url into package.json and add Typeplate to users list
@jonschlinkert
Copy link
Member Author

👍 great thanks! everything looks great. don't revert the commit, I guess the prefixer is something we could probably do without since we use less than 0.8% of our site visits come from IE 8 and lower (and we use less.js, so mixins should cover everything modern). But... given that it's a build step and we'll be using uncss, let's just leave it. At least the 0.8% might have a better experience.

Thanks a lot!

@jonschlinkert
Copy link
Member Author

btw, I know there hasn't been a lot of direct activity on assemble from @doowb and I recently, but we are working on assemble - can't say a lot yet but I think you'll be happy with what you see!

@pburtchaell
Copy link

No problem! Also, autoprefixer is great for checking to make sure you have all prefixes for all browsers in general. For example, when I get started on the homepage, I'll probably end up using Flexbox for some of the layout. Since the spec for Flexbox can be different between browsers, autoprefixer is a great tool to take care of it —which is the main reason I added it.

@jonschlinkert
Copy link
Member Author

Yeah, agreed it's a nice tool. We're probably going to either use autoprefixer in v2.0 of less.js or use it in a supported plugin for less.js.

Patrick Burtchaell added 3 commits June 8, 2014 22:55
It's worth noting as well that there isn't an -ms- prefix on these
properties. IE10 was the first browser to ship without a prefix on
these. The betas of IE10 did use the prefix however, so you may see
code using -ms-. It's not needed though.
- GitHub API requests are working
- Add Twitter cards, which will need to be approved by Twitter
- Add OG
- Add larger favicon support
@pburtchaell pburtchaell changed the title v0.3.0 - tracking Tracking Version 0.3.0 Feb 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants