jstjohn / flickribbon

Automatically exported from code.google.com/p/flickribbon
0 stars 0 forks source link

Setup code.flickribbon.com #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
<b>Task to be completed:</b>
Need to set up the blog (wordpress) and the docs wiki (mediawiki).
Need to import old wiki stuff and clean it up and re-organize it
Need to add some basic content to the blog pages.

This is definitely enough work for two people

<b>Goal behind this task:</b>
Have a development website.

Original issue reported on code.google.com by auzigog on 22 Dec 2008 at 11:51

GoogleCodeExporter commented 9 years ago

Original comment by auzigog on 22 Dec 2008 at 11:51

GoogleCodeExporter commented 9 years ago
Some wordpress plugins:
http://wordpress.org/extend/plugins/wptouch/

Original comment by auzigog on 22 Dec 2008 at 11:59

GoogleCodeExporter commented 9 years ago
Also, we need to set up google analytics for the wiki and the blog.

Original comment by auzigog on 22 Dec 2008 at 12:00

GoogleCodeExporter commented 9 years ago
Things I need:
Jeremy: Email me the admin login or make one for me so that I can add play with 
the
the blog and wiki. For the wiki I made a login username: eyerwolf could you 
make me
admin. Also could you point me to how you changed the wiki theme like for
fcwiki.auzigog.com

Original comment by danielmu...@gmail.com on 22 Dec 2008 at 7:28

GoogleCodeExporter commented 9 years ago
For wordpress, we need to install all the plug-ins we might use. We also need to
create an account for all the devs to blog (which I really hope everyone will 
do from
time to time!).

For mediawiki, I really want the themes to match. I used the current mediawiki 
theme
because it is close to the one on the blog. Someone needs to do the merging at 
some
point. If you want to do that, great, if not, Mike might be a good candidate.
Mediawiki themes aren't too hard to edit.

And yeah... Just add content to various pages. Especially the home page. That 
should
be styled and have boxes and look like other project home pages if possible. Go 
look
at a bunch of other open source projects to get an idea. :)

Also set up the sidebar so it has meaningful widgets in it, but not all the 
clutter.

Original comment by auzigog on 22 Dec 2008 at 8:22

GoogleCodeExporter commented 9 years ago
We also need GeSHi installed to do syntax highlighting on the blog and wiki.

Mediawiki: http://www.mediawiki.org/wiki/Extension:GeSHiCodeTag

I already installed the highlighter for wordpress but it isn't working. Probably
because GeSHi isn't installed on our server.

Also, if you could keep track of the things you do to set this site up and blog 
about
it, that would be great. I'll add the couple things I did to your blog before 
you
publish it (the .htaccess to get mediawiki working in a subdirectory of a 
wordpress
blog was the main thing I did). The blog should have all the plugins you used, 
it
should give a download option for the final versions of the themes. Etc. I'll 
post a
separate blog about setting up all the tools we used.

Original comment by auzigog on 22 Dec 2008 at 10:22

GoogleCodeExporter commented 9 years ago

Original comment by danielmu...@gmail.com on 22 Dec 2008 at 11:02

GoogleCodeExporter commented 9 years ago
Google analytics is setup for code.flickribbon with goals setup to monitor 
blog, wiki
visits.

Original comment by danielmu...@gmail.com on 23 Dec 2008 at 12:01

GoogleCodeExporter commented 9 years ago
Note for my self: Once skin is setup add google analytics to the main page
http://www.stoltenow.com/archives/2006/09/adding_google_a.html

Original comment by danielmu...@gmail.com on 23 Dec 2008 at 12:02

GoogleCodeExporter commented 9 years ago
A not about that blog you just linked to: That's the old style tracker code.

The new code can be found on google analytics. Adding it mediawiki is no 
different
than adding it any other site. Just add it right before the </body> tag in 
whatever
theme we end up using.

Original comment by auzigog on 23 Dec 2008 at 1:20

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
We could style our <code> blocks like this: 
http://github.com/cakephp/debug_kit/wikis

(block code and <code> inside a paragraph)

or like we do on fcwiki.

Original comment by auzigog on 23 Dec 2008 at 8:35

GoogleCodeExporter commented 9 years ago
Also, add this: http://wordpress.org/extend/plugins/footer-stuff/

So we can have the same footer no matter what theme we use (in case we change 
in the
future).

And you might try out this if you have CSS you want to add that would be used no
matter which theme we were using: http://wordpress.org/extend/plugins/mycss/
(you have to put my.css in the plugin directory after you install it).

Just some thoughts. Not totally necessary.

Original comment by auzigog on 23 Dec 2008 at 11:25

GoogleCodeExporter commented 9 years ago
Done with the wiki, start using it http://code.flickribbon.com/docs/Main_Page

Original comment by danielmu...@gmail.com on 24 Dec 2008 at 1:37

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I add user rights to the wiki, LocalSettings.php that only have users who are
confirmed to be
able to edit pages.

Original comment by danielmu...@gmail.com on 24 Dec 2008 at 4:08

GoogleCodeExporter commented 9 years ago
A almost feel like we should open it up to public edits. I mean it's not really 
a
wiki unless it can be edited quickly and anonymously by anyone.

The only reason we had it there was so we didn't forget to login. It's up to the
group whether we keep it in place for that reason.

