wecodemore / wordpress-gear Goto Github PK

As a follow up to #119 … details in this GH blog post

• Add .github directory
• Add .gitignore
• Add CONTRIBUTING.md
• Add ISSUE_TEMPLATE.md
• Add PULL_REQUEST_TEMPLATE.md

can be fixed by applying box-sizing: border-box to header element and display: inline-block to #header-wrap
but that moves the header elements to the left by 10-20px

Seems relevant: http://wppb.io/

Nice project.
Maybe you will als add hints to two projects:

Debug Objects - Debug Plugin with a lot of stuff
WordPress Basis Theme, Starter with php5.3 and small helpers

Best

The links to the nightly & stable builds just leads to the wordpress.org download page. If this is intentional, please disregard.
Misread the page, never mind.

The test data provided by WP Test would be very useful for theme and plugin developers in my opinion. Just wanted to let you know. (via WPSE chat)

Hi,

Thank you very much for the useful page!

I would like to make the Japanese version of your page, so I was wondering under what license the page is.

Of course I will always include something like "The page is based on WordPress Gear (http://wpgear.org/)".

Instead of just mentioning http://wycks.github.com/WordPress-Gear/ in the README, you can put it up in the URL field (above the ZIP button: https://github.com/wycks/WordPress-Gear)

For some reason github is not grabbing @ , maybe it needs to be in markdown.

In an effort to rework the design of WPGear.org I am submitting some sketches and ideas for public review and further discussion.

I'd like to keep the font of the logo (Font: Copse) as well as the primary color (Red: #d54e21) associated with a new color (Dark Blue: #3b596a). In reference to WordPress all icons are taken from the Dashicons iconfont.

For each section, plugins are displayed as cards together with the important metadata of the plugin.

More advanced users can search/filter the cards to display metadata necessary for developers.

Plugins with lot's of extensions can be grouped as collections for a clean visual structure.
Moreover, there are elements (suggest and edit) to increase participation and up-to-dateness of the information on the site.

Following up on the discussion in PR #103, I'm working on a PR which will have several links for some tools - especially plugin based ones -.

Layout wise, I'd like to hear some opinions on how this should look.

Option 1:

• [Plugin name linked to WP Repo](https://wordpress.org/plugins) \[[GH](https://github.com)\] - description

Option 2:

• [Plugin name linked to GH Repo](https://github.com) \[[WP](https://wordpress.org/plugins)\] - description

Option 3:

What do you think ?

IMHO Option 3 would look cleanest, however, will make editing/PRs more error prone.

We should have at least some basic analytics to see what people are actually searching. Enhancing the experience else is a guessing game.

Twitter, facebook, Google+, all have meta tags and there's microdata to be added. Currently the site has zero share value for anyone on those platforms. We should change that.

Basic Links to vendor docs

• Tweet Button
• Twitter "follow" Button
• facebook share link
• LinkedIn Share button
• Twitter Cards
• microdata (Google MarkUp Helper)

Additional links, ideas and constraints

• Use Shariff or similar for better sharing experience (performance wise)

Is Gears PHP 7 compatible?? I tried to run it through a PHP 7 Plugin Compatible software but it keeps coming back as too large to review.

If you move the header/footer to a file called _layouts/default.html and then move index.html to index.md GitHub pages will automatically compile everything from markdown to HTML every time someone pushes to GitHub.

The advantage is that folks that do not know HTML can contribute, and folks that do, can contribute a lot easier, both without losing the ability to edit from GitHub directly (or via Prose, etc.)

Took a first pass at it and glad to spend more time if there's interest.

Let's face it: Building is boring. We can automate that.

The current document outline is somewhat confusing in a semantic as well as in a visual way:

This button-like highlighting of »Unit tests« is a paragraph and gets followed by an h5 with the text »
Unit Testing and profiling«. So from a readers perspective the headline is duplicated. From a semantic perspective it is one headline and one paragraph that belongs to the section before.

I think we should talk about splitting the content into static pages. Using 5 levels in the outline is an indication that the structure is way to complex.

https://github.com/noeltock/prometheus

The link to the repository WPX is dead.
WPX - Make it easier to use WordPress as a CMS

Via settings in the top right corner. Will save developers the extra click of viewing on the web interface and will simplify git cloning.

I was very intrigued by the idea of a "child theme merger" type of tool that was described in this interview (search "child"):
http://build.codepoet.com/2013/06/20/bowe-frankema-interview/

I followed up on it, and apparently it's closed source for now:
https://twitter.com/BoweFrankema/status/348040188867518464

So I'm wondering, does anyone know of any other ways to go about doing this? Can any of the build/theme tools listed on wpgear.org be used for this already?

Original theme links scroll with an offset and overlaps current anchor links.