Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help Reshape The Structure Of Certain Ulog-Subtag URL-space, To Look Like 'Communities'. - Plus 100 steem #183

Closed
surpassinggoogle opened this issue Jan 17, 2019 · 1 comment
Milestone

Comments

@surpassinggoogle
Copy link
Owner

surpassinggoogle commented Jan 17, 2019

Complexity

Pretty Easy

Task

You will need the components created in #181 and #182 for this task.

In this task, we would like you to modify the structure of certain ulog-subtag-URL-spaces (prior/after-login), by adding more components to these pages, turning them into ulog-communities.

Below, i will cite the list of existing ulog-communities across ulogs.org, so that you easily find each:

Then, two core communities that form part of the ulogs.org ecosystem:

The general UI-structure for each of the addresses enlisted above, will now look like the image shown below:
new ulog design

Looking at the image above, just under the 'Overseeing Uloggers' column, you will need to add an area for labelled 'Direct Messaging' & 'Ulog-Games/Exchanges', that users can expand at will.

When they expand each of these areas, it will open the following components:
1.
new ulog designs
2.
image

Read more about these two components on #181 & #182

Now, the 'About Community' Column, will be titled according to the name of the Ulog-Community. I can provide you the 'raw text' for each one, when you take up the task.

On the 'About Community' column, you will notice the 'Post Now' button! We currently have 5 ulog-communities that have "dedicated post-editors". This means that the 'Post Now' button for these 5 ulog-communities should lead directly to respective dedicated post-editors.

Below, i will enlist the 5 ulog-communities and the URL for their respective dedicated editors:

Bonus:

As for the remaining 'ulog-communities' that don't yet have their own 'dedicated editor', their 'Post Now' button should all lead to 'https://ulogs.org/main-editor'

The video embed area: For now, we don't have all the videos ready for these segments. I will provide you with the available videos when you take up the task. In the meantime, you can use this video (https://youtu.be/kKZ1CixLG2s) as default for each one.

Finally, the "Quick Editor" for each ulog-community e.g #ulog-diy, already has #ulog as its first default tag. We would now like you to add a second default tag
e.g the "Quick Editor" of https://ulogs.org/created/ulog-diy, should be '#ulog-diy and so on and so forth.

@surpassinggoogle surpassinggoogle changed the title Help Reshape The Structure Of Certain Ulog-Subtag URL-space, To Look Like 'Communities'. Help Reshape The Structure Of Certain Ulog-Subtag URL-space, To Look Like 'Communities'. - Plus 100 steem Jan 23, 2019
@surpassinggoogle surpassinggoogle added this to the 4 Days milestone Jan 23, 2019
@nirvanaitsolutions
Copy link

PLease assign the task to us

surpassinggoogle added a commit that referenced this issue Feb 7, 2019
Implement Issue #183 and Fix little bugs in #181 and #182
surpassinggoogle added a commit that referenced this issue Feb 7, 2019
Revert "Implement Issue #183 and Fix little bugs in #181 and #182"
surpassinggoogle added a commit that referenced this issue Feb 24, 2019
surpassinggoogle added a commit that referenced this issue Feb 24, 2019
surpassinggoogle added a commit that referenced this issue Feb 24, 2019
…evelop

Revert "Revert "Partial Fix For #183 And #184""
surpassinggoogle added a commit that referenced this issue Feb 28, 2019
surpassinggoogle added a commit that referenced this issue Mar 1, 2019
surpassinggoogle added a commit that referenced this issue Mar 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants