Difference between revisions of "Main Page"

From AtoM wiki
(Releases: Added a still-to-do section so we don't forget what needs finishing here)
(Still to do: Added link and notes to Roadmap page vision)
Line 93: Line 93:
 
* [[Releases/Release announcements/Release 1.3]]
 
* [[Releases/Release announcements/Release 1.3]]
 
* [[Releases/Release announcements/Release 1.3.1]]
 
* [[Releases/Release announcements/Release 1.3.1]]
 +
 +
* [[Releases/Roadmap]]
 +
Our vision! Time to implement! We should have sections for things that we know are going in releases (e.g. we can start documenting 2.2 features in a section here, for example... will make it easy to move to a release announcement page later) and we should have a "Wishlist" section. Ideally, this would be short, bullet-list like - but where we have thoughts/wireframes/ideas/issue links/costing estimates, we can create a page in /Development for the feature, document it more thoroughly there, and then link.
  
 
== Resources ==
 
== Resources ==

Revision as of 16:24, 13 August 2014

Welcome to the Access to Memory wiki

TO DO

PRO TIP: Extension to add nice page titles is now installed! So if you have a page like "Community/Users", you can now add the following at the top

{{#pagetitle: Users }}

... and it will change the display, while keeping the nice hierarchy we have made. REMEMBER to make sure that a nice breadcrumb has been added first. Check out the Users page as an example.

You can also give links to pages that same clean look like this:

[[Community/Users|Users]]

More on this extension can be found here: https://www.mediawiki.org/wiki/Extension:PageTools

SUGGESTION:

I've noted that changing the page title display does not actually change the page name - so searching for "Users" will not bring up a result in the autocomplete for search (only searching for Community/Users will).

My suggestion, to at least try to make this more clear, is to keep the original page name in the breadcrumb - i.e. since the page you are on is not actually entered as a hyperlink when manually creating the breadcrumb, we might as well leave it as the full page name.

So.... NOT LIKE THIS:

[[Main Page]] > [[Community]] > Users

BUT LIKE THIS:

[[Main Page]] > [[Community]] > Community/Users

Community

  • Add Category: community to each page
  • Add to URL /Community/...

Pages already created

Development documentation

  • Add to Category: Development documentation
  • Add to URL /Development/...
  • Have not yet made: landing page for "Development" itself

Pages already created

Releases

  • Add all pages to Category: Releases
  • Add to URL /Releases/...
  • Landing page for Releases created

Pages already created

Still to do

Our vision! Time to implement! We should have sections for things that we know are going in releases (e.g. we can start documenting 2.2 features in a section here, for example... will make it easy to move to a release announcement page later) and we should have a "Wishlist" section. Ideally, this would be short, bullet-list like - but where we have thoughts/wireframes/ideas/issue links/costing estimates, we can create a page in /Development for the feature, document it more thoroughly there, and then link.

Resources

  • Add all pages to Category: Resources
  • Add to URL /Resources/...
  • Landing page for Resources created

Pages already created