|
|
| Line 55: |
Line 55: |
| | | | |
| | <div class="phrase"> | | <div class="phrase"> |
| - | <h2 style="width: 220px;"><span>This is our blog.</span> <span>It's not the journal.</span></h2> | + | <h2 style="width: 500px;"><span>We've been diligently journaling our progress.</span> <span>Have we?</span></h2> |
| | </div> | | </div> |
| | | | |
| Line 68: |
Line 68: |
| | </div> | | </div> |
| | | | |
| - | <div class="container blog"> | + | <div class="container diary"> |
| - |
| + | |
| | <article> | | <article> |
| - | <div class="line"><h3 class="posttitle">The Incredible Awesomeness of the First Post</h3><span class="date">24.05.2012</span></div>
| + | <h3> A very up to date journal</h3> |
| - | <span class="author">Jason</span> | + | <p> The journal is not ready yet. We have a <a href="https://2012.igem.org/ Team: UNITN-Trento/Blog">Blog page</a>, which is not the same thing, but we' ll be posting impressions there. Also, check out our <a class=" facebook" href="http://www.facebook.com/UniTNiGEM " target="_blank">Facebook page</a>.</p> |
| - | <div class="post">
| + | |
| - | <p> Hi everyone! I'm not sure how many "everyone" includes as of right know, since I'm not sure how many team members are already thinking about the Wiki. | + | |
| - | Being myself a web designer in my spare time, we're already on the Wikimedia train (I'm sure you've seen me cluttering the <a href="https://2012.igem.org/ Special: RecentChanges"> Recent Changes page</a> in the last few days), so I've decided to put up this little Blog page , in addition to the Journal. | + | |
| - | I'll have the others post something too.
| + | |
| - | </p> | + | |
| - | <p>The journal is still a work in progress (actually, it's kind of a mess), and I don't think it would be very useful until it's ready. But I also want to have a place to share our opinions during this exciting iGEM let's-call-it journey, so here it is.
| + | |
| - | </p>
| + | |
| - | <p>I'm gonna start with my thoughts on Mediawiki and some tips to manage to do something.
| + | |
| - | I say "manage", because, you know, Mediawiki sucks.
| + | |
| - | I have experience with other CMSs, Wordpress, Tumblr, ExpressionEngine, even some niche stuff like Kirby (if you do web design, check it out!), but this thing is bloated. I can't make myself like it, since I think it's overly complicated.
| + | |
| - | It's a wiki engine, so it should be much easier to use, since everyone should be able to edit things easily.
| + | |
| - | Just the action of editing content is a mess: take a look at Tumblr, for instance, it's much easier and self-explanatory. There's a clear separation between "Theme" and "Content" (the way it should be for non-experts), that here is very subtle. And it's beautiful: let's say it, the Dashboard is dead-ugly, and the themes feel like we're still in the 90s.
| + | |
| - | That said, I don't know other Wiki engines, so I can't compare it with others. It could be the best option.
| + | |
| - | </p>
| + | |
| - | <p>I still think a basic Wordpress installation would be simpler. Good-old HTML+CSS files even better, but that's just my opinion.
| + | |
| - | </p>
| + | |
| - | <p>Enough with the criticism, let's see some tips.
| + | |
| - | What I've been doing is creating the website on my local machine with .html and .css files, then creating the pages I needed here on Mediawiki, placing an html tag in the content box, and pasting everything inside the html tag of my file inside. Here's an example:
| + | |
| - | </p>
| + | |
| - | <img src="img/blog/0524-Jason.png" alt="0524-Jason" width="500" />
| + | |
| - | <p>What Mediawiki does is parse all that as HTML, in so doing achieveng our goal
| + | |
| - | Some notes: don't put the <!doctype html> definition, it's already in the Mediawiki template.
| + | |
| - | Notice that the stylesheet has to be hosted somewhere on a server, or it won't work, so be sure to specify the full url of the .css file.
| + | |
| - | </p> | + | |
| - | <p>For this to work, you also need to hide the default theme elements, so they don't display. It will be specific to your needs, just use the Web Inspector of your browser to find what the main.css file (the one Mediawiki is using) is saying, and correct in on your file, it will override the styles.
| + | |
| - | Ah, another important thing to consider are the Mediawiki controls (Edit, Recent changes, blah, blah): you'll have to add those manually, in order to keep them. Many are useless, but the Edit link is essential to you.
| + | |
| - | I hid them in the footer, making them display when the "Toggle Controls" button is clicked.
| + | |
| - | </p>
| + | |
| - | <p>You could also make a new Mediawiki template, but I gave up on that a long time ago, I find my way simpler.
| + | |
| - | Team DTU-Denmark made <a href="https://2011.igem.org/Team:DTU-Denmark/How_to_customize_an_iGEM_wiki" target="_blank">a nice page about it last year</a>, so check it out if you're interested.
| + | |
| - | </p>
| + | |
| - | <p>I believe that's all, I hope it will be of help (and that someone reads my rambling).
| + | |
| - | If you have questions, feel free to ask, please contact us on our <a href="http://www.facebook.com/UniTNiGEM">Facebook page</a>, I'll get back to you as soon as possible.</p>
| + | |
| - | </div>
| + | |
| | </article> | | </article> |
| - |
| + | </div> |
| - |
| + | |
| - |
| + | |
| - | </div> <!-- end blog --> | + | |
| | | | |
| - | </div> <!-- end main --> | + | </div> |
| | | | |
| | <div class="footer"> | | <div class="footer"> |
| Line 156: |
Line 118: |
| | })(); | | })(); |
| | </script> | | </script> |
| | + | |
| | </body> | | </body> |
| | </html> | | </html> |
"
