aspnet/vsweb-docs

Name: vsweb-docs

Owner: ASP.NET

Description: Showcase for Visual Studio web features

Created: 2015-03-10 00:32:52.0

Updated: 2018-02-09 22:28:54.0

Pushed: 2016-08-29 16:19:49.0

Homepage: http://vsweb.azurewebsites.net

Size: 3925

Language: C#

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

Visual Studio features for web developers

Build status

Deploy to Azure

Website: vsweb.azurewebsites.net/

Features
Getting started

The website itself is really simple. It consists of a single index.cshtml file. The entire site is built up around Markdown (.md) files located inside the pages directory by default.

If need to deploy to the IIS, need to install the http://www.iis.net/downloads/microsoft/url-rewrite

Folder structure

The folder structure determines how the menu is constructed as well as the URLs to each page.

Folder structure

Each folder MUST have a file called index.md with the exception of folders starting with an underscore (example: /pages/_images/).

Metadata

Each .md file has a bit of metadata at the top that allows you to customize various aspects of the file.

perties
pageTitle="FTP"
description="bla bla bla"
slug="ftp"
order="300"
keywords="ftp, deploy"


arkdown content goes here
Screenshots/animated GIFs

To maintain a consistent look to all the screenshots/animated GIFs, please adhere to these Visual Studio settings:

Font: 12pt Consolas
Theme: Light

Also, please make sure to have a ~5 pixel padding when making an animated GIF from one of the editors, so the things you show aren't located all the way at the edges of the image, but about 5 pixels from the top and left.

The padding rule only applies to screenshots/animated GIFs taken inside the editors.

The width of any screenshot/animated GIF, make sure to keep them at a maximum of 600 pixels wide.

Validation

To help make sure that each pull request meets the requirements of the metadata, the validator helps guide the contributors to write valid .md files for the MarkSite instance.

When using AppVeyor, each pull requests is automatically being build and the validator will automatically fail the build in case the pull request isn't satisfying the validator.


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.