Currently deleting a post can only be done by navigating to the URL. It should be done via some UI button e.g. a button with confirmation.

A TagHelper that pulls the blog description from the site configuration file. The TagHelper should be useable from any page and would be in the following format (can use dependency injection to get info from ISitConfig.cs:

<sitedescription></sitedescription>

Which would produce an output like this:

Site Description

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Issue #9 brought up a point that it is not obvious where meta data like twitter account can be found.

Potentially the PostViewModel could be expanded to contain meta data directly.

An advantage would be that the view would have direct access to this data via the model.

The current method of using dependency injection to get access to the data (IDasBlogSettings.IMetaTags) is a workable solution, but expanding the model could have benefits as well.

A concern for making this change is that it would affect users on the legacy dasblog from upgrading. The current mechanism would need to make changes to the security file.

• Ensure the list of shared partial views are in a shared location (any theme can use it)
• Document the list of shared views
• Document the list of partial views to be used

This is bad I mean really bad ... each contribution should have a minimum of one unit test so we are off to a slow start here.

A TagHelper that shares a Tweet for a blog post. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:

<posttweet post=@Model>Twitter</posttweet>

Which would produce an output like this:

<a href="https://twitter.com/intent/tweet?url=https%3a%2f%2fwww.baseurl.com%2fblog%2fsomepost&amp;text=Some+blog+post%3f &amp;via=poppastring+%23musings" class="">Twitter</a>

TagHelpers should be created in the DasBlog.Web project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Adding\Editing a new post only allows you to select an existing category. We should also allow new categories to be added at this point.

\this-is-a-post (this is the current default)
or
\20180604\this-is-a-post

DasBlog.Web.UI -> DasBlog.Web
DasBlog.Web.Repositories -> DasBlog.Manager (this is really a manager rather than repository pattern)
DasBlog.Web.Core -> DasBlog.Core

We have an XML based security file that stores identity data. Some of this was enabled with fixes required for XML-RPC.

Read and apply Custom storage providers for ASP.NET Core Identity

Route:

• /archive/
• /archive/year
• /archive/year/month
• /archive/year/month/day

This will be sent to the Archive controller here which has been stubbed out and does indeed call the correct repository for the data required.

Views/ViewModels need to be created to support this enhancement.

Page layout should approximate the following:

• https://www.hanselman.com/blog/monthview.aspx
• https://www.hanselman.com/blog/monthview.aspx?year=2018
• https://www.hanselman.com/blog/monthview.aspx?month=2018-01
• https://www.hanselman.com/blog/monthview.aspx?month=2018-01-30

[no html tables please]

After logging in you should be able to view unpublished posts so that you can continue editing and or publish. The current view of the home page only includes published posts.

We need a TagHelper that shows an comment link for a given blog post. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:

<postcomment post=@Model>Comment on this post</postcomment>

Which would produce an output like this:

<a href="//www.baseurl.com/blog/somepost/comment">Comment on this post</a>

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

I am interested to make contributions, however, not sure about sending PR and Unit Tests and preliminary checks need to be done. For most of the open source projects, there is a contributors guideline exists in repo.

I am happy to send PR with basic guidelines written for the same. However, as an owner of the repo, you can suggest what needs to be included and I can send PR for the same.

PS: Also, realized maybe issue template might also be helpful for the repo.

At minimum we should be able to update the existing admin

• change email, displayname, password and username

[There are problems to solve around serialization/deserialization in .net core i.e. reading two records from an xml file]

IDasBlogSettings.MetaTags has a lot of info. The naming is not completely unambiguous.

I think documenting the purpose of each setting would add useful info to future contributors.

Identity code is currently here:
\DasBlog.Web.UI\Models\Identity\

At minimum it should be moved from the Models folder., and would probably be better in the Core project.

Not interested in breaking the build because of style issues so we can use the editorConfig project for code consistency.

Remove the following from the solution (do not remove files/folders):-

• newtelligence.DasBlog.Runtime.Test (to be move to DasBlog.Tests)
• newtelligence.DasBlog.Runtime.Proxies
• newtelligence.DasBlog.Util.Test (to be move to DasBlog.Tests)
• newtelligence.DasBlog.Web
• Subtext.Akismet
• WebControlCaptcha
• Lesnikowski.Pawel.Mail.Pop3

This may require moving some fundamental types to DasBlog.Core or a new project all together.

A TagHelper that shares blog post via Facebook. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:

<posttofacebook post=@Model>Facebook</posttofacebook>

Which would produce an output like this:

<a href="https://facebook.com/sharer.php?u=https://www.baseurl.com/blog/somepost" class="">Facebook</a>

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Create a single login page to allow admin functions like approve/delete comments

Route:

• /category
• /category/$1

This will be sent to the Category controller here which has been stubbed out and does indeed call the correct repository for the data required. Views/ViewModels need to be created to support this enhancement.

Page layout should approximate the following (I know the link says archive but this is correct):

• https://www.poppastring.com/blog/archives.aspx
• https://www.hanselman.com/blog/archives.aspx

[no html tables please]

The PostViewModel.PermaLink is being hacked together (in the HomeController) to produce a link for each blog post. The actual solution should pull the format for the permanent links for each page based on the following:

• Compress the title (see SiteUtilities.GetPermaLinkUrl() ), this should probably exist in as IDasBlogSettings.
• Spaces replaced by TitlePermalinkSpaceReplacement (from site.config). For example "This Is a Title!" should be come "this+is+a+title" or "this-is-a-title".

There is currently no mechanism for creating/editing/deleting blog posts.

Requires resolution of security #23

Create a list of valid cultures from which the user can select.
Default to the language/culture of the server.

By convention we should only have files in the wwwroot folder that we intend to serve directly (js, css, html, etc).
We should move

• config
• contents
• logs

These folders and their contents can be kept in the project and marked for distribution.

A TagHelper that pulls the blog title from the site configuration file. The TagHelper should be useable from any page and would be in the following format (can use dependency injection to get info from ISitConfig.cs:

<sitetitle></sitetitle>

Which would produce an output like this:

Site Name

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

We need a TagHelper that shows an edit link for a given blog post. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:

<postedit post=@Model>Edit this post</postedit>

Which would produce an output like this:

<a href="//www.baseurl.com/blog/somepost/edit">Edit this post</a>

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Password hashing supports MD5 we want to upgrade this so that once updated we use a better hashing algorithm.

The original version of DasBlog implemented the following APIs for creating, updating and deleting posts:-
- Blogger
- MetaWeblog
- Moveable Type

We need to replicate that in this version also, the metadata of what is supported will be retrievable from /feed/rsd (See the Feed Controller).

In the traditional version of DasBlog the equivalent the url (/blogger.aspx, new version is /blogger) has both a GET and POST, the GET simply shows a HTML page (see here). A POST at the same URL will attempt to exercise one of the three available blogging APIs.

The original DasBlog Blogger API code that needs to be converted to Controller can be found here.

We can start with Moveable Type (as default).

You should be able to add a new post and attach new images or files as part of the post

Old way:
ASP.NET Core => /CategoryView,category,ASPNETCore.aspx
Development Process => /CategoryView,category,DevelopmentProcess.aspx

Update as follows:
ASP.NET Core => /category/aspnet-core
Development Process => /category/development-process

A TagHelper that pulls the blog sub title from the site configuration file. The TagHelper should be useable from any page and would be in the following format (can use dependency injection to get info from ISitConfig.cs:

<sitesubtitle></sitesubtitle>

Which would produce an output like this:

Site sub title

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Need to tie into the comments API

• Add comment (based on post, and global comment permission, comment date)
• Delete comment (admin function)
• Approve comment (admin function)

The "DasBlog" theme requires some work to ensure that the comments and add comments are formatted appropriately.

Audit posts
Audit login success/failure

In dasBlog's former life we would get an email summary of the activity. We should ressurect this feature.

If there is an easy to use nuget package that would be fine too. Would like to consider using MimeKit

[Removed existing comments as I have changed the approach]

We need a TagHelper that makes it easier to insert the created date of a post in the format selected. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:
<postcreated post=@Model>MMMM dd, yyyy</postcreated>

Which would produce the following output (based on MMMM dd, yyyy):
June 18, 2017

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

• Change Password
• User Settings
• Activity
• Configuration
• Register a new user

Allow comments on posts based on the permitted expiry contain in Site.Config (DaysCommentsAllowed).

Should also include a method for deleting and approving as admin.

We need a TagHelper that shows the categories associated for a given blog post. The TagHelper would be exclusively for the _PostPartial.cshtml and would be in the following format:

<postcategory post=@Model>Tagged in: </postcategory>

Which would produce an output like this:

Tagged in: <a href="//www.baseurl.com/blog/category/musing">Musing</a>

TagHelpers should be created in the DasBlog.Web.UI project under the TagHelpers folder, I have a blog post on authoring TagHelpers here. Find out about why we use TagHelpers here, and specific steps on authoring TagHelpers can be found here.

Please note that these tasks are for code newbies who are looking to make contributions to supportive open source project using ASP.NET Core MVC. Please feel free to reach out to me on twitter and I will be happy to help walk you through this.

Currently exists here:
/Account/Login

Not planning to open up the blog to general registration. The UI for registration should be an admin function only.

Move the implementation of XmlRpcService (MoveableType.IMovableType, Blogger.IBlogger, MetaWeblog.IMetaWeblog) to a new manager that inherits from BlogManager.

With Bower being deprecated I would like to use the newly introduced Library Manager (Lib Man), removing all bower config references.

Also update front page with new required version of the .NET Core SDK as follows

https://www.microsoft.com/net/download/thank-you/dotnet-sdk-2.1.300-windows-x64-installer

Convert [email protected] to the appropriate gravatar_id

//www.gravatar.com/avatar.php?gravatar_id=c5575d8d8e1fd116af76173dbf49ff31&rating=PG&size=60&default=identicon