Should the Pull Request Process section of contributing.md include a step to rebase their branch prior to a creating a Pull Request to ensure we don't run into this: #63 (comment)?

I was watching the youtube video from the last stream (5-3-2018) and noticed at 2:19:40 that this js was giving a 404 in the developer tools. That is probably what is keeping the modelstate errors from displaying corrrectly.

In different locations, we use different labels, for the same functionality:

Show the number of views/ read for an article.

Allow authors list your articles

Suggested Columns:

• [Title], [Create Date], [Last Changed Date] and [Status]

Should by redirect to /Details. Correct?

Needs another table with article, rating, date of rating, article version, some user information

Need an easy way to create a link to another wiki page, even if that pages does not yet exist. Then an easy way to create that page from within the referring page. Something similar to how SharePoint wiki does this.

Need to be able to upload images for articles

We could have an link in each article to navigate from LatestChanges to details page.

Need to be able to reference an article using PascalCase and have it converted into a link to another article

When I type an very long text in the topic field an exception is displayed. I think it's the limite of URL address.

Ex:

• [TOPIC] = HomePage dssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss ddddddddddddddddddddddddddddddddddd d d

OBS:

• [Edit] and [Create] the same problem.

In All.cshtml we are using:
asp-route-id="@item.Id" to form parameters for edit but in Edit.cshtml.cs we are trying to load using topic: SingleOrDefaultAsync(m => m.Topic == id)

We could edit Edit.cshtml.cs to take int Id as input, and remove first null check while chaning linq query to be SingleOrDefaultAsync(m => m.Id == id)

Comments for articles

Please re-enable being able to edit the topic as some times you need to fix simple things like spelling mistakes. Now the wiki uses an id an as key I don't see any reason why we can't edit the article topics.

If we remove the HomePage article the system doesn't work anymore.

Suggests:

• Make content localizable (Labels, DataAnnotations, ModelStateError, Dates)
• Provide localized resources for the languages and cultures you support (for example: pt-BR, en-US)
• Implement a strategy to select the language/culture for each request

Suggested:

• Draft - Only the owner/author can visualize and does not appear in the searchs
• Published - Everyone can visualize and appear in the searchs
• Deleted - Only the owner/author can visualize and does not appear in the searchs

In different locations, we use different labels, for the same functionality:

Need to add search - full text search of content

When I try to save an new article with the same name as an existing one, it presents an exception SQLite Error 19: 'UNIQUE constraint failed: Articles.Topic'.

EX:

• Topic = "HomePage"

Currently we are using querystring to [edit] and [delete] an article. How to change the route to action/topic.

Ex:

• /Edit/{Topic}
• /Delete/{Topic}

@csharpfritz: I understand that for [Details], [Create] and [LatestChanges] is resolved. Correct?

• /{Topic}
• /Create
• /LatestChanges

RSS feed of recently changes articles

When I watched the Jeff's livestream at Build I noticed a bug in my code in the edit page. I did not check this correctly and both my fix and the code Jeff did on stage do not feel the right way to do this.
Currently we push a complete EF Entity to the Page, and actually populate (data-bind) a full EF Entity as well.
But, when we start to add properties we might not need alle properties in a page, so posting all that data to the page is unnecessary.
Also when we do not form submit fields that we have put attributes on in the EF Entity, but we don't care about in the PageModel we run into problems with the databinding not being able to populate the Entity.
My pull request had that problem because I did not have some of the added code from the project_VersionsAndRatins branche.

Using viewmodels that only push the fields needed and only require back the fields we can actually fill or care about elevates this. Not only that it allows us to abstract away from the EF decorated classes to classes more closely resembling POCO classes.

Doesn't route properly between pages

Just tested the new UrlHelper with the following Article Topic (all the letters on my English keyboard):

--`~1!2@3#4$5%6^7&8*9(0)-_=+qQwWeErRtTyYuUiIoOpP[{]}\|aAsSdDfFgGhHjJkKlL;:'"zZxXcCvVbBnNmM,<.>/?--

and it creates the following url slug which does not work:

--`~1!2@3#4$5%6-7&8*9(0)--+qqwweerrttyyuuiioopp[{-}-|aassddffgghhjjkkll;:'"zzxxccvvbbnnmm-<->-?--

If I role back to the original UrlHelper that was created by the guys that run the SO site I get the following url slug that works properly:

123456-7890-qqwweerrttyyuuiioopp-aassddffgghhjjkkllzzxxcc

I think we need to rollback to the original UrlHelper as it has been tested on millions of stackoverflow pages & has also been tested with many other keyboards / languages.

To prepare three environments to deploy application [DEV, HML and PRD] in AKS.

Suggested:

• Use VSTS and Release in AKS (Azure Container Service)
• To Define better branch strategy to CI/CD

CoreWiki, seems to be simple to 10 users.

Now, let's imagine to 300mil users concurrents:

