laravelio / laravel.io Goto Github PK

lock forums
change design to remove theme / navigational elements
make a prominent highlight redirecting to new forums

Paste foundation allows for files to be pasted or dragged into the window. Pastes can be saved. Users can comment on pastes and the comments can be rated. Pastes can be published by their owner globally so that people can see a breakdown of the problem and the solution.

The goal of the additional mechanisms being added is to turn what is normally only IRC-based help into a persistent resource available via Google or our own site. This can help us make the most out of the volunteer help provided by the community.

This page should pull from GitHub and list people who have contributed to the app in as cool a way as possible.

The exact algorithm for this needs to be determined. But, the general goal is to allow as much community self-management as possible.

This is a general overview of all the features that the new laravel.io website will have. We'll use this as an overview to check for things missing and to check off features which are completed.

Initial development is being handled by the core team to ensure that the conventions / vision are established. Should one feel like contributing in some way to the completion of this list, definitely comment first on the individual task.

General

• Document coding conventions (#12)
• Decide on workflow for assets management and design tools (#11)
• Add Mandrill for email transaction (#24)
• Add soft deletes to everything (#25)
• Automate database backups (#26)
• Add maintenance page (#28)
• Add google analytics (#29)
• Add hosted by FortRabbit (#36)
• Contributors: create contributors page (#42)
• Contact: enable contact (#43)
• Add Laravel Weekly Subscription Form (#45)

Homepage

• list featured blogs and forum posts (#22)
• define the site (#23)

Users

• Enable Github authentication
• Add user profile page (#18)
• Add dashboard with subscribed forum threads (#20)
• Hide profile of banned user (#44)

IRC

• properly segment out pre auth and post auth chat (#47)
• Design chat page (#31)

Articles

• Allow users to create articles (#3)
• Add RSS feed (#5)
• Allow admins to lock articles (#6)
• Integrate tagging system (#7)
• Add Markdown editor (#8)
• Enable comments (#9)
• Decide which stats should be kept (#21)
• Design (#34)
• Add Laravel version indicator (#39)

Forums

• Determine starting sections (#48)
• Add Markdown editor to posts (#13)
• Stress test and optimize (#15)
• Allow users to subscribe to topics (#19)
• Design (#32)
• Create initial post explaining the site (#37)
• Old Forums: prepare for hibernation (#1)
• Old Forums: move them to an archive url (#41)

Pastebin

• Create initial foundation (#17)
• Design (#33)

Launch

• Change all caching / sessions to memcached (#46)
• Last minute double-check of all sql queries loaded per page (#27)
• Browser test / site responsiveness test (#30)
• Upgrade hosting (#35)
• Send mailer (#40)
• Write article that explains the site (#38)

They're hosting us for free, add a sponsorship message for courtesy.

We need to have a documented workflow explaining the policies for the assets and design tools used.

Shown during deployment while migrations / seeds run.

Give a new user a way to frame the site. Keep it as minimal as possible.

Identify users as contributors if they've contributed to the laravel-io repo.

Use Cloudinary for image hosting. Free plan. If needs ever expand, we find a sponsor.

In some ways it sucks, but it probably needs to happen anyway.

The user profile page is basically a link off to the user's content.

What is the best way to keep stats on these?

We'll move the old forums, then provide an htaccess that will do 301 redirects to it. In this way, FluxBB URLs will redirect to the archive location and be updated in Google. Additionally, we'll regain the option to use forums.laravel.io for our new forums.

list featured blogs and forum posts

So people can easily subscribe to the Laravel Weekly newsletter. The source code Mailchimp provided can be founded below.

<!-- Begin MailChimp Signup Form -->
<link href="//cdn-images.mailchimp.com/embedcode/slim-081711.css" rel="stylesheet" type="text/css">
<style type="text/css">
    #mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
    /* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
       We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
</style>
<div id="mc_embed_signup">
<form action="http://laravelweekly.us7.list-manage.com/subscribe/post?u=60fa14809d4de70a885daf382&amp;id=0e7e4b3c30" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>

    <input type="email" value="" name="EMAIL" class="email" id="mce-EMAIL" placeholder="email address" required>
    <div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div>
</form>
</div>
<!--End mc_embed_signup-->

Locking is a functionality that prevents an article from being modified by users who are not admins. The owner can still delete the article.

Determine the forum sections that we'll launch with. Currently, I'm thinking about a laravel 4 help section a laravel 3 help section, and a laravel io section (discussing contribution and the nature of the site).

Any discussion on this topic is naturally welcome.

Development conventions should be roughly documented to assist in managing contributions.

Mail blast their ass off so that everyone knows about the new site and starts creating content so it doesn't seem empty.

Create a clearly identifiable opportunity to contact the people managing the site. Before this, we probably want to think it through and make sure that it's implemented in a way that isn't a bad idea.

All user-generated content is produced and stored in Markdown.

Upgrade the hosting provided for free to us by FortRabbit.

I didn't get around to doing that.

Since this site is designed to allow the community to manage itself, a rating system is necessary to determine what content should be promoted and what content should be removed.

We must analyze various options, measure the strengths and weaknesses of each and design one for pastes, articles, and forum threads.

Before users can sign into chat, they either have to authenticate or acknowledge that they're lazy. This is currently hacked in, doing it better will only take a moment.

I wonder why the categories, articles and sidebar inside the HTML have a ID.. is it being used in JS or any other part of the application? i would suggest to drop the ID and only use it for javascript things... I allready added some classes to handle the styling.

Stress test the forum to identify capacity and any notable performance issues. The current laravel.io forums get about 18k pageviews per day, so we need to be able to match that and then some.

Forum posts need some kind of editor to ease the trouble of adding links, etc.