add blog

Author: [email protected]

blog/Use Dev-Docs with Continue.md

@@ -1,6 +1,4 @@
-
-
-  ---
+---
 title: Contextual documentation with Dev-Docs and Continue
 authors: andrew
 header_image: /img/dev-docs-assets/ClippedHeroBg.png
@@ -130,19 +128,22 @@ Try asking questions like "@dev-docs what technologies are used?"
 
 <br></br>
 
-# Step 6: Leveraging Dev-Docs context in Continue
+# Conclusion
+
+
+<br></br>
 
 Now that you have set up both Dev-Docs and Continue, you can take full advantage of the contextual documentation generated by Dev-Docs within Continue. Here are some additional ways to utilize this powerful combination:
 
-1. **Code explanations**: Ask Continue to explain specific parts of your codebase using the Dev-Docs context. For example, "@dev-docs explain the purpose of the main function in app.js".
+- **Code explanations**: Ask Continue to explain specific parts of your codebase using the Dev-Docs context. For example, "@dev-docs explain the purpose of the main function in app.js".
 
-2. **Architecture overview**: Use the generated documentation to get a high-level understanding of your project structure. Try asking "@dev-docs summarize the overall architecture of this project".
+- **Architecture overview**: Use the generated documentation to get a high-level understanding of your project structure. Try asking "@dev-docs summarize the overall architecture of this project".
 
-3. **Dependency insights**: Inquire about the libraries and frameworks used in your project. For instance, "@dev-docs list the main dependencies and their versions".
+- **Dependency insights**: Inquire about the libraries and frameworks used in your project. For instance, "@dev-docs list the main dependencies and their versions".
 
-4. **Best practices**: Leverage the contextual documentation to ensure you're following project-specific conventions. Ask questions like "@dev-docs what are the coding standards for this project?".
+- **Best practices**: Leverage the contextual documentation to ensure you're following project-specific conventions. Ask questions like "@dev-docs what are the coding standards for this project?".
 
-5. **Troubleshooting**: When facing issues, use the Dev-Docs context to help identify potential problems. For example, "@dev-docs are there any known issues or limitations with the current implementation?".
+- **Troubleshooting**: When facing issues, use the Dev-Docs context to help identify potential problems. For example, "@dev-docs are there any known issues or limitations with the current implementation?".
 
 By combining the power of Dev-Docs' contextual documentation with Continue's AI-driven code assistance, you can significantly enhance your development workflow and maintain a deeper understanding of your codebase.
 

src/theme/MDXContent/index.js

@@ -56,7 +56,7 @@ export default function MDXContentWrapper(props) {
                   <span style={{color: props?.children?.type?.frontMatter?.text_color}} key={index}>{" " + item.name + ","}</span>
                 ))}
 
-              &nbsp; <span style={{color: props?.children?.type?.frontMatter?.text_color}}>On {props.children.type.metadata.formattedDate},</span>{" "}
+              &nbsp; <span style={{color: props?.children?.type?.frontMatter?.text_color}}>Est Reading Time: {props.children.type.metadata.formattedDate}</span>{" "}
               <span style={{color: props?.children?.type?.frontMatter?.text_color}}>{Math.ceil(props.children.type.metadata.readingTime * 10) / 1} min</span>
             </h3>
             <div className="flex flex-row items-center mb-10 w-full">