200.000 Queries concurrents (features search, track changes, article ratings
50.000 Updates concurrents (update comments, update images, update article ratings)
50.000 Inserts concurrents (add comments, add images, add article ratings)

My suggestions is:

1. To explorer the CQRS Pattern
2. Use an docker container to ( Queries)
3. Use an docker container to ( Update, Delete, Insert)

OBS: See, I first think to change the database platform to SQL Server 2017. And both docker containers connected in another docker container with SQL Server 2017.

@csharpfritz, What do you think about that?

As a minimum viable... this could just be a page that contains links to other pages

Article topic should be the URL requested

Remove indent_size = 2 from the .editorconfig file

As tabs are being used this should probably default to an individuals editors preference.

We need an feature to list all articles. The feature LatestChanges list only 10 last published articles.

Suggested

• Create an new [Articles List] to list all articles
• [Articles List] should by our new home page
• [Articles List] allows users navigate to follows features:
  • [Edit]
  • [Delete]
  • [Detail]

Might be nice to have an estimated read time for articles in the wiki.

Logged in folks can edit and add content

CoreWiki

A simple ASP.NET Core wiki that we are working on during live coding streams.

NOTE: This project is the result of some streams transmitted using TWITCH platform. To collaborate and understand the project, please see the follows streams:

1) Implemented Feature List

HomePage - It's not a page or a feature. This is a default article that is presented as if it were the Home. When the user navigate to /Details, if topicName is not specified, the application redirect to default Article (HomePage)

Header Menu

• Allows the users navigate to the Default Article (HomePage). [Back to Home (CoreWiki)]
• Allows the users navigate to LatestChanges feature.[LatestChanges]
• Allows the users navigate to Create new article feature. [Create new article]

Details

• Allows the users see details of article.
• Allows the users navigate to Edit feature. [Edit]
• Allows the users navigate to the Default Article (HomePage). [Back to Home]

Create

• Allows the users create a new article. When success, redirect the user to Details Feature. Otherwise, stay in the page and show error message. [Create]
• Allows the users to navigate to the default article (HomePage). [Back to Home]

Edit

• Allows the users change the article (Topic, Published and Content).
• Allows the users navigate to the default article (HomePage). [Back to Home]

LatestChanges

• Allows the users see the last 10 articles. Ordered by Published Date.
• Allows the users navigate to Edit feature. [Edit]
• Allows the users navigate to Delete feature. [Delete]
• Allows the users navigate to Detail feature. [Detail]
• Allows the users navigate to Create new article feature. [Create new article]
• Allows the users navigate to the default article (HomePage).[Back to Home]

NotFound

• Occurs, always which default article (HomePage) is not found. To simulate page not found remove the article HomePage.

Error

• When an exception occur, o user is redirected to error page. [Not Simulated].

2) Topics covered in previous streams

Lessons - Visual Studio Live Sharing Extension

• Visual Studio Community x Visual Studio Code
• Visual Studio Community x Visual Studio Community

Lessons - GitHub

• Create New Repository
• Create Branch (Master, Dev)

Lessons - Git Cli

• Commit
• Push
• Clone
• [Others ...]

Lessons - Nuget

• Install Packages

Lessons - DOTNET Cli

• Dotnet new globaljson --sdk-version 2.0.2

Lessons - ASP.NET Core

• Navigation
• Razor Pages
  • BindProperty
  • RedirectPage
• Routing
  • Customization
  • Constraint
• Dependency Injection
• Tag Helpers
  • Install and Use External
• Validation Error UI
• Server-Side Validation
• Configure Minification
• Configure Bundling
• Data Model
  • Add Data Model to a Razor Pages
  • Add Database connection string
  • Register the database context
  • Add database context class
  • Scaffold the Model
  • DataType Attributes
  • ModelState Validation

Lessons - Entity Framework Core

• Code First Database
• Migrations
• Seed
• CRUD (Create, Read, Update e Delete)
• Update concurrency exception handling

Lessons - UI

• Bootstrap 4
  • Cards

If we click the Submit button several times the comment is duplicated. How to avoid?

When use ASP.NET Core 2.1 or later, Microsoft recommends change the metapackage Microsoft.AspNetCore.All by Microsoft.AspNetCore.App.

1. Change the following entry in the CoreWiki.csproj:

• FROM
  <PackageReference Include = "Microsoft.AspNetCore.All" Version = "2.1.0"
• TO
  <PackageReference Include = "Microsoft.AspNetCore.App"/>

2. Install Microsoft.EntityFrameworkCore.Sqlite

• Using Manage Nuget Packages install the Microsoft.EntityFrameworkCore.Sqlite Package (2.1.0)

OR

• Manually add the following entry <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="2.1.0" />

2. Remove Microsoft.EntityFrameworkCore.Tools.DotNet

• <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.1" />

We could have a feature, when creating or editing an article, to import a (.md) file and automatically fill the content field.

In header CoreWiki and Home has the same function. We suggest to remove the home menu.

Suggested by @bravecobra

This could be a configuration option, just like how Wordpress lets you choose comment engines

A history and list of changes to articles

This feels like a cool progressive web app waiting to happen!

Timestamps are not being replaced by the site.js script on Edge (currently running v42.17133.1.0).

site.js generates an error:

SCRIPT438: Object doesn't support property or method 'Symbol.iterator'
on the line for (var ts of timeStamps)

Authors need a way to save their profile

We should enable social logins as requested by banafys on stream