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

Create a Blog page #168

Closed
hotRedPanda1 opened this issue Jan 16, 2020 · 5 comments
Closed

Create a Blog page #168

hotRedPanda1 opened this issue Jan 16, 2020 · 5 comments

Comments

@hotRedPanda1
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I like reading through blogs related to work-life in the tech industry.

Describe the solution you'd like
A clear and concise description of what you want to happen.
(1) There should be various articles posted after a severe review and check to see that each article has met the specific guidelines of submission.
(2) We need an article submission page that will allow writers to submit their article for review before it is posted.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
There must be a page of clear, concise article submission guidelines for writers to follow.

Additional context
Add any other context or screenshots about the feature request here.
(1) There must be a limit to how many articles are accepted and posted every month.
(2) An article that meets the requirements yet cannot be posted for a specific month may or may not be recycled or saved and utilized in a later edition.
(3) All articles that are considered for publication become the property of IESD or SPARK.

@lloan
Copy link
Member

lloan commented Jan 16, 2020

@hotRedPanda1 This is great, but we actually could use this on www.iesd.com - if you visit the site, one of the first components you see is the newsroom, but we don't have an actual page dedicated to the newsroom, which I think would be very helpful, specially as we have people that actually want to start writing. Maybe this issue might be better fitted for this repo: https://github.com/inland-empire-software-development/main - You could lead the overall functional design of it and I could get you a developer or two to work with to create that page. It's a high priority item that we really need.

@hotRedPanda1
Copy link
Author

hotRedPanda1 commented Jan 18, 2020 via email

@lloan
Copy link
Member

lloan commented Jan 18, 2020

@hotRedPanda1 Definitely. As we talked about earlier today at the meeting, we would like to get this project out the door too as it would be very useful for the community to have. We have a lot of different kinds of topics to write about: updates, student journeys about their learning, tech articles, etc.

The way that you play in to this is that you bring your user experience and knowledge about learning.

Think about the following questions:

  • How do you think the newsroom should flow.
  • Who is our target user
  • Is the user able to get to where they need to get.
  • What do we want the user to get out of using the newsroom?
  • How do we get users to come back>
  • How can users interact with our articles and/or should they?
  • What is the ideal length?
  • Tools for article writers?
  • User experience for the user.
  • User experience for the writer.
  • What kind of pages do we foresee for this system? author pages, category pages, filter page (search), etc.

@lloan lloan transferred this issue from inland-empire-software-development/spark Jan 19, 2020
@lloan
Copy link
Member

lloan commented Jan 19, 2020

Transferred issue to main repository for www.iesd.com site.

@lloan
Copy link
Member

lloan commented May 22, 2020

Closing - The concept will be added to the new application.

@lloan lloan closed this as completed May 22, 2020
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