Return to General talk

Changes to Documentations Wiki and update on Graphene 1.6

Home Forums Graphene WordPress theme General talk Changes to Documentations Wiki and update on Graphene 1.6

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #1995
    Syahir Hakim
    Keymaster

    Hi everyone!

    I just made some changes to the theme’s Documentation Wiki today, to better organise the content.

    Previously, the documentation for all options in the General Options have been lumped together in a single page. Even though the auto-generated TOC helps in finding a specific option, it isn’t organised in any meaningful way (except that the listing of options follow their order of appearance in the theme’s options page). The result is a messy-looking page with not-so-easy-to-find information.

    The same goes for the Display Options documentation page.

    The change that I made is to move the documentation of each option to their own page, and then categorise them so they can be easily found. This is the basic structure of the categorisation:

    + Basic configuration
    + General options
    - Individual options documentation, sorted alphabetically
    + Display options
    - Individual options documentation, sorted alphabetically

    See this page on how the categorisation looks like:

    http://wiki.khairul-syahir.com/graphene-theme/wiki/Category:Basic_configuration

    Secondly, I have also copied over some templates from Wikipedia for tagging incomplete pages. This produces a convenient listing to see which pages need attention and for what reason. See the following page:

    http://wiki.khairul-syahir.com/graphene-theme/wiki/Category:Articles_needing_attention

    A link to the above page is also available in the Documentations Wiki sidebar.

    That’s all the major changes there. I’m hoping to get traction back on populating the documentations wiki.

    As for Graphene 1.6, now that the holiday season is over, we’re back on full speed in version 1.6 development. Even though this upcoming version has comparatively smaller numbers of items in the changelog, it is by no means a small update. In fact, it will be one of the biggest update yet, as the new features that it will include are much more complex to implement.

    I am positive we can have the first alpha version available for testing in the next week or two. So if you would like to help test the theme, but haven’t signed up for it at the theme’s developers group, now’s the time to do so.

    And lastly, happy new year to all!

    #12992

    It looks good. Thank you.

    I don’t know if anyone else has noticed this, but when I go to Graphene’s WP site, I can’t rate it when I’m logged in. I remember seeing a thread somewhere (either here or on the WP forum) where someone else mentioned having the same problem.

    The theme’s rating has been the same for some time now, so I suspect this is a problem with that particular page. idk. I haven’t found a place on the WP forum to bring it to the attention of someone over there who could take a look.

    Cheers,

    Ken

    #12993
    Syahir Hakim
    Keymaster

    Hey Ken,

    Thanks for the heads up on the rating issue. I’ve forwarded it to the appropriate (I think) mailing list in WordPress.org. We’ll see how it goes.

    #12994
    Prasanna SP
    Member

    Yes, I’ve also noticed the rating issue in WP theme repository. I can rate plugins, but not the themes.

    Well, I would like to become a beta tester this time.. 🙂

    #12995
    Syahir Hakim
    Keymaster

    Somebody in the mailing list suggested this:

    Quote:
    Log out of your account and go to the wp theme homepage and log in there. That what I needed to do

    #12996
    Prasanna SP
    Member

    No, it didn’t work either. It just shows “Your Rating” block. But there is no option to rate it!!

    #12997
    Prasanna SP
    Member

    Hmmm.. might be a DB error. Just saw this thread – http://wordpress.org/support/topic/how-do-i-rate-a-theme

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.