Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
wiki:editors_lounge [2014/02/20 15:51] – contrapunctus | wiki:editors_lounge [2014/03/23 23:40] – [Extend newbie introduction article] digisus | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Editors Lounge ====== | ====== Editors Lounge ====== | ||
- | This page should provide some space for editors | + | In this page we will discuss about how to edit this wiki, ad what kind of plans we have. |
- | Please feel free to add/ | + | Currently there are two sections: [[# |
===== Hardware support ===== | ===== Hardware support ===== | ||
Line 69: | Line 69: | ||
As the HW DB is still in its infancy, any suggestions to the rating system or the entry layout are still welcome - it will be difficult to change them as it grows. | As the HW DB is still in its infancy, any suggestions to the rating system or the entry layout are still welcome - it will be difficult to change them as it grows. | ||
- | What's still missing is a way to list things based on tags in a more advanced way. Right now users can only see all pages under one tag. It'd be way more awesome if they could see, for example, everything | + | What's still missing is a way to list things based on tags in a more advanced way. Right now users can only see all pages under one tag. It'd be way more awesome if they could see, for example, everything with tag A AND tag B..., entries with tag A but NOT with tag B, entries with tag A OR tag B..., and combinations of these. |
I discussed it with rgareus, but I did not (and still do not, sadly) have the time to look into the solution he gave me. Someone with skills in web development and some time to spare should help us with this. If we have this capability on the wiki, all three sections of the wiki would benefit greatly. - [[wiki: | I discussed it with rgareus, but I did not (and still do not, sadly) have the time to look into the solution he gave me. Someone with skills in web development and some time to spare should help us with this. If we have this capability on the wiki, all three sections of the wiki would benefit greatly. - [[wiki: | ||
- | ===== Brainstorming for a todo-list ===== | + | Significant changes to the HW DB today - |
+ | * Edited /hw/start , more clarity in ratings among other things. | ||
+ | * The Behringer BCD3000 entry is no longer the sample reference page, it has been replaced by [[http:// | ||
+ | * All the sections of fields on the (new) sample page (linked above) need not be included if they do not apply to a device - e.g. the 'MIDI interface' | ||
+ | * A more user-friendly HW DB submission page is coming up, courtesy nido. He may also help us with better tag listing. | ||
+ | * Updated the Behringer BCD3000 entry to the new format. | ||
+ | --- // | ||
+ | | ||
+ | * Better use of headlines, the page header for instances should use a Level 1 Headline. Unless you specifically do not want a TOC but I don't think using no TOC is desirable. | ||
+ | * Using a box might look a bit more visually appealing but can get in the way of code blocks or other layout options. | ||
+ | * The reference page lacks Linux specific details like ALSA device name or example JACK settings (see [[wiki: | ||
+ | * Categories != tags. Afaik this DokuWiki doesn' | ||
+ | --- // | ||
+ | |||
+ | Hey, Jeremy. | ||
+ | * Level 1 Heading - done. | ||
+ | * Box - I don't see any imminent issues. If and when the need arises, we can change it. | ||
+ | * Example JACK settings can be written in the notes area, I'll add a mention of this in the sample soon. | ||
+ | * ALSA device names can be useful. Is there a list of them somewhere? | ||
+ | |||
+ | (for others reading - it was clarified by Jeremy later, on IRC, that the tags -are- creating categories) | ||
+ | |||
+ | nido suggested yesterday that perhaps an actual DB is better for this. I'm inclined to agree. I'm scheduled to speak to him today, will update. | ||
+ | |||
+ | --- // | ||
+ | |||
+ | HW database looks nice! I added information about my soundcard, and process went ok. Template was a little bit hard to understand, but otherwise it was straightforward. Submission form would be easier method though. I think that could be achieved with Bookmarklet like we have in app submission (see http:// | ||
+ | |||
+ | I also got idea when added my card: should there be general tags for input? Like in_xlr or in_spdif? Now we have tags based by type and amount of inputs, like in_xlr_2 | ||
+ | |||
+ | Next big thing would have some kind of search functionality in frontside of HW database. Possibly based by tags. It really should be interactive, | ||
+ | |||
+ | --- // | ||
+ | |||
+ | Hey, happy to see your entry and that you dig the HW DB, hekkiket :) | ||
+ | |||
+ | It seems like a HWDB on an actual database will finally be a reality, thanks to nido. A submission form as well as a dynamic (interactive) UI for the wiki-based index was being considered earlier (the current template was the best I could do, but it is naturally no match for a submission form :) ), but no point any more, for as the new DB comes up, it'll have it. I just saw the Bookmarklet mere hours before I saw this post - it is indeed excellent. | ||
+ | |||
+ | Not sure what you mean about ' | ||
+ | |||
+ | HW-Index entries for the wiki will get replaced by the RDBMS-implementation when it comes, but it's easier to transfer entries to the new DB when they' | ||
+ | |||
+ | raboof moved some old hardware pages to /hw/start. It'd be cool if someone converted these to the HW-Index format, I'll be doing as many as I can find time for. | ||
+ | |||
+ | A note regarding HW-Index entries - posting links to insightful forum posts, ML discussions, | ||
+ | |||
+ | * info from link1 | ||
+ | * more info from link1 | ||
+ | * ...etc | ||
+ | from $link1 | ||
+ | * info from link2 | ||
+ | from $link2 | ||
+ | |||
+ | That way, the links are there to acknowledge sources, yet the user doesn' | ||
+ | |||
+ | --- // | ||
+ | |||
+ | ===== TODO-list for wiki ===== | ||
Please add, comment, etc. | Please add, comment, etc. | ||
- | ==== Get the newbie | + | ==== Extend |
- | [[wiki: | + | [[wiki: |
- | It should structure itself around different user stories and provide some starting points and guidance | + | |
- | Comments welcome. | + | |
- | I wrote a [[wiki: | + | Being a newbie myself, |
- | --- // | + | |
- | ==== Add release date and version to all applications in the database | + | --- // |
- | Seems like a dull job, is a dull job, but it should provide a better experience of this wiki once you can sort by it and | + | ==== Update |
- | hide e. g. 10 year old apps where you don't even get the source because a site vanished... | + | |
- | Proposed starting point: Categories listed on the front page: | + | Mark [[apps:start|application entries]] with tags: [[apps: |
- | * [[apps:categories: | + | |
- | * [[apps:categories: | + | |
- | * [[apps:categories: | + | |
- | * [[apps: | + | |
- | * [[apps: | + | |
- | * [[apps: | + | |
- | * [[apps: | + | |
- | * [[apps: | + | |
- | * [[apps: | + | |
+ | Please update also release date and other information while visiting at project pages. | ||
+ | |||
+ | --- // | ||
+ | |||
+ | ==== Update application lists ==== | ||
+ | |||
+ | Hide entries tagged with [[apps: | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | --- // | ||
==== Recommended Applications ==== | ==== Recommended Applications ==== | ||
Line 106: | Line 161: | ||
* a " | * a " | ||
* later we could focus on such entries and extent specifically this entries | * later we could focus on such entries and extent specifically this entries | ||
+ | |||
+ | I suggest we will extend [[introduction]] article and link it to other articles. Those other articles will offer recommended choices for new user. If no such article exists, we would then write it. What do you think? | ||
+ | |||
+ | --- // | ||
==== Redesign front page ==== | ==== Redesign front page ==== | ||
+ | Front page must have balance between offering information and showin links. Mainly it's for navigating to the contents of wiki. Some images would be nice also. | ||
+ | |||
+ | --- // | ||
+ | |||
+ | Thought the same, started on it today. | ||
+ | |||
+ | --- // | ||
+ | |||
+ | ==== Tutorials page === | ||
+ | I think it would be more user-centric to have all the tutorials on the respective app pages. That would mean, the tutorial page would be deleted after all tutorial links have been moved. Thoughts? | ||
+ | |||
+ | --- // | ||