Changes between Version 1 and Version 2 of create

Timestamp:

Oct 18, 2017, 9:15:28 PM (8 years ago)

Author:

Jamie McClelland

Comment:

--

create

@@ -14 +14 @@
  * If there are two pages for the same topic, one that is user facing and one that is admin facing, try to make the names reflect that. For example "mumble" could be the name of the user facing page and "murmur" could be the name of the admin facing page (since murmur is the program running on the server). You could also create mumble-acls page to instruct admins on how to setup permissions. When all else fails, add -admin to the name of the page.
 
+''Implementation details:'' We would need to convert all existing names that don't follow this protocol to better names. This could be partially automated, but would require a lot of human intervention to get things right. We should also strive to create automatic redirects from old page names to new page names.
+
 == Choose a wiki type ==
 
@@ -22 +24 @@
 
 You can choose one or the other by adding either `how-to` or `doc` as a tag. If you fail to add on or another, you will get an error message when you save.
+
+''Implementation details'' - If it was possible to create custom wiki fields, I would opt for a custom wiki field. But, not sure that's possible. If we go with tags, I think we should write a simple plugin that ensures one of these two tags is entered for every wiki page and prevent saving if it is not. 
 
 == Choose the audience ==
@@ -39 +43 @@
 Each item in the breadcrumb should be separate by a pipe (|). You must include the page name. Optionally add a colon followed by the display name if you want it to be different from the page name.
 
+''Implementation details'': this will require a plugin to be written. I don't see anything that does this. Also, this step should happen before page renaming - so that we can first take all pages like projects/membership-meeting/2017/timeline and create a breadcrumb for them in a way that is consistent with how we envison renaming them.