Original comment by auzigog on 24 Dec 2008 at 7:58

GoogleCodeExporter commented 9 years ago
Remind me to give you the code to get "recent changes" to show up in the drop 
down
menu. I had to modify the theme of fcwiki to get it working.

And I also need to take down the old wiki. Hooray! We're making progress.

Original comment by auzigog on 25 Dec 2008 at 12:35

GoogleCodeExporter commented 9 years ago
I know we've already decided on a theme, but you guys know how I love to throw a
wrench in plans. :)

http://themehybrid.com/demo/options/

With some styling, it could look really cool. It looks a bit more like the TED
homepage that Tai liked.

Comes with a ton of built in templates for different page layouts. 

Just a thought.

Original comment by auzigog on 25 Dec 2008 at 3:57

GoogleCodeExporter commented 9 years ago
I ran across this for the WPCandy theme that we're using on the blog. Thought it
might be helpful:
http://wpcandy.com/articles/tutorials/wordpress-template-hierarchy-diagram.html

Original comment by auzigog on 25 Dec 2008 at 3:58

GoogleCodeExporter commented 9 years ago
I don't think I comment on this ticket enough. :D

http://yoast.com/wordpress/sociable/

Original comment by auzigog on 25 Dec 2008 at 4:57

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
http://wordpress.org/extend/plugins/subscribe2/
http://wordpress.org/extend/plugins/pagemash/
http://www.deliciousdays.com/cforms-plugin

http://wpcandy.com/plugins/plugins-we-use.html

Original comment by auzigog on 25 Dec 2008 at 6:50

GoogleCodeExporter commented 9 years ago
http://wordpress.org/extend/plugins/all-in-one-seo-pack/

Original comment by auzigog on 25 Dec 2008 at 7:00

GoogleCodeExporter commented 9 years ago
http://codex.wordpress.org/Function_Reference/add_post_meta

What do you think of their styling? I definitely think we should have the table 
of
contents float to the right.

I also like how their primary <h1> is styled grey and really big and their 
secondary
<h2> is styled "font-family:Georgia,"Times New Roman",Times,serif;"

I am posting way way too much stuff for you to do? Please just yell at me if I 
am.

Original comment by auzigog on 26 Dec 2008 at 6:24

GoogleCodeExporter commented 9 years ago
Also, we should have a google custom search for our site. Because mediawiki 
search
mostly sucks. And the wordpress search engine won't search the docs part of our 
site.

Original comment by auzigog on 26 Dec 2008 at 6:24

GoogleCodeExporter commented 9 years ago
Threw in many different plugins, activated All-in-one SEO, pageMash, Search 
pages &
posts. As we get more into blogging will activate plugins we need. Will go 
through
http://wpcandy.com/plugins/plugins-we-use.html

Next:
Play with the content page look in clean skin.
Add content to the home page and blog, blog about all my work.

Original comment by danielmu...@gmail.com on 28 Dec 2008 at 12:36

GoogleCodeExporter commented 9 years ago
Added a blog about editing blog & wiki,
http://code.flickribbon.com/2008/12/setting-up-blog-wiki-to-track-development/

Add content to home page, contact form.

Cleaned up rest of the UI.

Remaining:
* Change wiki content box look
* Google search instead of wiki search

Original comment by danielmu...@gmail.com on 31 Dec 2008 at 9:17

GoogleCodeExporter commented 9 years ago
Changed the content box in wiki: http://code.flickribbon.com/docs/Installation

Original comment by danielmu...@gmail.com on 31 Dec 2008 at 9:42

GoogleCodeExporter commented 9 years ago
Implemented and integrated google search instead of the built in wiki search. 
All our
websites are going to be indexed so search results will also search google 
code, wiki
and any other pages.

Original comment by danielmu...@gmail.com on 1 Jan 2009 at 9:42

GoogleCodeExporter commented 9 years ago

Original comment by auzigog on 3 Jan 2009 at 8:26

GoogleCodeExporter commented 9 years ago

Original comment by auzigog on 5 Jan 2009 at 10:22

GoogleCodeExporter commented 9 years ago
It would be cool if the issues tab and the discuss tab (which should be added)
actually pointed to a wordpress page with iframe of the embedded page. And a 
link to
jump out to the actual page.

Added a "project stream" page. Like a news feed for the project! Need to add 
icons to it.

Original comment by auzigog on 9 Jan 2009 at 1:31

GoogleCodeExporter commented 9 years ago
Oh. We should also connect our google calendar to our website and rss feed.

Original comment by auzigog on 9 Jan 2009 at 1:33

GoogleCodeExporter commented 9 years ago
I added the flickRibbon calendar to the blog. I don't think we should have 
iframes
for the issues tab, I want it to be separate like it is right now. I like the 
project
stream, what you mean by add icons to it?

Original comment by danielmu...@gmail.com on 12 Jan 2009 at 8:07

GoogleCodeExporter commented 9 years ago
If you go to configure the Lifestream plugin and click on a feed you can 
configure an
icon that goes next to it for each feed item. Instead of the default RSS icon. 
Like
for the google groups one, I converted the google groups fav icon to a png and
uploaded it.

Original comment by auzigog on 12 Jan 2009 at 9:52