laraveluk / website Goto Github PK

The User Journey for Posts is a bit strange. First you click on the Post title from the excepts to see the full post, then click Edit Post button and then click 'Edit' button. This needs to be changed to the following steps;

1. Click on the post except title to see the single page post
2. To Edit, click on the edit button to the Edit form
3. Make changes and Save.

We have a front end nav and back end nav.

In a perfect world these would become one partial, which is used for both.

When you are not logged in you see the login button, when you are logged in you see the login button. This all needs to be changed to be more dynamic.

I'd like to defer to the <navbar> vue component.

Backend Blog Index should defer to the Frontend Blog Index

When creating a new blog post, you should be redirected to /blog/{slug} on the front end, not on the back end.

All the back end needs is /members/#/blog/create and /members/#/blog/SLUG (for editing and deletion).

At the moment when creating a post, a user can add as many tags as they like and also can name them anything.

I propose that we switch the tags to a select dropdown, where a user can then select the tags they want, and as many as they like, or also limit them to 3.

Similar to StackOverflow, we can eventually add a point system in where they can then earn the right to add tags etc.

The idea of this is to prevent the saturation and the number of tags that are created.

Like to know your thoughts

The drop-down SVG arrow for post type is a way of the page and is disjointed from the select element.

If you view the image you will see it highlighted on the right :-)

Create Post Image Select issue image

I'll have a look at this probably just to let you know.

Seems to happen when someone is already signed into another slack workspace - can replicate.

When not logged into another workspace the workspace url isn't pre-filled so I'm wondering if something is missing from setup?

We need a home page!

At the moment when any user log's in, they cannot only edit a post but also delete the post. We should ensure that ONLY the post's creator and/or a moderator/admin are able to edit these.

So there is a need to add some form of permission role system.

I'm not sure what your goals are for the site, with regards to users freedom, but there should still be some form or moderation applied to the submission of content, especially for legal reasons.

The way that the page produces the metadata is to use the current post title. This is wrong, as its displaying the title for both title and description. Also, the facebook metadata formation is also wrong.

I suggest further updating the post create/edit to incorporate an Excerpt section. Which will be text only so no wysiwyg editor but a plain textarea.

As well as feeding the post listings excerpts copy, we could then use this to feed the metadata description fields.

Also reformatting the metadata from within the main page views to a partial, so that it's just the one file and there for as the site grows prevents us from updating several pages. Also adding further metadata to include twitter.

I am willing to work on this section if needs be.

an example would be switchin out:

<title>LaravelUK - {{$post->title}}</title>
    <meta name="title" content="LaravelUK - {{$post->title}}" />
    <meta name="description" content="LaravelUK - {{$post->title}}" />
    <meta name="og_title" content="LaravelUK - {{$post->title}}" />
    <meta name="og_description" content="LaravelUK - {{$post->title}}" />

for
partials/metadata.blade.php

       <title>{!!$post->title!!}</title>
       <link rel="canonical" href="{{ URL::current() }}">

       <meta name="title" content="{!!$post->title!!}" />
       <meta name="description" content="{!!$post->title!!}" />
        <meta itemprop="image" content="/imgs/socials/twitter-share-image.jpg">

        <meta property="og:type" content="website">
        <meta property="og:url" content="{{ URL::current() }}">
        <meta property="og:title" content=""{!!$post->title!!}">
        <meta property="og:image" content="/imgs/socials/facebook-share-image.jpg">
        <meta property="og:description" content=""{!!$post->excerpt!!}">
        <meta property="og:site_name" content="Laravel UK">
        <meta property="og:locale" content="en_GB" />
        <meta property="og:image:width" content="1200">
        <meta property="og:image:height" content="630">

        <meta name="twitter:card" content="summary_large_image">
        <meta name="twitter:site" content="@UKLaravel}">
        <meta name="twitter:creator" content="@UKLaravel}">
        <meta name="twitter:url" content="{{ URL::current() }}">
        <meta name="twitter:title" content=""{!!$post->title!!}">
        <meta name="twitter:description" content=""{!!$post->excerpt!!}">
        <meta name="twitter:image" content="/imgs/socials/twitter-share-image.jpg">

There's a few more metatags that can be used but the above is just an example. :-)

Could be embedded on homepage or on it's own page

Simons interview link is missing on the about page: https://laravelphp.uk/about

Blog links go to here: https://localhost:3000/blog/events/laravel-london-september-2017

https://laravelphp.uk/blog

Per a discussion in the slack channel - I will add a moderation queue for blog posts, as all members of the site may create them.

We should use Laravel Shift to upgrade Laravel to 5.7 (and then to 5.8)

As title.

feature request - ability to wrap code with code blocks in posts

https://laravelphp.uk/members#/

https://laravelphp.uk/login

This page, i guess, is supposed to look like the sign up page, but apparently, it looks weird.

I am not a front end developer or a web designer, so i have no PR.

Sorry.

I just want you guys to know about this issue. Thanks.

This page looks weird on Chrome but it's good on Edge

My Chrome is Chrome Version 67.0.3396.99 (Official Build) (64-bit)